Skip to content

Export & Rendering

Conform has one export path: Adobe Media Encoder. It is optional — a run can publish its FCP XML without rendering anything.

Changed from earlier versions

Conform previously offered REDLINE and FFmpeg as additional export engines, with binary paths, auto-detection, and an engine priority order. Those engines have been removed. There is no binary path to configure, nothing to install alongside Scrub, and no per-engine settings. If you are following an older guide or screenshot, it no longer matches the plugin.

Adobe Media Encoder (AME)

Purpose: render each clip's used range — plus your handles — through an AME encoder preset, so the colorist receives trimmed media instead of full camera originals.

Enable it in the settings modal under Portable Output:

Setting Default Description
Queue needed clips in Adobe Media Encoder Off Queue every clip in the conform, using its exact handle-expanded source range.
AME Export Preset (none) The .epr preset each clip is rendered with. Required when queueing is on.

With queueing off, Conform still flattens, still builds the conform sequence, and still publishes the XML — the XML then references your original media rather than newly rendered files.

Selecting a preset

The preset dropdown shows all .epr files discovered from the system. Use Browse to select a preset file manually, or Refresh to rescan.

The folders that are scanned for .epr files are managed from the Export Preset Folders section inside the Conform settings modal. This list is shared with the Deliver module, so adding a folder in one place makes those presets available in both. See Deliver → Settings for how to add, remove, and rescan preset folders.

The preset must preserve frame rate and frame size

Scrub reserves each clip's output by exact frame range. A preset that changes the frame rate or the frame dimensions produces media that no longer matches the ranges written into the XML. Choose a preset that keeps the source frame rate and frame size.

How it works

  1. Scrub creates a MOV/ folder inside the run's output folder and reserves one output filename per clip.
  2. Each clip is queued to AME with its exact in/out points — the used range plus your start and end handles.
  3. When every clip reservation has been accepted, the FCP XML is published referencing those filenames.
  4. AME renders in the background.

Output container follows the preset

The output file extension is taken from the preset itself rather than assumed — an H.264 preset produces .mp4, a DNxHR preset produces .mxf, an audio preset produces .wav, and so on. The generated FCP XML references the same actual filenames, so re-import resolves correctly.

Queued is not rendered

AME accepting the queue is a handoff acknowledgement only. It does not mean the media has finished rendering, and Scrub does not verify the rendered files. Wait for AME to finish before importing the XML — the files it references may not exist yet.

All-or-nothing

If AME rejects any clip reservation, the XML is not published and the run reports "The XML was not published because Adobe Media Encoder did not accept every clip reservation." This is deliberate: a partially reserved run would produce an XML describing media that was never queued.

RED (R3D) footage

R3D clips are still detected and counted in the Preview step, but there is no separate RAW export path. Every clip — R3D or not — is queued through AME with the preset you selected.