Frequently Asked Questions
Answer:
Yes, this is possible for audio files with variable tempo or silent pauses. The second possible cause is a file access error or decoding error. In this case, BPM Counter cannot detect the BPM and will return a null value. You can enable the "Ignore decoding errors" option, but this may affect the accuracy of the results.
Answer:
This is the so-called octave error. A harmonic of a wave is a component frequency of the signal that is an integer multiple of the fundamental frequency. In some cases second harmonic may have higher energy, so BPM Counter will return double BPM value.
Answer:
First of all, make sure that you selected the correct folder with the audio files on the left navigation bar. BPM Counter supports only WAV and MP3 audio files, it will not see MP4 files from iTunes.
Answer:
Make sure that BPM saving in tags is enabled in the program settings and click the Refresh button. If the problem persists, the problem is most likely with the ID3 tag format. Windows Explorer only supports the old ID3v2.3 tag format. Even in Windows 10 this situation has not been fixed and ID3v2.4 support has not been added. To fix this problem, you need a tag editor or use tuneXplorer, which allows you to convert tags automatically.
Answer:
Yes, you can do that using the console version. You can run it in batch files or from other applications.
Answer:
BPM Counter can store BPM values inside ID3 tags so that any software can access them. Keep in mind that iTunes will need to refresh the audio library so that the BPM values are read from the tags anew.