Sessions

Pro

Sessions is an Orbit Pro feature.

Sessions let you build a working session of multiple tracks rather than opening a single file at a time. Use Sessions when you're QC'ing across an album or project where context and continuity matter — switching between tracks without losing playback state, view configuration, or marker lists.

For opening a single file the standard way, see Preview Mode.

Sessions vs Preview Mode

The two modes serve different jobs:

Preview Mode is the default — open a single file, listen, close, move on. Nothing is persisted between launches; the next file you open replaces the current one. State doesn't accumulate. This is the right mode for one-off QC passes.

Sessions is for the case where you have a body of work to step through — an album, a film reel, a TV episode batch — and you want all the context that goes with it (markers, the loop region, the video edit, view state) to follow you through the whole project rather than reset when you switch files.

A session bundles its tracks together so you can:

• Switch between tracks without losing your work — each track keeps its own markers, and the loop region and view state are saved with the session. (Solo / mute, monitoring mode and output routing are app-wide settings, not saved in the session.)
• Auto-advance through the playlist, audition tracks in order, or jump around at will.
• Reopen tomorrow and pick up exactly where you left off, with the same view and the same marker positions.
• Share the bundle with another QC engineer — the .orbsession is self-contained.

Creating a session

There are three paths to a new session, all under the File menu (Pro only):

• File → New Session… (⌘N) — opens the New Session screen. Enter a Name, pick a Location (Choose…) and a Sample rate, then click Create Session and start adding tracks. The session's sample rate is authoritative: Orbit runs the device at that rate and sample-rate-converts any file that doesn't match.
• File → Create Session from Preview… — when you've got a file open in Preview Mode and want to promote it to a full session. Copies the loaded audio file (and its waveform cache, if one exists, to save a re-render) into a new bundle.
• Welcome screen → Start a Session → New Session — same as the menu item, available before you've loaded anything.

Sessions can also be opened from:

• File → Open Session… (⇧⌘O)
• File → Open Recent → Sessions — recent sessions are listed separately from preview-mode files.
• Welcome screen → Recent — .orbsession entries appear alongside preview-mode files.

Anatomy of a session

A .orbsession is a macOS directory bundle — Finder shows it as a single document, but it's actually a folder with a known structure:

MyAlbum.orbsession/
├── session.json         — playlist, markers, loop region, view state
├── AudioFiles/          — imported ADM / IAMF tracks (copies, not references)
├── VideoSources/        — imported video files
├── VideoSources/Proxies/ — optimised ProRes proxies for heavy video sources
├── Graphics/            — still images imported for graphics overlays
├── RenderCache/         — background-rendered video preview chunks
├── Waveforms/           — cached waveform renders (.orbwave)
└── .orbit-lock          — present only when the session is open in a live Orbit instance

Audio and video files are copied into the bundle when you import them. Moving the bundle to another machine doesn't break references — the bundle is self-contained. The trade-off is disk space: a session with five 7.1.4 ADM masters will take roughly the size of those five files plus their waveform caches.

What's persisted

When you save a session (or rely on auto-save), the following state lives in session.json and survives close/reopen:

• Playlist — the ordered list of tracks
• Per-track markers — position, title, comment, colour and linked elements, stored with each playlist entry
• Region — one session-wide loop / selection region: start, end and whether looping is on
• Snap mode and the session sample rate
• View state — zoom level, scroll position and selected objects
• Video edit list — when video is attached, the clips, cuts and offsets, plus the imported video sources
• Custom speaker layouts — any custom .osls layouts are embedded, so a custom rig travels with the session

Things that don't live in the session:

• App preferences (theme, meter scale, frame rate, etc.) — those live in AppSettings and apply across every session.
• Monitoring and routing — monitoring mode, HRTF, head tracking, output routing and solo / mute are app-wide, not saved per session.
• Headphone EQ profile selection — also app-level, not per-session.
• Audio source files outside the bundle — once imported into a session, the bundle has its own copy; the original on disk is untouched and not tracked.

Working in a session

With a session open, the Tracks sidebar shows the playlist. Each row is one ADM or IAMF file, with its name, duration, and a thumbnail of the spatial waveform.

To add a track: use File → Import Audio into Session…, or the Import button at the top of the Tracks sidebar. The file is copied into AudioFiles/ and added to the playlist.

To switch tracks: click a row in the sidebar. Playback transports to the start of the new track, and that track's markers come back into view.

To advance automatically when a track ends: toggle the Auto pill at the top of the Tracks sidebar. Off by default — turn on for unattended audition runs.

Saving and closing

Save commands sit under the File menu:

• Save Session (⌘S) — overwrite the current bundle.
• Save Session As… (⇧⌘S) — save to a new name / location.
• Close Session (⇧⌘W) — close the current session. Prompts to save if there are unsaved changes; if you've never saved (untitled session), it offers a Save As dialog.

Auto-Save is off by default. Turn on Automatically save changes in Sessions preferences and Orbit writes to the bundle 2.5 seconds after every meaningful edit, so manual saves are rarely necessary. The save is atomic — a crash mid-save can't corrupt the bundle.

If you quit with unsaved session changes, Orbit asks whether to Save, Don't Save or Cancel.

Session locks

The first Orbit instance to open a session writes a .orbit-lock file inside the bundle. If you (or another user, on a shared volume) try to open the same session from a second instance, Orbit detects the lock and shows a Session is open elsewhere alert, naming the process, host and time the other instance opened it. There are two options:

• Cancel — leave the session in the original instance, don't open here.
• Force Unlock — claim the session for the new instance. Use this when the original instance crashed and left a stale lock behind, or when you've moved between machines.

The lock file is removed when the session is closed cleanly, or on app quit.

Untitled sessions

Opening a file in Preview Mode does not create a session — the file loads in place. Create Session from Preview… asks where to save the new session, builds a temporary untitled bundle, copies the loaded file and its waveform cache into it, then saves it to the location you chose.

Untitled bundles left in Orbit's temporary folder can be cleaned up via Preferences → Sessions → Clear All (see Sessions preferences).

See also

• Preview Mode — the single-file path; the right choice when you don't need session state to persist.
• Sessions preferences — the auto-save toggle and temporary-bundle cleanup.
• Overview — the Tracks sidebar and how it changes when a session is open.