Since 1.32 BPM Analysis on player will now reference ID3/Metatag data when running the analysis for improved accuracy. Some players / audio taggers store the BPM in the ID3 with format 13110 (for BPM 131.10). Prime 4 analyzes these files with high BPM ID3/Metatag with a BPM of 500. It is then impossible to get the BPM right on the unit.
Possible solutions:

Prime assumes that a BPM above 500 must be truncated to the first 3 numbers (such as 13190 becomes 131 as the starting point for analyzing)

Prime ignores ID3 BPM values above the logical values of a BPM range (such as above 200), or above its own limit (seems like this is 500) and calculates the BPM entirely on its own without ID3 info

Prime can logically declare the BPM in a tag from, for example, 1315 to 131.50 and a BPM from 13155 to 131.55)

Software or Firmware Version: (1.2, 1.3.1, etc…) Prime 4 V1.32

Steps to Reproduce: Load an unanalyzed file with high BPM ID3/Metatag and let Prime 4 analyze.

Expected Result: (ex: It does X…) Correct BPM calculation

Actual Result: (ex: It does Y…) BPM calculation of 500, only to double/half , not to be corrected

Reproducibility: (ex: Happens 1 out of 10 times.) Every file with BPM info above 500 (

Other Relevant Info: Cue / Play buttons also flashes like strobes, since their blikspeed follows the BPM, giving the looks of a defected LED