Pre-orders open. Official launch at High End Vienna — June 4–7, 2026.

OPEN SOURCE FOUNDATION

Built on foundations worth building on.

The DMP ONE runs on Linux. Our DMP NEXUS Player builds on Audacious. Our drivers conform to standards maintained by the open-source community. None of this is a shortcut. All of it is a deliberate choice — and one we credit fully.

This page documents what we use, why we use it, and how we honor the licenses that make it possible.

OUR POSITION

Why we chose open foundations.

Audio engineering is full of proprietary stacks that hide their internals. The justification is usually some combination of "performance," "differentiation," or "intellectual property protection." We are skeptical of all three claims when applied to fundamental software like operating systems, audio engines, and protocol implementations.

The Linux kernel has been peer-reviewed by thousands of engineers over three decades. Audacious has been refined by audio enthusiasts since 2005. PipeWire is the work of dedicated developers committed to better Linux audio. These foundations are not lesser because they are open. They are stronger.

Our engineering budget went where it actually matters: the layer where the DMP ONE differs from any other streamer. Custom drivers for native DSD512 transport. The Active DSD Bridging algorithm. The control software that makes the device useful. We did not waste resources rewriting what already works well — and we did not pretend that what we build sits on nothing.

Open source is not a shortcut. It is a starting point that has already been peer-reviewed by people who care more than any single team ever could.

THE FULL STACK

What runs inside the DMP ONE.

Below is every significant open-source component in the DMP ONE — hardware platform, operating system, audio infrastructure, and libraries. Each is named, licensed, and credited. The full license text for every component is available as a downloadable file.

HARDWARE PLATFORM

The single-board computer at the core.

The DMP ONE is built around a Khadas VIM3L — a single-board computer with mature Linux support, well-documented hardware, and a long-term software lifecycle. We chose proven hardware over custom silicon for one reason: bit-perfect audio transport does not require exotic processors. It requires excellent software running on stable hardware.

KHADAS VIM3L

Hardware platform · proprietary firmware, open hardware design

Single-board computer based on the Amlogic S905D3 SoC. Operating-system support: Linux mainline, U-Boot, vendor-supported.

OS & AUDIO INFRASTRUCTURE

The system layer that talks to applications.

On Linux, audio routing is handled by PipeWire. Our DMP NEXUS driver registers as a PipeWire sink. On Windows, our drivers conform to Microsoft's WASAPI and Steinberg's ASIO interfaces. The Linux components below are open source. WASAPI and ASIO are not — but our implementations of them are entirely our own work.

LINUX KERNEL

Operating system · GPL-2.0

The kernel of our embedded operating system. Long-term-support release, lightly customized for our hardware platform.

PIPEWIRE

Audio server · MIT

Modern audio and video routing for Linux. Used as the audio framework in our Linux driver implementation.

ALSA (ADVANCED LINUX SOUND ARCHITECTURE)

Low-level audio · LGPL-2.1+

Provides low-level audio device interfaces used by PipeWire.

PLAYER FOUNDATION

The audio player at the heart of DMP NEXUS Player.

DMP NEXUS Player is built on Audacious — an open-source audio player with two decades of refinement by audio enthusiasts. We have extended Audacious with proprietary plugins for native DSD512 playback and Active DSD Bridging, but the foundation is open. We document our changes. We honor the license.

AUDACIOUS

Audio player · BSD-3-Clause (core), various licenses for plugins

The base audio player on which DMP NEXUS Player builds. We use Audacious 4.x with our own DSD512 streaming plugin.

FFMPEG

Multimedia framework · LGPL-2.1+ (core), various

Used for format conversion and decoding fallback paths.

NETWORKING & STREAMING

The protocols that connect everything.

Networking, UPnP server functionality, and OpenHome compliance are handled through established open-source libraries. Our integration extends these libraries; it does not replace them.

GUPNP / GSSDP

UPnP framework · LGPL-2.1+

Library for building UPnP-compliant network services. We use it for the DMP ONE's UPnP music server functionality.

OPENHOME

Audio standard · BSD-2-Clause

The OpenHome architecture and reference implementations for multiroom and synchronized network audio.

LIBCURL

Network transfer · MIT-style

Used for HTTP/HTTPS communication, including streaming connections to online services.

Many smaller libraries are also part of the DMP ONE — too many to list inline. The complete inventory, including version numbers and full license texts, is available in the LICENSES file linked in the next section.

LICENSES

Full license documentation.

Every open-source component used by DMP NEXUS and DMP NEXUS Player is documented in our open-source downloads section: per-product End-User License Agreements (DE + EN) plus the full third-party notices listing each library's name, version, license type, license text, source URL, and any modifications we have made.

If you find any component missing from our documentation, please contact us — we treat license compliance as ongoing work, not a one-time checkbox.

Plain text · Updated with each release

THE COMMUNITY

Thank you.

To the developers, maintainers, and contributors of every open-source project named on this page — and the many smaller ones we did not name individually: this product would not exist without your work. Your decades of refinement, your peer review, your dedication to doing things well rather than quickly. We do not take it for granted. We honor your licenses. We contribute where we can.

— The 64bitAudio team

OUR CONTRIBUTIONS

Today, we credit. Tomorrow, we contribute more.

TODAY

Credit, comply, contribute where we can.

Today, our public commitment is documentation and compliance: every component we use is named, every license is honored, every required attribution is provided. We make occasional contributions to upstream projects when we encounter and fix bugs, but we have not yet built a structured contribution program.

Honest about scope.

TOMORROW

A more structured commitment.

As we grow, we plan to formalize our contributions: regular upstream patches to projects we depend on heavily, sponsorship of maintainers whose work we directly use, and open publication of any non-proprietary improvements we develop. The audio software ecosystem owes much to a small number of dedicated maintainers. Supporting them is a debt we want to repay properly.

In planning. We will document what we do, when we do it.

We document what we do today. We commit only to what we can sustain tomorrow.