Hello! It’s been a week since my last reply. I’m going to consider this topic completed for now so I can focus on others. However, please feel free to respond and we can definitely revisit this. Thanks!
Hi @echa0361, thanks for the follow up and additional information. Engineering has identified the issue and is working on a fix which should be included in an upcoming update (likely 5.6.8). Thanks!
Hi @turbopussy, please use search before creating new topics. I have merged your new topic with this existing one. Our engineering team is working on a fix which should be included in the 5.6.8 djay update. Thanks!
Ok sorry. But I thought it was a new issue. Didn’t imagine that you leave your users with such a major bug for such a popular controller… Any update when this will be fixed?
Fixes require changes to underlying code, that then needs to be tested and retested until it’s able to be signed off as working fully with no issues, and no knock on impacts to other devices etc.
This takes longer than a couple of weeks, and rightly so.
The same process applies, any changes made need to be tested. In fact id say bugs are far more important when it comes to testing as the original issue slipped through the net, so it needs to be 100% right before being corrected.
This is all pretty standard issue software release cycle behaviour, not just in DJ software world.
Hi again @turbopussy, as stated above, we do not have a release date for 5.6.8. When it’s ready for public release, I will let everyone know here. Thanks!