Home > Apple > Mac

USB Audio Devices not working on Intel Mac Sonoma

The seventeenth iteration of the OS has brought in a truckload of goodies for the end users, however, on the flip side, let’s not shy away from the fact that it has also paved the way for a few bugs. While we have already documented a plethora of such issues, unfortunately, that list seems to be expanding every other day. The latest entry to this list is the fact that numerous USB Audio Devices are currently not working on Intel-based Macs running the latest macOS Sonoma.

Various USB Audio Devices not working on Intel Mac Sonoma

USB Audio Devices not working on Intel Mac Sonoma

Some of the major players in the market, including the likes of Denon DJ, Apogee, Rode, FiiO USB DAC, MIC, and DJ controller, seem to have been impacted by this issue. According to Rode, “A limitation has been identified in Intel-based Mac devices running Sonoma that affects compatibility with some MFi-certified USB audio devices.” In this regard, here are the affected RODE products:

  • AI-Micro
  • NT-USB+
  • PodMic USB
  • VideoMic GO II
  • VideoMic NTG
  • Wireless GO II
  • Wireless ME
  • Wireless PRO
  • RØDECaster Pro II (note: this affects USB 2 only)
  • RØDECaster Duo (note: this affects USB 2 only)

As far as Apogee is concerned, it’s also experiencing issues with MFi devices such as the One and Duet 1. Here’s the complete list of the affected Apogee products:

  • Quartet
  • Duet for iPad & Mac
  • ONE for iPad & Mac (Black)
  • ONE for Mac (Silver)
  • HypeMiC, MiC+
  • Jam X, JAM+
USB Audio Devices not working on Intel Mac Sonoma
Credits: Apogee

On the other hand, the below-listed Apogee products are still functioning normally:

  • Symphony Desktop
  • Duet 3
  • Boom
  • Duet 2
  • MiC 96k, MiC
  • JAM 96k, JAM

Likewise, some other products such as RME Babyface Pro, Topping DX7 Pro, Focusrite Scarlet Solo, and Scarlet 18i8 seem to be unaffected by this bug.

As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.

  • The new public beta 3 has fixed this issue!