Possibly a really basic one here, but I can’t find any info. I’m having 2 problems with Tap Tempo -
it takes ages to get to tempo. ie to get from 120 to somewhere around 70 takes many many taps. Surely just as 2 points define a plane, 2 taps define a tempo! Why is it so gradual, and is there an option for this?
60bpm is the limit to how low I can go via tapping. As in I tap (for ages) to get the tempo down, but at 60 it just stops reacting. I can manually set it lower, but for tap tempo it gets stuck at 60bpm
A couple of years ago Steinberg decided to turn a perfectly fine tap tempo algorithm into a pile of garbage. And apparently they don’t give a {something with f} about users’ opinions in this matter.
The Steinberg folks are usually a lovely bunch. But at times they can be stupid and arrogant.
Stupid, because they crippled a functionality from “all is well” to “hardly usable” (while at the same time even removing another function altogether).
Arrogant, because afterwards they communicated here on the forum that everything is fine. They basically suggested that we are all idiots for thinking the tap tempo algorithm doesn’t work well.
I am here to be frustrated about the Tap Tempo weirdness, which is a problem for me also.
Most importantly the first point by @hempt that is a really broken function.
As a instinct-driven musician, I would very often use this to enter the tempo that I have in my head for a new piece or a section, but the only way to do that is to keep tapping until the tempo reading stabilises, which means that now my tapping is “accepted”. by the software.
The Steinberg folks may have had this idea that “when your taps are really stable, then you can have the tempo you imagined”. Well, it is pedagogy, after all… (irony)