Timer underestimate real processed time

[HansVanNeck]

Bug Description

The timer underestimates the real time with 10%. .

Steps to Reproduce

1. See attachment. The time i 00:06:04.
2. If you yse it in teleprompter mode it taks 00:06:41

Expected behaviour

The timer must be exact on the second.

Detailed description of display configuration (if applicable)

Velocity 6.

Screenshots (if applicable)

...

Device information

• Operating System: [e.g. Linux, Windows, macOS, iOS, or Android]
• QPrompt Version: [e.g. 1.0.0-beta-003]

Additional context
This is a showstopper for us. Without reliable timing, we cannot use the application.
.
G0210NL_Ewb.zip

[Cuperino]

I'm sorry this makes the app unsuitable for your workflow.

I already knew the timer's implementation was inaccurate for scripts of long duration; but this shows it is actually worse than what I was previously able to measure, affecting scripts of short duration as well. I already have a solution planned, but it requires refactoring code. I'm afraid that I won't be able to make these changes before January.

My apologies. I will keep you posted if anything changes.

[HansVanNeck]

It is always good to refactor code. In the mean time we will use our current application teleprompter Pro. However that application has an accurate time, but has extremely weak file management. If you have a new version I will be glad to test it again. From: Javier O. Cordero Pérez ***@***.***> Sent: maandag 13 december 2021 06:46 To: Cuperino/QPrompt ***@***.***> Cc: Hans van Nek ***@***.***>; Author ***@***.***> Subject: Re: [Cuperino/QPrompt] Timer underestimate real processed time (Issue #26) I'm sorry this makes the app unsuitable for your workflow. I already knew the timer's implementation was inaccurate for scripts of long duration; but this shows it is actually worse than what I was previously able to measure, affecting scripts of short duration as well. I already have a solution planned, but it requires refactoring code. I'm afraid that I won't be able to make these changes before January. My apologies. I will keep you posted if anything changes. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#26 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWYLK7ZPRA2VZNYI7XZBXXTUQWCDJANCNFSM5J4KDNSA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[Cuperino]

Thought of a simpler implementation that's not as performant as the one I was planning on using, but was faster to code and is precise to the second. The changes to the code already up. I'll make new binaries for all platforms and upload them as beta-006 in the upcoming days.

I'll share the link with you here as soon a they're up.

[Cuperino]

Fix ready for download at: