What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value.
I like that idea.
good one, I will try and incorporate it.
Yes, it's very often so that BPM software like "Mixmeister BPM Analyser" finds a BPM value half or double of the correct one.
An option like that suggested by mistresso would be exactly the thing to "round up" the BPM.tapper and make it a "perfect thing"