Topic: ADI-2: Why only 32-bit data format is supported in driver-less mode?
While the ADI-2 supports all sample-rates from 44100 to 384000 [Hz] in driver-less mode (Windows Class Complaint) and automatic switching of sample-rates it only supports 32-bit data format. Why are not 16-bit and 24-bits supported as well? As is the most common case of other DACs and built-in sound cards?
That’s the reason why, for example, Tidal cannot work in WASAPI mode with the ADI-2 and so achieving bit-perfect playback. Tidal uses the following sample formats:
- In 16-bit: 44100, 48000 [Hz].
- In 24-bit: 44100, 48000, 88200, 96000 [Hz].
When starting a new track, Tidal queries the output device to check if the current sample format (channels/bit-depth/sample-rate) is supported by its interface.
- When yes, Tidal uses WASAPI exclusive mode and the track is then rendered bit-perfect on the output device.
- When not (always the case with ADI-2 given its interface only supports 32-bit data), Tidal falls back to “shared mode” when the Windows Mixer down/up-samples the tracks to the current bit-depth/sample-rate set under Windows sound properties/Advanced before it reaches the DAC.
With application likes Foobar and MusicBee is possible to use the ADI-2 in WASAPI mode (push) only because these programs offer the option to set manually the output format to 32-bit (not necessarily bit-perfect playback anymore) but trying with 16/24-bit won't work.
Would it be possible then to add support for 16-bit and 24-bit data format?