Just upgraded to firmware 1.30 and now (in standalone mode) when I have a loop active and hit the loop 1/2X or loop 2X button with quantize for the deck off, it also jumps back to the beginning of the loop. I don't think it did this on firmware 1.20? I'm also not sure why anyone would want it to; it sounds awful.
If quantize for the deck is on, it just halves or doubles the loop without messing with the current play position, as I expect it to.
This is normal operation for the loop across all hardware -- we've asked for them to change it previously (personally, I can't envision any scenario where that's useful), hopefully it's something we'll see change in future.
投稿コメントは受け付けていません。
Wow that’s a serious bug if confirmed and would say it all about Pioneers testing practices (or lack of) on new releases... this firmware was supposed to a bug with looping and quantize.
I won’t be upgrading to 1.30 until I know more so thanks for posting!
This has always been the case with the XDJ-1000 MK1 as well, I just assumed it was the same for all Pioneer players. It makes halving/doubling loops while Quantize is off unusable.
the 1/2x and 2x function are meant to be uses with quantize anyway. unless you are precise as metronome when pressing those buttons!
@djDYVE If used with the Loop In / Loop Out buttons, you're right. But there are many other ways to make a loop on the XDJ-RX2: long-pressing Loop In for a 4-beat loop, the Beat Loop mode with the pads, and a loop saved to a Hot Cue (aka Hot Loop). With the first two, yeah, without quantize it won't be aligned to the grid exactly, but since the loop is a whole number of beats it often doesn't matter.
I still can't imagine why anyone would actually want their loop to jump back to the beginning when they double / halve it.
The extend or reduce loop button should NEVER jump back to the beginning of the loop. This is a bug. Worse, a regression bug which means Pioneer (or their developers) don't have sufficient tests in place to catch side effects of code changes. Poor.
@Kenn Hamm I check with Performance Mode and it doesn't restart to the begining of the loop so it must be bug.
But then again, I don't know why people want to 1/2x or 2x a loop when not in Quantize. just turn on Quantize and the problem is solved.
Remembering to turn on quantize before extending or reducing the loop and then remembering to turn it off immediately after isn't something you want to have to do. I don't use sync or quantize and although I don't hit beats 100% of the time, I'm used to bending the pitch when needed to correct any mistakes.
The issue for me on this is not that there is a bug or a workaround, it's that the product is so flawed with bugs that should have been caught in QA. It's just really poor quality software when see this kind of bug creeping in (I was in software development for nearly 20 years so I know how to spot bad testing). I suspect the code base for these players is a complete mess and when it gets like that, developers have a serious problem when making any changes. Hence the lack of fre
...hence the lack of frequent firmware updates.
Still happens with firmware 1.31 :-(
@Pulse Thanks for clarifying... though I'm pretty sure it didn't happen with firmware 1.21 on the XDJ-RX2.
I'm still on 1.21.
If you could make a video or a detailed list of steps of reproduce, I can test it.
@Plangin
Sure, it's extremely easy.
On firmware 1.30, firmware 1.31, and apparently other Pioneer products, step 4 will jump back to the beginning of the loop. As I recall, on earlier firmware this didn't happen. It doesn't happen on the XDJ-RX2 with firmware 1.30 or 1.31 either if Quantize is on.
@Kenn Hamm
I tested it with 1.21:
Shrunk and expanded at beginning and in 2nd half of the loop. Jumps always back to the beginning.
So, Pulse is right.
@Plangin Thank you for testing. Guess I just didn't notice it before (maybe I always had Quantize on? The XDJ-RX2 is my first DJ system so I need all the help I can get to not mess up the timing, etc.)
You're welcome. Personally, I also see ne sense for this behavior. I do also hope, this will be changed.
This has been driving me CRAZY!!! SUCH A POOR BUG. Easily fixed though with quantize. Thanks.