Running into an issue with new DDJ-RX and Rekordbox DJ software. When I hit the Hot Cue to engage, about 2/3 of the time it will behave appropriately, but 1/3 of the time it will engage late, thus train-wrecking my incoming mix. I've tried tweaking the Quantize settings to no avail. I suspect the issue is with Rekordbox itself as:
I know it's not my timing. There's something awry here. I'm hoping this is a known bug that's being worked on. I can be patient for the fix, but if this is the status quo it will prove a deal breaker for an otherwise solid piece of software. I appreciate any help the community can provide in tracking this issue down. Cheers.
Todd Michael
It's to do with the quantization, and we've asked the engineers to allow it to quantize backwards as well. It may not be in the NEXT update, but they are aware of the issue and will have it included in the future.
Post is closed for comments.
Have you tried adjusting your buffer settings?
Mark, this isn't a buffer issue. I've posted about this too (a few times, in fact). I believe Pulse said the engineers are aware of the bug.
From my testing, it is because RB always rounds up to the next nearest quantize. So to be on time, you have to hit the hot cue is activated before. So in order for you to be "on time", you have to be early. It never rounds down, even if you're 0.0001ms later than a beat marker, Instead it'll round up an entire beat.
I switched to RB on launch day, and still have problems with this. Hopefully this is addressed in the next update.
Yep... known issue. Hopefully the NEXT release (4.1.3). Who uses hot cues anyway? In the meantime please work on your timing.... ;)
Or... just turn off the quantization!
Really appreciate all the helpful responses. Just reassuring to confirm "it's not just me." Have disabled Quantize until this is resolved. Just looked over 4.2.0, but don't see anything in the CHANGELOG on this topic unless it's part of "miscellaneous fixes." Anyone know if this is resolved? Guess I'll just install later and test. Cheers.
NO! Please wait on installing 4.2.0 - we've had a few users who have pretty significant issues with 4.2.0 and are recommending those users downgrade to 4.1.2 and wait until a fix is released.
Appreciate the heads up following the 4.2.0 update. I took your advice and forewent that upgrade. I see that 4.2.1 is out. Anyone able to confirm or disconfirm if this update is (1) safe and (2) finally addresses this bug? If not, I'll install and test over the weekend and post my results. Thanks.
4.2.1 is much more stable, so far no issues.
hesitant to download to find out they haven't fixed this yet.