Hot Cue Delay

Hi all, I've been trying Rekordbox 4.01 with the Pioneer DDJ SX2, and for the most part am quite enjoying the new platform!

When using the hot cues in quantized mode I sometimes experience a delay. When it occurs, the delay puts the track a beat or so behind. I was wondering if there was any way to correct this action? I was expecting the hot cue to engage instantly the way it does in Serato DJ and Traktor.

I've also had the same issue when playing on CDJ 2000s. I'm wondering if it may have something to do with beat grids or I have it setup wrong in some way.

Any advice would be hugely appreciated!

Matthew Gibson 21. Oktober 2015 04:59 Beantwortet

Offizieller Kommentar

Yes, it's on the list to be corrected, but for the time being, you can lower the quantize value so it registers less than 1/1.

Pulse 27. November 2016 19:51

Post ist für Kommentare geschlossen.

Datum Stimmen

9 Kommentare

Yes this is the same problem I am having .... they should fix this.

The solution I have is a two step process (1) set the quantize value to 1 and (2) you must hit pad on the beat ... if you are slow ...result will be behind the beat.

This is not ideal, Pioneer and Rekordbox should fix this

Desmond Perry 21. Oktober 2015 16:02 0 Stimmen

same problem with controller
and also when i press the already set hotcue it takes around half a second before it gets there

Bera Polat 29. September 2016 11:04 0 Stimmen

Hello, i bought a Ddj-rb and i'm having the same problem as well.. its so anoying and i must say that im getting very frustrated with it. Every time i press a hot cue with quantize it gets delays and never match on the beat of the other deck that is playing.. Do you think pionner will solve that problem?

Soarez André 27. November 2016 07:09 0 Stimmen

Thanks for the reply Pulse. It's nice to see someone from Pioneer comment about this and I'm glad to know this is on the correction list.

Matthew Gibson 27. November 2016 20:31 0 Stimmen

I've noticed that pionner released an update , but i still have that quantize delay problem. Did you allready fix it?

Soarez André 8. Dezember 2016 13:36 0 Stimmen

No; the quantize is still a "quantize-forward" function, not "snap-to-nearest" function.

Pulse 9. Dezember 2016 19:04 0 Stimmen

ahh ok =) and that is a feature that will still be fixed?

Soarez André 9. Dezember 2016 19:39 0 Stimmen

We've requested it, the engineers are aware of it.

Pulse 9. Dezember 2016 19:39 0 Stimmen