The mighty Newellll retired in June. He stopped doing the shows live at some point & by the end, they were manely stock footage. Kind of disappointing to have seen a live show but no Newelll.
Some guy put in these parameters on the twitters. The lion den wouldn't be considered as comfortable as the map shows by lion standards. Surprised NM squeaked in & how bad ID is with its $1 mil houses. Ohio is the only one under $1 mil now. You have to keep working until you die in the red areas.
The lion kingdom could probably retire now in Ohio. Retiring in FL is going to require many more years of working. The experiment showed lions won't be bored or unhappy in retirement as long as there's any budget for crap. Those experimental years were the most fulfilling & busiest of lion lives. The daily schedule is already planned.
The lion kingdom's ace in the hole is going to be climate control & artificial scenery. That should significantly lower the cost of housing. The lion kingdom's declining tendons make an indoor future more likely. Big screen TV's are probably going to replace going outside.
The last 24 years have been pretty rough with no real climate control. The mane problem is lack of space to use AC & heaters. Instead, it's been a matter of spraying water for cooling & leaving equipment on for heating. With climate control & most of the economy moving to mail order, most anywhere is now acceptable for an animal who doesn't have to go outside.
--------------------------------------------------------------------------------------------------------------
Feels like 2001 again. Lots of distaste for the technology sector because no-one is making money. Then it all turned around by 2014 when startups made money again. Lions wish they could get rid of all the animations in the software no-one cares about anymore & all the useless user requests no-one cares about anymore littering their own software.
Generation X is all hitting the same phase at the same time. The trick is they've all gone offline so it's not obvious.
ASMR has manely disappeared from the tubes. Lions manely listen to old recordings done on webcams, before monetization or HD, by gootubers who long ago disappeared & moved on to raising families. The 1st one seems to be Dec 17, 2010 from serene whispers.
--------------------------------------------------------------------------------------------------
Introducing the razor function
Lions pondered the way the Edits::optimize function always tries to make the clips as contiguous as possible. The original goal of simulating contiguous data with non destructive editing was followed by the discovery of many tricks non destructive editing allowed, like shifting the in/out points. The automatic joining remaned, but it probably was never part of the DAWs which inspired the idea.
Some users created an edit function which tries to bypass the optimization by deleting a single frame. It's been manely confusing to have an edit disappear because of the optimization. It's probably time to get rid of the optimization except when 2 edits are silence & then create a proper* slice function to split an edit.
Helas, adding a slice function also requires adding a join function. For the last 30 years, simply hitting delete on a boundary would join the 2 edits, extending them as necessary. That now needs to perform the join. Edits::optimize is a very old piece of code going back to 1997 & it's very nostalgic.
---------------------------------------------------------------------------------------------------
Free drag continued
The next idea was arbitrary dragging of clips without being locked to edit boundaries. Arbitrary dragging is a difficult problem for something lions have never used. There was the start of a hotkey function to do it before young lion realized what a complex task it was. Lions have never used dragging & always wanted to get rid of it. Even if free dragging was finished, it would only support dragging 1 edit at a time.
There are ways lions could benefit from free dragging an edit in the timeline. Compositing has manely involved a bunch of lone edits with silence before them. It would be easier to drag the lone edits than adjust the silence.
If multiple edits were separated by silence, it was pretty involved to shift the edits in time. You had to paste silence on 1 end & cut silence from the other end or drag the silence endpoints separately. Most often, it was easier to let material after the edit go out of sync while repositioning the edit.
Without the ability to select multiple edits, there's no way dragging could shift a contiguous sequence of edits on 1 track. The user would still have to adjust silent regions. It would be a big deal to select multiple edits & drag multiple edits. It would be a scratch built editing program with a rewritten user interface.
There's no way to drag the 1st edit in a track with multiple edits to the right & shift all the later edits to the right. The user still has to manually paste silence.
The other problem with dragging is knowing when to replace the destination or insert in the destination. Because there's no way to define a destination region to
overwrite, the drag needs a way to differentiate insert & overwrite. Another 3 mouse button behavior like dragging in/out points was created. The left button does an insert & the right button does an overwrite.
Since there's no concept of locking the audio, arbitrary dragging makes synchronization difficult. It has to drag the audio based on the armed tracks & the alignment of the starting positions.
Ctrl was previously bound to select single edits "Drag only one edit if ctrl is initially down". This was replaced with the ability to enter free drag mode in I beam mode by pressing CTRL before the mouse button. It 1st probes all the bezier curves for a CTRL key event before going into dragging mode.
The destination start previously snapped to the cursor's current position so it wasn't possible to nudge an edit a single frame without effort. It was also not possible to nudge the end of the edit. The start of the edit snapped to the end. This was fixed to drag the edit by the relative cursor movement.
The heart of the drag sequence is Tracks::move_edits. The labels & plugins never followed the edits but the keyframes always did, regardless of the menu setting. This was changed to use the menu setting for keyframes.
Dragging routines for transitions, plugins, edits, assets, would all need independent implementations. For now, the effort was left at just free dragging edits & was minimally tested.
Comments
Post a Comment