Back
Please consider an option to accept lower precision in the "tap to set tempo" input. It is hard to use this feature to set slow tempos, and I believe it is because the Core requires a more steady tempo than I can tap "freehand".
Hi Tdj3311, I am not sure what you mean by lower precision? We just take the average of the last 3 taps and that's it. I am not able to imagine what you mean by precision exactly? Thank you for elaborating! Oh, perhaps you mean that we should take the average of more taps, so it's easier to tap more often and gradually get closer to the desired BPM?
The problem is that the Core does not accept the tempo when I tap slower than 40 bpm. (This is different from what I described, but I believe it is correct.) It accepts tap-tempos faster than 40 bpm. I expected the Core to accept tempos down to 20 bpm, the lowest that can be set explicitly. 40 bpm appears to be a fixed limit in the software. Will it be possible to set that limit to 20, same as the other ways to set the tempo, or to enable me to set the lower limit in the application? As a workaround, I can fool the metronome by (a) tapping twice the frequency and then (b) turning off the vibration for alternate beats, but this is distracting and time-consuming, and it limits my use of other features.
Hello, I can reproduce the issue you are describing in both our mobile app and the Core. I will report this as a bug to our engineers and se if they can fix it