Quantize of Hot cues not working well

I don’t want to be a dink about this, but this kind of thing has been an ongoing problem with this app ever since I started using it a couple of years ago. When using serato , tractor and engine prime, I never had any issues like this. It would be great if this was resolved once and for all. I will admit that those apps had their own issues. That’s why I moved away from them. And I’m still using this app so it must have a lot of other advantages.

1 Like

Hi @Nubium, sorry to hear you’re still experiencing this issue. Thanks for the feedback. I will let the team know.

Just bumping this. It’s definitely still an issue. I’m on the latest version of djay.

I think this got broken in v5.5 again.
Can somebody confirm, or it’s my laptop that’s buggy?

I was about to post this over a week ago but got towed away by other multiple performance issues I am having.

Hi @Austinjacobm94 I agree with you there. What mac/macOS are you using?
Last evenning I had a 3 hour set and all was fine in the first 1-2hours, but the final hour was hell with djay v5.5
Mac 2019 intel i7 16G RAM with Hercules T7 connected with DJTT Chroma USBC-USBB cable.
Hot Cue lag was massive. Cueing a song was mostly off due to the lag. Turning crossfader effects on actually made the audio to begin glitching too

Hi @Austinjacobm94, can you please elaborate and share a short video to clarify what your issue is?

Hi @Armigo, thanks for the info. Can you please share are short video to illustrate? Thanks!

I’ve shared a video and a description on August 12th. It’s the same problem.

1 Like

Got it. Thanks @Austinjacobm94

1 Like

Hi everyone, I’m a bit late to this topic but has some progress made to make available previous beat quantize like Traktor? Doesn’t have to be te standard, it should be an option so that we can choose the behaviour. This thing and the automatic cue on the first downbeat are the only issues I feel coming from Traktor, please listen to us Traktor refugees and give us a new home :folded_hands:t2:

Thanks for the additional input @Franz_Navas. We don’t have any news to share regarding this at the moment.