Once in a while, when using my XDJ-RX2 with USB drives and not connected to a laptop with rekordbox, I discover I am unable to use the Delete and Memory Cue buttons on tracks to set new memory cue points or delete existing ones; the bug does not simply disappear when a new track is loaded, and will occur on both decks. The Cue/Loop Call arrow buttons still work properly to jump between memory cue points, so it's not like the memory cue function itself is completely nonfunctional. The issue often disappears when I disconnect and reconnect my USB drive, but there have been a few times when the problem did not immediately disappear and required another reconnect.
Unfortunately this issue occurs infrequently so I have not been able to determine what factors allow me to replicate the situation, and my tendency to only use the USB 1 port means I am unsure if the problem can occur on both ports.
Is this likely an issue with the RX2 firmware, the USB port, or the drive being used? Is there a setting I can verify in rekordbox that could affect how the drive is set up, or any other tests I should try to get the issue to come back?
投稿コメントは受け付けていません。
Do you have any other issues with the drive in the way of certain files being a problem? You can test through by determining if the issue happens on particular types of tracks and the same tracks. You could also try moving the files off the drive and reformatting it and then reloading to see if it occurs so you could take the drive off the list.
Are you running the newest version of rekordbox and firmware?
I have not experienced any issues with specific tracks, and the Memory Cue problem does indeed to occur with any track regardless of whether it's pulled from a search or a playlist. I will see if reformatting the drive and re-exporting everything can clear things up.
I apologize for forgetting to mention it in the original post, but the firmware and rekordbox are indeed the latest versions respectively.
Was the deck playing a song when you tried to use the call or delete?
The decks were not actively playing the loaded tracks when attempting to set or delete Memory Cues, as per my usual method of using those functions.