Comentário oficial
I've just heard back that they're working to issue a fix for this in a future release. Thanks for your feedback on this issue!
Hello
I'm a happy XDJ-1000 owner, but I found a funny bug with the new Rekordbox. It appears that since I analyzed all of my songs again with 5.0(not 5.0.1) that the BPM hits the MP3 file fine, but when the player plays the song back, it is doubled. I've noticed this with many files in the 60 and 70bpm range. Here is one example in the screenshot where the file tag has 82 bpm, but the player is at 164 bpm. Is there any way to have these two align, and more importantly, have the priority on the player stick with the new analyze settings in Rekordbox 5.0?
I've just heard back that they're working to issue a fix for this in a future release. Thanks for your feedback on this issue!
Publicação fechada para comentários.
Any luck testing this?
Sorry, I've reported this to the rekordbox team but haven't heard back yet. I'll post again when I've got some info.
Does it happen with every track at / around that BPM or only select tracks?
@David > One more QQ: can you check in rekordbox and tell me if the beat grid is set to 164 or 82? I'm curious to know if the grid and the BPM number match.
Yes, it is set to 82. It seemed like many songs that could have been doubled, based on bpm math, were doubled, but nothing in say the 125-130 range for example. My guess is the picker in rekordbox 5 is not based on the same algorithm as inside of the XDJ-1000's since they are old.
Also, it happened to many, but not all tracks. Happy to do more testing as well.
Can you try re-analysing that track and export it again?
Which firmware version is running on that XDJ?
First was 1.05, then I updated firmware to 1.12 and that is where the screenshot came from.
I will use a new usb stick with a re-analyzed set of songs tonight and test it.
Check this out too. Some songs at 70/71 bpm from the song sorter at the bottom are showing as double up at the top preview player. 

I tried playing with the other BPM ranges. My hunch is that the XDJ-1000 responds to the same algorithm as the 70-180 formula and auto-analyzes songs based on that in the deck, even though i used the filter for 68-135 when scanning.
How was this testing?
Engineers are investigating the cause - thanks for your patience.
Great, thanks Pulse! You are the man
Update coming this week with a fix! :D
I'm having this trouble with my XDJ-RR (v1.0.3).
Was the fix ever implemented?
