An AI-built Dolby Atmos encoder decodes in open software, but certified hardware rejects it by design

A developer has published a Rust tool that re-encodes Dolby Atmos audio, and it works almost everywhere except the hardware Dolby certifies. The project, posted to the r/ffmpeg subreddit, converts a Dolby Atmos master into Dolby Digital Plus. Open-source players decode the result as real spatial audio. Dolby-certified gear refuses to touch it. The developer says they built it with help from Claude Fable 5, Anthropic’s AI model, though the code itself credits no AI.

How a developer rebuilt Dolby Digital Plus Atmos encoding in Rust

The tool, named dolby-atmos-encoder, takes a Dolby Atmos master pulled from a TrueHD stream and re-encodes it into E-AC-3, the codec also called Dolby Digital Plus, with the object metadata that carries Atmos. The author leaned on open decoders like Cavern and the truehdd project to read the format, then ported the encoding path. The GitHub repository is explicit that it contains no Dolby keys or source code, and calls the work interoperability research.

Run the output through ffmpeg or Cavern and it checks out: valid object-based Atmos, correct height and 3D positions. The audio is right. The problem shows up at playback.

Why Dolby-certified hardware rejects the encoder’s output

Dolby’s bitstream carries a per-frame value the developer traces to a field called emdf_protection. It reads like a checksum. It behaves like a signature. The author brute-forced all 256 possible CRC-8 settings against real Dolby frames and got zero matches, which points to a secret key, not a public formula.

Open decoders ignore that field, so ffmpeg and Cavern play the file fine. Dolby-certified hardware checks it, finds no valid signature, and falls back to plain surround sound. The audio coding is solvable in the open. Playback stays gated behind a signature only Dolby’s licensed encoders can produce.

What the Dolby Atmos lock means for spatial audio in music

Spatial audio is now a paid format. Apple Music and Tidal stream Atmos, and the encode side is licensed: only Dolby-approved tools produce files that certified hardware will play in full. This project shows why. The barrier was never the math of placing sound in 3D. The barrier is a signature that controls who gets to make a conformant file.

For producers, the practical read is simple. You can mix in Atmos, but delivering it to the platforms still runs through Dolby’s licensed chain. If you are weighing that step, our roundup of AI mixing and mastering tools covers the stereo side, and Apple’s own spatial push sets the demand. AI lowers the cost of understanding a closed format. It does not hand you the keys.

Why AI keeps mapping the moat without crossing it

AI made the reverse-engineering fast, and the result documents Dolby’s lock instead of breaking it. The encoder pins down exactly where the control sits, a single protected field, which is genuinely useful and also confirms the moat holds. Shipping audio that a licensed decoder accepts is still a different and legal problem. Probing Dolby’s signature scheme sits in the grey zone around DMCA anti-circumvention rules, and a takedown would not surprise me. The same pattern shows up wherever AI meets a licensed format: the model reads the rules faster, the rules still hold.