Neural Mix lag with TIDAL when BPM is adjusted

  • Device model IPad 9th gen and iPhone 14
  • Version of operating system iOS 18 on both
  • Version of djay * 5.2.5
  • Hardware/controllers used * Numark Mixtrack Platinum FX

Hi all, I notice that when I use neural mix on a song from tidal that has their bpm adjusted, there is a slight delay, as opposed to using unadjusted songs which is instant.

Is there any workaround for this. Occurs on both my iPad and iPhone. I’ve changed the Tidal quality to normal from High and still the same thing. I’ve also opened the neural mix on the waveforms as I heard this would help but still the same issue.

Hi @Abiodun237, try disabling Key Lock. This should reduce the overall latency.

Thank you. Is there no other way to resolve besides disabling key lock?

You’re welcome. Keylock and Neural Mix are computationally intensive functions, so using them both at the same time, especially on less powerful hardware, will result in some latency. In the djay Settings>Advanced>NEURAL MIX>Quality you could try a lower value to see if that helps.

You could also check out my personal tips for maximizing performance and stability on iOS:

Should it be possible to change the quality? In my case, this is only displayed without the option to change it. I don’t need that either, I just wanted to know.

Hmmm… I guess maybe this is only adjustable on Windows and maybe macOS.

I can’t say anything about Windows, but it can’t be set under MacOS either. Well, I don’t find that dramatic either, because if the quality and processing power are needed, then it’s for Neutral Mix, and I wouldn’t want to reduce that in particular.

1 Like

Many thanks. Removing key lock seems to have done the trick. Just out of curiosity, is there an iPad model that has the hardware to do both?

You’re welcome @Abiodun237. I don’t notice any latency with NM and Keylock on my iPad Pro M4 or my iPhone 15 Pro Max. Observed latency is one of those things that can be a bit subject though. Some people are more sensitive to it.

1 Like

This is a duplicate bug.
And yes, it still exists.