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

Post

2 followers Follow
0
Avatar

Waveform drift offset with RekordBox connected to XDJ-RX2 (Mac)

Hi. 

This weekend when I was DJing I discovered something strange (a bug?) when I connected RekordBox to my XDJ-RX2.

The Waveform/beatgrid was no longer in sync/drifting off in the XDJ-RX2 display when RekordBox was connected, but works fine with the same songs and settings when played from USB.

I have put together a short video showing the problem/error: https://www.youtube.com/watch?v=kuMi_AbpBac 

One can of course beatmatch just by listening, but that is not an excuse for not fixing unintended functionality. In my opinion, it seems like this is a bug since it works fine when playing from USB.

There is a possibility that I have missed a setting in the RekordBox settings that fixes this, but after having researched the problem and read multiple forum posts here, it seems like multiple users have experienced this problem.

I have also tried to enable DVS mode and "Waveform display", but without luck. (Is this setting only working if you have a RekordBox subscription, maybe?):


Issue is similar to:
- https://forums.pioneerdj.com/hc/en-us/community/posts/115009775786-Waves-drift-even-they-are-beat-matched-in-exact-sound-and-BPM-counter
- https://forums.pioneerdj.com/hc/en-us/community/posts/203112389--SOLVED-XDJ-RX-Waveform-not-adjusted-to-speed-of-track 

This answer https://forums.pioneerdj.com/hc/en-us/community/posts/115009775786/comments/115004413026 explains it fine given that DVS Waveform display is disabled, but is not applicable to this issue since it works fine when exported to USB, using the same songs and settings. 

I have researched this for a few days now, and noticed the responses to the multiple people reporting this problem.

I struggle to see how this is supposed to be intended functionality as it does not not occur when playing from USB, and only happens when playing from RekordBox Performance Mode when connected to XDJ-RX(2) with MIDI as input. See video for details. 

The argument that this "will not work with CDJs anyway" is also not viable and just besides the point of solving the actual problem, as one can clearly see the current player bars sync to the master player bars as seen in this image:


Any help on fixing this issue is highly appreciated. I will update this post if I find a solution to this, as I also know other people who are affected by this problem. 

Nicolai Prebensen

Post is closed for comments.

6 comments

0
Avatar

I suspect that there is a setting that is not being synced correctly when RekordBox is connected to the XDJ-RX2 unit as opposed to when using the internal XDJ-RX2 settings when using USB. 

Nicolai Prebensen 0 votes
Comment actions Permalink
0
Avatar

sadly this is a well known bug (since day one of rx2 release) that hasn't been fixed over all the years the rx2 is on the market. :-( the only answer you will probably get is that the cpu of the rx2 is somehow not that fast. its not related to mac it happens also on windows when using the rx2 in hid/performance mode.

Daniel Ventura 0 votes
Comment actions Permalink
0
Avatar
@Daniel Ventura

Thank you for providing some input on this issue. 

I have seen this response as well, but for me that does not make any sense. If it was a problem due to the CPU on the XDJ-RX2 unit being too slow then the same problem should have happened with USB as well, but it does not.

I see no logical reason as to why a different input should require more processing (CPU) power than the other. More so an I/O error if anything, or simply some settings not being synchronized correctly due to a bug in software or firmware.

If the CPU for some weird reason actually is the issue, I truly wonder what part of the I/O connection between RekordBox and the unit itself is causing CPU issues.

For reference, the issue also exists on XDJ-RX, XDJ-XZ, and probably other units as well. 
Nicolai Prebensen 0 votes
Comment actions Permalink
0
Avatar

i had the rx2 from day 1 of release and sold it a year later because of this issue. i have the xz since day 1 of release and this issue don't exist there.

 

Daniel Ventura 0 votes
Comment actions Permalink
0
Avatar

Interesting. I spoke to an individual who had the same issue on his XZ.

Nicolai Prebensen 0 votes
Comment actions Permalink