Hi @NathanielAlgo,
Could you give me a interim update on your latest findings and progress so that I know what to expect in terms of the timeline for the solution?
Hi @NathanielAlgo,
Could you give me a interim update on your latest findings and progress so that I know what to expect in terms of the timeline for the solution?
Hi @DJ_Big_Blender,
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.
Hi @NathanielAlgo,
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?
Hi @DJ_Big_Blender,
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.