Downstream Keyer

Downstream Keyer 0.4.3

avuser

New Member
I've found that if I use a buffered ndi source with a transparent alpha channel it works in the dsk but if I have it unbuffered then transparent becomes black so the dsk hides the content behind. This leaves me with lip sync issues.
 
@thomaslfessler can you try manually uninstalling the plugin be fore installing it?
Taking a look at the library /obs-studio/plugins... It appears the installer was failing to overwrite the existing package. downstream-keyer.plugin is dated 12-2-23. Renaming the file and running the installer, the new file was generated. This fixed it. Thanks.
 
Last edited:

angeloruggieridj

New Member
With OBS 32 and downstream Keyer plugin (updated to 0.4.1 version), OBS crashes when you try to change the scene collection on macOS.
Using the macOS dump, I've seen that:

Type of error: EXC_BAD_ACCESS (SIGSEGV), access to a memory address not valid.
• Caused by the function: obs_canvas_get_channel called from DownstreamKeyerDock::SceneChanged().

Is it possible to investigate? I've found solution removing the plugin.
 

CS Murphy

New Member
The latest version of OBS conflicts with the current version of Downstream Keyer. Not sure if someone has reported this yet but it keeps asking me to either update the plugin or remove it when I open OBS. Is there a workaround to this?
 

cryptopoboy

New Member
The latest version of OBS conflicts with the current version of Downstream Keyer. Not sure if someone has reported this yet but it keeps asking me to either update the plugin or remove it when I open OBS. Is there a workaround to this?
I'm getting the same thing. I have tried to update but it never installs. Has anyone else had this issue and found a fix or workaround?
 

AaronD

Active Member
Macos 15.4.1 with Downstream keyer Version 0.4.1 installed, OBS32 RC1 fails to load , delivering warning on startup. Installing a 2nd time for good measure has the same result.
The latest version of OBS conflicts with the current version of Downstream Keyer. Not sure if someone has reported this yet but it keeps asking me to either update the plugin or remove it when I open OBS. Is there a workaround to this?
I'm getting the same thing. I have tried to update but it never installs. Has anyone else had this issue and found a fix or workaround?
Same for me, except I updated from the official PPA on Ubuntu Studio Linux. Apparently, it was released with this bug still present. Get ready for yet another flood of, "YOU $#@! BROKE MY RIG!!!"
(I blame the core devs, not the plugins. They've done this many times before and don't seem to care. They think they can just do what they want with no warning (no, the RC versions do NOT count as warning), and it's always everyone else that's wrong.)

Fortunately, it seems to work anyway. But it would still be nice to not have the error message on every startup.
 
Top