Official comment
Hi Leon,
I'm creating a support ticket for this issue and will report back with any replies I receive from the engineers. Thanks for your patience.
Comment actions
Post
Follow
CDJ 2000 Nexus issue: from extended loop to a Hot Cue
Major Failure:
https://www.youtube.com/watch?v=tZgnhlpUmt8
1. create a loop (e.g. 4 beat)
2. double (or extend) this loop (for example 8 beat)
3. press a Hot Cue
All with Quantize ON
Both of my players do the same thing: instead of playing from the Hot Cue directly, they play 1 instance of the original loop (the 4 beat; unquantized), then finally play from the Hot Cue.....
Please try and tell me if you encounter the same issues
Post is closed for comments.
Date
Votes
8 comments
Thanks, Mark. I have to add this information: The issue occurs when I press the Hot Cue button during the extended part of the loop. So when I go from a 4 beat loop to an 8 beat loop, between beat 5 and 9.
Comment actions
Our engineering team has successfully replicated this issue and are working on a fix. Thank you for your patience and understanding.
Comment actions
Thanks, Mark. It's great to see that Pioneer is still improving the NXS. I'm looking forward to the update
Comment actions
I'd like to confirm this with 1.71 on a CDJ-2000NXS2. However, the symptom is slightly different.
Exactly the same scenario and setup. It only happens between beats 5-9 of the extended loop (the part that was extended), but instead of first playing one pass of the original unextended loop, it IMMEDIATELY jumps (not quantized) to 4 beats after the actual hotcue.
If I hit the hotcue in the first part (unextended part) of the loop, it behaves as expected, jumping to the hotcue in a quantized way.
Also wanted to point out that if you hit the loop button and hold it down for a second (thereby creating an 8-beat loop), you can hit the hotcue anywhere in that loop and it will jump to the hotcue in a quantized way. It's only a 4-beat loop that gets extended, when you hit the hotcue button in the extended range.
Posting here because it was slightly different than on the 2000Nexus and wanted to make sure the engineers test it out on the Nexus 2 and make sure it's fixed there as well.
Comment actions
Hello Kiyan,
It's unfortunate that the NXS2 has a similar issue. Maybe it's wise to create a new post for the issue on the NXS2, so it get's Pioneer's attention.
Regards,
Leon
Comment actions
No solution yet?
I'm having exactly the same problem on both of my NXS2 players :(
Comment actions
Good news! Yesterday I found out (by coincidence) that new firmware for the NXS1 is available (1.43)! The release date is tomorrow, but you can already download it here: https://www.pioneerdj.com/en-us/support/software/cdj-2000nxs/#firmware-update
The release notes have not been officially published yet, but I found them here: https://pdj-ecom-cdn.azureedge.net/-/media/pioneerdj/downloads/firmwares/players/cdj-2000nxs/cdj-2000nxs-firmware-change-history-ver143-en.pdf
Although the release notes do not exactly describe the issue (maybe that is why they have not been published yet), it looks like it has been fixed (along with some other issues). I tried it and could not replicate the problem after the firmware update!
Comment actions