FerretBomb
Active Member
This has been covered/requested before, but I had a new idea regarding how to handle it.
The Desire: Being able to (pre)view and edit a scene before switching to it.
The Reason: To allow easy setup/alteration of a 'key' scene (main game) and ensure capture feeds are set correctly prior to changing to it, so as not to present a black screen or malformatted display to viewers.
The Solution: Add a 'Lock Scene' button directly below the preview window. When clicked, toggle button text to 'Unlock Scene' and add a 'Scene locked to: Example Scene' text tagline after the button. Possibly also change the background of the bar to highlight that it is locked, make it harder to miss.
Allow the preview window to switch to the new scene (and allow editing of it) while the Locked Scene is displayed on-stream. Unlocking the scene would transition to the currently-selected scene.
This would allow a caster to view and edit an upcoming scene without needing to add a second preview pane (taking up less real-estate). It would also allow OBS to load the resources for the new scene in preparation for the switch, cutting down on transition-lag (or at least front-loading some of it, to make it less obvious). This method would also retain the simplicity of single-pane editing, without confusing the user as to which pane the edits would apply.
Issues: Greater GPU utilization, compositing two scenes simultaneously (one invisibly, the livestream-active one). As the preview would not actually be encoded until it was unlocked, CPU utilization increase should be minimal by comparison. Especially as OBS already does this on a shorter-term currently, when performing a smooth transition between scenes (essentially this would be putting OBS into a scene-switching state, and just hold at the start-point of the fade while locked).
The Desire: Being able to (pre)view and edit a scene before switching to it.
The Reason: To allow easy setup/alteration of a 'key' scene (main game) and ensure capture feeds are set correctly prior to changing to it, so as not to present a black screen or malformatted display to viewers.
The Solution: Add a 'Lock Scene' button directly below the preview window. When clicked, toggle button text to 'Unlock Scene' and add a 'Scene locked to: Example Scene' text tagline after the button. Possibly also change the background of the bar to highlight that it is locked, make it harder to miss.
Allow the preview window to switch to the new scene (and allow editing of it) while the Locked Scene is displayed on-stream. Unlocking the scene would transition to the currently-selected scene.
This would allow a caster to view and edit an upcoming scene without needing to add a second preview pane (taking up less real-estate). It would also allow OBS to load the resources for the new scene in preparation for the switch, cutting down on transition-lag (or at least front-loading some of it, to make it less obvious). This method would also retain the simplicity of single-pane editing, without confusing the user as to which pane the edits would apply.
Issues: Greater GPU utilization, compositing two scenes simultaneously (one invisibly, the livestream-active one). As the preview would not actually be encoded until it was unlocked, CPU utilization increase should be minimal by comparison. Especially as OBS already does this on a shorter-term currently, when performing a smooth transition between scenes (essentially this would be putting OBS into a scene-switching state, and just hold at the start-point of the fade while locked).
