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

投稿

5フォロワー フォローする
0
Avatar

SHIFT + BEAT JUMP = BIGGER JUMPS on XDJ-RX2

Currently on the XDJ-RX2, you can beat jump 1, 2, 4 or 8 beats (in both directions). It would be so helpful to be able to jump 16, 32 or more beats but this feature is currently missing. 

Since there are only 8 pads on the XDJ-RX2, pressing the shift key together with a beat jump pad could allow for the additional jump options without breaking the current functionality.

Shift could either provide 16, 32, 64 or 128 beat jumps or could change the jump distance from beats to bars, giving 1, 2, 4 or 8 bar jumps when shift is pressed.

Please consider this feature!

Marcus Mac Innes 回答済み

正式なコメント

Avatar

Sorry, the memory isn't large enough / fast enough to have those beat jump values stored internally.

Pulse
コメントアクション Permalink

投稿コメントは受け付けていません。

5件のコメント

1
Avatar

Shift could either provide 16, 32, 64 or 128 beat jumps or could change the jump distance from beats to bars, giving 1, 2, 4 or 8 bar jumps when shift is pressed.

 

I agree!

Alex Tozzo 1 票
コメントアクション Permalink
1
Avatar

Yes please Pioneer, make the upgrade to have 16/32 beatjump, same for the CDJ nexus2,  we miss the 32 beatjump. It's would be great for the House music.

 

Thank you.

Emmanuel Diaz 1 票
コメントアクション Permalink
0
Avatar

I'm confused - can't see how this is restricted by memory limitation? i.e. having the option to have larger beat jumps (or bar jumps) as suggested with Shift modifier.
Factors that would indicate it's possible via firmware enhancement :

  • You've got beat jump pads & a shift key
  • The beat jump presumably works off the beat grid and jumps ahead by the preset number of beats
  • A track is appropriately beatgridded so frame precision jumps in either direction aren't difficult to calculate, plus...
  • with needle lock deactivated – instant (awesome!!!) arbitrary jumps within a playing track are possible

Obviously don't expect you to amend the official position on this, but with above in mind this does seem rather puzzling that it's not a potential quick feature win, and would be warmly received :)

anotherpiouser 0 票
コメントアクション Permalink
0
Avatar

@anotherpiouser > Yes, it is a memory issue -- because in order for the unit to have the ability to jump immediately to 16 or 32 beats ahead (or back), it has to contain that audio within its buffer, and the ability to then rapidly buffer an additional 32 forward / back in case you press it again. For a simple example, let's take a 120BPM track...

16 beats would be 8 seconds, meaning 16 seconds total (combining 8s ahead and 8s behind the play position) would need to be buffered, with the ability to buffer an additional 8s nearly instantaneously should the DJ jump forward or back. Note that we don't need to buffer a full 16 seconds on a jump, as if we jump forward 16 beats, those 8s we just jumped were previously ahead of the play position, but are now behind the play position. It just takes some fancy memory management to shuffle that addressing around so it doesn't need to be loaded twice, but is still accessible in the right order. So the player would need the ability to buffer the maximum amount of audio needed after a jump (8s), and with the highest quality file supported by the RX2 being a WAV / AIFF at 24bit / 48kHz, the player needs to call up 2.25MB of audio instantaneously, while continuing to stream that song at 2304kbps. It's not just pulling the data from the USB drive at that speed, as I mentioned before - it has to process it as well. It's not just a matter of filling that memory buffer bucket. I know it doesn't sound like much, but this unit is a purpose-designed piece of DJ gear, not your computer running a CPU on a bus capable of handling massive amounts of data and flexible in its operation to perform different things a different times as needed.

Want to make that 32 or 64 beats? Just double or quadruple the numbers I've just posted (except the streaming rate, that's the same for the maximum quality audio). Don't forget, it has to support this on two decks, so double the capacity for the unit to perform these operations.

This is not an official statement, but if it were already possible, they would have included it. The fact they never did tells me that the hardware in the unit is simply not powerful enough to provide that kind of performance.

So yeah, it's a memory issue, and we'll close this topic now.

Pulse 0 票
コメントアクション Permalink