Hi Spotify Team,
I am writing to request a critical fix/update to the native Exclusive Mode feature on the Spotify Windows desktop app. Currently, the feature completely fails to initialize on hardware setups utilizing dedicated, high-quality 16-bit USB DACs, throwing the error: "Can't play this content, Exclusive mode is on."
The Technical Issue:
Unlike dedicated bit-perfect audiophile players like Roon or Foobar2000, Spotify's current desktop audio architecture appears to be hardcoded to request a 24-bit or 32-bit float container format (WAVEFORMATEXTENSIBLE) from the Windows audio driver when initializing an Exclusive session.
When Spotify attempts this handshake with a DAC whose driver strictly accepts a native 16-bit format, the driver rejects the initialization envelope. Because Spotify currently lacks the logic to query the device capabilities and fall back to a 16-bit container structure, the audio engine crashes completely.
Why This Matters:
Given that the vast majority of Spotify's library consists of standard Red Book CD-quality files (16-bit / 44.1 kHz), users with strict 16-bit hardware are artificially blocked from experiencing bit-perfect playback. We are forced to turn Exclusive Mode off and rely on the Windows Shared Mixer, which is highly prone to hidden inter-sample peak compression (CAudioLimiter) and system sound interference.
Requested Solution:
Please update the Windows desktop audio engine to query the connected hardware endpoint during the WASAPI Exclusive initialization handshake. If the device reports a maximum limitation of 16-bit, allow Spotify to stream the 16-bit file natively within a 16-bit container instead of forcing a 24-bit wrapper and failing.
Thank you for your time and continued dedication to audio quality!