-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Timer is skipping seconds #114
Comments
Just figured out the problem occurs if the timer text is on top of an animated webm background. The default OBS countdown script works fine - it's only happening with the plugin. |
This issue happens because the timer now relies on timestamps to keep accurate timing when using the At some point in the future I'll need to put in an option to just count up and ignore timestamps but the code for the timer is a bit of a pain (my fault) so it will be a while before I get to it. I'm thinking I'll put an option to |
So I was working on the plugin today and decided to try a fix for this. I've added an option in the settings to use an incremental counter as opposed to using timestamps. This should ensure smooth counter incrementing. Try out https://github.com/ashmanix/obs-plugin-countdown/releases/tag/2.0.8 to see if it works. If you can confirm that this resolves the issue I'd be grateful 👍 |
Hello, I've updated my OBS plugins to ensure best support for latest OBS version (31.0.1), and encountered the "lag" for the counter. I was ready to put that on the many problems I can have because of instabilities with AMD GPU, before finding this issue. I confirm that the "steady second increment" option did the trick to fix the countdown :) |
Hi @ashmanix. Thanks for your work on this plugin.
I'm running Win 11 and 30.2.3. I did a manual install of 2.0.5 (copied the files into my obs dir) and the timer is showing up in OBS and working. But I'm having issues with it stuttering and skipping seconds. For example it'll go from 10 to 8 instead of 10 to 9. Any ideas what the problem could be?
The text was updated successfully, but these errors were encountered: