DoP vs native DSD

What the two terms actually mean, and which distinction matters to your DAC.

Short answer: DoP wraps the DSD bitstream inside PCM frames; raw native DSD sends it on its own wire. But on a Mac that is not the choice you are making, because macOS has no raw DSD transport at all. The distinction that changes what your DAC receives is a different one — was the DSD converted to PCM, or not? — and DoP is on the “not converted” side of it.

Three things a player can do with a DSD file

1. Raw native DSD. The 1-bit stream goes to the DAC as a 1-bit stream, over a driver written by the DAC’s manufacturer. This is a Windows arrangement, carried by ASIO.
2. DoP (DSD over PCM). The same 1-bit stream, unaltered, packed into the data bytes of ordinary 24-bit PCM frames with a marker byte on top. The DAC sees the marker, unpacks the bits, and plays the original DSD. Nothing is converted — the carrier is a container, not a computation.
3. DSD→PCM. The 1-bit stream is decoded into multi-bit PCM in software and high-resolution PCM goes to the DAC. This works on any DAC and it is a genuine conversion.

People use “native DSD” for both (1) and (2), which is where the confusion starts. The useful line is between (3) and everything above it. How to play DSD on a Mac has the framing detail — the marker bytes, the carrier rates, and the step-by-step setup — and this page does not repeat it.

Why option 1 does not exist on a Mac

Core Audio speaks PCM. There is no audio path in macOS that carries 1-bit samples to a USB device, and a native 1-bit stream format is essentially never present on Mac audio hardware — which is why the meaningful question about a DAC on macOS is not “does it do native DSD” but “does it accept 24-bit PCM at the DoP rate”. That is the question BitMuse asks a device when it reports what DSD rate it can handle.

In BitMuse, the setting labelled “Native DSD (DoP)” means DSD carried in PCM frames without conversion. It is not a separate raw DSD transport. Signal Path distinguishes this from DSD-to-PCM playback.

What BitMuse does on each path

BitMuse reads DSF and DFF files from DSD64 through DSD512. Playback converts to PCM by default. In Audio settings, enable Native DSD (DoP) — experimental with Exclusive Mode to request an unconverted DoP stream. The device must support the carrier rate and a physical integer format of at least 24 bits. If a required check fails, BitMuse uses DSD-to-PCM conversion; Signal Path shows the result. SACD ISO files are not supported.

Five things have to be true, or it falls back

DoP is fragile in a specific and unforgiving way: the marker bytes are only markers if nothing rewrites them. Send DoP down a floating-point path and the markers become full-scale noise — not a quiet degradation, a loud one. So BitMuse checks, and drops to DSD→PCM rather than gambling, if any of these fails:

1. the device does not offer the required PCM carrier rate;
2. exclusive mode cannot be acquired;
3. the DAC will not take a 24-bit-or-deeper integer physical format;
4. the output stream fails to start;
5. or the integer format does not verify after the stream is running.

This is why integer output and DoP are linked: the DoP carrier must be integer, so the same machinery that gives you an integer PCM path is what makes native DSD possible at all.

The fallback is a real conversion, and it says so

When DoP is off or unavailable, BitMuse decodes DSD to PCM with dsd2pcm — an eight-to-one decimation through a 96-tap FIR with a −160 dB stopband — and sends high-rate PCM in the 44.1 kHz family. That path is Float32 and is flagged internally as a conversion, so nothing downstream reports it as untouched. The signal path tells you which of the two you got, per track.

The consequence nobody mentions: DSP

On the native DoP path the DSP chain is bypassed entirely, along with software volume. It has to be. The samples on that path are DSD bits wearing a PCM costume; an equalizer applied to them would not equalise anything, it would corrupt the bitstream. On the DSD→PCM path, where the audio really is PCM, the chain runs normally.

So “native DSD with EQ” is a contradiction, and the honest resolutions are the two BitMuse offers: keep the DSD untouched and lose the processing, or convert to PCM and have it. This is the practical version of the point made in DSD vs PCM — that you cannot apply digital volume or DSP to a DSD stream without turning it into PCM first.

It also changes how a bit-perfect claim is evaluated. Because the DoP path never goes near the PCM resampler, BitMuse ignores the sample-rate strategy when judging native DSD and gates on the conversion flag instead.

So which should you use?

If your DAC accepts DoP at the rate of your files, use it — the DAC gets the bits from the file and does what it was designed to do with them. If it does not, DSD→PCM is not a defeat; it is a good conversion done in software you can inspect rather than silently in the DAC. What you should not accept is not knowing which one is running. For the setup steps see how to play DSD on a Mac, and for why the format exists at all, DSD vs PCM.

FAQ

What is the difference between DoP and native DSD?

DoP carries the DSD bits inside PCM frames; raw native DSD sends them on their own. Neither converts the audio, so on the question that matters they give the same answer.

Can macOS send raw DSD to a DAC?

In practice no — Core Audio has no 1-bit transport, so on a Mac “native DSD” means DoP.

Is DoP lossy?

No. The bits are repackaged, not recomputed. It stops being bit-perfect only if something rewrites the PCM carrier, which is why it needs exclusive mode, integer output and unity volume.

Does BitMuse play SACD ISO files?

No — .dsf and .dff only. Extract the tracks first.

Play DSD untouched — free for 30 days

30 days, every feature, no account and no card.
$99.95 once if you keep it · macOS 15+ · Apple Silicon