Proposal: Using compositor nodes on VSE strips

[ok-what]

@tintwotin

Currently, there are already UIs for effect strips and UIs for modifiers, adding a UI for basically the same functions in a node editor(but add similarity to Resolve workflow), would just result in more UI clutter

Afaik effect strips are currently being phased out. The transform strip has already been removed, and the general idea seems to be that once there’s a better system they should be removed altogether:

@iss

So yes, we could get rid of effect strips, but we need a usable replacement for “go crazy” mode.

I would advocate for possibility of using node editor, because I could then rewrite whole pipeline as nodes and use linear process under the hood.
Having possibility to make my node setup as reusable template can make workflows faster and timeline cleaner.

So this would replace both the effect strips and modifiers. That would remove clutter from the current system.

@tintwotin

An alternative way to get strips in and out of the compositor could be as movie-clip-data-blocks.

@tintwotin

Using the movie clip node ex. the movie clip data-block(source file) can already be imported into the compositor

I think an issue with that is that the node setup is linked to a specific video clip. The same setup couldn’t be easily reused on different clips.

Moving the VSE content out of scene data structure […] is a superior solution.

I think these are separate issues.