-
Notifications
You must be signed in to change notification settings - Fork 45
Description
If OBS is live over night (I don't know how many hours, i haven't timed it) the glitch shader will effectively freeze and no longer tremor, showing only one frame, like this:
The workaround is to restart OBS, and it doesn't happen during a 4 hour stream, but any 12-24 hour streams are going to hit this issue, and running a second OBS with glitch -> media source or RTMP stream -> primary OBS is...a lil heavy. 😅
This seems like a counter overflow (or just too big) issue? Is there some line one-line patch I can put into the code to if (problem_value_too_big) set_it_to_zero_and_start_over to escape this entirely? Unfortunately my knowledge in shader languages is zero, so I wasn't able to really grok which field might be overflowing or if it's even within the shader file itself. Any ideas? I love this filter, I use it constantly for basically everything. 😅
Thanks for reading this! I recognize you're busy as hell and you bring a LOT of value to the OBS community, for which I'm very grateful. I use a LOT of your stuff.
