Neural Mix performance issue with master tempo

NOTE: Please use the search function above before posting to avoid creating duplicate topics.

  • Device model (e.g. 2020 iPad Air 4th Gen):
    Tested with MacBook Pro with M1 Pro / 16 GB RAM, iPhone 13 Pro Max, iPad M2, iPad Pro M4 1TB, PC with i9940X & 64GB RAM
  • Version of operating system (e.g. macOS 14.4.1): iOS 17.5.1, MacOS 14.5, Windows 10 H2
  • Version of djay (e.g. 5.1.2): 5.2, first noticed with 5.0
  • Hardware/controllers used (e.g. Reloop Mixon 8 Pro): without controller, with FLX4, with Rane One

Summary of the issue:
Neural Mix lags if master tempo is enabled (and in use = pitch +/-).
Unmuting drums need approx. 1 beat to be heard again instead of being back immediately.

How to reproduce the issue:
Load 2 tracks.
Enable master tempo.
Change the tempo of both tracks, so that master tempo has something to do (eg. +/- x %).
Play both tracks.
Mute the drums with Neural Mix on one deck on beat 4 and unmute on next beat (usually beat 1).
Usually you should hear the drums again on beat 1, but you won’t.
The waveform will show that the drums are back, but you won’t hear them.
You hear them on the next beat (beat 2).

Currently this only works if you disable master tempo.
If master tempo is off and you try this it will work and Neural Mix won’t lag.

Hi @Saiboter, thanks for sharing the details about your setup and the issue. To help us to replicate this issue and troubleshoot it with you, can you please try to capture a video of the issue, upload it to your Google Drive/Dropbox, enable sharing permissions, then share a link to the video here? Thanks!

2 Likes

Here you go, the kick on beat 1 is missing, because of a lag:

With tempo fader on 0 % (it’s the same with master tempo off) you can hear the kick on beat 1 = no lag:

Thanks for the videos @Saiboter. This is super helpful and clearly illustrates the issue. I have forwarded this to the engineering team to see if they can reproduce the issue and offer any suggestions. I’ll report back here when I have news. Thanks!

1 Like

Any update on this? Will this be fixed anytime soon?
With this lag STEMs are not a usable feature on djay pro.
It’s like djing with a bluetooth speaker - you can’t do it and you don’t do it.

I just tested it with the new update 5.2.8.
The issue still exists.
It is not a problem with the performance as I tested it on an iPad Pro M4 with 16 GB RAM.

Hi @Saiboter, thanks for the follow up and sorry for the delayed reply. The dev team is still examining options for reducing latency when using Neural Mix and Keylock at the same time. Please understand that this is a complex challenge to solve. In the meantime, I recommend that you disable Keylock when using Neural Mix and low latency is required. I hope that helps!

Hello ,
5.2.9 didn’t resolve this problem?
You think it’s something that can be solved in the future ? Can tell that if this neural mix latency is finally solved, djay pro is the best dj software by far

Hi @GrumpyCat, thanks for the follow up. The team is still working on improving NM performance. I’ll share news when it’s available. Thanks again!

1 Like

For anyone curious about this:
We celebrate the first anniversary of this bug which still is not fixed.

1 Like

Exactly. And this issue isn’t limited to Neural Mix; it also affects beatjumps and, I suspect, scratching as well. Keylock makes many features laggy and unsuitable for anything that requires perfect timing. I even find it problematic for practicing. I have to admit, for that reason alone, I’m still using Rekordbox

Hello everyone, please try updating to djay 5.4. We’ve recently made some improvements in this area. Thanks!

  • Significantly improved key lock latency for scrubbing, beat jumps, and applying Neural Mix routed FX
1 Like

Thanks for the super fast reply, tested it yesterday but I have to say I notice only a light improvements, but I still can see difference between keylock on and off, maybe now the delay is 1/2 beat compare to 1 beat from the previous version. Do you think that a fresh install of djay could help me to see those improvements?

You’re welcome @SIMSU_84. Thanks for the follow up. A fresh install certainly wouldn’t hurt along with potentially freeing up some drive space on your device. I suggest that you backup your djay Media Library database and any custom MIDI mappings, then uninstall djay, reboot your device, and reinstall the latest version of djay. You can find the files above in the following locations:

  1. iOS: using the Files App, navigate to Locations->On My iPhone/iPad->djay->User Data
  2. macOS: https://help.algoriddim.com/hc/en-us/articles/360014912211-Where-does-djay-Pro-store-playlists-cue-points-and-other-data-on-my-Mac
  3. Windows: https://help.algoriddim.com/hc/en-us/articles/360014912131-Where-does-djay-Pro-store-cue-points-and-other-metadata
  4. Copy the files to a new location or external drive before uninstalling djay. After reinstallation, you can simply copy these files back to their original locations to maintain your Hot Cues, Saved Loops, My Collection Playlists, History and Queue.
1 Like

I can only speak for myself, but the issue I originally reported seems to be fixed now.

I just tested it on my iPhone 13 Pro Max and the lag is gone.

I’ll check it on my iPad and Mac later, but since both devices are more powerful than the iPhone, I don’t expect any issues there either.

1 Like

Excellent! Thanks for the follow up @Saiboter

Hi there, just a brief update on this topic: I double-checked the latency problem after a computer restart and fresh installation. 'm not sure if one of those things had any effect, but I can say that it works properly now, and the improvement over the old version is HUGE. Thanks a lot for your amazing work!

1 Like

Excellent! You’re welcome @SIMSU_84. Thanks for the follow up!

Hi all,
I retested the echo-out timing issue as described in this ticket as well.

And there is good news because it seems that the echo-out on the vocal stem is now perfectly in sync with the beat grid all the time. Even without the re-installing hassle.

Apparently, it was a tricky problem, but it looks like the technical team has solved it.

So, many thanks to them!

1 Like

Thanks for the feedback @DJ_Big_Blender