OBS 27.2 Browser Source Audio Output device

jormunsormr

New Member
Prior to updating to 27.2, browser sources that were not "Control Audio Via OBS" would get sent to whatever audio device OBS itself was being routed to (My GoXLR's System output). Using Windows "App volume device preferences" that could be set to whatever device was desired and it would stick. Now with 27.2 it appears that "obs-browser-page.exe" is the App that needs to be routed for that audio and it needs to be changed away from and then to the desired device every single time OBS opens.
Otherwise it continues to show the correct device but doesn't route correctly without changing it and changing it back. It simply routes to the system default device otherwise.
How do I get it back to the original behavior that "sticks" correctly?

Attached a log but don't think it'll help even remotely.
 

Attachments

  • 2022-02-18 05-05-51.txt
    27.3 KB · Views: 44

jormunsormr

New Member
had you used the monitor OBS didnt play sound to devices witout monitoring !
I have always had monitoring off for this browser source and the browser source audio had always just gone to the device I told Windows to route OBS's audio to. Which it still does, except that the obs-browser-page.exe is now the source of the audio rather than OBS itself which doesn't seem to work properly with the routing and instead defaults to the system default every time OBS is opened.

Looking into to this more, it may be because it got updated and it's actually a Chrome(ium) issue that it doesn't work properly after reopening since it appears to be happening now with Chrome as well now that I'm testing that. (I rarely use audio on chrome on the OBS PC). Which likely means it's going to be stuck that way for basically forever.
 

nalv22

New Member
I have always had monitoring off for this browser source and the browser source audio had always just gone to the device I told Windows to route OBS's audio to. Which it still does, except that the obs-browser-page.exe is now the source of the audio rather than OBS itself which doesn't seem to work properly with the routing and instead defaults to the system default every time OBS is opened.

Looking into to this more, it may be because it got updated and it's actually a Chrome(ium) issue that it doesn't work properly after reopening since it appears to be happening now with Chrome as well now that I'm testing that. (I rarely use audio on chrome on the OBS PC). Which likely means it's going to be stuck that way for basically forever.
Have you been able to find a solution? I have the exact same issue and it's driving me crazy.
 
Top