Control Audio Via Obs Browser source function

[ReallyReallylongathon]

I run a speedrun marathon where we use browser source for both the restreaming and for the intermission (rainwave.cc)

Ive tried multiple fixes,
changed to monitor + output,
changed audio sources.
double checked monitor devices
tried enabled windows audio ducking
checked windows audio settings.

This is a PC we connect to via parsec that has an audio device plugged in for obs to recognize.

We moved from using Nomachine and linux (where this exact setup worked but nomachine wasent as good for remote connecting) to this setup using windows 11 and parsec.

It would be great if someone can provide me with some solutions.

 

[AaronD]

Are the controls inside the web browser? Or are you trying to control a player that happens to run in a webpage?

If it's the former, and you're okay with completely redoing the controls in a new language (easy, but still new), or having them in a separate tab or window, then you might look at Node-RED:

Low-code programming for event-driven applications : Node-RED

It's really made for Linux, but there's a Windows installer too. I have it on an Ubuntu Studio machine, by running their Raspberry Pi install script and declining the Pi-specific stuff.

Once you have it installed, you'll want to install the Dashboard and OBS palettes, and then you can do this:

which produces this webpage that switches to three specific scenes in OBS:

If you want the controls (or even the editor) to be on a different machine, like a phone or another computer or whatever, just replace localhost with the IP address of the machine that you installed Node-RED on.

To make it control volume instead of switching scenes, use the obs request node, and select it from the (long!) list of Request Types:

The Request Data field is:

{
    "inputName": "MEDIA - Video1",
    "inputVolumeMul": 0.7
}

The book icon next to the Request Type takes you to the online documentation for that Type, which is where the "inputName" and "inputVolumeMul" came from.

And you have to have OBS's WebSocket server running for Node-RED to connect to:

There are a few things that I didn't show here, like how to find and install the two palettes that you need, how to make the buttons bigger than default so I don't fat-finger them on my phone, etc. But a bit of poking around should have you stumble onto them soon enough.

 

[ReallyReallylongathon]

sorry i tottaly forgot to check this since ive been busy

i was refering to the actual browser sources withen obs, if i click "control audio with obs" its just muted, if i just play the audio through system sounds it works but thats very annoying and inconvient for scene swapping.

 

[AaronD]

sorry i tottaly forgot to check this since ive been busy

i was refering to the actual browser sources withen obs, if i click "control audio with obs" its just muted, if i just play the audio through system sounds it works but thats very annoying and inconvient for scene swapping.

Huh. I have a rig that runs the audience displays in a church, as a Projector from OBS. It also plays YouTubes as browser sources, which are routed through OBS's Monitor to the external sound board.

Control audio via OBS is checked (and I do a few other things as you can see here):

which creates a source in OBS's audio mixer when it's live:

and then the Advanced Audio Properties sends it to the Monitor:

And finally, that Monitor is sent to the physical device that feeds the board:

ALWAYS CHOOSE A SPECIFIC DEVICE HERE!!! NEVER USE Default!

Default defers the choice of device to the operating system, which can and will change it. When that happens, the exact same Default setting in OBS now goes to a different device, and you think it "suddenly broke". But no, it's just the OS being stupid again, and the Default setting in OBS follows that. It's good to show that a fresh installation works, by choosing the device that you're most likely to be using at that moment, but beyond that, it's a liability. NEVER keep the Default setting! ALWAYS choose a specific device. Then it ignores the OS's auto-switch, and keeps working.

Likewise for the Desktop and Mic/Auxiliary sources just above this. Always choose a specific device, or Disabled. Never Default!

...unless of course, you have a good, defensible reason to intentionally use Default, in which case you're probably not asking for help. :-)

 

[ReallyReallylongathon]

againapologies for necroing, adhd sucks and as soon as a marathon is done i forget about the problem

Id love to follow your instructions but setting the browser source to control audio via obs doesnt create a source in audio mixer.