The OBS package in Soundflow store is a critical piece for continuing operation of my studio because I primarily use my Stream Deck for changing cameras. I'd love to be pulled into the Soundflow Strea
Title
The OBS package in Soundflow store is a critical piece for continuing operation of my studio because I primarily use my Stream Deck for changing cameras. I'd love to be pulled into the Soundflow Stream Deck direct integration but I will be unable to do so if I cannot operate OBS from there.
What do you expect to happen when you run the script/macro?
I have OBS Studio 30.1.2 with the WebSocket Server enabled running on port 4455 with Enable Authentication turned off and the soundflow OBS Studio package says it cannot connect to the server.
Are you seeing an error?
I would imagine it should connect successfully to the OBS Server and then toggle the Stream/Stop state.
What happens when you run this script?
Popup message that says it cannot connect to the OBS server.
How were you running this script?
I clicked the "Run Script" or "Run Macro" button in SoundFlow
How important is this issue to you?
5
Details
{ "inputExpected": "I have OBS Studio 30.1.2 with the WebSocket Server enabled running on port 4455 with Enable Authentication turned off and the soundflow OBS Studio package says it cannot connect to the server. ", "inputIsError": true, "inputError": "I would imagine it should connect successfully to the OBS Server and then toggle the Stream/Stop state. ", "inputWhatHappens": "Popup message that says it cannot connect to the OBS server. ", "inputHowRun": { "key": "-MpfwYA4I6GGlXgvp5j1", "title": "I clicked the \"Run Script\" or \"Run Macro\" button in SoundFlow" }, "inputImportance": 5, "inputTitle": "The OBS package in Soundflow store is a critical piece for continuing operation of my studio because I primarily use my Stream Deck for changing cameras. I'd love to be pulled into the Soundflow Stream Deck direct integration but I will be unable to do so if I cannot operate OBS from there. " }
Source
const OBS = require('package:ck8ue17890001f7103bp5s47q');
OBS.sendMessage({ 'request-type': 'StartStopRecording', });
Links
User UID: zjMdzrDxU8WCXM0RpBRCa0ChOJp1
Feedback Key: sffeedback:zjMdzrDxU8WCXM0RpBRCa0ChOJp1:-NvXfdMFq01N-YPHNXNz
Feedback ZIP: Zj3VRG5FFC8m9LUWnC56p8164F6y9irmlpSxhmBvxG4pFJyxQSbLeq7a4OpJhrABPhQ6q//+zO7txjbgz+PjQxiz2aBrYDBSScNYnH4kVDWXv/U838e1cOGoiU1wgfwqT5xk4P9wLt6CuIqietQYXEGZwksWWb0O1YmP0jbzS9A9ULanAGHC5cvHFRWbJkaOssnbLicrFCs09iqE61V4x7hsjPK/R9XhlRmxVHss4LKGLCcKhhGDXAiWVemlayMPf2fbveod/Co5zU9B5FQ62G8jhZqOn8C+sT9Bdn3SgSi8NueFQpott5iSq+xl44382uNi5nf6kksuj0yhGL9YCw==
Linked from:
- SSoundFlow Bot @soundflowbot
Thanks for posting a question or an issue related to the 'OBS' package.
This package is made by @chrscheuer. We're auto-tagging them here so that they will hopefully be able to help you. - SIn reply tojmailakey⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-1182
- In reply tojmailakey⬆:Christian Scheuer @chrscheuer2024-04-16 16:33:30.673Z
Thanks for reporting. The OBS package is long overdue an update. Last time I worked on it, I was having trouble getting the websockets to play nicely with the new OBS version, but I'll take another look.
Dana Nielsen @Dana_Nielsen
Yes yes! I too have been eagerly awaiting an update to the OBS package - I miss it so much!
Thanks so much for looking into this for us - you rule, Christian!
- JIn reply tojmailakey⬆:jmailakey @jmailakey
Thank you for all your fantastic work for the community already @chrscheuer and eagerly anticipating your latest update!
- In reply tojmailakey⬆:Christian Scheuer @chrscheuer2024-06-11 17:06:17.261Z
We expect to reintroduce OBS 30+ support in the upcoming SoundFlow 5.8 version (and OBS package 2.0). Please let us know which commands you're interested in being able to control.
We've started with the ability to control the active scene.- MMike Indovina @Mike_Indovina
Even with the new version of Soundflow 5.8.0, and the updated 2.0 package, it still doesn't seem to work with OBS. I keep getting the error "This meta command doesn't implement useCommandBehavior or useFlowBehavior, so it can't be run" whenever I try to use it to switch scenes. I've even followed all the websocket instructions. Any idea what to do to fix that?
Christian Scheuer @chrscheuer2024-07-09 18:27:38.387Z
Hi Mike,
The new package is designed to be used on a Stream Deck right now. I'm assuming you were adding a keyboard trigger to it?
Christian Scheuer @chrscheuer2024-07-09 18:29:44.748Z
The reason for this is a bit technical, but the platform currently lacks support for keeping websocket connections open for something like keyboard triggers. We can do that for decks, which have a defined "lifespan", meaning SF knows when you navigate away from the deck to let go of open websocket connections, which provides a clear path for resource management. For keyboard triggers, SF wouldn't know when to close the connections, which could lead to memory bloat and poor performance without a visual way to configure this as a user.
- In reply tochrscheuer⬆:
Christian Scheuer @chrscheuer2024-07-09 18:34:24.473Z
Please see here for updated installation instructions btw - these changed in the new OBS package to account for changes in OBS
- MMike Indovina @Mike_Indovina
I am actually using a Stream Deck. It's strange. I was able to get the mute buttons to work but not the scene switching. Nothing happens when I press those :(
Christian Scheuer @chrscheuer2024-07-09 19:09:14.192Z
Can I get you to open a new support ticket for this so we can see your log files?
- JIn reply tojmailakey⬆:jmailakey @jmailakey
The basic OBS commands I use are select/change scene, start recording, stop recording, start streaming, stop streaming. Lesser used would be system hotkey.
- CIn reply tojmailakey⬆:Chris Winter @Chris_Winter
Oh yeah! I'd love to be able to Mute/Unmute particular audio channels by name.