kineticscreen
Member
This is great. Any chance that adding the 'move' transition can work the same as it does now when adding to source show/hide - immediately bringing up the filter window so you can set custom values just for the DSK?
- Thread starter Exeldro
- Start date
Exeldro
Active Member
@kineticscreen unfortunately that is not possible for plugins at the moment. I might suggest that feature to be added for plugins to use but that will take a while before it makes it to a new version of OBS
kineticscreen
Member
Thanks for the reply! The only other thing I'd request is a much more obvious indication that a DSK is selected - I think someone mocked up more of a red border or something earlier in this thread. At the moment it's quite difficult to just glance and see if the DSK is on just from the interface, especially when you only have one scene in it.
And 'grid view' would make a lot of sense for the DSK window.
datlaunchystark
Member
Hi Exeldro,
I do want to report a bug that I discovered in this plugin. To be able to change the layering for the DSK (by moving the tabs on the top), I have to restart OBS for it to take effect. Otherwise great work as always. :)
Currently using 0.2.0 and OBS 27.0.1
I do want to report a bug that I discovered in this plugin. To be able to change the layering for the DSK (by moving the tabs on the top), I have to restart OBS for it to take effect. Otherwise great work as always. :)
Currently using 0.2.0 and OBS 27.0.1
Jaimon Orlé
New Member
Exeldro
Active Member
@RichieTee @Jaimon Orlé duplicate not working correct is because there is no good way to see the difference to creating a new scene collection and duplicating a scene collection
I need this fix added to OBS for me to be able to make it working correct:
github.com
I need this fix added to OBS for me to be able to make it working correct:
obs-frontend-api: Send OBS_FRONTEND_EVENT_SCENE_COLLECTION_CLEANUP event by exeldro · Pull Request #4504 · obsproject/obs-studio
Description Send OBS_FRONTEND_EVENT_SCENE_COLLECTION_CLEANUP Motivation and Context OBS_FRONTEND_EVENT_SCENE_COLLECTION_CLEANUP was never send. The only place triggering it is in ClearSceneData() b...
github.com
PeteFraser
New Member
Is there a HotKey to turn ON the DSK? I can't find it in the HotKey list :( .... Or in the code
Exeldro
Active Member
@PeteFraser it should be on every scene that is added to a downstream keyer
Jaimon Orlé
New Member
@PeteFraser If you renamed the DSK it will appear in the hotkeys as that name.
e.g. the default DSK is titled "DSK 1"; therefore in the hotkeys, it will be titled "Show on DSK 1" under whichever scene you've set for the DSK.
Exeldro
Active Member
Exeldro updated Downstream Keyer with a new update entry:
Version 0.2.1
Read the rest of this update entry...
Version 0.2.1
Read the rest of this update entry...
Feature request:
1. Ability to set the "scene exclude list" for hiding DSK's on particular scenes (i.e. intros).
Details: it should be "per DSK".
Example: I use at least two DSK's now: logo bug and news ticker. I want to hide ticker and logo on scene "intro", but hide only ticker on scene "pool results".
2. Force switching DSK's on particular scene, i.e. two versions od logos - one dark, one light. Both in DSK "logos". When I switch to scene "camera 1", I want to use dark logo. When I switch to "pool results" scene, which has dark background, I want to switch automatically to light version.
It looks like the first feature request is just a specific case of the second one - I can put empty scene as one of DSK's and switch to this one (and actually I do it, it's easier to switch to empty DSK instead of disabling).
1. Ability to set the "scene exclude list" for hiding DSK's on particular scenes (i.e. intros).
Details: it should be "per DSK".
Example: I use at least two DSK's now: logo bug and news ticker. I want to hide ticker and logo on scene "intro", but hide only ticker on scene "pool results".
2. Force switching DSK's on particular scene, i.e. two versions od logos - one dark, one light. Both in DSK "logos". When I switch to scene "camera 1", I want to use dark logo. When I switch to "pool results" scene, which has dark background, I want to switch automatically to light version.
It looks like the first feature request is just a specific case of the second one - I can put empty scene as one of DSK's and switch to this one (and actually I do it, it's easier to switch to empty DSK instead of disabling).
^^
I think, this function is called "go with" (for next scene and DSK) and "go clear" (for nest scene without DSK) and shoud be set before transition for every scene.
In hardware mixers there's something like "next transition" and you can set, what you want to include with (ie. DSK): https://youtu.be/WCcoW47yFh8?t=362
I think, this function is called "go with" (for next scene and DSK) and "go clear" (for nest scene without DSK) and shoud be set before transition for every scene.
In hardware mixers there's something like "next transition" and you can set, what you want to include with (ie. DSK): https://youtu.be/WCcoW47yFh8?t=362
Nice, this is so much cleaner than adding an "Overlay" source to every single one of my scenes.
One question: Is there a way to make the input to the DSK accessible to the Source Record filter, or otherwise have some mechanism of recording the input to the DSK?
My use case here is that I have about 45 scenes (mostly composites of live RTMP and video file media sources) of different content that I will switch between during a stream, and apply a common overlay (mostly chatbox and donation alerts). Recording each of the scenes individually would be onerous and not capture the timings and flow of scene transitions during the show. Rather, I would just like to capture what is going into the DSK as a recording, so I can just re-overlay it later (e.g. for a rebroadcast) but otherwise record the scene-to-scene transitions as-is.
One question: Is there a way to make the input to the DSK accessible to the Source Record filter, or otherwise have some mechanism of recording the input to the DSK?
My use case here is that I have about 45 scenes (mostly composites of live RTMP and video file media sources) of different content that I will switch between during a stream, and apply a common overlay (mostly chatbox and donation alerts). Recording each of the scenes individually would be onerous and not capture the timings and flow of scene transitions during the show. Rather, I would just like to capture what is going into the DSK as a recording, so I can just re-overlay it later (e.g. for a rebroadcast) but otherwise record the scene-to-scene transitions as-is.
Wow, thank you! That does exactly what I was looking for and had previously thought was impossible.
For anyone else wondering what this means, the magic here is the Output Source that doesn't seem to have much documentation. It has a number of channels which I don't fully understand and will need to mess with more. But the net is that channel 0 of the Output Source without the DSK contains what's in the Program view (e.g. what you area stream). Probably for normal streaming, this would not be useful because since channel 0 is what you're streaming, it wouldn't make sense to then further generate any scene content which could, by its nature, not be streamed.
However, in conjunction with something like Source Record or the NDI Output filters, you could add additional overlays on top of the broadcast stream, and then send that somewhere else.
There is even more magic that can happen in conjunction with the DSK plugin. Channel 0 of the Output Source shows what is in the Program view before the DSK is applied, and channels >= 7 have the DSKs (e.g. if you have 1 DSK, that is in channel 7, if you have 2 DSKs, the first is in channel 7, the second is in channel 8). That means using the DSK, you can do some things that you can't do by copy/pasting an "Overlay" source into every scene.
Using these capabilities, my use case of recording the current scene prior to applying the DSK is simple, and only just the beginning.
If you have dynamic content in the DSK (like chat browsers), you could record those overlays separately. If you had a live control room with multiple monitors, you could create a scene that contained the stream output with additional monitoring data overlaid (e.g. from browser sources that contained other live stats) and send that via a Projector to a monitor. Or you could through a normal source projector, send the chat overlay to one monitor, and then send a composite of the clean stream view + monitoring stats over to another monitor.
This is amazing!
For anyone else wondering what this means, the magic here is the Output Source that doesn't seem to have much documentation. It has a number of channels which I don't fully understand and will need to mess with more. But the net is that channel 0 of the Output Source without the DSK contains what's in the Program view (e.g. what you area stream). Probably for normal streaming, this would not be useful because since channel 0 is what you're streaming, it wouldn't make sense to then further generate any scene content which could, by its nature, not be streamed.
However, in conjunction with something like Source Record or the NDI Output filters, you could add additional overlays on top of the broadcast stream, and then send that somewhere else.
There is even more magic that can happen in conjunction with the DSK plugin. Channel 0 of the Output Source shows what is in the Program view before the DSK is applied, and channels >= 7 have the DSKs (e.g. if you have 1 DSK, that is in channel 7, if you have 2 DSKs, the first is in channel 7, the second is in channel 8). That means using the DSK, you can do some things that you can't do by copy/pasting an "Overlay" source into every scene.
Using these capabilities, my use case of recording the current scene prior to applying the DSK is simple, and only just the beginning.
If you have dynamic content in the DSK (like chat browsers), you could record those overlays separately. If you had a live control room with multiple monitors, you could create a scene that contained the stream output with additional monitoring data overlaid (e.g. from browser sources that contained other live stats) and send that via a Projector to a monitor. Or you could through a normal source projector, send the chat overlay to one monitor, and then send a composite of the clean stream view + monitoring stats over to another monitor.
This is amazing!
Exeldro
Active Member
output channels:
channel 0: main video output
channel 1: desktop audio
channel 2: desktop audio 2
channel 3: mic/auxilary audio
channel 4: mic/auxilary audio 2
channel 5: mic/auxilary audio 3
channel 6: mic/auxilary audio 4
channel 7: first DSK channel
channel 8: second DSK channel
etc
channel 0: main video output
channel 1: desktop audio
channel 2: desktop audio 2
channel 3: mic/auxilary audio
channel 4: mic/auxilary audio 2
channel 5: mic/auxilary audio 3
channel 6: mic/auxilary audio 4
channel 7: first DSK channel
channel 8: second DSK channel
etc
mediacoordinator
Member
I've been noticing the same thing, but I thought it was just the setup I have for the hotkeys.
ExtraBulla
New Member
Hello good sir! So I updated to OBS 27.2, I have DSK installed but it doesn't work. When I'm on just the source the hotkeys work. But when I add the source to DSK and try to use it with hotkeys they don't work. It was working perfectly with 27.1.3 and was just wondering if anyone else has noticed this. Thanks a bunch. Your plugins are exceptional and 27.2 has been more of a pain than a gain at this point.