Macbook Pro USB to DJM 900 NXS - Cuts to buzzing sound

I'm running El Capitan and have the latest drivers for the DJM 900. When running USB audio to the 900, it is occasionally cutting out to a loud buzzing sound. To make it stop I have to disconnect and reconnect the USB cable.

No issues with other audio out from this Mac. Seems be an issue only with the 900.

This only started since I upgraded to El Capitan last week.

Is anyone else having this issue? Any way to fix this?

jake.barry 30. Dezember 2015 22:06

Offizieller Kommentar

Things to check...

current drivers
latest firmware
change the USB cable
adjust the latency (buffer) of the audio device

Pulse 4. Januar 2016 21:22

Post ist für Kommentare geschlossen.

Datum Stimmen

9 Kommentare

What audio program are you using?

Jay 31. Dezember 2015 04:31 0 Stimmen

Same to me. Using with Traktor Pro 2.10.10.15. I also installed DJM 900 NXS 1.4.1 drivers

Andrea Torre 1. Januar 2016 17:55 0 Stimmen

I have a very similar issue.

When I use the DJM-900nxs as soundcard Traktor has serious issues such as choppy and garbled audio, it also kinda changes pitch very fast.

In my case is completely unstable, I cannot use Traktor with the DJM-900nxs at all. I had to switch to my NI A6 which worked fine.

I am on macbookpro. Running latest El Capitan OS up to date with every update suggested from the App store. Latest Driver from pioneer (new DJM Utility)

I've used this same computer and mixer together in the past lots of times, this problem is new to known working hardware.

Jorge Molina 2. Januar 2016 18:55 0 Stimmen

To the question of what program, it has happened to me so far only with iTunes and SoundCloud through Safari. I have not yet had any issues with Traktor when playing through the DMJ as the sound card.

jake.barry 4. Januar 2016 03:38 0 Stimmen

Not even any digital click?

Andrea Torre 4. Januar 2016 15:07 0 Stimmen

Drivers are current, firmware i have to check, i changed usb cable but issue was still on. Have i got to set more or less latency?

Andrea Torre 5. Januar 2016 11:23 0 Stimmen

I double checked on firmware. Happens I was still on 1.30 upgraded to 1.310 and problem is now solved.

Jorge Molina 6. Januar 2016 03:13 0 Stimmen

@Jorge > Glad to hear it! Thanks for writing back.

Pulse 6. Januar 2016 22:09 0 Stimmen