OS-NATIVE STREAMING
The DMP ONE appears in Windows and Linux as a native audio output device. Bit-perfect streaming up to PCM 384 and native DSD512 is available in every application — no proprietary app, no middleware, no compromises. This is engineering most streamers cannot match, because it requires custom-built drivers — not bundled standard drivers.
This page explains the engineering. For protocol-level detail, see our white paper.
THE STANDARD APPROACH
Standard USB audio drivers conform to USB Audio Class 2 — a specification designed in 2009, primarily for PCM. They handle PCM up to 384 kHz / 32-bit competently. They struggle, or simply cannot, with native DSD.
For DSD playback, most streamers fall back to DoP — DSD encoded inside PCM frames. The DAC must unwrap DoP back to DSD. This works, but it is not native DSD transport. The signal travels as PCM through the chain, even though it carries DSD data.
Above DSD256, even DoP becomes problematic — bandwidth limits and timing constraints make reliable native transport impossible without custom protocol handling. This is why most streamers cap their DSD support at DSD256, or rely on DoP for everything above DSD64.
True native DSD512 over USB requires more than standard drivers. It requires drivers built for the task.
OUR APPROACH
We do not bundle standard drivers. We build them. Our DMP NEXUS driver stack is custom-engineered for the DMP ONE — conforming to the WASAPI, ASIO, and PipeWire interfaces that your operating system already understands, but extending those interfaces with the protocol handling required for native DSD512 transport.
From the OS perspective, the DMP ONE looks like a standard audio output device. Applications send their audio data to it the same way they send data to any other device. There is no special API, no proprietary integration, no application-side adaptation. This is the design goal: every audio application works, unchanged.
Beneath that conformant interface, the driver does work that standard drivers do not. It bypasses the OS audio mixer when bit-perfect transport is required. It packages DSD samples for native USB transport without DoP encapsulation. It coordinates timing so the DAC receives a continuous, untouched stream — at every supported sample rate, up to DSD512.
The driver is what makes the difference. The hardware is the carrier. The software is the engineering.
Each operating system has its own audio architecture. We engineered our driver stack to fit each one — not by abstracting the differences away, but by working with each platform's strengths.
WINDOWS · WASAPI
Our WASAPI driver claims exclusive mode when bit-perfect transport is requested — preventing the Windows audio mixer from resampling, applying effects, or otherwise modifying the signal. Native DSD512 streams travel through WASAPI exclusive directly to the USB endpoint.
WINDOWS · ASIO
Our ASIO driver provides applications that support ASIO — Roon, Audirvana, HQPlayer, JRiver — with the lowest-latency, most direct path to the DMP ONE. Audio bypasses the Windows audio subsystem entirely. This is the path most professional and audiophile users will choose.
LINUX · PIPEWIRE
On Linux, our driver registers the DMP ONE as a PipeWire sink with bit-perfect routing rules. PipeWire's modern audio graph allows applications to address the sink directly, with no resampling or format conversion. Tested on Ubuntu, Fedora, and Arch.
THE USER EXPERIENCE
In Windows, the DMP ONE appears in your Sound settings exactly like any other audio device. You select it as your output. Done. Whatever you play — Qobuz, Tidal, Apple Music, Spotify, your local FLAC library, the YouTube tab in your browser — flows to the DMP ONE.
In ASIO-capable applications, you select the DMP ONE as your ASIO device. The application talks directly to our driver, bypassing Windows audio entirely. This is what audiophile applications expect, and it is what they get.
In Linux, the DMP ONE appears in PipeWire-aware audio settings — pavucontrol, GNOME Sound, KDE Audio Volume — as a regular sink. Applications use it without modification. Audio servers like Roon Bridge or HQPlayer NAA recognize it through PipeWire's standard interfaces.
THE HARDEST CASE
Native DSD512 transport over USB Audio Class 2 is the most demanding case in consumer audio. The data rate — 22.5 MHz, single bit, continuous — pushes against the practical limits of USB 2.0 isochronous transfers. Standard drivers do not attempt this. They cap DSD support, fall back to DoP, or both.
Our driver handles DSD512 natively. The data leaves the application, traverses our driver, exits via USB, and arrives at the DAC — as native DSD, throughout. No DoP encapsulation. No format conversion. No fallback. The DAC's DSD512 input receives true DSD512, the way the file was created.
22.5 MHz
sample rate
1 bit
sample width
0 conversions
in the chain
This is what bit-perfect means at the highest end.
VERIFIABILITY
Bit-perfect transport is verifiable. Use a USB-audio analyzer or a DAC with digital monitoring output to capture the bit stream arriving at the DAC's USB input. Compare the captured stream against the source file. They should match — bit for bit, sample for sample, at any sample rate up to DSD512.
We have published the verification methodology in our white paper. The procedure is independent of our hardware — any streamer claiming bit-perfect output can be tested the same way. We invite the comparison.
WHERE IT WORKS
TODAY
Native DMP NEXUS drivers are available for Windows 10, Windows 11 (WASAPI exclusive and ASIO), and Linux distributions running PipeWire (Ubuntu, Fedora, Arch tested; others should work but are not officially verified). Both implementations are signed where required, free to download, and updated through DMP NEXUS.
Available with every DMP ONE.
TOMORROW
A native macOS driver is on our roadmap. macOS audio architecture (Core Audio) requires a separate driver implementation, and we want to do it right rather than ship something compromised. We have not yet committed to a release date — when we do, it will appear here, with the same engineering standard as our Windows and Linux drivers.
In planning. No commitment date yet.
We commit to what we can deliver. We disclose what we cannot — yet.