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 tried running it at 120 and it's significantly slower than actually 2 beats/sec. I'm not sure if the animation may be interfering with this or something, but other apps such as Tick have animations and can still accurately reach any BPM with no problem.
Samsung Galaxy S21 FE 5G on Android 12 (OneUI 4.0)
The text was updated successfully, but these errors were encountered:
I've tried to reproduce, but none of my two devices, nor the emulator, has this issue. Maybe when I set the tempo to 120 it is actually closer to 119 or 118, but that seems like a really minor difference (though I agree - significant in some cases).
I've checked, and TICK is built using completely different technologies, but the use of the standard Android tools in Musekit shouldn't make a difference. I also see no reason for the animation to be the reason behind a slowdown.
How big of a discrepancy are we talking about? Could you estimate how fast the metronome is going when you set it to 120 BPM?
I tried running it at 120 and it's significantly slower than actually 2 beats/sec. I'm not sure if the animation may be interfering with this or something, but other apps such as Tick have animations and can still accurately reach any BPM with no problem.
Samsung Galaxy S21 FE 5G on Android 12 (OneUI 4.0)
The text was updated successfully, but these errors were encountered: