Reports & Logs

evrExpanse keeps a complete record of every work session. At the end of each session it saves a Session Report — a structured summary of everything that happened — and it continues to write detailed logs for each workflow. Both are accessible from the Reports & Logs window.

Table of Contents

The Reports & Logs Window

Open it with ⌘⇧L or from Window → Reports & Logs.

The window has two areas, chosen from the selector at the top:

  • Session Reports — one report per work session, in a three-pane layout: the list of sessions on the left, the report in the center, and the log of the selected step on the right.
  • Logs — the raw log files, shown as text with per-line color coding. A search field filters the visible lines in real time.

Live interactive mockup — click the sidebar tabs to explore each report type.

Click blocks to expand, run a simulated session, and explore Preferences. [ Open in a floating window ↗ ]

Session Reports

A Session Report is a persistent record of a single work session, saved automatically when the session ends. Each report captures the source, the workflows that were planned, and the outcome of each one.

The session list

Each session in the sidebar shows, at a glance:

  • a status symbol for the overall outcome — 🟢 completed successfully, ⚠️ completed with exceptions, 🔴 completed with errors, 🟡 cancelled
  • the time, and the source volume and folder
  • a badge for each planned workflow (Offload, Transcode, Export), colored by its individual outcome
  • a shield icon summarizing folder sealing, when sealing was planned — green (sealed), yellow (sealed with exceptions), orange (failed), or grey (planned but not run)

The report

Selecting a session shows its full report in the center pane, with a section for each workflow:

  • Offload — per-destination totals: files copied, verified, transferred, data size, and verification status
  • Transcode — files transcoded out of the total, codec, and result
  • Export Metadata — files exported, active formats
  • Folder Sealing — the sealed folders, their MHL type and hash, and the sealing outcome

Sections that were planned but did not run — for example after a cancellation — are shown as N/A — not run, so the report always reflects the full intended composition of the session.

Opening a step's log

Within a report you can click an offload destination, the transcode, the export, or the folder sealing to open its log directly in the right-hand pane. These logs are read from the central repository, so they remain available even after the delivery disk has been disconnected.

Session status

The overall session status reflects what actually happened across all steps:

Status Meaning
🟢 Completed successfully All steps finished without issues
⚠️ Completed with exceptions A step reported a recoverable issue (partial or empty transcode, cancelled export, or sealing completed with exceptions). The copied data is intact.
🔴 Completed with errors An offload verification failed (a file did not match its checksum). This is the only condition treated as an integrity failure.
🟡 Cancelled The session was cancelled during a step

Folder Sealing states

MHL folder sealing reports three distinct outcomes:

  • Sealed — the manifest was created and matches its history
  • Sealed with exceptions — the manifest was created, but the tool reported notes against the history (for example, files referenced previously that are now missing). The full detail is in the sealing log.
  • Failed — no manifest was produced

Logs

The Logs area is the evolution of the previous log viewer. It lists four categories in the sidebar, selectable like before:

  • Event Log — global timestamped log of all sessions
  • Offload Reports — per-session Transfer Reports from Offload
  • Tag Reports — per-session reports from Apply Finder Tags
  • Zero-Byte Logs — reports from zero-byte file scans

Selecting a file displays its content in the detail pane with per-line color coding — green for success, yellow for warnings, red for errors. A search field filters visible lines in real time.

Transcode, Export and Folder Sealing logs are not listed as separate categories here. They are opened from the corresponding section of a Session Report (see Opening a step's log above).

Log Structure

Each log entry follows this format:

HH:MM:SS - [status emoji] Description of event

Status indicators used in logs:

Indicator Meaning
✅ Success
⚠️ Warning — process continued
❗ Error — process stopped
🔴 Verification failed
⛔ Critical failure

Session Header

Every log file opens with a session header:

---------- evrExpanse 7.x.x — macOS:xx.x —  system:CPU model with N cores and N threads —  process started YYYY-MM-DD HH:MM:SS ----------

Local Logs

Each workflow also writes a local log inside the processed folder, alongside the media.

Offload — a Transfer Report folder at the destination:

DestinationFolder/  
 SourceFolderName_offload_report/  
   Offload Report YYYY-MM-DD at HH.MM.SS — VolumeName — FolderName.txt

Transcode — a uniquely-named log inside the destination's evrE_ folder:

DestinationFolder/  
 SourceFolderName/  
   evrE_SourceFolderName/  
     evrExpanse_YYYYMMDD_HHMMSS_transcode.log

Export Metadata — a uniquely-named log inside the source's evrE_ folder:

SourceFolderName/  
 evrE_SourceFolderName/  
   evrExpanse_YYYYMMDD_HHMMSS_export.log

Global Repository

All logs and reports are grouped under a single Logs & Reports folder in Application Support. The table below lists every folder on disk. Items marked (viewer) are browsable from the Logs area; the others are opened from a Session Report or kept as the central, durable copy.

Category Path Access
Session Reports …/Logs & Reports/Session Reports/ Session Reports area
Event Log …/Logs & Reports/Event Log/ Logs area (viewer)
Transfer Reports …/Logs & Reports/Transfer Reports/ Logs area, as Offload Reports (viewer)
Tag Reports …/Logs & Reports/Tag Reports/ Logs area (viewer)
Zero-Byte Logs …/Logs & Reports/Zero-Byte Logs/ Logs area (viewer)
Transcode Logs …/Logs & Reports/Transcode Logs/ From Session Report
Export Logs …/Logs & Reports/Export Logs/ From Session Report
MHL Logs …/Logs & Reports/MHL Logs/ From Session Report

(Full base path: ~/Library/Application Support/EVRapp/evrExpanse/Logs & Reports/)

Session Reports are saved in dated subfolders and named Session YYYY-MM-DD at HH.MM.SS. Event Log files are named Event Log YYYY-MM-DD.log. Transfer Reports and Tag Reports use the format Report YYYY-MM-DD at HH.MM.SS — VolumeName — FolderName. Transcode, Export and MHL logs are saved in dated subfolders with a unique timestamped name.

Offload Log Entries

A typical offload log records:

  • Session start and configuration
  • Per-file transfer and verification status
  • Total files transferred, verified, and failed
  • Elapsed time
  • MHL generation result if sealing was enabled
  • Exit code and description on completion

Transcode Log Entries

A typical transcode log records:

  • Session start, codec, and TC Mode configuration
  • Per-file transcode start, completion, and duration
  • LUT application result if enabled
  • Metadata embedding result
  • TC time-of-day warnings if CreateDate was unavailable
  • Total files transcoded and elapsed time
  • Exit code and description on completion

Export Log Entries

A typical export log records:

  • Session start, active export formats, and TC Mode
  • Per-file metadata extraction result
  • TC time-of-day warnings if CreateDate was unavailable
  • Per-format file open and close confirmation
  • Total files exported and elapsed time
  • Exit code and description on completion

Transfer Report

When Save Transfer Report to Destination is enabled in Offload Preferences, a CSV report is saved at the destination and a copy is stored in the global Transfer Reports folder. The report contains one row per file:

  • Source path
  • Destination path
  • File size
  • Source checksum (xxh64)
  • Destination checksum (xxh64)
  • Verification result
  • Timestamp

Apply Finder Tags Reports

After every Apply Finder Tags session, a report is saved locally next to the metadata file and a copy is stored in the global Tag Reports folder.

Local report folder:

MetadataFile_tag_report/  
 Tag Report YYYY-MM-DD at HH.MM.SS — VolumeName — FolderName.log  
 evrE_missing_files_${CSVfileName}_${datelog}.tsv  
 evrE_duplicate_files_DateTime.tsv

Zero-Byte Logs

Before any session starts, evrExpanse scans the source folder for zero-byte files. When any are found, a report is saved in the global Zero-Byte Logs folder.

Report format:

Zero-Byte Files Report — DD Mon YYYY at HH:MM:SS  
Volume: VolumeName  
Folder: FolderName  
Path:   /full/path/to/folder  
Total:  N zero-byte files

/full/path/to/file1.mp4  
/full/path/to/file2.mp4

When no zero-byte files are found, the report records Total: 0 zero-byte files and No zero-byte files found.