DoP carries DSD data in a structure that a PCM-capable connection can transport. It is not, in itself, conversion of the music into PCM audio. That distinction matters when selecting an output or finding that a file works only at certain rates.
Payload and container
DSD64 uses a one-bit stream at 2.8224 MHz per channel; DSD128 and DSD256 double and quadruple that rate. These figures are not directly comparable to a multibit PCM sample rate and do not establish listening superiority.
DoP packs DSD bits into frames the connection handles as PCM words, with a marker to identify them. A compatible receiver extracts the payload. That differs from filtering and resampling DSD to produce usable PCM audio samples.
| DSD stream | DoP container rate |
|---|---|
| DSD64, 2.8224 MHz | 176.4 kHz |
| DSD128, 5.6448 MHz | 352.8 kHz |
| DSD256, 11.2896 MHz | 705.6 kHz |
These rates follow from carrying 16 DSD bits per frame and channel in the 24-bit DoP format; the remaining 8 bits carry a marker. They describe a path requirement, not guaranteed device support: a DAC accepting 352.8 kHz PCM may still lack DoP support or reject a particular DSD rate.
What “native” means in the player
Native DSD output uses the DSD path supported by the application, driver and device, without DoP encapsulation. Availability depends on the operating system, interface and versions. The 2012 DoP specification explains the protocol; its comments about contemporary drivers do not describe every computer today.
Native and DoP can carry the same DSD data. Choose a documented, stable route for your connection; the transport name offers no automatic sonic benefit. A “DSD input” also tells you little about processing inside the converter, which requires model-specific documentation.
Volume, EQ and conversion
Many common processing operations need a multibit representation. Software may convert to PCM, process the signal and, in some cases, encode it again. Read the component’s documented path: a .dsf or .dff source filename does not establish what reaches the DAC.
EQ can be a useful, deliberate choice. If correcting the system’s response is the priority, a properly configured PCM path may suit the job better than preserving unchanged DSD. The bit-perfect guide explains the distinction between data integrity and the perceived result.
Check the chain, not just one indicator
Check the file format, output method, driver and formats accepted by the DAC’s specific input. Disable or document DSP according to your goal, then check that player and receiver report consistent modes. The display is evidence of the recognised format, not a certificate for the whole chain or the absence of internal conversions.
Start with the analogue level low. If the device fails to recognise the stream or produces unexpected noise, stop playback and recheck compatibility. Do not use noise as a protocol test. For general player configuration, see the foobar2000 guide ; additional DSD components need their own version and provenance checks.
Sources
- DSD over PCM specification 1.1 ↗ — DoP open standard · accessed 2026-11-01
- foobar2000 FAQ ↗ — foobar2000 · accessed 2026-11-01
- Roon's conversion to PCM ↗ — Roon Labs · accessed 2026-11-01

