Exeldro
Active Member
Exeldro updated Downstream Keyer with a new update entry:
Version 0.4.1
Read the rest of this update entry...
Version 0.4.1
Read the rest of this update entry...
- Thread starter Exeldro
- Start date
thomaslfessler
Member
Thanks for the update. However - 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.
Exeldro
Active Member
@thomaslfessler can you try manually uninstalling the plugin be fore installing it?
thomaslfessler
Member
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.
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.
Exeldro
Active Member
@CS Murphy version 0.4.1 should work with OBS 32. Can you verify updating the plugin was successful?
CS Murphy
New Member
Ahh updating did the trick. . . Thank you sir and all that you do. Aloha from Maui
angeloruggieridj
New Member
Any update about OBS 32 crash when changing scene collection?
cryptopoboy
New Member
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.
Exeldro
Active Member
Exeldro updated Downstream Keyer with a new update entry:
Version 0.4.3
Read the rest of this update entry...
Version 0.4.3
Read the rest of this update entry...
kevinlemaguer
New Member
Hello! Is there a macOS Silicon version in production?
angeloruggieridj
New Member
Crash when changing fixing collection is not solved at all. When you switch from a project where you have DSK defined on another where there aren't DSK defined, it crashes.
Here's the macOS dump: https://pastebin.com/rGyLuqeF
Solved at the moment uninstalling the plugin.
cptroger76
New Member
Hi Exeldro, thanks for the update. But question, from the downloads, what is the 'downstream-keyer-0.4.3-windows-programdata.zip' used for? I'm using the OBS portable on Windows, so I guess, I don't need it?
Exeldro
Active Member
@cptroger76 that is for if you want to install into your global OBS, but don't want it in program files, you can put the plugin in program data
2SmokinBarrels
New Member
Hi Exeldro, in the next update, can we get checkboxes in the Exclude list so we can check multiple scenes at 1 time. If I want to exclude 10 scenes, I need to click exclude for each item. Aldo, would be nice to have all new scenes excluded by default as each time I make a new scene, typically just a scene that will be nested, I need to remember to go into all my DSK's and exclude the new scene.
Either way, thank you, you are a legend!
Either way, thank you, you are a legend!
I second that! It's tedious to have the list go away when I select one, and have to reopen it for the next one, and reopen it for the next one, and......
It would be so much nicer to open it once and then check all of them without it closing until I'm actually done.
That should probably be a setting. I can see arguments either way.