Numark Mixtrack GO (Latest Firmware as far as i know - no new FW available on Numark’s website)
With USB audio routing enabled, both MIDI controls and audio output exhibit approximately 200–500 ms latency. Enabling Android Developer Options → Disable USB audio routing immediately eliminates both MIDI and audio latency. MIDI remains responsive because the Mixtrack continues to function as a MIDI controller, but audio is then routed through the S24 speaker and controller headphone cueing is unavailable. Tested direct USB-C connection, powered USB-C 3.1 hub, original Mixtrack USB-C cable and another known-good USB-C data cable with identical results.
Does djay Android currently use a fixed USB audio buffer for class-compliant controllers, and can you confirm whether the Mixtrack GO’s USB audio interface is known to have excessive latency on Android 16?
Hi @tripnot, welcome to the Community! Thanks for the detailed write-up — the cable and hub testing you’ve already done saves us a lot of back and forth.
On your first question: djay for Android configures audio automatically. Whether there’s a fixed internal buffer behind that on Android isn’t something our public documentation covers, so I’d rather put that to the team than guess at it.
On the Mixtrack GO specifically: it’s officially supported on Android, but I can’t point you to any confirmed issue with its USB audio interface on Android 16. Our support docs do note that USB audio support varies between Android devices and manufacturers.
Some quick things to check before I escalate this with engineering:
Thanks for the quick reply and sorry for the delayed reply on my behalf.
I tested both suggestions.
Battery optimization: djay was set to Unrestricted. I relaunched djay and retested, but there was no change in the latency.
Mono Output: I enabled Mono Output under Settings → Sound → Audio Output. There may be a very slight reduction in latency, but the difference is so small that I’m not confident it is a real change. The latency remains very significant (roughly 200–500 ms).
Unfortunately, I don’t have another supported controller with a built-in audio interface available for comparison.
The most reproducible finding remains the Android Developer Option “Disable USB audio routing”:
Disable USB audio routing OFF → Mixtrack GO USB audio active → approximately 200–500 ms latency affecting both MIDI controls and audio.
Disable USB audio routing ON → Mixtrack GO remains connected and MIDI works normally, but audio is routed to the S24’s internal speaker → MIDI and audio become essentially immediate.
I have also tested the Mixtrack GO directly connected to the S24 and through a powered USB-C 3.1 hub, as well as multiple known-good USB-C data cables, with no meaningful difference.
This makes me suspect that the latency is specifically related to the USB audio path rather than the MIDI connection itself.
Could engineering check what USB audio buffer size/sample rate djay selects for the Mixtrack GO on Android, and whether there is any way to force a lower-latency configuration (Recordbox has this feature in their Android version)?
Hi again @tripnot, no apology needed. Thanks for the additional testing and info!
You can go ahead and switch Mono Output off. Sometimes this solves audio issues with certain Android devices and hardware. Your read on this looks right to me. The MIDI side isn’t lagging on its own — you only hear a pad hit through the audio path, so when that path is delayed, the controls feel delayed with it. The USB audio routing toggle isolating it that cleanly is the strongest evidence we have.
I’m going to escalate this with our engineering team. I’ll include the buffer size and sample rate question and the request for a low-latency option on Android. No promises on the outcome, but the report is detailed enough for further internal investigation.
If you’re up to it, could you please test one more thing? Connect the Mixtrack GO with USB audio routing enabled, then open any app where tapping produces an immediate sound — a drum pad or metronome app — and see whether that delay is there too. If it is, the problem sits below djay in the S24’s USB audio path. Thanks again!
I performed the additional test you requested, and the delay is also present outside of djay.
I connected the Mixtrack GO to the S24 with USB audio routing enabled and routed the audio through the Mixtrack GO’s USB audio interface. I then opened Easybrain’s Drum Pad Machine.
The app does not appear to provide MIDI input routing, so I couldn’t trigger it from the Mixtrack controls. Instead, I tapped the drum pads directly on the S24’s touchscreen.
The result was the same: the drum-pad sound was delayed by approximately 200 ms when played through the Mixtrack GO’s audio interface.
For comparison, when I enable Android Developer Options → “Disable USB audio routing”, the audio immediately comes from the S24’s internal speaker with essentially no noticeable delay.
So the behavior appears to be:
• S24 touchscreen → internal S24 speaker: immediate
• S24 touchscreen → Mixtrack GO USB audio interface: approximately 200 ms delay
• djay + Mixtrack GO USB audio: approximately 200 ms delay
• djay + Mixtrack GO with USB audio routing disabled: MIDI and audio essentially immediate
This seems to confirm that the latency is occurring below djay, in the S24’s USB audio path.
I’m happy to provide any additional information or logs that would help your engineering team investigate this.
Hi @tripnot, no problem regarding the delay. That’s the answer, and it’s a clear one. Thanks for running it. Touchscreen tap to Mixtrack GO output at ~200 ms with djay not even open puts the delay below the app, in the S24’s USB audio path. djay is subject to it like any other app on that device. So, there’s likely little that can be done on the software side of things
Two things worth considering in the meantime.
Report it to Samsung. A test showing a third-party audio app hitting the same 200 ms through a USB interface, cleared instantly by a developer-options toggle, is about as clean a bug report as they’ll get.
Try a plain USB-C to 3.5 mm dongle. If a simple audio dongle plays back without the delay, then it’s the Mixtrack GO’s interface specifically rather than every USB audio device on the S24. That’d be genuinely useful to know, and it opens a workaround — see below.
If the dongle path turns out to be clean, you can mix with Settings > Split Output enabled: master and cue over one stereo pair through a stereo/mono DJ split cable, with the Mixtrack GO still connected for MIDI. You’d need a USB-C hub that handles both. Not as tidy as using the controller’s own outputs, but it would get you playing again. I hope that helps!
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!
