[NOTE: Please use the search function above before posting to avoid creating duplicate topics.
- Device model (e.g. 2020 iPad Air 4th Gen):
- Version of operating system (e.g. macOS 14.4.1):
- Version of djay (e.g. 5.1.2):
- Hardware/controllers used (e.g. Reloop Mixon 8 Pro):
Your question:](mailto:segundo.broggi@yahoo.com)
Device: 2022 MacBook Air M2
OS: Sequoia 15.2
Djay pro: 5.2.8
Hardware: Reloop Mixon 8 pro
Hi, when doing sets with my controller, everything goes great until the streamed online output starts having a crackling sound. I don’t hear it in my monitors, I am being informed by listeners.
After several times of this happening, today I turned off my controller and turned it back on again (without stopping the set) and the sound was fixed but it starts again shortly after ( maybe after 30/40 mins of playing).
Any thoughts of what can be going on?
All drivers are updated.
Thank you
Hi @Segundobroggi, thanks for the details about your setup and the issue.
- Do you have iCloud Sync enabled in the djay Settings>Advanced?
- Are you running any other applications in the background while DJing (iCloud backups, TimeMachine, anti-virus software, etc.)?
- Is your Mixon 8 connect to power with the supplied adapter or are you running off USB bus power from your Mac?
- Is your Mac connected to power using the original Apple charger?
- Are you using the supplied USB cable from Reloop or another high quality cable, ideally with dual ferrites on either end?
- What streaming service are you using?
- How exactly is your Mixon 8 connected to the sound system?
HI Thank you for responding. Answers below:
- iCloud Enabled
- None of the applications mentioned. Yes, Online Streaming and audacity for recording
- Power supply adapter
- Mac Connected to power with NOT apple charger
- Not original USB, and with adapter on laptop side for USBc
- Mixlr
- Monitor out put into home amped speakers
The strange thing is that sets start sounding great, the crackling happens around 40 mins in, just powering down controller and powering it up again (without stopping the set since it runs through laptop) and cracking sound disappears. around 40 more minutes into the set, it happens again, same fix fixes it.
Thank you again
You’re welcome @Segundobroggi, Thanks for the additional info.
- Try disabling iCloud Sync and retesting.
- Okay
- Okay
- Try to use your original Apple charger whenever possible.
- I highly recommend that you don’t use cheap USB Adapters. Instead get a proper, high quality USB-B to C cable like the ones made by DJ TechTools.
- What is Mixlr? Are you using Tidal, SoundCloud, Beatport, etc? Or are you using local music stored on your internal drive.
- What kind of cables exactly? Cheap RCAs?
- will try
- ok
3)ok
- understood
5)understood
- Mixlr is how I broadcast/stream on line. Music Source is Tidal/Beatport/SoundCloud/My Library
- I have better RCAs than the ones I am using, these are not the cheapest one though.
Any thoughts on why it starts ok and then start crackling?
Any thoughts on why power down controller (Mixon * in this case) and power up again fixes it?
Thanks
Thanks @Segundobroggi. There’s a known performance issue with iCloud that has affected a small number of macOS users so I suspect this is the case. If turning iCloud off solves it then I can share a more permanent repair process with you later.
ok, I am in Los Angeles so due to time I will test tomorrow. iCloud Sync is off already.
I appreciate your help and support.
I’ll reach back out with update
Hi Again. I had the chance to try again with iCloud Sync turned off and teh sms problem persist. I was able to track the minute by minute and it I sat exactly 40mins that the crackling sound starts. It continues until I power off, and then on, the controller and works well again for another 40 minutes.
When it works well, it works fantastic.
Thoughts?
Thanks for the update @Segundobroggi. In this case, I would try the following. I’m guessing since you are using Mixlr and Audacity you are creating an Aggregate Audio Device in macOS. While aggregating audio devices usually works fine, some combinations of audio devices can be unreliable e.g. if they don’t support the same sample rates or if their clocks cannot be brought in sync.
That being said you can try adjusting the settings in the “Audio MIDI Setup” system app to see if that helps:
- While djay is running and configured with an aggregate device, select the “Aggregate-Audio-Device” device in the “Audio Devices” window of Audio MIDI Setup.
- Try disabling “Drift Correction” for one or both devices that are being aggregated.
- Try adjusting the sample rate of the aggregate device.
- Try changing the “clock source” of the aggregate device.
If that doesn’t solve your issue, then I recommend you disable Mixlr/Audacity and retest without using an aggregate audio device setup.
I hope that helps!
Hi there, thank you again for all your support.
1st, I am not that savvy with technology, so when I read these last suggestions I was a little overwhelmed.
I tried to follow your steps, had to do some research until I found the MIDI Audio Settings, and a little more until I realized I had to had the controller connected to be able to change those settings. Through out the research, I found that using “BlackHole 2ch”, which I do to split audio that goes online an audio that goes tom y monitors, presented similar crackling sound and that that sound could appear several minutes into the set. A further search on solving that issue lead me to EXACTLY your steps.
I just played for over 60 minutes and the crackling sound did not appear. I just played long tracks to ge to those minutes because I wa snot going to do a real set at 7am when I tried it, ha.
I found that SAMPLE RATE was the same in all devices ( 48k)
I am not sure if “DriftCorrection” made a difference.
I think that changing the Clock Source on the Aggregate device is what did it.
This wknd I’ll do a proper set and report back with actual feedback from online listeners.
Thank you so much for your support.
1 Like
Excellent! You’re welcome @Segundobroggi. I’m glad we got it all sorted out. Thanks for the detailed reply as this will likely be helpful to others that potentially encounter the same issue.
I’ve also changed the title of this topic to describe the issue more clearly.
1 Like