Exeldro
Active Member
@NickTheGreekGeek For Aitum Vertical there is a different downstream keyer dock, so don't try to change the existing downstream keyer dock, but open the vertical downstream keyer dock from the OBS docks menu.
Git gud.reeeeally hated you guys today, prepared my broadcast one week ago counting on this plugin, suddenly stopped working with my obs, can't switch scenes with this f**** plugin, if I delete the files from the plugins folder everything works perfect. I wanna cry.
- Add OBS 31 support
- Add hide after option
- Add vendor requests for adding and removing downstream keyers
- Add saving and loading tie state
Exeldro updated Downstream Keyer with a new update entry:
Version 0.3.3
Read the rest of this update entry...
Have you been able to reproduce this?I suspect DSK is crashing on close. I ran this rig every week for many months before, and it was fine. Then I converted a bunch of duplicated scenes with different overlays, to fewer scenes with DSK. It still runs just fine, but now it asks for Safe Mode on startup. Using DSK 0.3.2 for Ubuntu 22.04, on Ubuntu Studio 22.04 and OBS 30.2.3.
Close OBS, reopen, decline Safe Mode, upload previous log:
The Analyzer doesn't say anything beyond the obvious (list of plugins, no output session because it's not needed to demonstrate the problem), and I can't tell much either...except that all the other plugins have closing messages at the end and DSK doesn't. Don't know if that means anything, but maybe it does???
This is fantastic info, and is exactly what I needed to get button functionality working for downstream-keyer.I figured out how to do this and thought I'd post my solution here in case others find it necessary to do this-
In companion, set up the connection to OBS like you usually would, and then create a regular button.
The press action is obs: Custom Command
For Request Type, enter: CallVendorRequest
For Request Data, enter: {"vendorName":"downstream-keyer","requestType":"dsk_select_scene", "requestData": {"dsk_name":"DSK 1","scene":"Overlay 1"}}
Above, replace "DSK 1" with whatever you called your DSK tab, and then replace "Overlay 1" with whatever your scene name is that you want to activate.
If you want to hide whatever is displayed, instead of "scene":"whatever", use "scene":""
I am having this issue as well. I have had to create a channel point redeem on twitch for "CANT HEAR GAME" because i have all game audios set up in DSK and sometimes (seemingly without reason) DSK will de-select causing sounds to be muted as well as anything else i have in the "GLOBAL" scene i have set to the DSK.Great plugin. Used it first time in live stream and noticed, that it disables one scene after some time, where all my standard overlay sources are in (graphic, video, text). The other scene with all the triggered overlays allways is on. No interaction with OBS. Nothing triggered, cause only still viewers with not chat interaction. Is this a bug or a feature and it is not for scenes that should be on the whole time?
Great plugin. Used it first time in live stream and noticed, that it disables one scene after some time, where all my standard overlay sources are in (graphic, video, text). The other scene with all the triggered overlays allways is on. No interaction with OBS. Nothing triggered, cause only still viewers with not chat interaction. Is this a bug or a feature and it is not for scenes that should be on the whole time?
I too am running into this.I am having this issue as well. I have had to create a channel point redeem on twitch for "CANT HEAR GAME" because i have all game audios set up in DSK and sometimes (seemingly without reason) DSK will de-select causing sounds to be muted as well as anything else i have in the "GLOBAL" scene i have set to the DSK.
Okay, I set the "Hide After" to 0 ms and my downstream keyer stayed on past the 16.67 minute max (999,999 ms). So set your "Hide After" value to 0 ms if you need your DSK to stay on.I too am running into this.
I think the root cause is that in the settings under "Hide After", there is only an option to set the number of milliseconds. The max value is only for 15 minutes. There does not appear to be a way to set it to "never" so that the selected downstream keyer stays on forever.
...though, as I am typing this, I am wondering what would happen if I set the "Hide After" to 0ms. Maybe that is the way to set it to "never". I'll give it a try and report back. If it stays on for more than 15 minutes then I will assume that it will remain on until I turn it off.
@Exeldro the crash was related to something else for AES67 network audio. Apparently OBS was trying to initialize it as a sound device at startup. Anyhow, your plugin is running perfectly now that I uninstalled the network audio stuff (I wasn't using it anyway).@bcampbell OBS should log multiple things before plugins are loaded, so there should always be something in the log file if the plugin triggers a crash. I would look at how far it got before the crash to see what might be triggering the crash.
Did you ever get this figured out? I can't get it to fire myself. Trying to have it blink the button when the DSK is visibleThis is fantastic info, and is exactly what I needed to get button functionality working for downstream-keyer.
I am curious to know if you or anyone has been successfully able to get button feedback working with the downstream-keyed module. It looks like the current version of Companion (3.5.2) in the OBS module, has a place for "Vendor Events" under "Feedbacks" however, no matter how I try entering the data into the given fields, it does not seem to work. I am including a screenshot of this area from Companion with the data fields to be populated. Please note that he first three fields populate with what is shown here automatically and immediately upon adding this feedback option.
Thanks!!
View attachment 112072