Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser Sources: Unexpected behavior when 'Control audio via OBS' is checked #10586

Open
AcidicVoid opened this issue Apr 22, 2024 · 2 comments

Comments

@AcidicVoid
Copy link

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

30.1.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/f8qs1OL4QQxzEMmw

OBS Studio Crash Log URL

No response

Expected Behavior

I used alerts from Streamlabs and Blerp.
They should show a gif or video and play a sound if a correspondent events fires.

Current Behavior

The alerts work as expected for a seemingly unpredictable time.

I think it takes about 10 to 20 minutes until the alerts stop working.
The sounds won't work anymore. Animations sometimes still work.

Steps to Reproduce

  1. Add a browser source with Streamlabs or Blerp alerts (It probably works with anything that uses sound and/or video)
  2. Make sure "Control audio by OBS" is checked in the browser source's properties
  3. Activate "Monitor and Output" for the browser source's audio
  4. Start a stream (not sure if necessary)
  5. Wait 10 to 20 minutes
  6. Fire an event that should trigger an alert

Anything else we should know?

No response

@Penwy
Copy link
Contributor

Penwy commented Apr 23, 2024

Does OBS being minimized or hidden by another window have any influence on this happening?
If it only happens with OBS minimized/hidden, this is likely related to #7588

@AcidicVoid
Copy link
Author

AcidicVoid commented Apr 23, 2024

I'm sure it was never minimized.
Sometimes it was covered by another window (OBS and the other window both maximized), but I don't think that would be considered "hidden"?

EDIT:
One of the steps to reproduce #7588 is "open OBS again wait 10 seconds the problem disappears".
I can confirm that this not working in my case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants