saimox — compare: ADM-BWF, IAMF and SMX

The chain

Nothing is a one-way door.

Material comes in as objects, stays objects while you work, and leaves as whatever the client asked for. Convert in either direction, as often as you need.

Studio masters

ADM-BWF

Import with CHNA + AXML
Export as delivery master

Working format

Objects

Discrete tracks
Motion + triggers
Real-metre world

Streaming

IAMF / Eclipsa

Import
Export
YouTube + Samsung route

ADM-BWF

The master format the industry already trusts.

A Broadcast Wave file with an XML description of every object and its movement embedded alongside the audio. It is an open ITU standard, it is what distributors accept for immersive delivery, and it is the format most immersive tools can already write.

Strength — universal acceptance. If a distributor takes immersive audio at all, it takes ADM-BWF
Limit — it describes a finished scene. Once written, the movement is fixed and nothing can respond to the listener
Here — full import with CHNA and AXML parsing, and export as a delivery master

IAMF · also shipped as Eclipsa Audio

The open route to streaming platforms.

IAMF is the royalty-free immersive container developed inside the Alliance for Open Media. Eclipsa Audio is the consumer-facing name the same technology carries on certain platforms and televisions — supporting IAMF means supporting Eclipsa, with no extra work.

Strength — no licence fees, and the only practical immersive path onto the largest video platform in the world
Limit — still a rendered container. Better economics than the incumbent, same fundamental ceiling
Here — import and export, including conversion straight from an ADM master

SMX and SMXD

Where the objects stay objects.

A plain container — a ZIP with a manifest, a spatial description and the audio. SMX is the working master, SMXD the streamable delivery. Both carry three things the formats above cannot: real object audio, live reactive rules, and per-object streaming.

Object audio — every source stays a discrete track with its own metadata, not a channel in a fold-down
Live reactive — trigger rules travel with the file and resolve during playback, on the listener's device
Streamable — each object is individually addressable, so a player fetches what it needs and silence costs nothing
Codec agnostic — Opus, AAC, FLAC or plain WAV. The container does not care
Licence free — we hold no patents on it and charge no fee per unit, so it is free to read and free to write

Hear what that sounds like → Reading the format is free for anyone, forever. That is deliberate: a format nobody can play is not a format.

At a glance

What each format can carry.

Capability	ADM-BWF	IAMF / Eclipsa	saimox
Discrete objects with metadata	yes	partly	yes
Adapts to the playback layout	no	yes	yes
Streamable per object	no	no	yes
Reacts at playback time	no	no	yes
Free to decode	yes	yes	yes
Accepted by distributors today	yes	growing	not yet

This is why conversion is part of the tool rather than an afterthought: you deliver in what the client accepts today, and keep the reactive version for everywhere that will take it.

Conversion is one feature, not the product.

The reason the bridges exist is so you never have to choose between what a client accepts today and what a listener could have tomorrow.

Read about the saimox format → · How SMX and SMXD are built → · Everything the tool does → · Try it for fourteen days →