Does anyone else have the issue where a track bpm is locked, but the prime 4 will still analyze the track and change it to something wrong? It’ll show the correct bpm in library and then changes it to 120bpm when loading it? This has only started happening since 5.0