I recently discovered a frustrating issue with Apple’s Music.app on macOS when using an external DAC (Chord Hugo 2), and after some research, I realized this has likely been a problem for years.
The Issue: High-Res Audio Is Being Resampled Incorrectly
If you play a high-resolution file (e.g., 96kHz) through an external DAC, even if you manually change the DAC’s sample rate to match, macOS internally down-samples it to whatever sample rate was set when Music.app launched (e.g., 44.1kHz) and then up-samples it back to 96kHz.
This means that Music.app is not delivering true bit-perfect playback—instead, it’s feeding your DAC a resampled version of what should be lossless, high-resolution audio.
This Also Affects the Built-In Headphone Jack
This resampling issue isn’t exclusive to external DACs. If you’re using the built-in headphone jack on a Mac, macOS will resample high-res files if the sample rate in Audio MIDI Setup doesn’t match the file. The only way to get proper playback is to manually change the sample rate before playing each track, which is completely impractical.
Why This Is Frustrating
• Music.app does not automatically switch sample rates to match the playing file—something Audirvana, Roon, and even iTunes with BitPerfect used to do.
• CoreAudio forces resampling, even if you try to manually match the DAC’s settings.
• Apple markets Music.app as a lossless audio player, yet it’s quietly degrading playback quality.
• Pro audio apps like Logic don’t have this issue, so why does Music.app?
Third-Party Players Work Fine—So Why Can’t Apple Fix This?
Third-party apps like Audirvana and Roon establish their own direct connections to the DAC, completely bypassing CoreAudio’s system mixer. They deliver true bit-perfect playback without this unnecessary resampling.
But why does Apple’s own Music.app—on the platform that introduced lossless Apple Music—fail at properly handling high-res playback? This feels like an unforced error.
Sources & More Discussion:
• GitHub Discussion – LosslessSwitcher Issue
• CoreAudio API Mailing List (2008) – Sample Rate Handling
The Issue: High-Res Audio Is Being Resampled Incorrectly
If you play a high-resolution file (e.g., 96kHz) through an external DAC, even if you manually change the DAC’s sample rate to match, macOS internally down-samples it to whatever sample rate was set when Music.app launched (e.g., 44.1kHz) and then up-samples it back to 96kHz.
This means that Music.app is not delivering true bit-perfect playback—instead, it’s feeding your DAC a resampled version of what should be lossless, high-resolution audio.
This Also Affects the Built-In Headphone Jack
This resampling issue isn’t exclusive to external DACs. If you’re using the built-in headphone jack on a Mac, macOS will resample high-res files if the sample rate in Audio MIDI Setup doesn’t match the file. The only way to get proper playback is to manually change the sample rate before playing each track, which is completely impractical.
Why This Is Frustrating
• Music.app does not automatically switch sample rates to match the playing file—something Audirvana, Roon, and even iTunes with BitPerfect used to do.
• CoreAudio forces resampling, even if you try to manually match the DAC’s settings.
• Apple markets Music.app as a lossless audio player, yet it’s quietly degrading playback quality.
• Pro audio apps like Logic don’t have this issue, so why does Music.app?
Third-Party Players Work Fine—So Why Can’t Apple Fix This?
Third-party apps like Audirvana and Roon establish their own direct connections to the DAC, completely bypassing CoreAudio’s system mixer. They deliver true bit-perfect playback without this unnecessary resampling.
But why does Apple’s own Music.app—on the platform that introduced lossless Apple Music—fail at properly handling high-res playback? This feels like an unforced error.
Sources & More Discussion:
• GitHub Discussion – LosslessSwitcher Issue
• CoreAudio API Mailing List (2008) – Sample Rate Handling