That would put the responsibility on the user to remember all that. If I decide to do something like that, I'll need to save the original myself, and allow the user to go back to it.
But yeah, now I get the appeal of having something like this. I've added it to my todo list -- if enough people want this, I can certainly implement it (it would disrupt quite a bit of my internal workflow, since I view "videos" as constant, and optimize them as such. so I would need to find a workaround for editing in place, but it's certainly doable).
> In my view, there is scope for innovation here by making it easier over how most software applications do this.
Agreed!
> Here's an example of a very different workflow: https://www.descript.com/video-editing
Yeah, that is kinda' very very cool :D
I know they used to be audio only a few months back. Apparently they moved into video as well. Interesting, I will certainly take another look at them.
Yes.
An example would be extracting or eliminating segments from a video recording.
>> Just imagine this - you put some text on top of your video. In 5 minutes you want to move the text a bit lower.
Sure. It's understood that once rasterized, further edits are nearly impossible.
However, it's not that a similar thing is unseen elsewhere. If I delete some text from a document, save, and close the application, and in 5 minutes, I want to get it back ...
If the user wants to keep the original, they just use "Save as ..."
The added complexity of 'project' based workflows is not worth for all edits.