Verified hardware

Does the Qudelix 5K run bit-perfect on Android?

Yes. Meringo has captured bit-identical output from the Qudelix 5K at 24-bit / 96 kHz, and the SHA-256 of that capture is published in full — so you do not have to take our word for it. You can recompute the same hash yourself with ffmpeg, which is a tool we do not control.

The receipts

Two captures, eleven weeks apart, on two different builds. Both bit-identical.

The second capture matters more than the first. Anyone can get one clean measurement; the point of publishing a dated series is that a regression would show up here as a hash that stopped matching, in public, with our name on it.

What “UAC1 full-speed sync” means for this dongle

The 5K enumerates as a USB Audio Class 1 device in full-speed synchronous mode. That is the older, simpler transport — and for bit-perfect purposes it is completely fine. What matters is not which USB class a DAC negotiates but whether the bytes that leave the phone are the bytes that were in the file.

That is the only thing the receipt claims, and it is the only thing worth claiming.

Why this needs proving at all

On Android, the path from a file to a USB DAC has more than one place where audio can be quietly resampled or mixed before it leaves the phone. The frustrating part is that resampled audio still sounds like music. Nothing announces itself. You can own a capable DAC, play a 24/96 file, and get 48 kHz out of the other end without a single thing on screen suggesting it.

A hash settles it. Either the captured bytes match the source or they do not.

Check it yourself

Every entry in the registry is recomputable without Meringo running, using ffmpeg and sha256sum. The steps are on the registry page, and if your own capture disagrees with ours we want to know — a receipt that cannot be falsified is not a receipt.

→ The receipt registry

What Meringo will not tell you