Video Optimisation

Pro

Video Optimisation is an Orbit Pro feature.

When you import a video, Orbit optimises it into an Apple ProRes proxy for smooth, frame-accurate playback and scrubbing — this is what lets you scrub a long clip against your ADM or IAMF audio without stutter.

Why ProRes?

ProRes is Apple's professional editing codec, and it's ideal for QC playback on macOS:

• Every frame is a keyframe. ProRes is an all-intra codec — each frame is stored complete, so Orbit can jump to any frame instantly. Delivery codecs like H.264 / HEVC use long groups of inter-frames that must be decoded in sequence: fine for linear playback, slow for scrubbing.
• Hardware-accelerated on Apple Silicon. ProRes encode and decode run on Apple Silicon's dedicated media engine (via Apple's VideoToolbox), keeping the work off the CPU and GPU so the rest of your QC session stays responsive.
• Real-time, predictable playback. Decode cost is consistent frame-to-frame, so timeline performance doesn't spike on complex footage — exactly what you want when scrubbing back and forth during QC.

Automatic optimisation on import

Proxies are created automatically on import whenever the source video will benefit from optimisation. Each clip is ready to scrub as soon as its own optimisation completes.

While optimisation runs, an Optimizing media indicator appears at the top of the Video View. It shows overall progress as a running total across everything currently being optimised — whether clips in the bin or footage on the timeline.

Timeline rendering

Optimising the source clips isn't the whole story. Whenever an edit changes what a frame should actually look like — anything that departs from the original clip, such as fades, keyframing, text, graphics, or transforms — that part of the timeline needs to be rendered.

Orbit renders the composited timeline in chunks and saves them to the session. Once a region is rendered, scrubbing through it is instant.

To keep editing responsive, Orbit waits for a small gap in timeline activity before it renders, so rendering never competes with what you're doing.

You'll know a region still needs rendering by a green line between the video lane and the audio lane — it clears as each chunk finishes baking.

Timeline rendering is controlled by the Background Render settings in Preferences → Video below — including the render codec and a disk budget. Render files are derived data and safe to delete; Orbit re-bakes them when you return to that part of the timeline.

Choosing the optimisation level

The optimisation level is set in Preferences → Video.

• Playback Quality — Better Quality uses full-resolution (source-res) ProRes for the sharpest playback and render, at the cost of larger proxies that are slower to optimise (opt in for final QC). Better Performance uses a lighter proxy for faster, lower-disk playback. Switching re-optimises imported footage at the new resolution in the background.
• Proxy Optimisation — the ProRes tier used for the proxy: ProRes 422 Proxy (smallest, ~45 Mbps at 1080p — recommended for QC reference), ProRes 422 LT, or ProRes 422 (sharper, more disk). Applies to newly imported clips and to Re-optimise.
• Background Render — optionally bakes the composited timeline (clips + titles + graphics + fades) to disk while idle, so scrubbing rendered regions is instant. Pick the render codec and a disk budget; render files are derived data and safe to delete.
• Storage — shows how much disk the optimised media and render cache are using. Optimised media persists with the session; the render cache is regenerable and capped by the budget above. Both live in the current session bundle.

Storage and disk budget

All of Orbit's optimised video — the ProRes clip proxies and the timeline render chunks — is kept inside the session's .orbsession bundle, so a project stays self-contained and portable. The Storage panel in Preferences → Video shows how much space each is using.

How much you need scales with the project:

• Short pieces — music videos and short-form content use very little storage, especially at the ProRes 422 Proxy tier.
• Large projects and feature films — raise the disk budget towards the maximum so more of the timeline stays rendered for instant scrubbing.

Because everything lives in the session bundle, if you need more room you can run the session directly from a portable SSD or a high-performance network drive.

Re-optimising a clip

To re-run optimisation on a clip — for example after changing the proxy tier — right-click the Video Clip in the bin and choose Re-optimise. A progress indicator shows the optimisation running. It uses the same hardware-accelerated pipeline, so there's minimal impact on CPU and GPU.

See Video Importing & File Support for importing clips and the full right-click menu.