evrExpanse User Manual v.6.0.0 - updated June 23, 2025

Installation

How to Install evrExpanse

Open the DMG file and drag & drop evrExpanse.app to the Applications folder.

Uninstalling evrExpanse

1. Locate the evrExpanse application in the /Applications folder.
2. Drag the evrExpanse.app file to the Trash bin.
3. Alternatively, you can right-click on the evrExpanse.app file and select "Move to Bin."

Please note that uninstalling evrExpanse will remove the application from your system while retaining the application preferences.

Grant Permissions

To ensure evrExpanse works correctly, macOS must grant it specific permissions. These allow access to essential system features like file management, user interaction, and automation. Without them, some functions may not work as expected.

If not already enabled, follow the steps below to configure Full Disk Access, Accessibility, and Automation permissions.

How to Grant Required Permissions

Full Disk Access

• Open System Settings → Privacy & Security → Full Disk Access
• Click the lock to make changes, then enter your admin password if prompted
• Drag evrExpanse into the list, or enable the toggle next to its name

Accessibility Permission

• Go to Privacy & Security → Accessibility
• Unlock to make changes, if needed
• Drag evrExpanse into the list, or enable the checkbox next to it

Automation Permission

• Go to Privacy & Security → Automation
• Under evrExpanse, check the box for System Events

Activating the License

Open the evrExpanse application, a startup window will open.

Upon clicking the Run button, a pop-up window will appear.

If you have a license key, please enter it along with the email address used for the purchase, then click Activate. Demo licenses also require activation.

If the inserted license key is validated, a message confirming the successful validation will appear.

Deactivating the License

Deactivating a license is an essential step, particularly during an upgrade from a type of license to another one. This process seamlessly reverts evrExpanse to its initial state, prompting users to activate a new license upon startup.

To deactivate the license, follow these simple steps:

1. Open the Preference panel in the application.
2. Locate the "Deactivate License" button.
3. Click on the "Deactivate License" button.
4. A confirmation message will appear, asking if you want to proceed.
5. After confirming your decision, a new message will appear, confirming the successful deactivation of the license.

Deactivating the license will revert it to an unactivated state, removing access to all premium features and benefits of the licensed version.

How to use

After clicking the Run button the main window will pop up.

Media Workflows

evrExpanse offers flexible tools to manage key stages of your media pipeline. You can run each process independently or combine them using Process Plus for a streamlined, integrated workflow.

Metadata Export

Extract metadata from a variety of sources—including multiple camera types—and import it into NLEs such as Final Cut Pro®, DaVinci Resolve®, Avid Media Composer®, Assimilate SCRATCH®, and Pomfort Silverstack®. This enhances metadata management and improves editorial workflows.

Transcode Master Files

Convert source files into intermediate codecs such as ProRes®, DNxHR®, GoPro CineForm®, HEVC (H.265), DPX®, or OpenEXR®, with support for MOV, MP4, MXF, and MKV containers. Embedded metadata and Finder Tags are preserved for seamless integration downstream.

Offload Data

Securely transfer and back up media using the xxh64 checksum to verify data integrity. This ensures your assets are safely offloaded and backed up.

Process Plus: Automate and Integrate

Use Process Plus to combine Transcode + Metadata Export or Offload + Metadata Export in one action, improving efficiency and maintaining metadata continuity throughout. This feature processes the files and then automatically exports the corresponding metadata. Ensure all transcoding/offloading and metadata settings are properly configured beforehand. The metadata export destination will match the output folder defined in your process settings.

Zero-Byte File Alert

Before any process begins, evrExpanse scans for and alerts you to any zero-byte files, which can indicate corruption or incomplete transfers. This safeguard applies to Transcode, Metadata Export, and Offload workflows.

Alerts are triggered before processing begins.

You can click “View Zero-Byte Files” to open a TextEdit document listing all affected file paths.

The tool continuously monitors for zero-byte files and includes them in the final report.

This proactive check helps maintain media integrity by ensuring that all processed files are complete and usable.

Quick Actions

evrExpanse offers five macOS Quick Actions that let you quickly set key folder paths—Source, Destination, and up to three additional Offload Folders—directly from Finder, without opening the app. These actions are added to your macOS Services (Quick Actions) menu and can be downloaded here: Download Quick Actions.

Available Quick Actions:

→ Set as 📁 Source Folder
→ Set as 📂 Destination Folder
→ Set as 📦 + Offload 1 Folder
→ Set as 📦 + Offload 2 Folder
→ Set as 📦 + Offload 3 Folder

How to Use:

Right-click any folder in Finder.

Go to Quick Actions and choose the desired option.

Examples:

• To set a media source: right-click ExternalDrive/Media/Day_02/ and select Set as 📁 Source Folder.
• For your output folder: right-click RAID/MainProject/Exports/ and select Set as 📂 Destination Folder.
• For backups: right-click your backup folder and choose one of the Offload actions. Repeat as needed for Offload 2 and 3.

Each Quick Action updates evrExpanse’s configuration file with the selected path. When you launch the app, your folder selections are already set—streamlining setup for Transcoding, Offloading, or Metadata Export.

Note:
If you use a Quick Action while evrExpanse is open, changes won’t appear immediately. To refresh, go to Preferences and then return to the main window.

To Remove a Quick Action:
Open ~/Library/Services/, find the relevant .workflow file (e.g., Set as 📂 Destination Folder.workflow), and move it to the Trash. The Quick Action will disappear from Finder.

Metadata Export

Selected Source Folder

To select the folder containing your media files in evrExpanse, simply drag and drop the desired folder from Finder into the designated area of the app. This makes selecting media for metadata export quick and easy.

Selected Export Format

Select the export format for the metadata file.

The available options are: Final Cut Pro (FCPXML or FCPXMLD), DaVinci Resolve (CSV), Media Composer (ALE), Silverstack (CSV), evrExpanse (CSV), Sony Real Time Metadata (CSV), SCRATCH Integration (.XML), and Extract LUT File from media (.CUBE).

Media Composer ALE Settings

Check the default values of Format, FPS or Bin Name. By default, the value of Bin Name is automatically filled with the name of the selected folder, but can be changed.

Assimilate SCRATCH Integration

By choosing SCRATCH Integration, an XML file with your media and metadata is sent directly to the SCRATCH Watch Folder. When you load your SCRATCH project, the files and metadata are imported automatically.

A copy of the XML is also saved in a folder named evrE_[ProcessedFolderName] for easy organization.

Transcode Master File

Selected Source Folder

To select the Source folder containing the media files you want to transcode in evrExpanse, simply drag and drop the folder from Finder into the designated area of the app.

Selected Destination Folder

To select the Destination folder for your transcoded media files in evrExpanse, simply drag and drop the desired folder from Finder into the designated area of the app.

Transcoding Mode

Smart

Smart Mode in evrExpanse analyzes the source file and decides whether to transcode or pass through the video and audio streams:

• Video: If the codec is an intermediate or mezzanine format (e.g., ProRes, DNxHR, CineForm), Smart Mode passes the video through without re-transcoding. If "Optimize for Final Cut Pro in Smart Mode" is enabled, only ProRes video is passed through for Final Cut Pro compatibility.
• Audio: If the audio is PCM (16-, 24-, or 32-bit), it is passed through. Otherwise, evrExpanse transcodes it to the selected PCM bit depth..

This mode avoids unnecessary re-transcoding and preserves quality whenever possible.

Manual

Manual Mode gives you full control: both audio and video are transcoded using your chosen codecs, bitrates, and settings.

Rewrap

Rewrap Mode passes through both audio and video at full quality, embedding metadata in the native and XMP formats (for Adobe Premiere Pro support). The output is in QuickTime (.MOV) format, except for MP4 input files, which remain in MP4 to maintain compatibility.

Include Source Metadata

The Include Source Metadata option lets you control how metadata is managed during transcoding.

When enabled:

• All source metadata is embedded in the transcoded file, preserving important camera information like CreateDate, camera model, lens info, and more.
• Finder Tags and file Flags from the source are also embedded, supporting Smart Collections and future reference.
• The filesystem creation date of the transcoded file is updated to match the original camera CreateDate, ensuring correct capture time in NLEs like Final Cut Pro and DaVinci Resolve.

When disabled:
evrExpanse skips metadata integration, which may slightly speed up transcoding and is ideal when only output-specific metadata is needed or original metadata is not relevant.

Transcode A/V Settings

Video Codec:

Select your preferred ProRes, HEVC, DNxHR, CineForm, DPX, or EXR profile. Available profiles follow the Apple ProRes white paper and Avid DNxHR specification.

• Apple ProRes
  Codec type: hardware accelerated (Apple VideoToolbox)
  Pixel format:
  • YUV 4:2:2 - 10-bit (ProRes 422 Proxy, ProRes 422 LT, ProRes 422, ProRes 422 HQ)
  • YUV 4:4:4:4 - 10-bit (ProRes 4444, ProRes 4444 XQ) with support for alpha channel
• Avid DNxHR
  Codec type: software accelerated (CPU)
  Pixel format:
  • YUV 4:2:2 - 8-bit (DNxHR LB, DNxHR SQ, DNxHR HQ)
  • YUV 4:2:2 - 10-bit (DNxHR HQX), YUV 4:4:4 - 10-bit (DNxHR 444)
• GoPro CineForm:
  Codec type: software accelerated (CPU)
  Pixel format:
  • YUV 4:2:2 - 10-bit (low, medium, high, film1, film2, film3+ )
  • RGB 4:4:4 - 12-bit (RGB 444)
• DPX:
  Codec type: software accelerated (CPU)
  Pixel format:
  • RGB 10/12/16 bit per channel
  • RGBA 8 bit per channel
• EXR:
  Codec type: software accelerated (CPU)
  Compression: Uncompressed/Zip1/RLE
  Pixel format:
  • RGB half/float (16/32 bit)
  • RGBA half/float (16/32 bit)
• HEVC (H.265) [available in Manual mode only]
  Codec type: hardware accelerated (Apple VideoToolbox)
  Pixel format:
  • YUV 4:2:0 8-bit per channel (High, Medium, Low)
  • YUV 4:2:0 10-bit per channel (High, Medium, Low)

Downscale Video Resolution

This option applies only in Manual Mode, resizing the output video only if the source exceeds the selected target, ensuring quality, compatibility, and reduced file size.

• As Source – Keeps original resolution.
• Downscale Profile – Precise control with:
  • Standard: 720p / 1080p (maintains aspect ratio).
  • Scaling: 50% (Half), 25% (Quarter).
  • Common Heights: 1440px 🖥️ QHD, 2160px 🖥️ 4K, 4320px 🖥️ 8K.
  • Vertical: 1280px 📱 HD, 1920px 📱 FHD, 3840px 📱 4K, 7680px 📱 8K.
  • DCI Scope: 858px 🎥 2K, 1716px 🎥 4K, 3432px 🎥 8K.

Downscaling is applied only when the source video's resolution exceeds the selected target, ensuring high quality, better compatibility, and reduced file size where necessary.

HEVC Bitrate

evrExpanse offers two ways to set the HEVC bitrate during transcoding:

1. Custom Bitrate
Manually enter your preferred bitrate in the Transcoding Options section for full control over video output size and quality.

2. Automatic with Profiles
Let evrExpanse automatically adjust the bitrate based on your video’s resolution and frame rate. Choose between High, Medium, or Low quality profiles—these are calculated adaptively for each video, ensuring a balance between quality and file size.

Note: High is based on a 4K UHD (3840x2160) reference bitrate of 24,000 Kbps at 30fps. Medium uses 50% of High, and Low uses 25%. The system automatically scales for other resolutions, frame rates, and aspect ratios.

10-bit HEVC Support
evrExpanse supports HEVC transcoding up to 10-bit. If your source is 10-bit, the Auto option preserves this color depth. For 8-bit sources, evrExpanse uses 8-bit output, avoiding unnecessary conversion.

Audio Codec

evrExpanse supports PCM audio in 16-bit, 24-bit, and 32-bit formats.

You can re-encode audio to any of these PCM formats, or

Use Passthrough mode to copy the original audio stream without re-encoding, preserving its original format and quality.

Audio is transcoded in a 1:1 configuration with the source, keeping the same number of tracks and channels as the original.
For image sequence formats (like DPX or EXR), audio tracks are exported separately as a WAV file, since audio can’t be embedded in these formats.

Burn-in Metadata Overlay

The Burn-in Metadata option overlays key metadata directly onto the video during transcoding, embedding it permanently into the output file. Common uses include displaying timecodes, camera settings, or applied 3D LUTs for quick reference during review or post-production.

This feature is especially valuable for collaboration, quality control, and workflows where visual access to metadata is essential.

3D LUT Application and Smart LUT Finder Features

evrExpanse adds advanced color grading tools with its 3D LUT Application and Smart LUT Finder features.

3D LUT Application

Burn a 3D LUT directly into your transcoded files for consistent color across all outputs.
Options include:

• Use Sidecar LUT: Automatically applies a LUT from the same folder as your media, matching filenames.
• Custom LUT Folder: Select a folder of LUTs, which are auto-matched to your media files.
• Apply LUT File: Use a single, user-defined LUT for all files in the batch, ensuring uniform color grading.

Smart LUT Finder

Smart LUT Finder simplifies color grading by automatically detecting and applying the correct LUT using video file metadata.

How It Works:

• Sidecar File Detection:
  evrExpanse looks for a sidecar .cube LUT file with a name that starts with your media file name.
  Example: For video123.mp4, valid LUT files include:
  video123.cube, video123_lut.cube, video123_custom.cube.
• Metadata-Based Extraction:
  For supported cameras (Kinefinity, McPro24fps, ARRI), if no matching sidecar is found, evrExpanse reads the video metadata to locate and extract the correct LUT.

Note:
Metadata-Based Extraction only works if "Include Source Metadata" is enabled during transcoding. This ensures the needed metadata is available for proper LUT handling.

Destination File Name

You can customize the name of transcoded files by adding custom text to the end of the original file name.

Example:
If your source file is A005C039_201101OZ.mov and you add "CamA":

• If "Preserve Source File Name" is disabled:
  [SourceFileName]_evrE_[CodecName_CodecProfile]_YourText.mov
  Example:
  A005C039-201101OZ_evrE_DNxHR_CamA.mov
• If "Preserve Source File Name" is enabled:
  [SourceFileName]_YourText.mov
  Example:
  A005C039-201101OZ_CamA.mov

This feature helps you quickly identify transcoded files and add context or notes for easier organization.

Duplicate Source File Name

When source files from different folders share the same name, naming conflicts can occur.

• If "Preserve Source Folder Structure" is enabled, evrExpanse keeps the original folder hierarchy, so files remain in separate subfolders and conflicts are avoided.
• If disabled, all transcoded files go into a single output folder. In this case, files with the same name could overwrite each other.

To prevent this, evrExpanse automatically renames duplicates using this format:
[SourceFileName]_(checksum_DupRefx)_YourText.mov

This guarantees every transcoded file has a unique name, even if the originals were identical.

Breakdown of the Naming Convention:

• SourceFileName: Original file name.
• checksum: A unique xxh64 hash of the original file, distinguishing files with the same name but different content.
• X (DupRef): A unique reference number for each transcoding process.
• YourText: Optional custom text you can add.

Example:
For a source file named A005C039-201101OZ.mov, the destination file might be:
A005C039-201101OZ_(38efdc3d5595ff1d_DupRef3)_CamA.mov

This convention helps:

• Identify identical files (same checksum, different DupRef):
  Clip0001_(38efdc3d5595ff1d_DupRef3)_CamA.mov
Clip0001_(38efdc3d5595ff1d_DupRef7)_CamA.mov
• Distinguish different files with the same name (different checksums):
  Clip0001_(38efdc3d5595ff1d_DupRef3)_CamA.mov
Clip0001_(3799dc67f0aaeafc_DupRef5)_CamA.mov

This ensures every transcoded file in the destination folder is unique and easy to identify, preventing data loss or accidental overwriting.

Offload

Source Folder

To select the Source Folder for offloading media files in evrExpanse, simply drag and drop the desired folder from Finder into the designated area of the app.

Destination Folder

evrExpanse lets you choose where your files are transferred, with support for:

• One primary Destination Folder
• Up to three additional Offload Destinations

This enables you to offload media to a working drive and multiple backups at once.

To assign each folder, simply drag and drop it from Finder into the corresponding field under Processing Options. You can enable or disable each destination using the checkboxes next to each path.

When you click "Start Process", evrExpanse will:

• Verify the source folder
• Apply your selected preferences (such as skipping hidden files or preserving Finder tags)
• Transfer files to all enabled destinations
• Verify the transfer at each step to ensure data integrity

Offload Summary Reports

After offloading, evrExpanse provides a clear summary based on your configuration:

Single Destination:
You’ll see a compact summary window with verification status, total files, processed and verified counts, and options to:

• Open Destination Folder
• Transfer Report
• Event Log

Multiple Destinations:
When using more than one destination, evrExpanse displays an overview indicating all folders were processed and verified.
Click Show Offload Summary to view a detailed breakdown for each destination, making it easy to confirm offload success at a glance.

Tip: In multi-destination setups, this summary helps confirm that each target location received the full file set, and flags any inconsistencies for quick follow-up.

Detailed Transfer Report

If "Save the Transfer Report to the destination" is enabled, evrExpanse generates a detailed report alongside the offloaded files. This report provides a comprehensive record of the transfer process.
You’ll receive a confirmation notification when the process completes, ensuring every transfer is documented for enhanced data integrity and transparency.

File Integrity Check & Duplication Handling

When a file already exists at the destination, evrExpanse performs a full checksum comparison—ignoring file size or modification date—to ensure both files are truly identical.

• If the checksums match, the file is considered verified.
• If the checksums differ, evrExpanse saves the source file as a duplicate at the destination, appending "2 (evrE copy)" to the file name.
• The checksums are then recalculated and compared again for complete accuracy.

This process ensures secure, incremental transfers and reliable duplication handling, maintaining bulletproof file integrity.

Apply Finder Tags

The Apply Finder Tags process in evrExpanse enables you to batch-apply macOS Finder tags—including both color tags and custom labels—to your media files. This makes it easy to organize, group, and locate your content directly in Finder.
You can access this feature directly from the main window. Apply Finder Tags is designed for seamless integration with metadata exported from DaVinci Resolve (CSV format), with support for additional NLEs—including Final Cut Pro, Premiere Pro, and SCRATCH—planned for future updates.

1. Export Metadata:

Export your metadata file from your NLE. For DaVinci Resolve, use the CSV export and ensure the file contains the Keywords column.

2. Import Metadata File:

In evrExpanse’s main window, drag and drop the exported metadata file (e.g., a DaVinci Resolve CSV) into the Source area.

3. Start the Process:

Click Start Process. evrExpanse will analyze the file and present a Pre-Processing Report showing:

• Metadata format and tag field
• Total files detected and files ready for tagging
• Duplicates removed (see note below)
• Any issues detected (e.g., missing columns, encoding problems)

🔎 Note: If the same file appears more than once in your metadata file (e.g., added to multiple bins in Resolve), evrExpanse will skip tagging that file entirely to prevent conflicting Finder Tags.
A detailed list of skipped duplicates is saved in the Duplicates Log inside your report folder.

4. Choose Tagging Mode:

Select how you want tags to be applied:

• Append: Add tags to any existing Finder Tags.
• Overwrite: Replace all existing Finder Tags with those from your metadata.
• Remove: Remove the specified tags from files (useful for undoing a previous Append operation).

5. Monitor Progress:

A real-time progress bar and status updates are displayed. You can cancel at any time.

6. View Final Report:

After processing, a summary window appears detailing the outcome. Detailed logs—including lists of missing or duplicate files—are saved in a report folder next to your metadata file.
The status of the operation is color-coded (green for success, orange for warnings, etc.) for easy review in Finder.

Log & Report Locations

After every Apply Finder Tags operation, evrExpanse creates a dedicated log/report folder next to your metadata file.

The folder is named [YourMetadataFile]_tag_report and contains:

• evrE_log_events_[YourMetadataFile]_[timestamp].log — Main event and result log
• evrE_missing_files_[YourMetadataFile]_[timestamp].txt — List of any missing files
• evrE_duplicate_files_[YourMetadataFile]_[timestamp].tsv — List of duplicate file references excluded from tagging

Example:
If your metadata file is at /Volumes/MyDrive/Project/metadata.csv,
the report folder will be:
/Volumes/MyDrive/Project/metadata.csv_tag_report/

You can open this folder directly from the final report dialog in evrExpanse, or locate it manually via Finder.

Additional Details & Best Practices

• Supported Metadata:
  Currently, DaVinci Resolve CSV (Keywords column) is supported. Support for other NLEs and metadata fields (e.g., FCPXML, ALE) is coming soon.

⚠️ Important – Double Quotes in Keywords (DaVinci Resolve CSV Export Bug):
Due to a known bug in DaVinci Resolve’s CSV export, using double quotes (") inside keywords can corrupt the exported CSV file. This may cause errors, skipped tags, or incorrect tagging during the Apply Finder Tags process in evrExpanse. To avoid issues, do not use double quotes in keyword fields in Resolve—replace them with single quotes or remove them before exporting your metadata.

evrExpanse will attempt to flag problematic entries during pre-check, but manual review and correction are strongly recommended.

⚠️ Note: When applying Finder color tags (such as Green, Red, etc.), please note that color tag names are localized according to your macOS system language.

Color tag names are language-specific.
For example, the color tag for “Green” is:

• Green in English
• Verde in Italian
• Vert in French
• Grün in German
• Verde in Spanish
• ...and so on for other languages.

Using the wrong language will not apply the colored Finder label.
If you use a color name that does not match your system language, it will be added as a plain text tag, not as a colored label.

No universal tag name exists.
There is no single color name that works for all macOS language settings.

Recommendations
Always use the color tag name that matches your macOS language.

• Duplicates:
  Duplicate file paths in the metadata are automatically excluded from tagging, and a log is generated for your reference.
• Missing Files:
  If a file listed in the metadata does not exist on disk, it is skipped and recorded in the missing files log.
• Validation:
  evrExpanse checks encoding, column presence, and file format structure. Warnings and errors are shown before tagging begins.
• Undo:
  Only Append operations can be reversed using Remove mode. Overwrite cannot be undone via evrExpanse.
• Full Logging:
  All processing events, errors, and actions are logged for easy troubleshooting.

Tip:
Always check the report folder after tagging to review the process details and resolve any issues.

Results

During each process, a progress bar displays the current status.
To stop a batch, click Stop. When prompted, click End and wait for the current file to finish. For best results, always allow the process to shut down properly—this usually takes just a few seconds.

Once finished, a completion window appears, with options to access processed files, review the event log, or view a detailed report.

Metadata Export Process

• After exporting metadata, a folder named evrE_FolderName is created in your destination.
• This folder contains the exported metadata in your chosen formats, ready for use in NLEs (Non-Linear Editing systems).

Transcode Process

• Transcoded files are saved in the destination folder.
• If Preserve Folder Structure is enabled, a subfolder named after the source folder will hold the transcoded files.
• A folder named evrE_FolderName will also appear in the destination, containing the event log and details about the transcoding process.

Offload Process

• A folder named FolderName_offload_report is created alongside the offloaded folder in the destination directory.
• This folder contains a report detailing the transferred files.
• For all processes, if media integrity verification is required, you’ll find a folder named ascmhl with ASC MHL files, or a single MHL file inside the offloaded folder.

Event Log

For every process, evrExpanse generates log files to help you track activities and troubleshoot if needed.

• For Metadata Export and Transcode processes, a log file named evrExpanse.log is created inside a sub-folder called evrE_FolderName within the processed folder.
• For the Offload process, a folder named FolderName_offload_report is created next to the offloaded folder in the destination directory. This contains a detailed log of the offload operation.

In addition to these “local” log files, evrExpanse also maintains a global Event Log. This Event Log collects and records all events from every process run on your machine, providing a comprehensive overview. You can easily access the Event Log at any time from the Preferences panel.

This dual logging system ensures you have both detailed, folder-specific logs for each operation and a centralized record of all activity for complete traceability.

Preferences

Before starting any process in evrExpanse, review the Preferences to confirm or adjust default settings.

General Preferences

Seal processed folder (MHLs)

Sealing a folder with an MHL (Media Hash List) creates a digital fingerprint of your files using cryptographic hashes, allowing you to verify file integrity and detect any changes later.

evrExpanse supports two MHL formats:

• ASC MHL – Modern standard by the American Society of Cinematographers (ASC) for robust media workflow consistency.
• MHL v1 – The original format, developed by Pomfort.

When enabled, folder sealing applies to Metadata Export, Transcode, or Offload processes.

Select MHL type and Hash Format

Within Preferences, you can enable or disable creation of ASC MHL or MHL v1 files.

• Each processed file receives its own hash list, saved alongside the media or in a specified folder.
• Disabling this option skips hash list creation, offering workflow flexibility.

Supported hash formats:

• ASC MHL: xxhash (64), xxh3 (64/128), md5, sha1, sha256, c4
• MHL v1: md5, sha1, xxhash, xxhash64be, xxhash64

Ignore Hidden Files and Folders

By default (when the option is not selected):

• ASC MHL automatically ignores system files like .DS_Store and the ascmhl folder.
• MHL v1 includes all files, but evrExpanse still filters out .DS_Store for consistency.
• The file evrExpanse.log is always included in both MHL types.

When the “Ignore hidden files and folders” option is selected:

• All hidden files and folders (not just .DS_Store or ascmhl) are excluded from the hash list, giving you extra control over what’s included in the sealed folder.

This setting helps you decide whether to include or exclude additional hidden items in your MHL sealing process, according to your workflow needs.

Comparing the behavior differences between ASC MHL and MHL v1 files or folders:

When creating an MHL or sealing a folder, evrExpanse checks for older MHL files and verifies all referenced files exist. Any issues are recorded in evrExpanse.log and the Event Log.

In order to commence the Metadata Export process within evrExpanse, it is imperative to ensure the fulfillment of a basic condition: activating either an export format, SCRATCH integration, or sealing the processed folder using your preferred MHL type.

ASC MHL Creator Info

In the ASC MHL settings, you can add Creator Info—details about the author, contact, location, or comments for better documentation and traceability. Choose your preferred hash format to match your workflow requirements.

CPU Allocation

The CPU Allocation option in evrExpanse manages how much of your CPU is dedicated to Transcoding, Metadata Export, and Offloading processes, optimizing performance based on your system.

CPU Load Profiles:

• Full: Uses all CPU threads for maximum performance—best for fast transcoding and export.
• High: Uses 75% of CPU resources, balancing speed and system stability.
• Medium: Uses 50% of CPU resources, reducing heat and preventing throttling.
• Low: Uses 25% of CPU resources—keeps your system responsive, ideal for multitasking or lower-end hardware.

When using hardware-accelerated codecs, CPU allocation has less effect, but it’s still important for software-based tasks.
For most users, High or Medium is recommended to avoid overheating and maintain stable performance during longer jobs.

Adjusting the CPU profile allows you to fine-tune evrExpanse for your specific hardware and workflow needs.

Custom FFmpeg Binary Folder

In the Preferences panel, you can customize the FFmpeg binary used by evrExpanse by setting a folder containing the desired FFmpeg binary. Simply drag and drop the folder from Finder into the designated field within the Preferences panel. If needed, you can revert to the default FFmpeg folder by enabling the Reset to Default checkbox, which will automatically restore the application’s original FFmpeg binaries.

Export Metadata Preferences

SCRATCH Integration

In the Metadata Export Preferences section of evrExpanse, you can configure settings for seamless integration with SCRATCH. This includes specifying the SCRATCH Watch Folder, which is pre-filled with a default location where evrExpanse will send media files and their associated metadata for automatic import into SCRATCH.

You can also define the SCRATCH project name, group, and timeline. It is essential to enter a valid and existing project name—matching exactly with what’s set in SCRATCH—to ensure the transfer completes successfully. Incorrect project names can result in a failed or incomplete upload.

Final Cut Pro XML

In the main window, clicking on the "Preferences..." button takes you to the "Metadata Export Settings" section where you can choose the desired Final Cut Pro FCPXML format (FCPXML v1.9, FCPXMLD v1.10, FCPXMLD v1.11, FCPXMLD v1.12 and FCPXMLD v1.13).

Process Transcode Preferences

YUV Format Preservation in Smart Mode

The "Preserve YUV Format" option provides greater control during transcoding in Smart Mode. When enabled, evrExpanse analyzes the input file and, if it is already in YUV format, it will bypass transcoding and directly copy the video stream to the output.

This saves time and system resources by avoiding unnecessary processing of files that are already optimized for delivery. It also helps preserve the original video quality and characteristics.

Maintain Final Cut Pro Compatibility in Smart Mode

When Smart Mode is enabled and the "Optimize for Final Cut Pro" option is selected, evrExpanse automatically transcodes media files using CineForm or DNx codecs to Apple ProRes. This ensures compatibility with Final Cut Pro, which does not support these codecs.

With this option enabled, only ProRes profiles will be used during transcoding, guaranteeing that your media is fully compatible for seamless import and editing in Final Cut Pro. This eliminates codec-related issues and simplifies workflow integration.

Rotate Transcoded Files According to Source Metadata.

When enabled, evrExpanse automatically applies rotation to transcoded files based on the source file's metadata, ensuring the correct orientation is preserved in the output.

This Auto-Rotation feature is only available during transcoding in Manual or Smart Mode. It does not apply when using Rewrap Mode or when no transcoding takes place. Because the rotation relies on metadata extraction during the transcoding process, it is skipped if transcoding is not performed.

Preserve Source File Name in Transcoded File

The "Keep Original File Name" option in evrExpanse ensures that transcoded files retain the same name as the source file, making it easier to track and organize media assets.

When enabled, the original file name is preserved. For example, a source file named example_video.mp4 will be transcoded to example_video.mov, maintaining consistency for easier identification.

When disabled, evrExpanse applies its default naming convention:

[SourceFileName]_evrE_[CodecName_CodecProfile].mov

This option is ideal for workflows that require file name consistency. For advanced customization, additional naming options are available in the evrExpanse settings.

Maintain Folder Structure

The "Maintain Folder Structure" option, found in the Preferences panel, ensures that your transcoded files mirror the original folder organization of your source media. This is especially useful for workflows that rely on structured directories for project management and archival.

HEVC Bit Depth

evrExpanse allows you to customize the bit depth when transcoding to HEVC. You can choose from the following options:

• Auto: Automatically matches the bit depth of the original file.
• 8-bit: Applies an 8-bit depth to all files in the batch.
• 10-bit: Applies a 10-bit depth to all files in the batch.

This flexibility ensures you can tailor the transcoding process to meet the specific needs of your project.

Process Offload Preferences

Ignore hidden files and folders

The "Ignore Hidden Files and Folders" option ensures that hidden items within the source directory—such as system files or configuration data—are excluded from the offload process. These files are typically not intended for user interaction and can clutter the destination if transferred unnecessarily.

By enabling this option, evrExpanse focuses solely on visible, user-relevant media, streamlining the offload and avoiding the transfer of unwanted or system-related data.

Include extended attributes

The "Include Extended Attributes" option ensures that Finder tags—such as color-coded labels used for organizing files—are preserved during the offload process in macOS. These tags help users categorize and visually identify files and folders.

Save the transfer report to the destination

When enabled, this feature saves a comprehensive transfer report directly to the destination folder, alongside the offloaded files. The report includes detailed information such as file names, timestamps, verification results, and any issues or errors encountered during the offload process. This provides full transparency and allows you to easily review and confirm the success and integrity of the transfer.

The Preferences Buttons

In the preferences panel there are three buttons (from left to right): Deactivate Licence, Event Log, Default Settings, User Manual and Return to Main Window

Deactivate Licence

See Deactivating the Licence

Event Log

Clicking the "Browse All Past Months Logs" button provides access to the application's comprehensive log file, which captures events from every process executed since the first run on the host machine. The Event Log is saved monthly using the naming convention Event Log YYYY-MM.log.

When you click the "View Current Month Log" button, a window will open, allowing you to view the current month's event log or browse logs from previous months.

The event log tracks all events for each process and is saved on a monthly basis. Additionally, a local log file is generated within the processed folder's report subfolder, providing detailed logs specific to each process.

Reset to Default Settings

The Reset Settings button is located in the Preferences panel of evrExpanse. Clicking this button will reset all application settings to their default values. This can be useful if you encounter issues with the software or simply want to revert to the original configuration. Note that using this feature will erase any custom settings you have configured, so it is recommended to use it with caution. To ensure the reset settings take full effect, it is necessary to reboot your Mac after performing the reset.

User Manual

In order to ensure a smooth user experience, we recognise the significance of comprehensive documentation. To facilitate easy access to information and guidance, we have introduced a User Manual Button in the Preference panel.

Return to Main Window

When clicked, it seamlessly guides the user back to the main interface or primary window of evrExpanse, ensuring easy access to essential features and functions.

Media Files and Camera Specifications

evrExpanse supports a wide range of media file types including MOV, MP4, MKV, NEV and MXF formats. Additionally, it is compatible with various camera models from popular manufacturers such as Panasonic, Nikon, Sony Alpha, Fujifilm, Canon, Sony XDCAM*, Z Cam, Kinefinity**, Atomos (Ninja & Inferno), McPRO24fps, GoPro, FiLMIC PRO, Apple iPhone, and ARRI.

While the Export Metadata feature is specifically tailored to the cameras mentioned above, the Transcoding functionality is available for all supported file types, including MOV, MP4, MKV and MXF.

For an up-to-date and comprehensive list of cameras supported by evrExpanse, please refer to our Camera Compatibility Tables.

How to import CSV file in DaVinci Resolve

1. Open Your Project:

Start DaVinci Resolve and open your project. Make sure the Media Pool is selected (indicated by a red line).

2. Import Metadata:

• To import metadata for all clips, go to File > Import Metadata To > Media Pool...
• To import metadata only for selected clips, choose File > Import Metadata To > Selected Clips...

3. Select the CSV File:

In the Import Metadata dialog, select the CSV file generated by evrExpanse and click Open.

4. Set Matching Options:

By default, DaVinci Resolve tries to match using both filename and clip start/end timecode.

• Uncheck “Match using clip start and end Timecode”
• Check “Match using source file paths”
  This ensures clips are matched correctly, since imported metadata may not include timecode.

5. Choose Merge Options:

Select how you want metadata to be updated:

• Only update metadata items with entries in the source file (recommended): Only updates metadata fields with valid entries in the CSV; all other fields remain unchanged.
• Update all metadata fields available in the source file: Overwrites all referenced fields for matching clips, regardless of value.
• Update all metadata fields available in the source file and clear others: Overwrites referenced fields and clears any other metadata fields not included in the CSV.

6. Complete the Import:

Click OK. Metadata from your CSV will be imported to the selected clips.

Finder Tag Integration:
If your media files are tagged in macOS with Finder Tags, these will appear in the Keywords and Flags sections within DaVinci Resolve. This makes it easy to organize, categorize, and locate tagged assets within your project.

How to import in Final Cut Pro

Importing media and metadata into Final Cut Pro using FCPXML is simple:

1. Double-click the exported .FCPXML or .FCPXMLD file. Final Cut Pro will open automatically and prompt you to choose the library for import.
2. Alternatively, you can import the FCPXML file directly from within Final Cut Pro via the application's import options.

Once imported, select your media in the browser.

• Metadata will appear in the information inspector, grouped under a new Metadata View called evrExpanse.

Note:
Any media files already present in an FCP event or timeline will inherit the imported metadata from the processed files.

You can further customize metadata views by opening the Metadata Views window and selecting "evrApp Properties" to add the imported metadata to any view as you prefer.

Creating a Smart Collection in Final Cut Pro Using evrExpanse Metadata

1. Export FCPXML from evrExpanse
   Export your media with embedded metadata in FCPXML format.
2. Import the FCPXML into Final Cut Pro
   • Via Menu: Go to File > Import > XML and select your exported FCPXML file.
   • Via Finder: Double-click the FCPXML file to open it directly in Final Cut Pro.
3. Verify Metadata
   Select a clip and check the Inspector to confirm metadata fields are populated.
4. Create a New Smart Collection
   Right-click your library in the sidebar or click New Smart Collection at the bottom.
5. Set Smart Collection Criteria
   Use dropdowns to set your filter (e.g., Text > All Text) and enter your desired metadata string.
6. Add Additional Criteria (Optional)
   Click "+" to refine filters. Add more Text > All Text conditions as needed.
7. Save the Smart Collection
   Close the window. The Smart Collection will now automatically update to include all clips that match your criteria.

Troubleshooting

Activating evrExpanse Metadata View in Final Cut Pro

If you’ve upgraded to evrExpanse from an earlier version or are importing metadata for the first time, you might not immediately see the new metadata in Final Cut Pro’s Inspector after importing your XML file. Don’t worry—your metadata is still there! You just need to activate or refresh the enhanced evrExpanse Metadata View. This is a one-time setup, and future projects will inherit the new view automatically.

How to Activate the Metadata View

1. Export Metadata from evrExpanse

• Launch evrExpanse and select your media’s source folder.
• Export metadata in Final Cut Pro format.

2. Import Metadata into Final Cut Pro

• Open Final Cut Pro.
• Double-click the exported .FCPXML or .FCPXMLD file to import both media and metadata.

3. Access Metadata View

• Select a clip in the timeline or browser.
• In the Info Inspector, open the Metadata View dropdown.

Activate Metadata View

• Choose Edit Metadata View… from the dropdown.
• In the list, find and select evrExpanse.
• Click OK to confirm and activate.

Note:
Steps 1 and 2 are required to "wake up" the enhanced evrExpanse Metadata View. Once completed, the new view and imported metadata will be available for all projects.

Refreshing Metadata Labels in Final Cut Pro

If your custom metadata fields don’t show updated names or labels after upgrading evrExpanse, follow these steps:

1. Open Final Cut Pro.
2. In the Info Inspector, open the Metadata View menu and choose Edit Metadata Views…
3. Select any old evrExpanse fields (e.g., Record date) and delete them
   (Right-click > Delete Custom Metadata Field).
4. Close and reopen Final Cut Pro.
5. Import the updated FCPXML exported by evrExpanse.

Your updated metadata labels will now display correctly in the Info Inspector.

How to import in Assimilate Scratch

Importing multimedia files and metadata into Assimilate SCRATCH is even easier than with Final Cut Pro. Once evrExpanse completes the export, the XML file is placed in SCRATCH’s Watch folder and automatically loaded when the app and project are opened.

Just ensure the project name in evrExpanse matches the one in SCRATCH—done! The media and metadata appear in the right panel.

A backup XML is also saved in the processed folder (evrE_FolderName) for use on other workstations.
After processing, SCRATCH logs the import in Scratch_insert_log_FolderName.log within the same folder.

How to import ALE file in Avid Media Composer

After having created the .ale file in evrExpanse, go to the Avid Media Composer and import the clips if not done so far. They should thereon be available as master clips.

Select the bin in the Avid Media Composer which contains the relevant clips.

Select those clips and choose “Input > Import Media…” from the context menu in the bin.

Open the “Options”, then click on “Options…” navigate to the Shot Log tab and select

“Merge events with known master clips”.

Navigate to the ALE file you created before and click “Open”.

Avid Media Composer now matches master clips and metadata information from the .ale file according to their TimeCode, Bin Name and Name of clip.

The information from the .ale file is attached within additional columns in the bin table. Some of the columns are already known by the Avid Media Composer, all unknown information will be added as custom columns.

If you cannot see any custom columns, perform the following steps:

1. Close and re-open the bin
2. Right-click in the free space of the bin window and click on “Choose columns…” in the context menu.
3. Then select and unselect columns, the custom columns from the imported .ale file you will find at the end of the list.

How to import CSV file in Silverstack

After having created the .csv file in evrExpanse, go to the Silverstack Composer and import the clips if not done so far.

To be able to import metadata evrExpanse will use the Drylab CSV import feature in Silverstack.

Select the folder or bin in the library of Silverstack that you want to import metadata for.

Then, in the “Import” menu button in the toolbar select the option Drylab CSV:

When the Finder dialog points you to select a file, choose the CSV file exported from evrExpanse and select “Open”.

There are two options to match the events in the CSV to the clips in the library:

• by Clip Name
• by Creation Date

Select Clip Name and Creation Date (Date only) and click “Continue”.

Import Section: In this step you can select or unselect the metadata that should be imported from the CSV to the Silverstack library.

evrExpanse metadata are under the sections:

• Camera Settings
• Lens and Filter
• Comment and Caption
• Append Tags
• Day Number + Day Date (as Custom 1)

Insert/Update Behavior: Choose if you only want to insert new metadata if a fields is empty or you want to force an overwrite.

Select the option in bold and click "Finish"

If the media files have been tagged using the macOS Finder Tag, the information will be reported in Tags column in Silverstack.

Canon XF Utility Integration Workflow

📌 Applicable to Canon EOS Cinema cameras prior to the C80 and C400 series, including: C300 / C500 / C200 / C700 / C70 / R5 C and others.

Note: Canon C80 and C400 (2024) embed metadata directly in the MXF files — evrExpanse natively supports those without this integration.

Prerequisites:

• Download Canon XF Utility from Canon’s official site.
• Install Canon XF Utility and the latest evrExpanse on your macOS system.
• Store your .MXF clips in their original folder structure, including the INDEX.MIF file.
• Ensure you have write permissions for creating symlinks (if needed).

Workflow Steps

1. Open Canon XF Utility

• Launch Canon XF Utility.
• Load the card or folder containing your .MXF files.
• Important: The INDEX.MIF file must be present. Without it, Canon XF Utility will not recognize or load the clips or metadata.

2. Set Preferences in XF Utility

• Frame Grab 1 tab:
  • File Type: Set to JPEG
  • Image Quality: Set to 1 (metadata is preserved at any quality)
  • Folder for Frame Grabs: Set your export path
    (Default: /Users/username/Documents/Canon/XFUtility/Photo)
• Frame Grab 2 tab:
  • File naming is not critical; evrExpanse matches by folder structure, not filename.

3. Manually Grab a Frame for Each Clip

• Select each clip in Canon XF Utility.
• Click "Grab a Single Still Frame" at the bottom of the interface.
• Note: Batch frame grab export is not supported. This step must be done manually for each clip.

4. Make JPGs Accessible to evrExpanse

Option A: Copy/Move JPGs

• Place the JPGs inside any folder or subfolder within your selected Source Folder in evrExpanse.

Option B: Create a Symlink

ℹ️ Note: A symlink (symbolic link) is not the same as a macOS Alias. Symlinks behave like actual folder paths at the system level, which evrExpanse can follow reliably. In contrast, Aliases are macOS-specific pointers that may not work correctly in automated workflows.

• Create a symbolic link (not a macOS Alias) from the XF Utility’s frame grab folder.
• Move the symlink into the Source Folder you will use in evrExpanse.
• Tip: This is a one-time setup if your XF Utility export path stays the same.
• A Quick Action is available to download to automate this symlink creation.

5. Run Export or Transcode in evrExpanse

• In evrExpanse, select the Source Folder containing your Canon MXF footage and either the actual .JPG files or the symlink folder.
• Run Export Metadata or Transcode as needed.

What evrExpanse Does

• Automatically matches .JPG frame grabs with corresponding .MXF clips.
• Extracts enhanced metadata using these matched pairs.
• Embeds enhanced metadata into transcoded files (when transcoding is performed).