Hi everyone.
I'm at a point where i'm pretty much about to sell off my whole set up unless this can be resolved, so any ideas would be appreciated.
I have two CDJ 900's, and a DJM-750.
Using my Rekordbox analysed music, I can beatmatch two tunes that are of the same BPM quite successfully, its when I match tunes with different BPM's that I have the problem. Using the tempo slider, I adjust the bpm to match a tune say 2/3 bpm's higher, when I had my Pioneer 350 set up, this would work fine, and the two songs would beatmatch just fine and stay in sync with each other . Since I got my 900's, after about 3 weeks of having them, I noticed that whenever I use the tempo slider to alter the BPM, after about 15 seconds, even though the display says they are the same BPM, the right hand side deck will slip out of time and will require speeding up using the jog wheel. It will slowly get more and more out of sync as time elapses, I have tried everything I can think of:
I analyse my music in Normal Mode, and I have done this over and over again. NOT DYNAMIC MODE.
I've swapped the decks around and it still seems to be the right hand side deck, this makes me think that its the music, not the actual decks (hopefully).
I tried the music on a friends identical set up, and the same thing was happening which also gives me the impression its the Rekordbox analysed data.
The firmware is fully up to date.
Anyone ever had this problem before?
I'm all out of ideas. HELP
Post is closed for comments.
From your description it seems that the bpm value given by rb is wrong. Does it happen regularly with all tracks or only with a few ones?
If it's only some tracks you can check them again in rb with the metronome and see if the bpm is really correct.
Hi
It's with all the tracks, I basically can't mix two tunes with different BPM values, I can mix together songs with the same value, but whenever I have to use the the tempo slider, the right hand side deck will usually be slower than the left. I have to speed it up using the jog wheel. It will beatmatch fine but after approximately 15 seconds, it will go more and more out of sync. Ive checked the grid's in RB, some of them are off but most of them are fine, but that shouldn't really affect the problem I'm having id have thought?
The same thing happened when I played on my mates identical set up, so Im pretty sure it isn't the decks themselves, it has to be the data...
Really strange and puzzling if it happens on all tracks.
When grids are off, it can be for two reasons, either the grid is simply detected and put at the wrong phase or the grid is off phase because the detected bpm is wrong. The first case is quite common with rekordbox but this doesn't have impact on the manual beatmatching, while the second case is less frequent but it still happens that rekordbox detects a wrong bpm.
Having a grid mismatched with the actual beats in second half of the track is usually a symptom of a wrong bpm detection: at the beginning the grid is aligned and then later it will go away because it's not at the correct speed.
I never had very good results with the bpm and grid analysis of rekordbox 2, I also tried rekordbox 3 that is a bit better but that too is still poor compared to other software. With rekordbox I had to correct manually grid and bpm on around 10-15% of my tracks so I abandoned it and I do my analysis in Traktor then I port my data over to rb to upload it to the USB sticks.
My advice for you would be to check manually each track. Turn on the metronome and check the following (supposing that you are analyzing modern electronic music with a steady computer generated beat, not music played by human drummers):
If the bpm is not a round value (for instance 125.00 bpm) be wary, most likely it's wrong
line up precisely the beatgrid at the beginning of the track if it's not aligned. it must be lined up both visually on the monitor and in your ears the tick of the metronome must be in sync with the beats.
listen to the track in the middle and at the end: is the metronome still in sync? if not then the bpm is wrong, even if it is a round value it can still be wrong
if the grid is not in sync at the end of the track then you need to correct the bpm (increase it if the grid comes after the beat, reduce it if the grid comes before the beat). After correction restart from point 2 and repeat as many time as necessary.
Other test that you can do is to use different versions of rekordbox (version 3 is a bit better in the analysis).
Is this not a normal thing? I mean even if the tracks are analyzed perfectly, they will never stay in time forever. The BPM display only goes down to two decimal places, if a third decimal place was shown it may show where the difference lies, hence why the tracks will drift out over time.
I have been using 2000's for about 3 years now and I would never expect to move the pitch slider to the right place to match the BPM's and be able to hit play and make no adjustments during mixing. Is that not just normal dj'ing?
i have 2000nxs and you always have to make some the adjustments in the beginning, than after beatmatching rarely some minimal changes. But when you analysed your tracks in rekordbox, your bpm counter has to be still... ;)
I'll look into it, but yes some adjustment is normal when matching tracks with CDJs.
In my experience (cdj 2000 nexus, music analyzed with traktor + keyfinder, checked against metronome after analysis and uploaded on usb devices with rb, mostly modern electronic music with steady computer-generated beat), the tracks stay perfectly in sync for a very long time almost always. I mean if I match them and listen after 2 minutes they are still matched. Maybe once every 20-30 times one track drifts slightly and I can here a small mismatch after one or two minutes. As for matching, I do not use the automatic sync function, I just set the bpm to the same value on both cdjs and then I line up the beats with the jogwheel.
What is described above in the original post is not normal, if a track goes out of sync within 15 seconds then something is wrong.
Something worth to look at is at what range you set the pitch on the cdj, if you pick a big range then the resolution of the pitch gets worse. My one is set at a small range, I can't remember now which one, maybe 8 or 6%, and I can change the pitch by 0.1 bpm on the bpm display and a little bit finer on the % display.
I checked and found out that I use my CDJ at 10% pitch range. I tried set it at 6% range and realized that you can move the fader quite a lot without changing the bpm, that is when you move the fader you will see that the bpm value does not change (because the display goes only to 0.1 bpm steps) but the actual bpm changes and you can see it on the % display, it will change of course less than 0.1 bpm but it will change.
In a nutshell, if you use a small pitch range you might be easily almost 0.1 bpm off and not realize it if you look only at the bpm value, so you probabily should look at this thing.
Yes Julia. You are 100% right. the 0,1 BPM step is 3 steps in %. So all the nudges is that the BPM is correct but the percent is not and you have to nudge between these three steps to find the ideal position and the track will stay in sync "forever" then. I am doing this always;)
Hi all,
I have exactly the same problem on my CDJ-900 Nexus.Cant find any solution for this.
The bpm is changing approx. every 5-6 seconds.
Any ideas what can be the problem?
I have the problem that when I play 2 diffrent tracks in rekordboxDJ with the same BPM. After Beatmatching and stopping one track the BPM of the new Master track is changing 0.1 BPM down.
For example:
Track 1 (120BPM) Track 2 (125BMP). I take Track 2 as Master and Sync Track 1 on 125BPM to beatmatch 1 and 2. If I stop Track 2 now, the BPM of Track 1 loses 0,1 BPM. So the BPM of the Track 1 is now 124.9 and no more 125 BPM.
Can somebody explain that?
Also with Mastertempo activated the problem still existis. Ok its just 0.1 BPM but its not the tempo I want.
I am having the same issue with the 2000 NXS2 CDJs, but I use Serato, and all my files were analyzed in serato. Can anyone explain this
@Ella > That would have nothing to do with the analysis in Serato - that information is not read by the CDJ.