Looking for Clarity on New Browser Source Parameter

[Surge42]

When setting up a browser source there's a parameter titled "Page Permissions" at the bottom, it's a pulldown. The selections in this pulldown are the following.

1. No access to OBS
2. Basic access to OBS (Save replay buffer, etc.)
3. Advanced access to OBS (Change scenes, start/stop replay buffer, etc.)
4. Full access to OBS (Start/Stop streaming without warning, etc.)

Can I assume the browser source has the ability to control OBS? Is their a working example that demonstrates this capability?

 

[Surge42]

Can I assume the browser source has the ability to control OBS? Is their a working example that demonstrates this capability?

I continued to dig and found the answer which is YES, HTML can no do the following with OBS studio.


obs-browser introduces a cross-platform Browser Source, powered by CEF (Chromium Embedded Framework), to OBS Studio. A Browser Source allows the user to integrate web-based overlays into their scenes, with complete access to modern web APIs.

On Windows, this also adds support for Service Integration (linking third party services) and Browser Docks (webpages loaded into the interface itself). macOS support for service integration & browser docks is in the works, and Linux support is planned.

The following actions can be performed.

1. Hiding and showing sources
2. Starting and stopping the stream
3. Scene selection.
4. Starting and stopping the virtual cam.
5. Starting and stopping the replay buffer

For 99% of most users this parameter should be set as "No access to OBS"

 

[Mango]

Is there any way to do this with a browser dock?

alert(window.obsstudio.pluginVersion); // alerts 2.17.13
window.obsstudio.getControlLevel(function (level) { alert(level); }); // does nothing
window.addEventListener('obsSceneChanged', function(event) { alert(event.detail.name); }) // does nothing

If I'm doing this wrong I'd be delighted to know how to fix it.