Have a feature request or suggestion? Post your idea here!

Post

4 Follower Folgen
0
Avatar

[CLOSED] Track BPM not accurate on CDJ

Hi,

I analyzed a track using Rekordbox and the bpm readout is inaccurate on the CDJ-850. To make sure it wasn't the USB I re-analyzed it again in Rekordbox, deleted and re-loaded the track onto the USB. Same issue. All of my software/firmware is up to date. 

abk5074

Post ist für Kommentare geschlossen.

24 Kommentare

0
Avatar

What does rekordbox say the BPM is and what does the CDJ say?

Gavin 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Rekordbox itself analyzed the track at 134 bpm. The CDJ reads 135 at bassline. The track is most definitely 134 bpm. 

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Yes it was analyzed at exactly 134 bpm. The CDJ reads it at 135.

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

@Alex > I'm going to speak with a member of the dev team tomorrow and ask him what he thinks.

Gavin 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Cdj 350 does the same ... I can read lets say 140 bpm on my CDJ2000 and a few songs on the CDJ350 will run +1 bpm higher

D.j. Cosmic Sunrise 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Update:

Tried the track out on a CDJ-900 and it read it perfectly. So this pretty much definitively points to a bug in the CDJ-850 not in rekordbox. Still looking forward to more information on this. Thanks

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Any word on this? Its been over a month since I raised this issue.

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Does the track actually play back at 135 or is it just the display?

Pulse 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

It's analyzed in Rekordbox at 134. Plays on 900's at 134. Displays at 135 on the CDJ 850s. It is without a doubt an issue with the player. 

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

i also have an incorrect bpm when i'm using my cd's, i'm not working woth rekordbox 

is this normal or is there gonna be an update for this?

 

indy erens 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

It plays at 134 on the player. But still shows 135 on both CDJ 850s.

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

@Alex > I'm not after forgetting about you - I'm awaiting further information from the team.

Gavin 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

I appreciate the update Gavin. Please let me know ASAP.

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

@Alex > I hope you don't think I'm asking mundane questions for the pleasure of it but does your USB contain rekordbox-exported data ONLY or does it contain the original audio files, which you then imported to rekordbox and re-exported to the USB stick?

Have you updated to the latest version of rekordbox which was released this week? How many tracks does this happen with?

Gavin 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Gavin, I have not updated my rekordbox past 2.0.7. Is there a newer version that came out this week? If so where is it.

The usb only contains rekordbox exported data. I drag my files from iTunes over to Rekordbox for analyzation and then export my tracks from rekordbox onto my usb stick. This happens with alot of tracks infrequently where the player will read the wrong bpm on the display but play at a different speed. This is easily fixed (although extremely tedious and not practical if gigging) by going back to my main playlist and reloading the track on the player.

This track however is the only one that has never read correctly on my player despite having been analyzed at the correct bpm in rekordbox, and exported as such. I have tried deleting and reloading the track from rekordbox which didn't fix the issue which makes me believe there is a bug in the player itself since it fails to recognize the rekordbox data on a consistent but infrequent basis with other tracks, and also this one continuously.

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Thank you Gavin, but that did not solve my issue. Wondering if you might have some insight from the Engineers?

abk5074 0 Stimmen
Aktionen für Kommentare Permalink
0
Avatar

Does it matter what the "team" said? It sounds to me like it's just a tiny glitch in a display that doesn't affect the audio output.

Pulse 0 Stimmen
Aktionen für Kommentare Permalink