code.matx.ca

A SwiftUI macOS application designed to verify which files have been archived by Archiware P5. Simple drag-and-drop interface to check folders against your P5 Archive with detailed reporting.

Two separate apps, each with its own updates. P5 Archive Manager CLI (v3.7.2 build 6) is the established nsdchat edition and remains the stable choice. P5 Archive Manager API (v4.5.0 build 67, beta) is where new development happens: it connects over the network and can search every configured archive index without local CLI access to the P5 server.

Restore from Project File. Drop the project an editor delivered — a Resolve .drt timeline, a Resolve or Premiere XML, a Final Cut Pro .fcpxml or .fcpxmld bundle, or a plain text list of paths — and the app finds each media item in P5, across every archive index. Each row says what to do: needs to be restored — not in its original location, in its original location, or not in P5. Prepare Restore shows versions, archive dates and tapes, and whether each tape is online, then one P5 job restores everything to the original location or into a folder on a P5 client, and the app follows it to the end.

What is read from each file. Resolve or Premiere XML: every pathurl. Final Cut Pro .fcpxml: every original-media reference, with proxies ignored. Final Cut Pro .fcpxmld bundle: the Info.fcpxml inside it. DaVinci Resolve .drt (a zip): every MediaFilePath. Text, TSV, CSV or log files: one absolute path or file:// URL per line. P5's own media-list restore accepts an XML or FCPXML but not a .fcpxmld or .drt, and knows nothing about RED clips.

RED clips come back whole. A RED clip is a .RDC folder of _001.R3D, _002.R3D and so on, but a timeline names only _001.R3D, and restoring that one file gives a clip that stops after its first segment. With Restore the whole RED clip folder on (the default), any .R3D inside an .RDC folder is replaced by the whole folder. The row shows how many segments P5 holds and which ones the project named, and on LTO it is one linear read instead of many single files.

Media that was moved or imported before it was archived is found by name through P5 volume-inventory TSVs, through P5 Archive Browser's tape catalogue when it is on the same Mac, or from a location pasted from the P5 web app. Restore into a folder first: restoring to the original location of imported media has not yet been tested against a live server.

Imported volumes, through the REST API alone. P5 does not list the volumes of an Imported-Volumes index over REST, so Find imported volumes… tries each volume's label as a top-level name and keeps the ones the index answers for. Media that was moved before it was archived (into a “To Archive” folder, say) is then found by listing those volumes for the project's folders, and every path is confirmed with P5 before an item counts as archived. On a real project file, all 53 items were found this way with the TSVs and the Browser catalogue turned off, and Prepare Restore and Restore into a folder worked on them.

The REST API edition adds a complete proof-first lifecycle. Delete local copies that are already verified in P5, then submit files that are not yet archived directly to a configured P5 plan and client, monitor the archive job, re-check the files, and delete the newly archived local copies only after P5 proof is confirmed.

The REST edition keeps an ordered list of historical archived locations for each server. If the current or mapped path returns no archived files, Archive Manager automatically checks those older storage roots and reports which locations were tried, which one matched, and why the others did not.

An archive plan can be configured in P5 to delete at the source — either the archived files, or the files and their folders. Archive Manager reads both flags, names in the plan picker and the confirm dialog exactly what a plan removes, and blocks such plans by default: P5 performs those deletions itself, without this app's proof report or receipt. The guard can be turned off in Settings ▸ Archiving.

Each server chooses HTTP or HTTPS, with certificate inspection, explicit trust and Forget Certificate. Redirects are refused, and there is no automatic fallback to HTTP.

Server lists and site settings. The REST edition reads and writes the P5Servers.json file shared with P5 Health Check, P5 Archive Search and P5 Archive Overview, so servers set up once are not typed in again; a file in /Users/Shared or Documents is offered when the app opens, showing which servers it would add before anything changes. For administrators, a P5SiteSettings.json supplies the TSV inventory folder, path mappings and historical locations for every server or for one. Operators' own mappings stay editable, settings are suggestions unless a configuration profile holds them, and Settings can import a site file into place or export one from a Mac that is already set up. Passwords and pinned certificates are never in either file.

A SwiftUI macOS application designed to query current and recent archives via the P5 REST API. Monitor archive job status, view pool usage, and maintain historical records of archive operations.

Uses the Archiware P5 REST API endpoint /rest/v1/archive/overview to retrieve archive job data, making it accessible from any machine on the network without requiring CLI installation.

A SwiftUI macOS application for browsing and searching P5 Archive Index inventory. Navigate through archived directories with a familiar file browser interface and maintain a local SQLite database for fast offline searching.

Uses the P5 REST API endpoint /rest/v1/archive/indexes/{index}/inventory/{path} to browse archive contents. Features breadcrumb navigation, double-click to drill down into folders, and comprehensive search functionality.

Search now restores. Right-click an archived file in Browse or in Search DB and choose Restore from P5, or submit a whole folder as one directory handle and let P5 perform the recursion. Before anything is submitted, the app asks P5 which tape the item is on, whether it is online and where it is, so a restore that will wait for a cassette says so rather than looking stalled. Progress names the tape P5 is loading, a job still running when the window closes is picked up again at next launch, and every attempt — including the ones that did not finish — is kept in Restore History.

Restore is new. Try it on a small folder you can afford to lose, and keep your own backup.

Imported volumes. An imported-volumes index is rooted at each volume's label rather than at a folder such as Volumes, and P5 does not list those labels over REST, so a scan had to be given each one by hand. Find imported volumes… in the server sheet tries each volume's label as a top-level name in the index and adds the ones it answers for as scan paths and browse roots; a pasted list covers a label it cannot find. The drive-icon menu lists them below Volumes and mnt, with a Scan all item that puts them into search.

A failed request says why. The log shows the HTTP status and what it means, or the cause when there was no answer (P5 answers a wrong password with HTTP 400, not 401), and every request the app makes is recorded in the system log without the password.

Each server chooses HTTP or HTTPS, with certificate pinning for P5's self-signed placeholder certificate. Servers configured before this keep working unchanged.

A native macOS app for browsing the contents of P5 Archive volumes, usually LTO tapes. Import per-volume TSV inventories, search filenames and paths across the complete local catalog, and identify the exact tape to load for a restore.

The Browser combines fast SQLite-backed offline navigation with an optional P5 REST connection. Organize tapes into archive groups, add operator-owned aliases and location notes, review catalog data sources, and safely import matching volume-list CSV metadata.

Restore straight from the catalog. Right-click a folder and restore its whole subtree in one request, or restore a project from the search result that found it. Restore is off by default and enabled in Settings ▸ Restore. The confirmation sheet gives the expected file count and bytes, the tape's online state, your own location note and P5's last known slot, and says plainly that P5 waits for an offline tape. After the job the Browser reconciles what arrived against what was expected rather than trusting the job's own result.

Everything else the Browser asks P5 is read-only — refreshing volume metadata and verifying selected paths change nothing on the server.

Works with P5 Archive Manager API. When the Browser's catalogue is on the same Mac, Manager API's Restore from Project File uses it to find media that was moved before it was archived. The Browser is still in beta: restore only what you can afford to test with, and keep your own backup.

A SwiftUI macOS application that reads the Archiware P5 resources.db database and exports archive job data to CSV. Features a full dashboard with sidebar query browser, results table, progress reporting, and a filterable log viewer.

Ships with 14 analytical queries covering throughput, weekly volume, storage growth, tape utilization, size distribution, and stale job detection. Add custom SQL queries with the {{MIN_SIZE_KB}} placeholder for configurable size thresholds.

Charts. A Charts tab draws archived volume per week, month, quarter or year, cumulative growth, outcome by year, and where the volume sits by size range. Quiet periods are shown, not skipped. The charts come straight from the database, or from a folder of exported CSVs on a machine that never sees the database. Every export run also writes the chart data as CSV, plus a self-contained HTML dashboard and a PDF of it. These sit beside the existing CSV analysis by week, month and year and the per-volume TSV inventory export.

Keep the server's queries current. Deploy to Server writes the bundled queries straight into the server's query folder. A signed, notarized installer package does the same through the macOS installer, and leaves a receipt showing which query set a server has.

Charts without the app. A standalone script, p5chart.py, draws the same weekly, monthly, quarterly and yearly charts as a self-contained HTML dashboard from the P5 job database or from a folder of exported CSVs, and can find which resources.db on a server holds the job history. The exports now carry plain numeric columns beside the formatted ones, so the CSVs chart cleanly in a spreadsheet too, and a weekly volume query was added.

Both apps have an in-app user guide and What's New under the Help menu.

Also includes a Volume Inventory Export powered by nsdchat — export per-volume TSV inventories to dated run folders for snapshots or a standard VolumeExport folder for incremental runs. Sort by LTO generation, filter archive-only volumes, export a volume list CSV, and optionally copy outputs to a network destination.

The backup workflow creates compressed archives of the local P5 config and log folders, with optional clip exclusion and separate clip backup support for migration, disaster recovery, and regular server snapshots.

A lightweight menu bar companion that provides the same SQL, volume inventory, and backup export engines as the windowed app, accessible from an always-visible archive box icon. No Dock presence — click the icon to open a popover with status, one-click exports, and inline settings.

Shares the same P5ExportCore library and settings as the full Mac app. Add it to Login Items for unattended, always-on scheduling on your P5 server.

P5 Health Check provides quick operational visibility into one or more P5 servers. It includes a full Mac app (P5Window), a menu bar monitor (P5MenuBar), an iPhone companion app (P5iPhone), and a CLI script (p5_health_check.sh) for terminal automation.

The tools surface actionable signals including server uptime, drive cleaning requirements, warning/error jobs, and tape mode pressure across Appendable, Readonly, and Full volumes.

Version notes are on the GitHub releases; tags below show the Mac app version that added a feature.

A SwiftUI macOS app that bridges Jumper — a local media analysis app that builds a searchable cache of visual and speech analysis over your footage — and Archiware P5, which holds the source media on tape.

Search Jumper's analysis cache for the exact shot or spoken phrase you need. When the source file is no longer on disk, resolve its exact P5 ArchiveEntry handle and restore just that file, straight from the result. The restore folder defaults to the file's original parent directory, so a missing file returns to the path it came from.

Restores are handled conservatively: a restore to this Mac is refused if the destination file already exists, and a canceled or terminated P5 job now ends as a failed restore rather than waiting out the timeout and reporting a timeout. Files whose archived path contains a backslash now resolve correctly. Search Jumper uses the shared P5Kit library for its P5 connection. It is a beta: test restores on files you can afford to lose.

Requires a Jumper analysis cache, local or on shared storage. Search Jumper does not create the cache; it searches one Jumper has already built.

Creates one numbered project across edit, archive, cloud, or custom storage from a single main folder template. The same project number and name land everywhere they need to, with the copy rules each destination requires, rather than being made by hand on one volume and forgotten on the next.

The app opens in Simple mode: a project number, a project name, the projects already on the storage, and one row per storage saying whether it is loaded and how much room is left. Nothing in that window can change what gets created. Advanced — the other half of the picker in the header, or ⇧⌘M — is where the template, copy rules, renaming, and destinations live. Storage is checked before you type, so an unmounted archive is reported up front rather than after a number, a name and a wait.

Saved profiles carry a whole set-up, including the template itself, to another Mac. Destinations can be taken from a CopyTrust preset.

The command-line half of the Media Trust tools. mhl-tool creates and verifies MHL manifests without a window, so the same hashing and the same manifest format used by CopyTrust, Drop Verify and MHL Verify can run inside a script, a cron job, a watch folder, or a render-farm step.

Manifests are written into the folder they describe, beside the files they list, so their relative paths resolve in any vendor's reader. Older manifests still sitting in a Receipts, *_Receipts or ascmhl subfolder keep verifying against the parent, so nothing already written is stranded.

A macOS SwiftUI utility for Final Cut Pro XML work. FCP Reports (formerly FCPXMLD Drag Convert App) archives Final Cut libraries as byte-for-byte FCPXML evidence with OpenFCPXMLKit validation, builds Excel / PDF reports from .fcpxml files or .fcpxmld bundles, and converts bundles to standalone .fcpxml output.

Four tabs: Library Capture, FCP Reports, Convert FCPXMLD, and Settings.

A macOS menu bar utility that automatically backs up Final Cut Pro project bundles. Watches your FCP backup source folder, compresses new .fcpbundle files into zip archives, and copies them to one or more destinations while maintaining a manifest to prevent duplicates.

Runs silently in the background with configurable schedules, smart project filtering, and retention management. Supports local folders, external drives, NAS shares, and SMB volumes as backup destinations.

A lightweight SwiftUI macOS menu bar utility for connecting to SMB network shares without digging through Finder dialogs. Save frequently used servers, launch connections quickly, and keep your most-used file shares one click away.

SMB Connect is designed for environments that bounce between shared storage, edit bays, and archive volumes, giving you a faster way to mount the same destinations throughout the day.

Load an existing MHL (Media Hash List) file and verify that media files still match the recorded hashes. Works with MHL manifests from any compatible tool — Drop Verify, CopyTrust, Silverstack, OffShoot, ShotPut Pro, or YoYotta.

Use MHL Verify to re-check copies on another drive or machine, confirm archived or handed-off media still matches the original manifest, or validate MHLs received from external teams and facilities.

A lightweight macOS app for one-folder trust reporting. Drag in a folder and generate an MHL manifest, contact sheet PDF with thumbnails and camera data, and an EXIF metadata CSV — all in one step.

Artifacts are written to a Drop Verify_Receipts/ folder inside the dropped folder, with an optional export to a separate location. Only media files are hashed; hidden files and system artifacts are excluded by default.

A SwiftUI macOS app for understanding what is actually consuming storage inside production folders. Add a watched folder on a RAID, NAS, SAN, LucidLink filespace, or external SSD, and Find File Type scans it recursively into a local SQLite database so you can inspect file usage by extension, category, group, stage, and workflow role.

It is especially useful when post-production editors are asking why "camera originals" are taking over an edit volume. Instead of guessing, you can open the folder, look at the type breakdown, and confirm whether formats like .mxf, .r3d, .ari, .braw, or camera-original .mov files are still sitting on storage that should now hold only proxies, editorial media, or exports. Scheduled scans and historical snapshots also make it easy to prove whether the problem is growing over time or already under control.

A macOS utility for verifying that two folder trees are identical, file-by-file. Drop a source and a destination, and Folder Copy Compare hashes every file with xxHash64 — the same engine used across the MHL toolset — and reports exactly what matches, what doesn't, and what's missing on either side. It also helps clean up leftover P5 stub files before final delivery or archive handoff.

Subfolder Comparison: the Subfolder view scans one level deep and shows a per-subfolder pass/fail summary instantly, without hashing. Click any subfolder pair to trigger on-demand xxHash64 hashing for just that pair, so you can pinpoint a problem reel or card dump without waiting for the entire tree. Combined with P5 stub files cleanup, it fits naturally into a camera-to-archive handoff workflow alongside MHL Verify and CopyTrust — compare the copy, remove archive stubs, confirm it's clean, then generate an MHL manifest to lock in your chain of custody.

A macOS menu bar backup app for folders that change every day. BackupTrust creates scheduled plans that copy only new or changed files from a source folder to one or more destinations, helping protect active projects without repeating a full backup every run.

Built for real working storage on macOS, BackupTrust supports local disks, external SSDs, NAS volumes, and other mounted folders. Plans can include file filters, excluded-directory presets, mirror mode, versioned overwrite protection, optional post-copy verification, and overflow routing for files that need a separate destination.

Two editions. BackupTrust Standard is the sandboxed edition and ships through the Mac App Store. BackupTrust Pro is the direct-access edition, notarized and downloaded from GitHub, with its own update checking. Pro adds per-file encryption of chosen destinations, pre- and post-backup shell scripts with timeout and abort controls, and opt-in proactive SMB preparation through SMB Connect. Standard neither creates nor restores encrypted backups.

Encrypted backups you can open without the app. Pro encrypts each file with Apple Encrypted Archive using a public key, so the Mac that runs the backup holds no secret and cannot read its own backups. Recovery uses a key file you export and keep. Restore Files… rebuilds the original folders and modification dates, skips files already present unless you ask, checks the key before writing anything, and reports any file that fails without stopping the rest. Every encrypted destination also carries a restore script that works with Apple's own aea tool on any Mac. Test a Restore… proves a backup opens without writing anything.

Pro is a beta. It is for testing only, is not a commercial product, and comes with no support or warranty. Keep your own independent backup of everything you protect with it. It has not yet been tried against every kind of storage (SMB NAS and LucidLink volumes in particular), so test it before you trust it.

A full camera card ingest system with multi-source, multi-destination copy and verification. CopyTrust detects camera cards, copies media to multiple destinations simultaneously, verifies every byte with xxHash64, and generates MHL manifests, contact sheet PDFs, and session receipts.

Per destination, CopyTrust can also create proxies and archive to P5. Tick Create proxies and Archive to P5 on the destination rows you want them on — a typical chain archives the camera original from the first stop and generates editorial proxies on the last — and the run submits the archive and encodes the proxies after verification and the other artifacts have finished.

Beta. CopyTrust is being tested on real jobs. Test on media you can afford to lose and keep a separate verified backup. The newest build writes a Final Cut Relink Aliases folder beside the proxies, so Final Cut Pro’s Locate All relinks every proxy at once instead of one by one; proxies sent to a proxies-only drive, such as a cloud volume, get their own aliases there and the delivery is counted, so a shortfall is reported. Recent builds merge the pre-copy warnings into one review that opens with a banner saying Looks good — start the copy or Read below before you start, shows every destination's full path and whether a proxies-only destination will actually receive proxies, and warns No destination set for proxies when nothing is making them. The session summary now reports proxies, and the build also adds a Reveal menu with one section per destination, contact sheets for MKV cards, and plain-words P5 archive status (Archiving in P5 job…, Archived by P5 job…).

Enforced naming presets. A facility can describe how it files footage — project, unit, roll, and the folders each destination expects — and CopyTrust applies it as cards are staged. One preset sets up a whole job: the ingest options, the naming convention, what each destination is for (including proxies-only and P5), and the P5 server. Every card shows where it will land before the copy starts, and receipts record the project, unit, roll and exact folder each destination received. A card with no unit has no roll, and a preset can name which units get their files renamed (Drone files, for example) so the Rename choice is only offered where it matters. A preset can reload itself, and open in Card or Folder mode, every time the app launches, and a tested preset can be pinned by name with a configuration profile so a fleet stays on one setup.

Ordinary presets, too. Not every job needs a naming convention. Preset ▸ Build a Preset steps through how a copy is checked, the reports made afterwards, proxies, what is left out, folder names and who is notified, and starts from the defaults so nothing is inherited from an earlier preset. Preset ▸ Unload lets go of a loaded preset. Almost nothing is excluded by default, so a facility’s own proxy folders are copied.

Check footage against the manifest it arrived with. A card offloaded elsewhere with OffShoot, Silverstack or ShotPut Pro can be verified against that MHL when it reaches the facility. CopyTrust can also be shown larger (1x to 2x).

Power, ports and resume. On a laptop a power chip in the bottom bar shows the charge, or the battery and the time left, and turns orange or red when the queued copy will not fit; a banner warns if the battery is draining while plugged in. Every drive shows how it is connected (USB speed, Thunderbolt, network), a card reader or drive on a slow USB 2 port is flagged, and CopyTrust suggests the fastest drive first in relay order. A copy stopped at Quick verification resumes where it left off instead of starting over, and the Dest button in Volumes can make a new destination folder.

Features a Volume Browser for discovering mounted drives, camera cards, and network shares. Per-destination preflight checks validate free space, write permissions, and reachability before copying begins. Four-phase tracking shows progress from scanning through verification.