NOTE: Please use the search function above before posting to avoid creating duplicate topics.
- Device model (e.g. 2020 iPad Air 4th Gen): MacBook Pro i9 2019
- Version of operating system (e.g. macOS 14.4.1): Tahoe 26.1
- Version of djay (e.g. 5.1.2): 5.5.2
- Hardware/controllers used (e.g. Reloop Mixon 8 Pro): flx 10
- Hardware firmware version (e.g. 1.0.1): 1.14 latest for Mac
- Please consider sharing a short video or screenshots to help clarify your issue
A) SUMMARY OF ISSUE:
When pressing crush then followed by noise on sound colour fx there is a crackling popping noise.
B) DETAILED STEPS TO REPRODUCE:
Press crush then noise press crush then noise and repeat
C) EXPECTED RESULTS:
Should be able to press crush effect and noise and not hear cracking or popping
D) ACTUAL RESULTS:
Crackling and popping sound
@Slak_Jaw done. Also pressing space and noise also gives some interference.
Hi @Dysfunk_DJ, thanks for the details about the issue and your setup - this is very helpful. Is this a new issue since updating to 5.5.2 and/or macOS 26.1?
Really not sure mate I only noticed it yesterday. Hopefully engineer team can replicate it. Doesn’t happen on iOS or Rekordbox so not hardware issue.
Thanks @Dysfunk_DJ, there seems to be an issue with the video you uploaded. Can you please trying uploading it again? Thanks!
Done my friend. Thank you
1 Like
Thanks @Dysfunk_DJ, I can view it now.
Excellent. Please let me know what engineers say.
1 Like
Hi @Dysfunk_DJ, our team was able to reproduce this and they’re investigating further.
Excellent. Looking forward to a resolution. Hopefully will be a quick fix.
Hi @Slak_Jaw is there any update on this bug? I checked with new M5 MacBook and bug remains with M chips also. I know it’s Christmas period so not expecting to be fixed until new year but was wondering if engineers have found the source of issue.
Hi @Dysfunk_DJ, I don’t have any updates from engineering, but I will check in again with them after the holidays. Thanks!
Thank you @Slak_Jaw much appreciated
You’re welcome @Dysfunk_DJ
Hi @Dysfunk_DJ, engineering has identified the issue and is working on a fix which should be included in an upcoming update (likely 5.6.3). Thanks!