Reading the current Scene from remote OBS

[Kirbo]

Read the GetCurrentProgramScene from remote OBS instance.
Currently I can add a "Scene" action from Multi OBS Controller, but that only shows whether the given scene is active or not.
I'd want to see which scene on the remote OBS is active at the moment.
The "Stats" would be sufficient, if it only had an option to show GetCurrentProgramScene.

I tried using the Raw WS Request, but it looks to me that it's meant to be used only for setting/commanding the remote OBS, not to read data from it. Correct me if I'm wrong.

[theca11]

There is currently no way to display in text the active program scene.

Raw WS Request was indeed meant for set-like requests. While trying to send a GetCurrentProgramScene request does send it, the response isn't parsed and therefore it's efectively useless at the moment. Even if it did work, you would have to press the key to update the information, which probably wouldn't be ideal. The Stats action is tied to the GetStats request and that's why it doesn't have such info.

I guess I could potentially add a new action, similar to the Stats one, to allow displaying some extra info. What is your exact use case and ideal solution? Not promising anything, but open to suggestions.

[Kirbo]

I guess I could potentially add a new action, similar to the Stats one, to allow displaying some extra info. What is your exact use case and ideal solution? Not promising anything, but open to suggestions.

I think I'll fork and play around with the plugin at some point anyway 🙂 Didn't mean you shouldn't/couldn't make this enhancement/feature, but since I also know TypeScript, I could do a Pull Request. Not sure when I'd have time or energy to do that, but even if you did this feature request, I'd still play around and perhaps try to come up with some ideas worthy enough to create Pull Requests 🙂

In any case, thanks for your awesome plugin! Made my life a whole lot easier, since I have a OBS running on my separate machine, that handles the streaming and my PC is running another instance of OBS (and broadcasts the Current program via NDI to my stream machine), and I have Stream Deck connected to my gaming PC, so I'd like to be able to see directly from the Stream Deck that which Scene is active on the Streaming machine.
For now I can manage with the Scene action, as I only have 2 scenes on the remote machine;

• Gaming PC
• Local

..but I plan to add more scenes there as well, so the Scene action wouldn't suffice anymore as it would just tell me if e.g. Gaming PC scene is active or not, but it wouldn't tell me which scene is active and I'd like to know without opening a remote control for the machine, that which scene is it currently streaming..

Edit:
Forgot to answer your question..

What is your exact use case and ideal solution?

So my use case is like following.
I have 2 computers:

• Gaming PC, that has OBS capturing the game and broadcasting via NDI to my "Streaming Mac"
• headless "Streaming Mac" that has OBS and it listens to the NDI broadcast

Currently the "Streaming machine" has only 2 scenes:

• Gaming stream
• Local

..but I intend to add more scenes in the future.

My Stream Deck is connected to my "Gaming PC". I'm using the "Multi OBS Controller" at the moment to be able to see directly on my Stream Deck, whether my "Streaming machine" is streaming or not and for how long has the stream been active.

What I'd like to achieve, that is currently not possible;
I'd like to be able to add an action on the Stream Deck, that would subscribe for the CurrentProgramSceneChanged event and just bluntly show the name of the Scene that is currently active, on the remote OBS instance. It doesn't need to be fancy, just show the name of the scene.
Not sure how you could achieve this if you intended to still have the support for 2 OBS instances for the action..? Perhaps have 2 lines, where the top line would show the scene name of the OBS 1 and the bottom line would show the scene name of the OBS 2?

Instead of having this, I'd like to just see the Active Program Scene Name here:

Currently I have 3 scenes, and my workaround is that I created a Folder on Stream Deck and inside the folder I created 3 separate "Scene" actions:

But if you intended to make this actually usable for other use cases as well, I think you should add a "Listener" action, that would contain a drop down for all the subscribeable events (with the possibility for the user to type there whatever they wish, so the user wouldn't be limited by the pre-defined list of types, perhaps all of these?) that OBS Websocket currently provides, then have another field where user could "code" that what data do they want to read from the event data ("response"). Then this new action would be dynamic and re-usable for any other event as well, not only for my use case.

Sorry for the wall-of-text and most likely somewhat obscure post anyway.. 😅 I made some modifications during the comment and I didn't feel like it'd be necessary to update the previous statements (namely; having 2 scenes and the names of the scenes).