Maybe deactivate Quantization
Comment actions
Post
Follow
XDJ R1 - Random problem when setting cuepoints
Hello!
I'm having a very weird Problem on my Pioneer XDj R1.
When I want to set normal cuepoints while mixing, it randomly happens that it doesn't get set where I intended it to be, but moved a bit.
Example: I want to set a Cuepoint at 22:08, but when I "lock it in" it hops to 22:29, and I can't do anything to fix it. Only solution would be a total restart of the System and hope that it works afterwards.
As said, this is completely random, it could happen on the same song for 3 sessions, and doesn't happen on the 4th.
There are days (sessions), where the issue seems to not exist, but sometimes I have it on literally every tune.
Is this a known issue or similar? Because this is going to drive my beyond crazy...
Additional Information:
- Latest Firmware (1.13)
- I play my music from my USB Stick only. Exported from Rekordbox (tried v 3.2 and the latest 5.0.2, also with a brand new USB Stick)
- Music files are 90% original ones bought on Beatport
- I play my music from my USB Stick only. Exported from Rekordbox (tried v 3.2 and the latest 5.0.2, also with a brand new USB Stick)
- Music files are 90% original ones bought on Beatport
Do you guys have any idea how I could solve this issue?
Thanks and have a nice day!
Post is closed for comments.
Date
Votes
6 comments
@David > Are you pressing play/pause to stop the playback before you create the cue?
Comment actions
@George: That's an interesting idea, I will try that!
@Pulse: Yes. As far as I know thats the only way to create cuepoints on the fly, or am I missing something? (except Hot Cues on the mixer/in recordbox)
Comment actions
Quantization wouldn't throw it off by 21 seconds.
Yes; if you press play/pause, or hold your hand on the jog to stop playback, pressing the cue button will set the main cue to that location. Where it might be a problem is if you wound the track forward with the jog and tried to set it, but it wasn't in pause mode - it might jump back to the original cue.
Comment actions
@Pulse: It's not the whole 21 seconds, it's 21 milliseconds in this example.
Like if I want to set it on 22:08, it hops to 22:29 (just a random example)
I already had two sessions without quantisize activated and had no bug so far.
Maybe this is really the solution? But still, is there any explanation to this behaviour?
Comment actions
Ah - that's my bad, I'm used to HH:MM:SS.ms notation. ;)
Yeah, if it was only off by 21ms, it could certainly have been due to quantization.
Comment actions