You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated my streamdeck and experienced a severe impact in OBS -- if I delete the plugin and open OBS, my frames render at a fairly consistent 20ms. When I have the plugin present, however, my overall rendering time can jump to over 60ms, and depending on what I am modifying can cause noticeable hang ups of much longer.
I have a fairly large scene collection of about 9 megabytes, and my scenes actively move sources around, change visibility of sources, and activate/deactivate filters. The plugin making a heavy use of OBS signal handlers is my guess at the problem without looking too deeply into it. At the moment, as a workaround, I have started using my streamdeck to trigger streamer.bot and have streamer.bot communicate to OBS (I already had corresponding actions in streamer.bot anyway, so this was a quick workaround for me).
Suggested update to the plugin is to minimize what is monitored and install fewer overall handlers.
The text was updated successfully, but these errors were encountered:
I recently updated my streamdeck and experienced a severe impact in OBS -- if I delete the plugin and open OBS, my frames render at a fairly consistent 20ms. When I have the plugin present, however, my overall rendering time can jump to over 60ms, and depending on what I am modifying can cause noticeable hang ups of much longer.
I have a fairly large scene collection of about 9 megabytes, and my scenes actively move sources around, change visibility of sources, and activate/deactivate filters. The plugin making a heavy use of OBS signal handlers is my guess at the problem without looking too deeply into it. At the moment, as a workaround, I have started using my streamdeck to trigger streamer.bot and have streamer.bot communicate to OBS (I already had corresponding actions in streamer.bot anyway, so this was a quick workaround for me).
Suggested update to the plugin is to minimize what is monitored and install fewer overall handlers.
The text was updated successfully, but these errors were encountered: