Suggestion: Make the Sequencer contents into data-block, which can override the switched to Scene-Sequencer contents

My thoughts on this as a reply to @Bachadam 's post here: Proposal: Using compositor nodes on VSE strips - #28 by Bachadam Read it first for context. I replied here since this is a more relevant thread.

The “principal VSE” as I understood is similar to @tintwotin’s idea. Independent of the scene, with the ability to apply node based effects etc. on the strips. I like that idea.
I don’t understand why the old “Scene VSE” would be left in though, if it’s just a more limited version of the “principal VSE”

If it’s there to have a link between the Scene and a specific sequence, I propose this:
The checkboxes in the “Post Processing” section are replaced with a dropdown:
image
The option in the dropdown tells what to render when Render → Render Image/Animation is pressed, just like now.

  • When “Scene” is selected, sequencer and compositing is disabled.
  • When “Compositor” is selected, it gives you the option to choose which node group to use, like in the previous proposal:
    image
  • When “Sequencer” is selected, it gives you an option to choose which sequence to use.
    image

For “Compositor” and “Sequencer” whether or not a 3D scene is rendered depends on whether the sequence includes a 3D scene. This works the same way as it does now, but the difference is that you can now choose which Sequence and node tree to use.
A sequence that has Scene strip “Scene.001” with the input as “Sequencer” can’t be used as the sequence for the same scene (“Scene.001”). That would be the only limitation. The same scene can be used if it uses the camera as the input, as that won’t lead to recursion.

Individual compositing trees and sequences (regardless of Scene) can be rendered with the play button (like in @tintwotin’s proposal):


How the resolution and frame rate would be defined for separate sequences is something I’m not quite sure about yet.