Dig_Douglas
New Member
Hey all,
I am currently setting up a new set of alerts with small .webm files rather than .gif. Everytime an alert is triggered that serves up one of the .webm files, the browser source layer in OBS becomes unresponsive altogether. Only a restart of OBS as a whole will reset the browser source layer.
Bringing up the alert page in Chrome and triggering playback of the .webm file results in perfect playback, so I doubt that the issue lies with Streamlabs.
Any idea what could be causing this? It would be nice to finally move away from lower quality .gif files and onto .webm
Recording of a test here. First a gif alert is played, then a webm. You can hear when Browser Source crashes because it only plays the first fraction of the alert sound.
The size of the .webm file is 455.4KB. I have tried multiple different files as well.
Thanks
I am currently setting up a new set of alerts with small .webm files rather than .gif. Everytime an alert is triggered that serves up one of the .webm files, the browser source layer in OBS becomes unresponsive altogether. Only a restart of OBS as a whole will reset the browser source layer.
Bringing up the alert page in Chrome and triggering playback of the .webm file results in perfect playback, so I doubt that the issue lies with Streamlabs.
Any idea what could be causing this? It would be nice to finally move away from lower quality .gif files and onto .webm
Recording of a test here. First a gif alert is played, then a webm. You can hear when Browser Source crashes because it only plays the first fraction of the alert sound.
The size of the .webm file is 455.4KB. I have tried multiple different files as well.
Thanks
Attachments
Last edited: