Batch ADM to Eclipsa Audio™ Export

Batch export turns every ADM master in your session's playlist into Eclipsa Audio™ (IAMF) files in one go. Tick the tracks, tick the presets you deliver to, and Orbit writes one file for every track and preset pair, checks each one, and saves a delivery report beside them.

It's built for album and episode deliveries: eight masters to YouTube and Esfera is sixteen files, set up once and exported in one run.

New in 1.6.0 (beta)

Batch ADM to Eclipsa Audio™ Export arrived in 1.6.0 beta 7.

Orbit Pro

Batch export is part of Orbit Pro.

Opening it

Choose File → Batch ADM to Eclipsa Audio™ Export…. You can also find it in the Command Palette (⌘K) by typing "batch".

The menu item is available once the session's playlist holds at least one ADM master. The tracks come from the Playlist, in playlist order, so build the session first, then open the batch.

The window opens on the setup: a matrix of tracks and presets on the left, and the inspector on the right.

The matrix

Each row is a track from the session playlist, with its number, title, an ADM summary line (for example ADM · 23 ch · 48 kHz) and its duration. Each column is a preset you've ticked. One cell is one file.

The rail above the matrix reads the total, for example one cell = one file · 8 tracks × 2 presets = 16 files. Each preset's column header shows how many files it makes and their estimated total size, for example 8 files · ≈ 38 MB.

A cell shows its state and a short line beneath:

Cell reads	What it means
Auto	Planned automatically from the track and the preset, the same way the single exporter would route that master.
Edited	You've edited this file's graph. Your edit is used for this file only.
Checking…	Orbit is still working out this file's plan and size.
A warning (amber)	The file can't export as it is, for example Source missing or Edited graph out of date. The line beneath says why. See Before the export starts.

The line under Auto or Edited is the container and the estimated size, for example .iamf · ≈ 6.4 MB. Sizes are upper-bound estimates; the real files are usually smaller.

Ticking tracks

Tick the tracks to export, or use Select all and Select none above the track list. Only ADM masters can be ticked. Other playlist entries are listed with the reason they can't be:

• Already IAMF — not an ADM master
• Not an ADM master
• Listed twice in the playlist — exported once
• Source missing: the file isn't where the session expects it. Relink it, or leave it ticked and the check before export will list it.

Presets

With no cell selected, the inspector shows Presets ("Where are these files going?") and then the Batch settings. Tick every preset you deliver to. Each one makes one file per ticked track.

• Built-in presets are YouTube, Esfera and Full Master, the same destinations as the single Eclipsa Audio™ exporter. YouTube and Esfera arrive with their routing locked, as they do there.
• Your own presets appear beneath them. Make one with + New preset…, or Duplicate any preset from its … menu (or right-click it). Your own presets can also be Edited and **Delete…**d; built-ins can only be duplicated.

A preset holds encoding choices only: Codec (Opus, FLAC or LPCM), Quality (Streaming, Studio or Archive, for Opus only), Profile (Simple, Base or Base-Enhanced), Container (Destination decides, .iamf or .mp4), Output layout, and Include a binaural layout.

Presets never change routing

A preset never changes how a master is routed. Routing comes from the master itself (Auto) or from an edit you make to one cell. That way a preset made for one album behaves sensibly on the next.

Presets are saved on this Mac, not in the session. If you open a session whose presets aren't on this Mac, Orbit unticks them and says so above the list.

Selecting a cell

Click a cell to see that one file in the inspector:

• A read-only graph preview: the sources, the elements they feed, and the mix presentation.
• Profile: the IAMF profile and how much of its element and channel budget the file uses.
• Output: where the file will be written, relative to the destination folder.
• Size: the estimate for this file.

Edit Graph… opens the full routing graph for this one file. It's the same graph as the single exporter, with the batch's own choices shown but disabled, each with its reason: the destination cards ("Set by the cell's preset"), loudness ("Batch measures every file at export"), range ("Batch exports whole files") and video ("Not available in batch export"). Click Save and the cell reads Edited. Saving a graph that's identical to Auto puts the cell back on Auto.

Reset to Auto throws your edit away and goes back to the planned graph.

Click Batch settings at the top of the inspector to go back to the presets and batch settings.

If a master changes after you edit it

An edited graph remembers the master it was made for. If that file changes on disk, the cell reads Edited graph out of date, and Orbit asks you to decide: Edit Graph… to check it, or Reset to Auto. Orbit never quietly redoes an edit.

Batch settings

Destination

Click Choose… to pick the folder the files go to. The line underneath names the volume, whether it's writable and how much space is free, for example Macintosh HD · writable · 812 GB free.

File names

Files are named with two patterns: a Folder (inside the destination; a / makes a folder) and a File name. Each mixes your own text with wildcards. Click Wildcards ▾ at the end of either field to insert one at the cursor. The menu shows each wildcard's value for the selected cell (or the first cell), so you can see what you'll get.

Wildcard	Inserts	Example
$session	The session name	Esfera Welcome Tracks
$preset	The preset name	YouTube
$codec	The preset's codec	Opus
$profile	The IAMF profile	Base
$title	The track title	01-listen
$tracknumber	The track's position in the playlist, two digits	01
$date	The date of the export	2026-10-06
$year	The year of the export	2026

The defaults are Folder $session/$preset and File name $title, so a delivery lands as Esfera Welcome Tracks/YouTube/01-listen.iamf. The track number is there when you want it, never by default.

• The extension comes from the preset's container (.iamf or .mp4). Don't type it.
• The line under the fields shows where the first file will go.
• A $ word that isn't a wildcard (a typo such as $titel) is named in amber: "$titel isn't a wildcard — it will appear as written".
• Characters a file name can't hold (such as : or / inside a title) become -.
• Names are capped at 120 characters per folder or file name. A longer one is shortened, and Orbit says so under the fields and lists every shortened name in the check before export.
• An empty File name blocks the export: "Name the files — the File name is empty."

At once

How many files Orbit encodes at the same time: Auto, or 1 to 4. Auto lets Orbit decide for your Mac. Choose a lower number if you want to keep working in other apps during a long batch.

Delivery report

A PDF and a CSV are written beside the files when the run ends. See The delivery report.

Before the export starts

Click Export… and Orbit checks every file before anything is written. The headline says how many are ready, for example 14 of 16 files are ready, and the rest is in three groups:

Needs a decision: these files won't export as they are.

Shown as	What to do
… — the source file is missing	The master isn't on disk where the session expects it. Reconnect the drive or relink the file.
… — edited graph out of date	The master changed after you edited its graph. Click Edit Graph… to check the edit, or Reset to Auto.
… — would overwrite its source	The file would be written over its own master. Choose a different destination or naming pattern. Orbit always refuses this.
… — Refused · IEnn	The exporter can't make this file as it's set up. The code links to what it means and what to try.

Deliberate changes: these will export, and are listed so nothing is a surprise: files that will replace existing files (with Show in Finder), cells with an edited graph, presets whose routing is locked by the destination, names that were shortened to 120 characters, and any saved edit that couldn't be read ("Saved graph couldn't be read — using Auto").

Destination: whether the folder is writable, how much space the export needs (an upper bound) and how much is free. If the folder isn't writable or there isn't enough space, nothing can export until you fix it.

Then choose:

• Export all: available when nothing needs a decision.
• Export N, skip M: exports the files that are ready now and leaves the rest. Come back later for the ones you skipped.
• ‹ Back to setup: change something first.

While it runs

Each file has its own row, grouped by track. Several files encode side by side (as many as At once allows), and each row shows its own progress, so you can see which file is slow.

A row reads Queued, then Preparing and the step it's on (whichever the file needs: Checking for silence, Pre-rendering, Rendering compatibility stereo, Matching loudness, Analysing scene, Verifying loudness), then Rendering with a percentage.

Step	What Orbit is doing
Checking for silence	Finding sources that are silent for the whole file, so they're left out of the export
Pre-rendering	Rendering the mix the file is built from
Rendering compatibility stereo	Rendering the stereo track an MP4 carries for players without Eclipsa Audio™
Matching loudness	Measuring the master so each render in the file plays at the master's own loudness — it doesn't normalise to a target
Analysing scene	Reading how the scene moves, for files that carry one
Verifying loudness	Re-measuring a render the limiter touched, so the loudness written into the file is right
As it renders, the row draws the file's waveform, scaled to that file's loudest moment so quiet material still shows.

A file that has finished rendering but is still being written and checked reads Finishing…. That's normal. Each file is written under a temporary name, checked, and only then given its real name.

A file that fails doesn't stop the others. Cancel stops the run; files that hadn't finished are marked Cancelled.

The complete screen

When the run ends, the window shows what was delivered.

• The grid: one cell per file, track against preset, with a tick and the file's size. A file that failed or was skipped shows in place, so nothing is hidden.
• The headline: for example 16 files written and checked, or 14 of 16 files written.
• Loudness · BS.1770-5: the integrated loudness and true peak the encoder measured and wrote into each file, per layout. A speaker render that peaks above 0 dBTP is flagged in amber, with its track, preset and layout; otherwise the line reads Every speaker render peaks at or below … dBTP.
• Written as planned: how many files were written, how many tracks went through how many presets, how many were skipped, failed or cancelled, and whether the delivery report was written.
• Bitstream check: every file is read back and checked as valid IAMF and against its profile, for example 8 conform to Base. Any finding is listed with its file below.
• Files: every file, grouped by track, with its codec and profile, its loudness per layout, and bitstream ✓ / profile ✓. A failed file shows its code, for example IE07, with a link to what it means.

Why binaural peaks above 0 dBTP aren't flagged

A binaural layout passes through HRTF filtering, which lifts true peak by design: a master at −18 LUFS can reach +3 to +4 dBTP once it's binaural. Orbit shows binaural peaks as they are but doesn't flag them. Only speaker renders over 0 dBTP are highlighted.

Back to setup returns to the matrix. If anything wasn't delivered, it reads Back to setup · retry N and ticks just those files again. Open report (PDF), CSV and Show in Finder open the report; Done closes the window.

The delivery report

When the run ends, Orbit writes _Delivery Report.pdf and _Delivery Report.csv beside the files, in the folder they share. With the default naming that's the session folder, for example Esfera Welcome Tracks/_Delivery Report.pdf. The bottom bar says where.

The PDF opens with a summary: how many files were delivered, failed and skipped, how long the run took, the presets, the format, any speaker render over 0 dBTP, and any bitstream or profile finding. Then one section per track lists every file with its outcome (Delivered, Delivered with findings, Failed with its code, Skipped with its reason, or Cancelled), its codec, profile and container, whether its graph was edited, and a table of Layout, Integrated loudness and True peak. Pages are numbered Page N of M.

The CSV has one line per file and layout, with these columns: track, preset, file, outcome, user_code, code, param, message, codec, profile, container, edited_graph, bitstream_valid, profile_conformant, layout, integrated_lufs, true_peak_dbtp, loudness_match_gain_db, duration_s.

File paths in both are relative to the destination folder, so the report stays correct when you move or hand over the whole delivery.

Sessions

The batch setup is saved in the session (.orbsession): which tracks and presets are ticked, your edited graphs, the destination folder, the naming patterns and At once. Save the session and the next batch is ready when you reopen it. If the destination folder can't be found when you reopen the session, the Destination row says so; choose it again.

Troubleshooting

You see	Try
The menu item is greyed out	The session's playlist has no ADM master. Add one to the Playlist.
A track can't be ticked	Its row says why: it's already IAMF, isn't an ADM master, or is listed twice.
Source missing	Reconnect the drive or relink the master, then reopen the batch.
Edited graph out of date	Click Edit Graph… to check the edit, or Reset to Auto.
Refused · IE13	Opus needs a 48 kHz master. Use a preset with FLAC or LPCM. See IE13.
Refused · IE17 or IE19	The master needs more elements or channels than the profile allows. Use a Base-Enhanced preset, or fold objects in Edit Graph…. See IE17.
IE07 after the run starts	The destination folder went away. Reconnect the drive or choose the folder again. See IE07.
IE31	A custom HRTF's SOFA file is missing. See IE31.
IE32	Orbit ran out of memory. Set At once to a lower number and retry. See IE32.

Every code is listed in Export failure codes. For uploading the files to YouTube, see Eclipsa Audio on YouTube.