Reference

Validation Messages

Before a session can start, evrExpanse continuously validates the current configuration. Problems are surfaced in two places, depending on what they refer to:

• Inline card alerts — shown as an orange sub-line directly under the affected path card (Source, Offload, Transcode, or an additional destination). These point at a specific folder or volume.
• Bottom-bar messages — shown along the bottom of the Workflow tab for problems that are global to the session or tied to the Transcode / Export options rather than to a single card.

Almost every message listed below prevents the session from starting until it is resolved: the Start button stays disabled while any of these conditions is active. The few purely informational cases are called out explicitly.

Inline card alerts

These appear under the relevant path card and always refer to that card's folder or volume.

The disk-space and duplicate-volume alerts use the same wording on every card; the card the alert sits under identifies which folder is affected.

Path not set or not found

When a required folder is not yet chosen, evrExpanse shows a guidance hint rather than an error, and the Start button stays disabled:

If a folder was chosen but no longer exists on disk (renamed, unmounted, or moved), the card instead shows an invalid-path alert:

Transcode option messages

Shown in the bottom bar when a Transcode option is incompatible with the selected mode or workflow. The control that needs attention is also outlined in orange in the Transcode card.

Workflow compatibility

Shown when Transcode and Export are chained but the chosen output or export option cannot be combined.

Environment and tooling

Export configuration

In addition, the Start button stays disabled if Export is active but no export format is selected. Choose at least one format in the Export card to proceed.

Supported Cameras

evrExpanse extracts and maps camera-specific metadata for the following manufacturers:

Panasonic · Sony Alpha · Sony XDCAM · Canon · Nikon · Fujifilm · ARRI · Z Cam · Kinefinity · Atomos Ninja & Inferno · McPRO24fps · GoPro · Apple iPhone · FiLMiC Pro · Blackmagic Camera App

For the complete and up-to-date compatibility table including specific camera models and supported metadata fields, see the Camera Compatibility page.

Supported File Formats

Metadata Export and Apply Finder Tags

Default formats are always processed. The way optional formats are handled depends on the workflow:

• Metadata Export processes an optional format only when it is enabled in the Source Formats section (Workflow tab) or in Preferences → Metadata Export.
• Apply Finder Tags always processes every optional format, regardless of the Source Formats selection. This ensures no file is left untagged simply because its format was disabled for a different workflow.

Transcode Input

MOV · MP4 · MKV · MXF

Transcode Output Containers

MOV · DPX · EXR

Export Format Field Reference

This section documents the exact field layout written by each export format. Column order is fixed and matches the order shown below. Empty fields are written as empty values, not omitted — every row always contains every column.

Camera-specific availability varies: a field is populated only when the source camera records that metadata. The example values below are representative of a typical cinema/mirrorless clip and are illustrative only.

evrExpanse TSV (.tsv)

Tab-separated. The master format — contains the full field set and is the recommended input for Apply Finder Tags. One header row, one row per clip.

Notes: e.Tag carries the macOS Finder Tags of the file; e.Flags carries Finder color labels. e.XMP_Subject and e.Camera_Notes preserve commas; other multi-value fields have commas substituted to protect the column structure.

DaVinci Resolve CSV (.csv)

Comma-separated, comma-quoted. Import via File → Import Metadata To → Media Pool or Selected Clips. One header row, one row per clip.

Notes: Keywords is derived from macOS Finder Tags; Flags from Finder color labels. In DaVinci Resolve's import dialog, uncheck Match using clip start and end Timecode and check Match using source file paths.

Pomfort Silverstack CSV (Drylab, .csv)

Semicolon-separated. The file begins with two identity lines (evrExpanse and the product URL) before the header. Import via the Import menu → Drylab CSV; match by Clip Name and Creation Date (Date only).

Notes: dutch carries camera rotation/position. File preamble lines (rows 1–2) are part of the Drylab format and must remain for Silverstack to parse the file.

Avid Media Composer ALE (.ale)

Tab-delimited Avid Log Exchange. Three sections: a Heading block (delimiter, video format, FPS), a Column block (the field header row), and a Data block (one row per clip). Format, FPS, and Bin Name are set in the Export block before running.

Heading block:

Heading
FIELD_DELIM TABS
VIDEO_FORMAT    1080
FPS 23.976

Column
<header row — see table>

Data
<one tab-delimited row per clip>

Column layout:

Notes: standard ALE columns (Tape, Start, End, Bin Name) use Avid-native names; evrExpanse-specific columns are prefixed e_ and appear as custom columns in the Media Composer bin. Import via Input → Import Media…, then in Options open the Shot Log tab and select Merge events with known master clips.

Final Cut Pro FCPXML / FCPXMLD

XML. Versions 1.10 and later are written as .fcpxmld bundles (containing Info.fcpxml); 1.9 is a flat .fcpxml file. Each clip produces one <asset> (with an evrExpanse metadata block) and one <asset-clip> (with FCP-native production metadata).

evrExpanse metadata keys on the <asset> (namespace com.evrApp.evrExpanse, all type="string"):

FCP-native keys on the <asset-clip>:

The <note> element on each <asset-clip> carries the camera rating (e.g. star rating) followed by comments. To view the evrExpanse fields in FCP: select a clip, open the Metadata View dropdown in the Info Inspector, choose Edit Metadata Views…, and enable evrExpanse.

Assimilate SCRATCH XML (.xml)

XML insert command sent to the SCRATCH Watch Folder (and copied locally). The document wraps construct → slots → slot → shots → shot → metadata, with one <slot> per clip. Project, Group, and Timeline names come from Preferences → Metadata Export; the Project name must match the existing SCRATCH project exactly.

Per-clip <metadata> keys (<dataitem> key/value pairs):

Notes: SCRATCH receives a compact production-metadata subset rather than the full field set. The local copy in evrE_FolderName can be used to import the same data on other workstations.

Sony RTMD CSV (.csv)

Comma-separated, transposed — each row is one metadata parameter, columns are per-frame samples (Real-Time Metadata is sampled per frame). One *_rtmd.csv file per Sony clip, saved to the Sony RTMD folder. Generated only for Sony source media.

Parameters (row order):

Notes: because the file is transposed, the first data column corresponds to the first recorded frame and subsequent columns advance frame by frame. Sony RTMD .csv files are written to the log folder inside the source directory, not to the evrE_FolderName export subfolder.

Extract LUT (.cube)

Not a tabular format. Extracts the embedded 3D LUT from supported camera media (Kinefinity, ARRI, McPRO24fps) as a standard .cube file, saved in evrE_FolderName. The file is the camera's native LUT; evrExpanse does not rewrite or re-grade it.

MHL Hash Format Reference

ASC MHL

MHL v1

Keyboard Shortcuts

TC Mode Reference

TC Mode is configured in Preferences → General and applies globally to Export Metadata and Transcode.

Log warnings — Time-of-day mode:

Third-Party Components

evrExpanse bundles the following third-party tools. For the full declaration see the Third-Party Software Declaration page.