Add RFC: Downstream keyer #11
Conversation
|
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 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. |
|
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. |
|
|
||
| ## User UX | ||
|
|
||
| - Have an extra dock for the DSK scene (same as the scenes dock) |
There was a problem hiding this comment.
I agree with this, and it should be treated like a secondary scene list, probably with its own transitioning. Question is how to handling transitioning, especially considering people might want to use different transitions for DSKs.
| ## User UX | ||
|
|
||
| - Have an extra dock for the DSK scene (same as the scenes dock) | ||
| - Have the dock on by default, so users easily know about it |
There was a problem hiding this comment.
I don't agree with this, I think this goes against the current design pattern where advanced features are hidden/separated by default.
|
|
||
| - Have an extra dock for the DSK scene (same as the scenes dock) | ||
| - Have the dock on by default, so users easily know about it | ||
| - Users could switch between DSK channels with combo box in the dock |
There was a problem hiding this comment.
Personally, I would prefer to just have a DSK 1 scene list, DSK 2 scene list or something like that. Probably even separate docks for them. I'm not sure how others would feel about that idea however. @dodgepong might have some strong opinions here.
| - Have the dock on by default, so users easily know about it | ||
| - Users could switch between DSK channels with combo box in the dock | ||
| - Alternatively, use hotkeys to change DSK channels, so we don't clog up the UI | ||
| - There would be an extra option in the combo box for disabling the DSK |
There was a problem hiding this comment.
Yea, having a "None" option for the DSK which it would be set to by default or something would likely be necessary.
There was a problem hiding this comment.
I think the issue is that the DSK is functionally a clone of the Scenes list so you can only show one at a time, where you'd reasonably expect to be able to toggle DSK 1, 2, 3 on and off like muting or unmuting audio sources.
There was a problem hiding this comment.
I think DSK should reuse the original scenes, may have separate transition effect. So we needn't make a whole new scene lists for them, we can just add a "Transit to Global Overlay" option to scenes' right-click menu. And add a "Global Overlay Transition Effect" selector below the original scenes' transition effect selector, or may just use current active transition effect. In this way, it's more like a traditional hardware switcher.
Using a new Scenes list for DSK is also acceptable.
| - Users could switch between DSK channels with combo box in the dock | ||
| - Alternatively, use hotkeys to change DSK channels, so we don't clog up the UI | ||
| - There would be an extra option in the combo box for disabling the DSK | ||
| - Call the DSK "Global Scenes" so users would more likely know what it is |
There was a problem hiding this comment.
Because it's more of an advanced feature, I don't think we necessarily need to dumb down the name.
There was a problem hiding this comment.
I agree it's a more advanced feature but when users realise this is the way to do channel bugs etc. I suspect it will get more use, and thats more likely if it's called global rather than DSK.
It might be interesting in future to add a notification when a user adds a source to multiple scenes (3+) the first time to show a dialog that tells them about global scenes and offers to enable it for them.
There was a problem hiding this comment.
I think it should be called "(Active) Output Overlay Scene" or "(Active) Global Overlay Scene".
There was a problem hiding this comment.
I think DSK should reuse the original scenes, may have separate transition effect. So we needn't to make a whole new scene lists for them, we can just add a "Transit to Global Overlay" option to scenes' right-click menu. And add a "Global Overlay Transition Effect" selector below the original scenes' transition effect selector, or may just use current active transition effect. In this way, it's more like a traditional hardware switcher.
In this way, we won't change the UI too much, and it will be ignored for those who doesn't need this feature.
DSK is a really necessary function for live production makers, please consider raise the priority.
|
|
||
| # Motivation | ||
|
|
||
| Users won't have to create meta scenes and copy them to every scene. |
There was a problem hiding this comment.
My opinion:
# Motivation
1. Users won't have to create meta scenes and copy them to every scene.
2. The global scene won't affected by scenes transition effect.
| - Users could switch between DSK channels with combo box in the dock | ||
| - Alternatively, use hotkeys to change DSK channels, so we don't clog up the UI | ||
| - There would be an extra option in the combo box for disabling the DSK | ||
| - Call the DSK "Global Scenes" so users would more likely know what it is |
There was a problem hiding this comment.
I think it should be called "(Active) Output Overlay Scene" or "(Active) Global Overlay Scene".
| - Have the dock on by default, so users easily know about it | ||
| - Users could switch between DSK channels with combo box in the dock | ||
| - Alternatively, use hotkeys to change DSK channels, so we don't clog up the UI | ||
| - There would be an extra option in the combo box for disabling the DSK |
There was a problem hiding this comment.
I think DSK should reuse the original scenes, may have separate transition effect. So we needn't make a whole new scene lists for them, we can just add a "Transit to Global Overlay" option to scenes' right-click menu. And add a "Global Overlay Transition Effect" selector below the original scenes' transition effect selector, or may just use current active transition effect. In this way, it's more like a traditional hardware switcher.
Using a new Scenes list for DSK is also acceptable.
|
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:
OPTIONAL NICE TO HAVES:
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: I apologize for posting this feedback so late. |
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