Bug Report Browser Source Refreshes Too Late

deetari

Member
When adding a browser source, there's no way to hide it when it's not active. Since I'm using the source to animate a scoreboard that needs to slide in upon switching to a particular scene, I need it to start from blank each time the scene is switched in.

Unfortunately, "Refresh browser when scene becomes active" literally refreshes the browser source immediately after the scene is loaded, causing the scoreboard to appear briefly before the refresh kicks in, flash out of existence as the refresh happens, and then finally slide back in. This is because the scoreboard is loaded into the preview window in Studio Mode, then refreshed upon being pushed live.


Is there any way to get the source to stay inactive until it's pushed live? Or to either refresh the browser source before the transition or delay the start of the transitions by a minuscule amount to allow for the refresh to go off before the scene is pushed live?


Thanks!
 
Last edited:

deetari

Member
Here's a video to clarify the problem:

https://www.youtube.com/watch?v=OGU7Oo5PUW8


When pushing the scene live (switching it to the right-side window), the scoreboard flashes before the browser refreshes.

I've set the transition to a hard cut to make the problem easier to see. It still exists with every other type of transition, though, and is very noticeable when using a fade transition.


The desired behaviour can be seen on the left side window, when simply switching scenes without pushing them live (basically the behaviour you'd get when not using Studio Mode).
 
Last edited:

deetari

Member
I'll take a look at those, and perhaps file a bug report if I can't get things worked out.

Thanks for the suggestions. :)
 

deetari

Member
What you could do is trigger the animation on the page by using a callback in the obs-browser source
See https://github.com/kc5nra/obs-browser/blob/master/README.md#js-bindings

Another method is to trigger the animation by using websockets (https://github.com/lebaston100/htmlOverlayFramework)

If you think this is a bug that needs to be looked at, file a bug report here: https://obsproject.com/mantis

This appears to be a bug or an overlooked issue, upon further inspection. Implementing the scoreboard reset via a callback in javascript encounters the same problem, due to the fact that the scene change is only reported after the transition is completed.

I've submitted a bug report (https://obsproject.com/mantis/view.php?id=1001).

Thanks again for the help. :)
 
Top