[Bug Report] Can't control OBS remotely from examples

[nt3rp]

Summary

VDO.ninja is not able to control OBS remotely.

Reproduction Steps:
Following the &controlobs example

1. Add a browser source to OBS Studio with this URL: https://vdo.ninja/?view=streamid12345&remote&controlobs
2. Give page permissions to the browser source (Full access to OBS)
3. Open this "Push" link in a browser: https://vdo.ninja/?push=streamid12345&wc&as&controlobs&remote
4. Click on this 'controller' button
5. Control OBS Studio remotely via VDO.Ninja

Expected:
Some controls should appear in the browser to control OBS

Actual:
"No remote controllable instances of OBS Studio are found."

Screenshot

Additional Context

VDO.ninja lists a number of examples, including some examples for controlling OBS remotely:

• OBS Remote Dashboard
  • Connect button can be pressed, but no visible changes in browser UI
  • No websocket related events either
  Screenshot

  
• OBS Remote Mini
  • Connects (in UI)
  • ... but still says "No remote controllable instances of OBS Studio are found."
  • No visible UI for controlling OBS
  Screenshot

  

The latter example references the &controlobs.

In all cases, the result is the same, "No remote controllable instances of OBS Studio are found."

There's also this issue (that may have been previously addressed) still open from 2020.

At least one of the examples may be based on this repository, that does mention the following:

This code needs to be re-developed to support v5 of OBS websockets, as OBS no longer uses v4.

...So I'm not sure if that's related.

System Details

• Operating System: Windows 11 (x64)
• OBS: 32.0.2

[steveseguin]

Thank you for the report. I'll take a look.

[nt3rp]

If I debug the examples, I can definitely see messages being sent over websocket, but nothing is particularly illuminating.

If I debug the &controlobs example, it looks like session.pcs[UUID].obsState.details is undefined, which means it can't even read the access level to do other operations (but I don't know if this is a case where VDO.ninja has fallen behind obs-websocket, or if it's a OBS / network configuration issue)

[steveseguin]

There must be a bug in my newest v28.6 update, as it's working on a previous version.

Please try with the following URLs to see.

https://vdo.ninja/v28/?view=streamid12345&remote

https://vdo.ninja/?push=streamid12345&wc&as&controlobs&remote

Side note: I don't use websockets in this mode for controlling OBS.

[nt3rp]

I can confirm that using v28 does work! 🎉

[steveseguin]

I pushed a patch out for this. I think I figured it out; a js mutation-state error. Anyways, assuming you do a browser cache refresh in you OBS browser source settings, I think it will work on production now. It seems to work for me at least in an initial test.

Thank you kindly for the bug report.

[nt3rp]

I had one follow-up question; the docs seem to indicate that this should work while directing.

The ability for VDO.Ninja to Remotely Control OBS Studio while streaming/directing

The menu button to control OBS auto-shows in the director's view or push-mode, if OBS Studio is set to give VDO.Ninja "full" permissions.

... But I haven't been able to figure out the correct combination of parameters to allow multiple directors to control the OBS instance. Any suggestions?

[steveseguin]

are you talking about vdo.ninja directors or just multiple people trying to use the push/view links?

What is your preference on how this all works?

[nt3rp]

Directors as in the context of a room, from the control room (not with push/view links)

[steveseguin]

Do you have the director setup as co directors? My assumption would be that they would all be able to control the OBS remotely the same, but if not, I'll find time to take a look shortly

[nt3rp]

I think I figured it out; I'll share the result later and you can correct me 😆

(And if all looks good, we can close out this issue 👍🏻 )