Add RFC: Downstream keyer

[cg2121]

Description

Add the ability for users to create global scenes thats are on top of every scene.

Motivation and Context

Users won't have to create meta scenes and copy them to every scene.

Link

https://github.com/cg2121/rfcs/blob/downstream-keyer/accepted/0011-downstream-keyer.md

[ryantheleach]

Personally I fail to understand what advantage global scenes gives over meta-scenes, other then taking up more real estate. Maybe it's because I don't understand the channels concept, or how the UX improves (It just looks like crowding to me)

In addition the terminology DSK used in the RFC may be familiar to those from a broadcast background, But I've only encountered the term once or twice in my research into doing this as a hobby, and even then it seems/feels dated, much the same way as applications that still use a floppy disk icon for save.

Global Scenes makes much more sense, But I again have to ask, what UX is achieved by adding it?

If it's a matter of viewing 'sources' for 'non current' scenes-as-sources / shared meta scene, I'd argue that maybe it should be possible to create 'source' dock panels for all scene-as-sources instead, and let the user work out how they would like it handled, and on which scenes they should be visible.

Global Scene's as described in the RFC seems like a compromise that gives a 'simple' solution, to a 'complex' request, that will only serve to confuse newer users, and frustrate power users, unless I'm missing something fundamental.

I'd be interested in seeing some mockups, to make sure that my understanding from the text is sufficient.

As an aside, I much prefer the 'pinning' of sources, for a simplified global source (mentioned in the PR), instead of using meta-scenes. But it's clearly not going to cover all use-cases as it's on all scenes. However Pinned Sources should have an additional Visibility button, that toggles the visibility, not globally, but per scene.

[kkartaltepe]

RFC is missing a how to teach section which might help with the above concerns.

RFC proposes multiple channels but does not mention any method of synchronizing channel to scene changes. I think thats likely to be a big issue if we support multiple channels (or a non-issue if we stick to single channel). Meta sources solve that issue at least, and clever hotkeying can let you change the active metasource while live.

[Fenrirthviti]

After a lot of internal discussion, I think this approach is slightly confusing and a little more complicated than it needs to be. For an MVP for DSK, or really, DSK-like functionality as replicating DSKs 1:1 is a bad idea for us, here is what we think would be best as a workflow:

• Create a scene, add sources to that scene to your hearts content
• "Pin" the scene as the top layer (either through an icon next to the source or the context menu)
• For first iteration, only one scene is allowed to be "pinned"

OPTIONAL NICE TO HAVES:

• Allow a toggle for on top of or below normal transitions
• Allow a transition if switching which DSK is "pinned"
• Allow for editing a scene while it is already layered on top
• Hotkeys

An example UI that shows (potentially) multiple pinned scenes:

And an example that shows how one might potentially pin a scene using the context menu: https://cdn.discordapp.com/attachments/352910054208307211/802062309471158282/CrappyMockup.mp4

I apologize for posting this feedback so late.