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
Not the most accurate. #2
Comments
If you can get the tempo to be accurate, you on to something great. Keep going. |
Thanks for taking a look. Do you remember about what you had the metronome set at and about what the tempo read on the site? Knowing the direction and magnitude of the error might help diagnose it. There are probably practical limitations to accuracy from relying on browser API's for time and click information, but I wouldn't be surprised if there is low-hanging fruit to improve the accuracy from where it is now. |
No problem. I was kind of excited when i ran accident it. And i had my
metronome in my DAW set to 120 bpm, and the tempo online when be at 120 for
about 8 beats or so and then it would continue to increase going up to
about 150 or so. I hope this feed back helps a lot.
…On Sat, Nov 20, 2021 at 10:57 AM Blake Johnson ***@***.***> wrote:
Thanks for taking a look. Do you remember about what you had the metronome
set at and about what the tempo read on the site? Knowing the direction and
magnitude of the error might help diagnose it. There are probably practical
limitations to accuracy from relying on browser API's for time and click
information, but I wouldn't be surprised if there is low-hanging fruit to
improve the accuracy from where it is now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWSQVAKGGR3XCZ27N5U443LUM7APTANCNFSM5IMQBB6A>
.
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>.
|
Appreciate it - that definitely sounds wrong. I may not be able to get it 'perfect' but the tempo running away like that isn't even usable. I forgot to ask, which browser was this in? Since I'm relying on browser API's via WASM this behavior might be browser-specific. I'm off work all next week and will be able to poke at this a bit. Knowing the browser might help me reproduce and troubleshoot. |
Yes exactly like if it at least stuck around the 120-130 that would be a
whole different world. I was using googles chrome browser on my iphone xs
and on my ipad 5th generation same browser on both.
…On Sat, Nov 20, 2021 at 11:40 AM Blake Johnson ***@***.***> wrote:
Appreciate it - that definitely sounds wrong. I may not be able to get it
'perfect' but the tempo running away like that isn't even usable. I forgot
to ask, which browser was this in? Since I'm relying on browser API's via
WASM this behavior might be browser-specific. I'm off work all next week
and will be able to poke at this a bit. Knowing the browser might help me
reproduce and troubleshoot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWSQVAMPBNRJPPUSXPF3TBTUM7FODANCNFSM5IMQBB6A>
.
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>.
|
When i saw this i was like wait whats going on, there were no real instructions on how to use it. But once I figured out what was on, I quickly realized it wasn’t that accurate.
I even used my metronome with it to be sure i was tapping with consistency/on beat. But regardless of the tempo i was goin at the tempo seem to rise regardless on the app.
The text was updated successfully, but these errors were encountered: