Is it possible for you to look into the log that must have been produced during the live set I performed last Saturday night (January 18, 2025)? The set started at 19:46 and included 77 songs.
During that set, again I encountered several issues, such as stuttering, stopping, and tracks that wouldn’t start.
I’m not sure exactly what is recorded in the log, but I hope it contains some clues.
I also just sent an email directly from DJay app on MacBook to support.
Of course, looking into the log refers to this issue as well as another one that you might already be aware of:
I believe I may have found a breakthrough after retesting this issue thoroughly. I tested it with a few different tracks, as shown in the video and this all points in the same direction!!
(Additionally to the video, I tested it with Neural Mix activated on Deck 2 and normal settings on Deck 1. The stuttering and freezing occurred on Deck 2 but not on Deck 1, making the test quite convincing. Also, when assigning an effect to one of the Neural Mix stems, the problem appears as well.)
So, it appears to be directly related to using Neural Mix (which I have mapped to the EQ knobs). This makes sense to me a lot because I use Neural Mix quite often, and since I’ve been using it more and more, the issues have also increased.
Even the issues arise in cases where the Neural Mix knobs were still “active” because of the previous track—as you obviously don’t always reset the knobs before loading a new track.
This root cause, involving Neural Mix probably together with something like caching, could possibly also be connected to that other persistent issue I experience—tracks that won’t start, stutter, or fail during live sessions.
I think I’ve now pointed you in the right direction to resolve this. Given that Neural Mix is one of DJay’s key USPs, I strongly believe this should be fixed as a priority. Users rely on this feature, and it should work flawlessly in all situations.
I hope for your continued support in investigating this issue. Since I haven’t heard anything for 3 days, and I’m eagerly awaiting a response to my latest findings regarding Neural Mix messing up the stability.
Last time, you mentioned, “we have yet to reproduce the issue in question.” With the additional testing and evidence I’ve provided, I believe this should now significantly aid in pinpointing the root cause.
As this issue is severely impacting live performances, I kindly request an update at your earliest convenience. Additionally, I plan to start a new thread to see if other users have encountered similar problems, which might provide further insights for your analysis.
Following up on my earlier post, I’ve even been able to narrow down the issue a bit more.
The stuttering and freezing seem to occur only when I use the Skip Forward or Skip Backward buttons on my Reloop Mixon 8 Pro controller. If I scroll through the waveform manually with cursor (forwards or backwards) using the DJay Pro software, the problem doesn’t happen—even when the controller is connected, and the audio runs through it.
I’m curious if anyone else using a Controller (Mixon 8 Pro or other) has experienced this as well.
Have you noticed the same behavior when using the Skip buttons?
Any additional insights would be greatly appreciated!
ATN I am on the current version of DJay (5.2.8.)
==
Device: MacBook Pro (16", 2019)
Processor: 2,6 GHz 6-Core Intel Core i7
Operating system: Apple OS / Sanoma 14.7.2.
Memory: 32 Gb
Djay version: Djay Pro 5.2.8
Hardware/controllers used: Reloop Mixon 8 Pro
(Firmware up-to-date: 5339)
I’m reaching out to see if others like you have experienced similar issues with stuttering, freezing, or tracks not starting properly after using Neural Mix in Algoriddim DJay.
I will show it to you. In my case, I have toggled Neural Mix to the EQ knobs. but I’m not sure if this is related, but the issues also persist if the Neural Mix settings aren’t fully reset before loading a new track.
You can see for yourself(*) in this video the problems I encounter. Like you can see there also seems to be a 100% correlation between these problems and quickly scrolling through a track.
(*) E.g. on5m02, 5m32 and 8 min in the video
If you seem to have this problem as well, could you please share your experience?
Specifically:
What hardware are you using?
Does the issue occur only after you ‘activated’ Neural Mix in a track or also without?
Have you noticed any patterns or specific triggers?
Your feedback would be incredibly helpful, both for troubleshooting and for providing the developers with more insights to resolve this.
Hey @DJ_Big_Blender
I tried this. It works fine.
I am using no 3rd party hardware.
Maybe process of elimination?
Disconnect your hardware and try again.
Also, when in doubt, reboot your Mac.
Hey @DJ_Big_Blender
I only use the Mac for iTunes to sync with my devices. I do not use djay on the Mac at all. I’m a non-pro so I really don’t need the map at all. I just need it to sync.
Following up on my earlier post, I’ve been able to narrow down the issue a bit more.
The stuttering and freezing seem to occur only when I use the Skip Forward or Skip Backward buttons on my Reloop Mixon 8 Pro controller. If I scroll through the waveform manually with cursor (forwards or backwards) using the DJay Pro software, the problem doesn’t happen—even when the controller is connected, and the audio runs through it.
I’m curious if anyone else using a Controller (Mixon 8 Pro or other) has experienced this as well.
Have you noticed the same behavior when using the Skip buttons?
Any additional insights would be greatly appreciated!
Thank you for your patience with this matter and for the additional information. We have some good progress news.
Our teams believe they have pinpointed the issue, but we’d like to ask you one more thing.
In djay, the skip controls behave slightly differently than waveform scrubbing. It would be interesting to know if you can reproduce this issue with the skip / beat jump controls in the app without a controller.
Thanks for the update and for looking into this issue!
I tested it as you suggested, using the skip / beat jump controls directly in the app without a controller, and I’m seeing the same problems occur. However, when I scroll through the song by clicking randomly on the waveform of a playing track, it goes smoothly without any hiccups.
So I wonder is this good of bad news for your findings?
Thank you for your patience regarding this issue, we appreciate the additional information as well!
While I can’t provide a timeline, I can share that our teams are actively working on this. Your issue has not been forgotten, as it is still in active resolution.
I will reach back out when more information is available.
Thanks for the update. I appreciate that the issue is actively being worked on. However, could you at least provide insight into whether the team has identified a concrete cause and is working on a fix, or if this is still in the investigation phase?
I understand that Algoriddim avoids committing to timelines, but as paying customers—many of us using this software professionally—we expect and need at least some more transparency. This malfunction has caused real issues in my work, and without any indication of a resolution timeframe, it’s impossible to plan accordingly.
To put it in perspective: if my customers ask me whether I can deliver something, I also need to inform them whether it will take a week of month or a year. Right now, I have no idea if or when I will be able to use stems as intended again. Could you at least give a rough idea of where things stand? Even something like “we aim to…” would help.
Also, I previously asked whether my findings—where the issue occurs with skip/beat jump but not with waveform scrubbing—are considered good or bad news for your investigation. Could you share any thoughts on that?
I completely understand how frustrating this has been, especially since you’re using djay in a professional setting. We truly appreciate your patience and your detailed input—it has been valuable in helping our team investigate the issue further.
At this stage, our team is still in the investigation phase, as the root cause is more complex than initially anticipated. While I can’t provide a timeline, I can assure you that the issue is being actively worked on. We recognize that transparency is important, and while we don’t want to make commitments we can’t guarantee, I’ll do my best to share meaningful updates as they become available.
Regarding your specific findings (where the issue occurs with skip/beat jump but not waveform scrubbing) our team has taken note of this. It does help narrow down potential factors, and I’ll continue to share your observations with our engineers as they refine their approach.
I completely get that this lack of a concrete timeframe makes planning difficult for you. Please know that we’re taking this seriously, and as soon as we have more substantial information, I’ll be sure to update you here. Thanks again for your patience and for working with us to improve djay.
Thank you for your previous communications regarding the issues we have encountered. However, I must once again express my concern that this problem remains unresolved after all these weeks and, more importantly, the apparent inability of Algoriddim to address it promptly. The software increasingly seems to be turning into a Rube Goldberg machine to me; if issues cannot be resolved within a few weeks, it raises serious doubts about whether its complexity is still manageable.
I am not in a position to judge the work of the development team, nor do I intend to. I fully assume that they are doing their utmost to address these issues. That being said, the fact that these problems persist despite their efforts only reinforces my concern that the growing complexity of the software is making it increasingly difficult to maintain and troubleshoot effectively.
Critical problems—such as this one or other performance-related issues—should, in my opinion, be solvable by a team within a relatively short timeframe, especially since I have provided clear directions on where to pinpoint them. The fact that these issues have persisted for months is troubling and suggests that there may be deeper challenges in the development process.
As time goes by without progress, I am also increasingly concerned that this issue will be forgotten, overshadowed by new challenges and a decreasing attention span. This concern is reinforced by the fact that you are not sharing any insights, intermediate findings, or progress whatsoever, along with reading many cases on the forum where important issues seem to fade away without any follow-up from your side. Of course, users grow tired of having to repeatedly chase down solutions to reported issues, and eventually, they move on—whether still dissatisfied or, even worse, quietly leaving the Djay platform.
Now that this is off my chest, I would appreciate an update on the status as promised, as well as the next steps regarding this matter.
after retesting this issue thoroughly. I tested it with a few different tracks, as 
I think I’ve now pointed you in the right direction to resolve this. Given that Neural Mix is one of DJay’s key USPs, I strongly believe this should be fixed as a priority. Users rely on this feature, and it should work flawlessly in all situations.
You can see for yourself(*) 
