Thanks a lot, Ocram, for testing on newer Windows systems, and also for
your "like" and your review. I have a penchant for doing idle blah blah on
this forum, so you will excuse me if I take your screenshot as an
opportunity to indulge.
You pointed out exactly the kind of use case that I had in mind! Cheap
consumer mic, and a diver case that, I believe, does not help. If we
imagine an absolute beginner, he will almost invariably be more or less in
such conditions. At least I was in these conditions (and I still am an
absolute beginner at best). The only option that one can trust and does
not involve some form of commitment is to use generic audio editing
programs like Audacity. This method is sure, but so slow and boring that
even I (despite being thorough _and_ slow) became discouraged.
Also one can see in your screenshot my other reason not to include a
numeric display for the amplitude. When the audio is bad, it might be
still possible to get the rate and the beat error, but the amplitude is
often lost because the first pulse is to weak to come through the noise.
The user can read the graphs and decide very easily, but, at least for me,
to design an algorithm that reliably does that is a nightmare (or perhaps
a dream). And also pointless, because the user can do it better than the