Quantized beat effects on DJM900NXS2 drift out of time
Not sure why this is happening. If you use one of the 2 roll effects and put the parameter knob so that you can hear both the effected and non-effected sounds mixed together, you hear the roll drift out of time. This happens even when quantize is on.
Post is closed for comments.
Can't find help? Search our Support Site or alternatively, reach out to our Support agents
Yeah this happened on the DJM900NXS as well. I'm not sure how intelligent the 900NXS2 is but a nudge button like the RMX units is likely needed.
I asked the DJM engineers about this and they replied:
If you touch and turn the Time knob, even slightly, while controlling the Level depth with the knob just below the Time knob, Quantize will be disabled. This might be the cause of the roll drifting out of time.
If Quantize is on, you can see the Quantize button is lit red and [Quantize] is shown in the same small screen as BPM. When Quantize is on, the BPM of the effected and non-effected sounds are always matched.
Please check that the red Quantize LED and the letters Quantize on the screen when you have this issue.
Just checking in to see if you've had a chance to test the steps above?
Any status on this? This has been an issue for me since DAY1... and now I am finally getting the time to ask for help. I am having this same problem and I posted a youtube video.
Tested with DJM900NXS2 FX 4 BEAT ROLL vs CDJ3000 4 BEAT LOOP
I followed @pulse instructions and never touched the time knob. still drifts.
https://youtu.be/jjAJ4Imim2c
This is still an issue in the DJMA9. Quantize is on, time knob is never touched.
I'm talking specifically to the roll effect. Doing an 8 beat roll, then transferring to an unused channel and the roll loop is very quickly out of time.
If I nudge the source cdj so everything is back in time again, it drifts once again.
In fact, it's drifts even before reassigning it to a new channel. Just keeping it on the same channel the issue persists. Even if both tracks are the same BPM, at 0.00%
Is there a fix to this? Or even a workaround?
5 comments