Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 224 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

Hedge

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Settings

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Requirements

macOS

macOS 11.x (Big Sur) and newer

Final Cut Pro

FCP 10.3.x and newer

Welcome 👋

Welcome to the documentation for all of Hedge's products.

Hit some hurdles in your workflow? Try the Search, it's pretty good at generating answers from the doc articles.

Office Hours

We don't guarantee a reply within 24 hours on working days, but it has rarely happened that we were not able to send a reply within a fraction of that. Our response time is typically under an hour, with 90% of emails responded to within 15 minutes.

Please don't email us to ask if we received your email if you didn't get a response within 24 hours, as that will only add to the response time as we then suddenly have two emails waiting for a reply 😁

Evenings, Weekends, and Holidays

During evenings, weekends and holidays, we monitor our inboxes for issues we classify as blockers: things that prevent you from working, not being able to log in to one of our services, not receiving your shiny new license key, etc. Not a blocker? Your email gets snoozed until Monday morning — then you'll be the first.

Remember, support outside office hours is a courtesy, not a privilege.

Releases

Arctic 25.1

Send to PostLab!

Arctic 24.3

Final Cut Pro 11

Arctic 24.2

Final Cut Pro 10.8 & Importing from FCLM

  • Improved migration flow from FCLM to Arctic

  • Fix for some background crashes lingering in FCLM's codebase

  • If FCLM data is found, Arctic now offers to copy it over.

  • It's now easier to add additional activations to your license.

  • Arctic now ignores "stateless" Libraries, which are Libraries stored but not downloaded locally on cloud drives like iCloud, Amove, Box, and DropBox. This prevents Arctic from beachballing when attempting to process Libraries that don't actually exist locally.

  • Support for Final Cut Pro 10.8

Arctic 24.1

  • Adds cleanup of stabilization data, grouped with the Optical Flow under the new Data header

  • Simplified accessing the list of missing files

  • Improved behaviour of the updates-available ribbon

  • The External Media popover behaves more nicely now

  • Opening settings now remembers the last panel selected

  • Improved handling of offline usage

  • Improved activating directly from the license email

  • Fix for a crash on Monterey (Thanks for reporting, Niek, Dave, Yarrow, Thomas, and Manuel!)

Arctic 24.1 (April 2, 2024)

  • First Arctic release 🎉

Legacy Versions

Questions

Why is there a hand icon over a Library?

in use on another Mac. Hover over the hand icon to determine which Mac has that Library open.

Can I tell Arctic to rescan a Source for FCP Libraries?

Yes. Control-Click a Source, then choose Force scan for new libraries.

Why can’t I find something in Arctic’s scan results?

First, make sure all filters are enabled (purple, not gray).

Next, clear the 🔍 Search field, ensuring all search parameters are enabled (yellow, not gray).

Finally, Arctic stores its scan results in an internal database. On occasion, that database may become damaged. If this happens, you can safely reset Arctic’s database with these steps:

  1. Quit Arctic.

  2. Press and hold Option-Command while relaunching Arctic.

    • Once Arctic launches, release those keys.

  3. Arctic will scan all Sources connected to your Mac once more.

Resetting Arctic’s database will not endanger your Final Cut Pro Libraries.

?

If some Libraries are still missing from an Arctic scan, you may need to reindex Spotlight on your Mac.

How can I reset Arctic’s preferences?

If all else fails, you can reset Arctic’s preferences using this command in Terminal.app:

defaults delete video.hedge.Arctic.Mac

Why can't I activate Arctic?

You're likely trying to use a Final Cut Library Manager license key. Both apps use a license key in this format: ABCD-EFGH-IJKL…, but an Arctic license key contains seven groups of characters while an FCLM license has around twenty.

Confirm you're trying to activate Arctic instead of Final Cut Library Manager, then activate Arctic using the corresponding license key.

How can I migrate my existing Final Cut Library Manager data to Arctic?

  1. Quit both Final Cut Library Manager and Arctic.

  2. In Finder, head to Go > Go to Folder... (or Shift-Command-G).

  3. In the dialog box that appears, copy/paste this path: ~/Library/Application Support/Final Cut Library Manager.

  4. Copy the contents of that Final Cut Library Manager folder to ~/Library/Application Support/Arctic.

How do I uninstall Final Cut Library Manager?

There is no need to remove Final Cut Library Manager before installing Arctic, you can keep both apps installed at any time.

In Finder, drag-and-drop Final Cut Library Manager.app from /Applications to the Trash, then empty your Trash.

To perform a comprehensive uninstall:

  1. Drag-and-drop Final Cut Library Manager from /Applications to AppCleaner then click Remove.

  2. In Finder, empty your Trash.

If needed, you can also use these steps to uninstall Arctic.

Need help?

Upgrades

Final Cut Library Manager customers can receive a discounted upgrade for Arctic.

Can't find what you need? Or just plain stuck? Reach out, we're happy to help:

You can us about anything 24/7, and you'll likely get a fast reply if it's between 9 AM CET and 6 PM CET. If you email us outside those hours, we'll pick up your email in the morning. That means that if you're in the USA, you can expect a reply overnight.

During these hours, don't expect a reply within minutes. We're likely busy with things like living a life, putting kids to bed, talking to people who are not thinking about workflow, you get the gist

Live status of our online services:

Arctic 25.1 (Apr 23, 2024) -

  • Send to PostLab, from within Arctic

Arctic 24.3 (Nov 14, 2024) -

  • Support for Final Cut Pro 11

  • A spiffy new UI

Arctic 24.3.1 (Dec 19, 2024) -

  • Improvements for migrating FCLM data

  • Fixes for some UI render issues

  • Fixes for some old crashes

Arctic 24.3.2 (Mar 28, 2025) -

  • Support for Final Cut Pro 11.1

Arctic 24.2.3 (Aug 22, 2024) -

Arctic 24.2.2 (Jul 17, 2024) -

Arctic 24.2.1 (Jul 3, 2024) -

Arctic 24.2 (Jun 21, 2024) -

Arctic 24.1.3 (May 22, 2024) -

Arctic 24.1.2 (May 7, 2024) -

Arctic 24.1.1 (April 3, 2024) -

(Dec 4, 2023)

If you can’t locate your license key for Arctic, you an look it up online in the .

Download AppCleaner -

If you didn't receive your upgrade coupon when Arctic was released, email us –  – and we'll send you an upgrade discount.

😉
hello@hedge.video
email
https://status.hedge.co
Download
🎉
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Final Cut Library Manager v3.98
Hedge License Manager
https://freemacsoft.net/appcleaner/
Need help?
arctic@hedge.video

Features

Canister has a lot of visible and invisible features.

Arctic

Arctic scans the volumes connected to your Mac and displays a list of Final Cut Pro (FCP) Libraries (.fcpbundle files) it detects on those volumes.

Arctic can help you inspect, filter, and search the contents of your Libraries.

Arctic can also generate media reports to help you track which media was used in a Library.

Finally, Arctic enables you to clean your Library safely for:

  • Preparing Libraries for archival purposes

  • Removing reproducible Library data in preparation for PostLab use

  • Reducing a Library’s size, recovering storage space

Getting Started

  1. Connect or mount any volumes containing FCP Libraries to your Mac.

  2. Launch Arctic to scan those volumes, called Sources.

  3. Locate the Library listed in Arctic, then inspect or clean that Library.

Sources

A Source can be any volume connected to your Mac, such as:

  • Direct-attached storage

  • Network-attached storage with a shared folder mounted over SMB, AFP, or NFS

  • FUSE-based volumes, such as a LucidLink Filespace

  • A subfolder from any of these eligible volumes

Your user must be able to read and write to a Source.

Click the ➕ in the lower-left corner to add a Source.

To remove a Source, Control-Click a volume in the list, then choose Remove from List.

You can temporarily remove the scan results from a Source by unchecking it in the list.

Inspecting

Arctic shows you how much storage these items use inside a Library .fcpbundle:

  • Original Media Files

  • Optimized Media Files

  • Proxy Media Files

  • Optical Flow Files & Stabilization Files ("Data")

  • Render Files

Click a Library in Arctic’s scan results to see a per-category breakout of what’s inside each Library and how much storage each category of items consumes.

Arctic also displays a color-coded bar graph for each category, which you can contextualize by clicking:

  1. Fixed - displays that bar at 100%, regardless of the storage space consumed

  2. Proportional - resizes a bar in proportion to the percentage of the storage used in that Library

Finally, you can inspect the contents of individual Events by clicking the disclosure arrow next to that Event.

Cleaning

Arctic allows you to safely clean any temporary, reproducible data stored in your Library, such as:

  • Optimized Media Files

  • Proxy Media Files

  • Optical Flow Files & Stabilization Files ("Data")

  • Render Files

To clean a Library:

  1. Select the desired Library from Arctic’s scan.

  2. Click the checkbox(es) under the column(s) for the items you wish to remove.

To remove the same category of data across multiple Events in a Library, click the multi-select checkbox under Arctic’s scan results.

  1. Once you complete your selections, click the broom 🧹, read the confirmation dialog, then complete your cleaning or Cancel.

Filtering

You can filter an Arctic scan by two categories: Library and Media Status.

Library

  • Show only libraries that are currently open in FCPX

  • Show only libraries that have alerts

  • Show other libraries items

  • Show cache items

  • Show external media folders

  • Show external media items

Media Status

  • Show online items

  • Show offline items

  • Show missing items

Enable/disable individual filters to include/exclude results from your Sources, or Option-Click an individual filter to display results based on that single filter.

Does a Library seem to be missing from Arctic’s scan? Make sure all filters are enabled by Option-Click-ing either set of filters until all are enabled (purple, not gray).

Searching

You can 🔍 Search Arctic’s results, then refine those results by:

  • Search library names

  • Search event names

  • Search project names

  • Search media filesnames and also their custom names, notes and keywords created in FCP

  • Search Finder comments for libraries and events and also the project notes created in FCP

  • Search exported projects

You can also enable/disable individual search parameters to include/exclude results.

Does a Library, or something in your Library, seem to be missing from Arctic’s results? Make sure the 🔍 Search field is clear and all search parameters are enabled (yellow, not gray).

Reporting

Arctic can generate reports for the media used in your Libraries. These media lists are exported as Comma Separated Values (CSV) files you can store along with the associated Library and media for archival purposes.

  1. Select the desired Library from Arctic’s scan.

  2. Control-Click that Library and choose Export Media List to CSV….

  3. Choose where to save your media list (the CSV), then Export To CSV.

Creating Library Templates

Do you have a Library with a frequently used set of Events, Keywords, media, etc.? Select that Library in the list, Control-Click it, and choose Create Template from Library….

macOS

Installers

Preflight Checks

Using LTO on a Mac requires a range of drivers to be installed properly. Getting your drivers sorted out can be a bit of a hassle, especially on Big Sur and later macOS versions.

Canister's Preflight Checks functionality tries to help you as much as possible by detecting any missing, outdated, inconsistent, or incomplete drivers when LTO hardware is detected.

Upon each app start, Canister will do a complete systems check - looking for Thunderbolt devices, Host Bus Adapters, and SCSI devices. On the software side, Canister checks for all required frameworks and drivers.

In a nutshell:

🟢 Everything green - you're good to go, and Canister will automatically continue.

🟠 Orange indicates a part of your setup is not 100% up to date, but it's fine to continue as is.

🔴 Red means your setup won't do. Preflight Checks will tell you how to resolve it, if possible.

Downloads

For reference, here's a list of all drivers and dependencies. Thanks to Canister Preflight Checks, you don't need these - we'll serve you the ones you need based on your system.

That said, sometimes it helps to have direct links. We regularly update this list of drivers, so there's no need to worry about checking if they're the latest version.

Hardware

Each Thunderbolt-based LTO drive consists of three devices:

  1. The Thunderbolt-to-PCI board

  2. A Host Bus Adapter (or "HBA"), a device translating PCI to SCSI

  3. The LTO drive itself

Non-Thunderbolt LTO drives, connected via SAS or Fibre Channel, will connect to a HBA that lives in an external box or as a PCI card inside your computer.

The only part of your hardware that requires a driver is the HBA.

Since Big Sur's release, Apple no longer ships drivers for HBAs. HBA drivers are macOS kernel extensions. Starting with Big Sur, kernel extensions require additional steps to install. On top of that, Apple silicon devices require you to change security settings to allow those extensions to run. Configuring these settings is expected behavior with Apple silicon, but cumbersome nonetheless.

We've tried to smooth out the process as much as possible, but be prepared for a bunch of successive reboots and raised eyebrows 🤷‍♂️

Host Bus Adapters

HBAs come in different flavors, and (to make life easy) not all work with LTFS.

  • Most brands, including recent mLogic units, use ATTO. Three possible ATTO drivers make matters easy: 6G, 12G PCI-3, and 12G PCI-4 ("GT").

  • Most MagStor units use Areca, but sometimes they use ATTO.

  • Old mTape units also house Areca cards (eg. ARC-1320). These tend to be incompatible with newer builds of LTFS.

  • Some brands might use HighPoint "RocketStor" HBAs which are not suitable for use with tape.

  • Older LSI HBAs do not work on a Mac. These cards are also sold under HP's brand name.

Symply

OWC

MagStor

If Canister detects a MagStor LTO Thunderbolt device, it will ask you to input its serial and serve you the correct driver for the HBA inside. Not all units are made equal, so don't rely on memory. Through our partnership with MagStor, we have an up-to-date list of products, serials, and HBAs.

Locate your serial on the back or bottom of your unit.

mLogic

Other Vendors

If your setup is not mentioned above, you'll need to install your HBA driver by hand. In most cases it's easiest to ask the vendor for support.

Installing drivers

Installing drivers (AKA kernel extensions or system extensions) can be a tedious ordeal, thanks to Apple. If you run into trouble, grab a coffee, carve out some time, and we'll walk you through the process with this documentation.

If your Mac is managed through MDM, stop now and contact your System Administrator. The following steps below will not apply when using MDM.

Apple silicon and Reduced Security

On Apple silicon, you'll first need to set your Mac's security policy to "Reduced Security" to be able to load signed kernel extensions. If you're on Intel, you can skip to Installing the HBA driver.

Apple's use of "Reduced Security" language is misleading. With it, your Mac's security is on par with the level of security you've come to expect with previous versions of macOS.

  1. Shut down your Apple silicon Mac.

  2. Press and hold down the power button until your Mac boots. Your Mac will either send you directly into macOS' Recovery environment, or you'll see an Options button leading to that.

  3. Log in with your user account and select the disk you want to use.

  4. In the menu bar, go to Utilities, then select Startup Security Utility.

  1. Click Security Policy...

  1. Select Reduced Security, then enable: Allow user management of kernel extensions from identified developers .

  1. Click OK.

  2. In the menu bar, select Shut Down.

  3. Turn the Mac back on (press but don't hold the power button this time) and log in.

Installing the HBA driver

Now, install the driver for your HBA that Canister provides.

During installation, you'll see a System Extension Blocked or System Extension Updated dialog appear.

Confirm which version of macOS you're using with Canister, then follow these steps to approve the HBA driver to load in macOS:

  1. In the System Extension Blocked or System Extension Updated dialog, click Open System Settings.

  2. System Settings will launch, taking you to Privacy & Security > Security.

  3. Under the System software from developer "(Name of HBA Driver Vendor)"… prompt, click Allow.

  4. Two Privacy & Security dialogs will appear:

    1. In the first Privacy & Security dialog (Privacy & Security is trying to modify your system settings.), enter the password from a local macOS Administrator account, then click Modify Settings.

    2. In the second Privacy & Security dialog (Privacy & Security needs to authenticate to continue.), enter your macOS account’s password, then click OK.

  5. Restart your Mac. It may restart multiple times.

  1. In the System Extension Blocked or System Extension Updated dialog, click Open Security Preferences.

  2. System Preferences will launch, taking you to Security & Privacy > General.

  3. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  4. Once Security & Privacy > General is unlocked, next to the System software from developer "(Name of HBA Driver Vendor)"… prompt, click Allow.

  5. Click OK, then Restart your Mac. It may restart multiple times.

  1. Launch System Preferences, then go to Security & Privacy > General.

  2. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  3. Once Security & Privacy > General is unlocked, click Allow.

  4. Click Restart Now.

After rebooting, macOS might prompt you to Open System Settings or Open Security Preferences and do the whole thing again (and sometimes, a third time.)

Next, launch Canister. If Canister detects the driver isn't loaded, it will tell you to Allow driver in system settings to trigger macOS to show the much-coveted Allow button.

When successful, Canister will show you this:

Is there a 🟢 next to LTO? You may proceed to installing theSoftware bits 🥳

If not, keep reading. We suggest finding a cozy spot and a big bag of patience.

Troubleshooting kexts

We've found multiple workarounds and listed them in order of success rate. If one doesn't work for you, be sure to try the other suggestions.

Install macFUSE first

Manually load the kernel extension

Since most people use ATTO HBAs, we'll use those as an example. But you can use these steps with any kext.

First, look up your driver's name in /Library/Extensions :

  • For ATTO 6G, use ATTOExpressSASHBA2.kext

  • For ATTO 12G (PCI-3), use ATTOExpressSASHBA4.kext

  • For ATTO 12GT (PCI-4), use ATTOExpressSASHBA5.kext

Then, try loading the kernel extension manually in Terminal:

sudo /usr/bin/kmutil load -p /Library/Extensions/ATTOExpressSASHBA2.kext

sudo kextload /Library/Extensions/ATTOExpressSASHBA2.kext

You'll need to enter your password. Then, open the Security & Privacy pane again – it should show you the Allow button.

Remove the kernel extension

If you finished the installation, and your LTO drive works but stops working after each reboot, forcing you to load the kernel extension over and over again, there's likely a remnant of an older ATTO driver of your system. Here's how to remedy that:

Suppose you finished the installation, and your LTO drive works. However, after each reboot, it stops working, forcing you to load the kernel extension over (and over) again. There's likely a remnant of an older ATTO driver in your system. Here's how to remedy that:

  1. In Finder, hit Shift-Command-G, then go to /Library/Extensions .

  2. Delete any ATTOSASHBA*.kext in that folder (password required, most of the time).

  3. In Terminal, copy/paste this: sudo kextcache --clear-staging (password required).

  4. Reboot if macOS doesn't already force you to.

  5. Reinstall the ATTO driver your LTO machine requires.

Talk to IT

If any of the Terminal commands above return errors like system policy prevents loading, your computer is very likely under IT management policies that prevent kernel extensions from loading. Talk to your IT department first; they'll know what to do.

Reset the Local Kernel Extension Database in macOS

Starting in macOS Big Sur, the local kernel extension (i.e. kext) database in macOS may not retain your decisions on approving third-party system or kernel extensions to load in macOS. If macOS doesn't load a kernel extension despite multiple approvals from you, you can safely reset macOS' kext database, which revokes approval for all third-party kexts installed on your system volume.

Once you reset the local kext database, you can log back into macOS and approve any/all system or kernel extensions installed on your Mac.

  1. Save any open work and quit any open apps.

  2. Power down your Mac.

  3. Choose your system volume, log in with a macOS Administrator account, then launch Terminal.

  4. Use this command to reset your Mac's Kernel Extension database:

    1. kmutil trigger-panic-medic --volume-root /Volumes/(SYSTEM VOLUME)

      • If your system volume has a space in its name (e.g. Macintosh HD), enclose the volume name in quotation marks (e.g. "/Volumes/Macintosh HD").

    2. Press the (Return) key.

      • If you entered this command correctly, you'll see this response, All third party kexts have been unapproved and uninstalled from /Volumes/(SYSTEM VOLUME).

  5. Restart your Mac.

Once you log into macOS, you'll likely be greeted with multiple dialog boxes saying...

  • System Extension Updated

  • System Extension Blocked

...along with confirmation that you triggered the Panic Medic Boot.

You've successfully reset your local kext database in macOS.

Reinstall macOS

Do you keep running into non-loading kernel extensions? Then there's something wrong with your macOS install, likely due to upgrading your OS instead of doing a fresh install. At this point, it's just faster to reinstall macOS. Less daunting than it sounds and won't take long, thanks to APFS:

Software

Now that you have installed your HBA drivers, the biggest hurdle is behind you. Let's move on:

Installing macFUSE

To make LTFS work, you'll first need to install macFUSE. LTFS uses it to represent the data onto the tape as a volume on your computer. It's also a kernel extension, so yes, more reboots.

Confirm which version of macOS you're using with Canister, then follow these steps to approve macFUSE to load in macOS:

  1. In the System Extension Blocked or System Extension Updated dialog, click Open System Settings.

    • If you clicked OK instead, click Open Security & Privacy System Preferences in the installer.

  2. System Settings will launch, taking you to Privacy & Security > Security.

  3. Under the System software from developer "Benjamin Fleischer"… prompt, click Allow.

  4. Two Privacy & Security dialogs will appear:

    1. In the first Privacy & Security dialog (Privacy & Security is trying to modify your system settings.), enter the password from a local macOS Administrator account, then click Modify Settings.

    2. In the second Privacy & Security dialog (Privacy & Security needs to authenticate to continue.), enter your macOS account’s password, then click OK.

  5. Restart your Mac. It may restart multiple times.

  1. In the System Extension Blocked or System Extension Updated dialog, click Open Security Preferences.

    • If you clicked OK instead, click Open Security & Privacy System Preferences in the installer.

  2. System Preferences will launch, taking you to Security & Privacy > General.

  3. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  4. Once Security & Privacy > General is unlocked, next to the System software from developer "Benjamin Fleischer"… prompt, click Allow.

  5. Click OK, then Restart your Mac. It may restart multiple times.

  1. Launch System Preferences, then go to Security & Privacy > General.

  2. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  3. Once Security & Privacy > General is unlocked, click Allow.

  4. Click Restart Now.

Not getting that Allow button?

Use this command in Terminal (all on one line):

sudo /usr/bin/kmutil load -p /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext

kextload /Library/Filesystems/macfuse.fs/Contents/Extensions/10.15/macfuse.kext

Again, you'll need to enter your password, then open the Security & Privacy pane – it should show you the Allow button.

Installing LTFS

When Canister detects an HBA and LTO drive, it will deduce which LTFS you need. LTFS has a dependency called ICU to support international characters, so Canister will tell you to install ICU first. Then, you install LTFS. No reboots are needed; it's pretty straightforward.

Installing Catalogs

From 24.1 Catalog support is bundled with the Canister installer. This section is retained for legacy purposes, but no longer supported.

Up until 23.2, Catalogs requires additional drivers. Preflight Checks will prompt you to install Apple's Command Line Tools ("CLT") first:

If CLT doesn't download (it happens, as Apple hosts it themselves), you can do so manually with this Terminal command:

xcode-select --install

If the Catalog installer states "The Installation failed"

Sometimes, macOS won't properly finish the Catalogs installer, stating the installation failed. If so, CLT most likely wasn't installed properly or completely. Reinstalling CLT will fix that:

  1. Delete the folder /Library/Developer/CommandLineTools. (If this folder isn't present, CLT wasn't installed anyway.)

  2. Reinstall Command Line Tools by using the following Terminal command: xcode-select --install

  3. When done, run this command to make sure the installation is correct (all on one line):

PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec"; export PATH; m4 --version
  1. It will output some text, which should look like this:

GNU M4 1.4.6 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Written by Rene' Seindal.

  1. Then, rerun the Catalog installer.

Still not successful? Send us your Catalog installer log.

  1. Immediately after installation, go to Finder and hit Shift-Command-G.

  2. Go to /tmp.

"My LTO was showing up, but now it won't."

If your LTO drive previously worked, but your Mac no longer can see an LTO drive, neither can Canister.

There are typically two situations you can end up in:

Looking for LTO drives...

Your Mac doesn't detect any LTO SCSI device. Canister will keep scanning until it finds one.

Possible causes include:

  • You have an mLogic device, but your Thunderbolt cable probably isn't connected properly.

  • Your device requires a Thunderbolt cable, but you are using USB-C type instead.

  • You're using an LTO drive with a separate HBA, but the HBA likely isn't detected. Check if it's listed under System Information > SAS. If not, install its driver.

Looking for LTO devices

Your Mac somehow lost the connection to the LTO drive. Your best bet is to power cycle all gear, including the Mac.

Once the power cycle completes, check if all devices are listed in the System Information.app. You should see at least two entries on the SAS page:

  • A Host Bus Adapter, like ATTO or Areca

  • A Ultrium LTO SCSI, device made by IBM, HP (or HPE), Quantum, or Tandberg

"I give up"

Can't get up and running? Running in circles?

Installation

Canister supports both macOS and Windows, each with its setup instructions.

Tape Media

Generations

Every few years, the Ultrium Consortium (consisting of IBM, HP, Quantum, and tape manufacturers Sony and Fuji) releases a new version of LTO. These versions are known as generations. Each generation holds more TB per tape, and sometimes newer drives are also faster.

As any generation older than LTO-5 does not support LTFS, we don't take these into consideration.

Tape Capacities

With all the marketing that surrounds LTO, it's good to set things straight from the get-go; the advertised tape capacity is not a realistic value.

The advertised capacity is a raw byte count, and doesn't account for file system overhead and the space the index partition will require.

As not having enough free space for the indexes results in unmountable tapes, Canister reserves 5% of the free space for indexes. The result is a more realistic free space calculation, as shown in the last column.

If required, you can decrease this reserved amount of space using this Terminal command:

defaults write nl.syncfactory.Canister.Mac ReservedTapeIndexPercentage -int n

where n stands for the percentage integer, e.g. 5 for 5%.

Be very careful with this setting: the few extra GBs you'll gain might not be worth the trouble. If you decrease this value and end up putting too much data on a tape without sufficient room to spare for the index, LTFS won't be able to finish writing the index. The result is a tape that will no longer mount. You can consider the data to be lost, as you need to reformat the tape to be able to use it again.

WORM Media

As Write Once Read Many ("WORM") tapes cannot be partitioned, they are incompatible with LTFS. Be sure to use rewritable tapes with Canister.

NanoPure™ Support

Canister for Windows does not support NanoPure tape media.

In the event of a poor result you might consider retiring the tape, or contacting your hardware vendor for a thorough diagnostic check.

Tape Initialization

Up to LTO-9, tapes do not require initialization. When inserting a new LTO-9 tape into a drive for the first time, the LTO drive will spool through the whole tape. This process can take as long as two hours and is indicated on the Single Character Display as a lowercase c. For convenience, some vendors like Symply sell pre-initialized media.

If your drive is of an older generation that LTO-9, you can simply insert a tape and continue with formatting.

Migrating

While the LTO consortium touts a 30-year lifespan for tapes, their hardware definitely won't last that long. That's why it makes sense to migrate your archive to a newer generation once every few years. How often depends on the size and value of your archive.

Here's how many tapes you can migrate to a newer generation:

Windows

Installers

Preflight Checks

Setting up an LTO drive can be daunting, even for experienced users. Canister's Preflight Checks function tries to help as much as possible by conveniently linking to the relevant bits and pieces.

Upon each app start, Preflight queries WMI (Windows Management Instrumentation) for a list of compatible LTO drives. On the software side, it also helps to setup LTFS and its dependencies.

In a nutshell:

🟢 Everything green - you're good to go, and Canister will automatically continue.

🟠 Orange indicates a part of your setup is not 100% up to date, but it's fine to continue as is.

🔴 Red means your setup won't do. Preflight Checks will tell you how to resolve it, if possible.

Downloads

For reference, here's a list of all drivers and dependencies that we host for Windows. We regularly update this list, so there's no need to worry about checking if they're the latest version.

Hardware

Each Thunderbolt-based LTO drive consists of three devices:

  1. The Thunderbolt-to-PCI board

  2. A Host Bus Adapter (or "HBA"), a device translating PCI to SCSI

  3. The LTO drive itself

Non-Thunderbolt LTO drives, connected via SAS or Fibre Channel, will connect to an HBA in an external box or as a PCI card inside your computer.

The only part of your hardware that requires a driver is the HBA.

Host Bus Adapters

Pro Tip: Device Manager can be located by searching in the Windows Start menu.

First, ensure your LTO drive is visible in Device Manager. That will require you to manually install the appropriate driver for your host bus adapter (HBA). LSI cards tend to be recognized automatically by Windows, but ATTO and Areca HBAs generally require a driver download.

Once your HBA is functioning, your LTO drive should appear in the Cassette/Tape drives list.

Installing LTFS

Installing IBM LTFS on Windows is a straightforward process. Follow the steps below in order, then reboot the system.

"I give up"

Can't get up and running? Running in circles?

Before April 2024, Arctic was known as Final Cut Library Manager.

The latest installer for macOS is available here:

(6xx series, PCI-3) (12xx series, PCI-3) (12xx series, PCI-4)

A full list of compatible hardware is available

Symply exclusively uses ATTO HBAs, but the model varies with the unit. To find out which driver you need, ask Symply support or use the tool to get started.

Other World Computing's Mercury Pro & Archive Pro solutions typically use ATTO HBAs. Refer to their documentation for guidance on which driver to install.

mLogic typically use ATTO or Areca HBAs, but the model varies with the unit. To be sure which driver you need, ask mLogic via their .

Try first, then reinstall the HBA driver. Even though the install FUSE link is greyed out in Canister, you can still click it. Installing macFUSE first seems to get macOS out of its not-showing-the-Allow-button funk.

Once your Mac is fully powered down, .

Now you can approve , , and any other existing system or kernel extensions to load in macOS.

Then, continue with the Catalog install either by clicking "finish installation" or by downloading the Catalog installer from .

Locate the canister-catalog-installer.log file, and that to us.

It can happen and is typically an indicator of a deeper problem. The company that sold you your LTO drive and/or Host Bus Adapter should be your first line of contact, as this is about your hardware - not Canister. That said, we're happy to help if that's a dead end. Don't hesitate to contact us, and be sure to include a screenshot of .

We won't give up on you

LTO
Advertised
Maximum
Realistic

From 23.2 onward, Canister for Mac supports tape media by MagStor. NanoPure tapes are pre-cleaned, with calibration data recorded to the Cartridge Memory after testing. Canister uses this information to calculate system health at the end of each Archive or Retrieve operation. Each Transfer Log will contain a NanoPure score: Good, Average or Poor.

From
To LTO-8
To LTO-9

The latest installer for Windows is available here:

(6xx series, PCI-3) (12xx series, PCI-3) (12xx series, PCI-4)

A full list of compatible hardware is available .

Install

Install

It can happen and is typically an indicator of a deeper problem. The company that sold you your LTO drive and/or Host Bus Adapter should be your first line of contact, as this is about your hardware - not Canister. That said, we're happy to help if that's a dead end. Don't hesitate to contact us, and be sure to include a screenshot of .

We won't give up on you

👍
Read more...
https://hedge.video/download/canister/macos
https://hedge.video/external/canister/hba/areca
https://hedge.video/external/canister/hba/arecaM1
https://hedge.video/external/canister/hba/atto-6
https://hedge.video/external/canister/hba/atto-12
https://hedge.video/external/canister/hba/atto-GT
https://hedge.video/external/canister/fuse
https://hedge.video/external/canister/ltfs/hp
https://hedge.video/external/canister/ltfs/ibm
https://hedge.video/external/canister/ltfs/quantum
https://hedge.video/external/canister/icu/hp
https://hedge.video/external/canister/icu/ibm
https://hedge.video/external/canister/icu/quantum
here
SymplyATOM
here
Help Center
power up your Mac again in Recovery mode
https://support.apple.com/en-gb/HT204904
here
email
installing macFUSE
the HBA driver
macFUSE
Canister's Preflight Checks

9

18 TB

17.5 TB

16.7 TB

8

12 TB

11.7 TB

11.1 TB

7

6 TB

5.73 TB

5.4 TB

6

2.5 TB

2.45 TB

2.3 TB

5

1.5 TB

1.43 TB

1.4 TB

LTO-5

8

12

LTO-6

4 or 5

7

LTO-7

2

3

👍
Installing Canister on macOS
Installing Canister on Windows
NanoPure
https://hedge.video/download/canister/windows
https://hedge.video/external/canister/hba/win/atto-6
https://hedge.video/external/canister/hba/win/atto-12
https://hedge.video/external/canister/hba/win/atto-GT
https://hedge.video/external/canister/visualc++
https://hedge.video/external/canister/ltfs/ibm/windows
here
Microsoft Visual C++ 2010 Runtime x64
IBM LTFS for Windows 2.4.5.1
Canister's Preflight Checks

Canister

Canister is so simple to use that most users don't need anything to get started. If you don't have a tape drive at hand, check out this video:

Catalogs

Each time a tape is mounted, Canister will create a Catalog for it. This makes it easy to see what's on a tape without having to mount it first.

The LTO Archive drive

Don't see the LTO Archive drive? Check if your user has administrator permissions.

Creating Catalogs

Canister automatically creates a Catalog the first time it mounts each tape, and updates existing Catalogs upon each consecutive mount. Also, after each Archive transfer the Catalog for that tape is updated automatically.

Importing Databases with NeoFinder

Finding files using Catalogs

Retrieve from Finder

On macOS Canister installs a Finder extension that allows you to retrieve a file or folder directly from the Catalog. Right-click the folder you want to retrieve and select "Retrieve" to launch Canister. This will trigger Canister to check if the correct tape is mounted and automatically select the required files. Then, Canister will ask to specify a location to retrieve to.

Catalog History

Canister creates a Catalog when mounting a tape and updates it after each Archive. Catalog history is stored for safe keeping as described below.

Old Catalogs are moved into a hidden folder named Tapename (serial).history, essentially archiving them.

To see previous generations of your Catalogs, enable Show Hidden Files in Finder with the shortcut Shift-Command-.

The most up-to-date Catalog is stored in: /Users/Username/AppData/Roaming/Canister/$TAPE/Current

Previous versions of a Catalog are stored in: /Users/Username/AppData/Roaming/Canister/$TAPE/History/YYYY-MM-DD

Editing and removing Catalogs

Use the steps below to clean up the Catalog, or remove test entries:

To access the catalogs location, bypassing the virtual drive, Alt-Click the Catalog icon in Canister (top-right) and a folder in ~/Library/Application Support/Canister will open with editable catalogs.

Navigate to/Users/Username/AppData/Roaming/Canister/Catalogs using Explorer, then either delete the folder representing tape you wish to remove.

Changing the Catalog location

On macOS, it's possible to set a custom Catalog location using a User Default.

  1. Open Terminal.app and enter defaults write nl.syncfactory.Canister.Mac CatalogLocation followed by the full path of the folder, all on one line. eg. defaults write nl.syncfactory.Canister.Mac CatalogLocation /Users/[username]/Documents/Canister/Alternative\ Location

Pro-tip: don't type the folder path, but drag the folder you want as Catalog location from Finder into the Terminal.

Note: when checking for a User Default value for the Catalog location, Canister expects a full path, including the name of the Catalogs folder itself. If a path is unreachable (e.g. if on a network server or cloud drive) or Canister doesn’t have the correct permissions, Canister will use the default Catalog location.

On Windows, it's possible to set a custom Catalog location using a Registry Switch.

  1. Open Registry Editor.

  2. Locate Canister here: Computer\HKEY_CURRENT_USER\Software\Canister

  3. Right Click to create a new String Value called AlternativeCatalogLocation.

  4. Define your full path including the drive letter.

  5. Restart Canister.

Migrating Catalogs

In the event you need to move to a new computer, Catalogs can be moved as follows:

Due to the typically large amount of files in a catalog, it's best not to copy catalogs but to archive them first.

Run this command in Terminal, and it will create an archive on your desktop:

Navigate to /Users/Username/AppData/Roaming/Canister using Explorer, then right click the Catalogs directory and choose Send to -> Compressed (zipped) folder.

Next, copy the zip to the new computer and extract.

Rebuild the Spotlight index on your Mac - Apple SupportApple Support

On a Mac, when Canister is open, all Catalogs are available as a virtual drive called LTO Archive. Since a driver installation is required, Canister will prompt you for the installation. You can also directly from our servers.

NeoFinder for Mac offers integrations between many other LTO-focused apps and Canister, making it a breeze to convert your old databases to Catalogs. For more information, refer to NeoFinder's .

On macOS, Catalogs live in Finder so you can utilize all the power of Finder's search.

When Canister is open, you'll see the LTO Archive mount in Finder. You can also click the Catalog icon in Canister to go there. There, you can do a Finder search. Just hit Command-F and be sure to select LTO Archive as the scope. Pro-tip for online/offline workflows: use Smart Folders.

Here's an example of a search for the file Quitter.zip, with Finder indicating it's located on LTO tape "A":

On Windows, Catalogs can be accessed by clicking the Catalog button pictured below.

The Storage Browser will open. It provides a neat overview of all tapes in the Catalog. Folders can be expanded by clicking the > button.

You can copy this archive to a new machine, then unpack it with a free app like .

tar -cvzf ~/Desktop/catalogs.tar.gz ~/Library/Application\ Support/Canister/Catalogs
Logo
download the installer
documentation
Unarchiver

Archiving

Archiving

Copying data to tape is called Archiving, as its goal is to be an independent copy of data that doesn't rely on other backups to be retrievable. Archiving with Canister is simple:

First, select the disk or folder you want to archive by either dragging in a folder from Finder or by browsing to a Source Folder. Then continue, and mount a tape. Next, confirm the transfer(s).

Canister will order the files-to-be-archived logically so that they won't end up on your tape in a fragmented order.

Collections

Like with OffShoot, Canister allows you to combine folders and files into a Collection to be used as the source for your transfer.

To create a Collection, either multi-select files and folders in Canister's source browser, or simply drag and drop a selection from Finder/Explorer into the drop zone provided.

Duplicate Detection

Canister automatically applies Duplicate Detection to all transfers. When a file is identical in name, size, and modification date, it is skipped. When a file has been changed, the already stored file will be renamed by appending its modification date and hidden. That means all previous versions of a file will always be available for retrieval at a later time.

Incremental Backups

As Canister comes with Duplicate Detection, it will detect what is new or has changed and only copy those files and folders to tape. Keep in mind that due to the linear nature of LTO, this will cause your data to be stored in different sections of the tape and thus will impact retrieval time as the tape head has to make a lot more movements to access a folder's contents across a tape.

Simultaneous Transfers

Canister can write to multiple drives at once. If the tapes used are of equal generation and thus speed, it will be as fast as writing to a single tape. However, there may be a bit of deviation as tape drives often have slightly different speeds.

Shoeshine Prevention

When selecting files to be archived, often files that appear to be consecutively and part of the same folder are not actually stored in consecutive order on disk. When working with LTO files must be lined up and written in consecutive order to prevent shoe-shining upon retrieval. Canister handles this for you, ensuring files that live together in a folder will also live next to each other on your tape.

Illegal Characters

Many legacy systems use a deny-list of characters, severely complicating many workflows. To solve that without relying on a database and thus introducing vendor lock-in, Canister utilizes percent-encoding for all illegal and unsupported characters. You cannot only use any of the forbidden characters / * ? < > " | \ : but also use any internationalization in all file and folder names. Canister will know when it needs to replace them and when not to.

Upon retrieval, Canister automatically converts percent-encoded characters back to Unicode. If you make use of illegal characters heavily and plan to retrieve a Canister-made LTO with a different mechanism or app, it's easy to use a percent-decoding script after doing the retrieval.

Verification

By default, each archive is fully verified by reading back the files after being transferred. Verification can be skipped at any time by clicking the x button next to the progress bar.

By default, Canister uses XXH64BE for verification. For legacy workflows, it's also possible to use MD5. Or, disable verification altogether in Canister's Preferences.

Additionally, Canister for Windows has the ability to verify duplicates identified during the archiving process. This is a huge time saver when something goes wrong with your LTO drive. Simply set the same source and both Canister's Duplicate Detection and Verification engine will work together to ensure you get a Transfer Log with a complete set of checksums.

Choose files to Skip

Canister provides a simple way to skip files based on their extension. This option is located in Settings > General. System level junk eg. .DS_Store, thumbs.db are always ignored, so no need to add these by hand.

Compression

Although touted as a big feature for LTO, don't expect any wonders from it. LTO compression only works well for text files and not at all for video or photo material, so never expect to be able to save more data to a tape than the bare capacity.

Encryption

Canister currently does not support hardware-based LTO encryption.

Retrieving

Retrieving files from a tape is easy; you can either retrieve a full tape or cherry-pick contents to retrieve just a few files.

Select the Retrieve tab. If no tape is loaded, do so first:

Mount the tape:

To retrieve the tape in full select the tape icon, and a border will appear. Click Next and then select a destination, and continue.

To retrieve a specific file, folder, or a collection of files and folders, click the drive menu (three horizontal lines) and select Select Files...

By default, the full tape's contents are selected. Unselect the root of the tape to deselect everything, and then navigate to what you need to be retrieved.

Canister will show you the size of your selection:

When done, click Next to select a Destination:

And continue...

When done, the progress bar turns green:

Open the accompanying Transfer Log if needed:

Retrieve with Finder

This feature requires macOS Big Sur or newer.

Canister makes it easy to retrieve files using Catalogs. In the LTO Archive, select a file or folder on a tape, right-click and select the "Retrieve..." Finder extension.

Retrieve with Full Path

When checked, files and folders selected for Retrieve will be copied to the destination, including the recreation of full paths as they exist on tape. This is useful when restoring projects that are sensitive to path changes.

Example:LTO-42/Production X/0001.mov is to be retrieved to ~/Desktop

  • Without Retrieve with Full Path enabled, 0001.mov will be copied directly to your Desktop.

  • With Retrieve with Full Path enabled, after retrieving 0001.mov your Desktop will be populated with a Production X folder containing 0001.mov.

Formatting

Before using a LTO, it needs to be formatted. When Canister detects a non-formatted tape it will prompt to format the tape.

Tape Initialization

Up to LTO-9, tapes do not require initialization. When inserting a new LTO-9 tape into a drive for the first time, the LTO drive will spool through the whole tape. This process can take considerable time. If you do no have this luxury, some vendors like Symply sell pre-initialized media.

If your drive is of an older generation that LTO-9, you can simply insert a tape and continue with formatting.

Formatting

Each LTO tape needs to be formatted before usage, kind of like with a hard disk. If a tape is not yet formatted, Canister will prompt you to do so:

Each LTFS-formatted tape requires a name and may use an optional serial. A serial must be 6 characters.

If you do not have a system in place to track tapes using the serial, we suggest allowing Canister to prepopulate the serial using the date. This simple mechanism results in a value like 240724 for July 24th, 2024, and gives context for when a tape was created.

Erasing Tapes

LTFS requires a tape to be unmounted before erasing a tape. If Erase is disabled, first eject the tape.

Due to LTO's linear nature, files written on tape cannot be deleted without erasing the whole tape. Erasing a tape can be done in-app through the LTO menu:

Renaming Tapes

This feature is not supported on Canister for Windows, yet.

As of Canister for Mac 23.1 it's possible to rename tapes without formatting. In order to rename, the tape cannot be mounted. Changing a tape's serial is not possible without a format.

Discovery Channel-Compatibility

Some years ago, the Discovery Channel created a delivery spec for LTO. This specification requires the party delivering LTO to Discovery Channel to add a specific XML file to the root of the tape. This XML file needs to be written to the index partition instead of the data partition of LTFS tapes. A specific LTFS setting is required when formatting a tape to make this possible. As this setting is not obstructing any non-Discovery Channel workflow, all tapes formatted by Canister adhere to this spec.

Netflix-Compatibility

When delivering tapes to a major studio such as Netflix, it's best practice to disable LTO hardware compression. The Netflix-Compatibility option does just that and is available when you Format or Erase a tape.

NanoPure™️ Support

Canister for Windows does not support NanoPure tape media.

In the event of a poor result you might consider retiring the tape, or contacting your hardware vendor for a thorough diagnostic check.

Spanning

When a source is too big for a single tape, Canister's Spanning engine comes in handy. This feature makes it quick and easy to Archive datasets that are larger than a single tape.

Getting Started

Adding new data to spanned tapes

It's likely that you won't fill up the last tape in a spanning set. Therefore, you can add anything you want to that last tape at a later time - no previously archived data will be affected. If the to-be-archived files fit, Canister will add it to the tape. If not, you'll enter the Spanning flow described above.

Pro Tip: If the data belongs to an existing Spanned Archive, Mac users might find it useful to set the same Spanning Label as before. This way, the newly added data gets grouped in the same Catalog.

Spanning Questions

Spanning is an advanced feature that tends to lead to a few workflow questions. Be sure to check the FAQs below before reaching out to support.

Do I need to preformat my tapes?

No, Canister will ask you to format at the relevant points in the Spanning workflow. Insert the next tape, then follow the prompts.

How should I name my tapes?

This comes up quite a bit; the best bet is to name each tape sequentially, for example:

  1. Archive_pt1

  2. Archive_pt2

  3. Archive_pt3

Is there a tape/item limit when Spanning?

Canister doesn't enforce any limits, however Spanning is best used with dataset that requires between 2-4 tapes.

Why? Because Spanning requires Canister keeping the entire source index in memory, which is a heavy lift. The chance of something going wrong on the hardware side of LTO increases exponentially the longer your LTO drive operates. As an upper limit we recommend Spanned Archives containing less than one million items.

How do I redo Spanning if something goes wrong?

As with all things LTO, hiccups happen. While with hard disks it's easy to redo something, due to LTO's linear nature errors tend to be showstoppers - at least temporarily. While Spanning, the chance that a tape runs into an issue or that an archive fails for some reason is, of course, compounded.

Canister gets around this problem by using its Dupe Detection implementation to the fullest: in case an error happens with any tape during a spanning archive, simply start over. It's important to feed Canister the tapes in the order they were finished, then let Duplicate Detection skip items already existing on each part.

Can I incrementally update a Spanned Archive?

While Canister supports Dupe Detection, due to LTO's linear nature, we don't recommend incremental updates to a Spanned Archive. File changes are likely to end up distributed over multiple tapes, which will get complicated when retrieving.

Why does Canister leave free space at the end of each Spanning Part?

Splitting files between multiple tapes is not a standard LTFS feature. As a result, each tape is likely to have a small pocket of space at the end.

Can I perform Simultaneous Spanning?

Canister for Mac does not support Spanning while creating simultaneous archives. Canister for Windows follows a different flow, which allows the next tape to be inserted for each drive.

Logs & Manifests

Canister creates a range of log files for archival purposes, and console output for troubleshooting.

Transfer Logs

For each Transfer, whether it's an archive or retrieve, a Transfer Log is created.

Transfer Logs are accessible through the Transfer Log viewer (Command-L) or directly in Finder:

~/Library/Application Support/Canister/Transfer Logs

Transfer Logs are accessible via the Canister menu or in Explorer:

/Users/Username/AppData/Roaming/Canister/Logs/Transfer Logs

Manifests

To create a manifest of a tape, containing paths and names of all files stored, use Create Manifest option in the LTO disk menu.

Canister's Console

Besides Transfer Logs, both Canister and LTFS events are recorded in the Console Log. This console output is essential to tackle issues with tapes, drives, and drivers.

To access the Console on macOS, use Shift-Command-C. Text is selectable, and also searchable (Command-F).

To view the Session Log in real time, click the Canister menu -> Log Viewer.

Connect

Get a live overview of Canister transfers in progress – plus receive push notifications on completed transfers wherever you are.

Requirements

  • Canister 23.2 or newer

  • A modern web browser

How to use

  1. Go to Settings > Connect.

  2. Toggle Enable Connect to ON.

  3. Copy the Connect Code by clicking the clipboard icon.

  1. Enter the Connect Code into the Connect site.

  2. Start a transfer in Canister, and your transfers will appear on the Connect site.

Receive Notifications

Connect can send push notifications about completed Canister transfers to a network-connected device.

  1. Click Allow in the notifications popup on your device.

  2. When the grey bell turns blue, Connect will send you notifications for completed transfers.

Enable Push Notifications from the Connect site on mobile devices

  • iOS 16.4 and newer:

    1. Save Connect as a web app by tapping the share button in the iOS toolbar, scrolling to the bottom of the menu, and tapping Add to Home Screen.

    2. Open the web app and click the notification bell icon.

    3. Enable Notifications for this website when prompted.

If the notification button is disabled, your browser does not support notifications, or notifications are disabled.

Change connection name

By default, Connect will display the Computer Name.

The connection name can be changed in Canister > Settings > Connect > Computer Name.

Revoke access

Use the Revoke Access button in the settings panel to cancel all connections to the Connect site. A new Connect Code will be generated automatically.

On the Connect site, you can delete a connection to a device by hovering over the device listed under Connections, then clicking X next to it.

Licensing

How many LTO decks can I operate with a Canister license?

Canister supports multiple tape decks being connected to the same computer, and they can all be used at the same time.

I have multiple computers with each its own tape deck.

How do I add Windows Support to my License?

I have a tape library, do I need Canister Pro?

Yes, Canister Pro is required to work with tape libraries. Support for tape libraries is currenly limited to macOS.

My license key won't activate the latest Canister

Collections can be further expanded by "Picking and Mixing" more items in any order. Canister outputs the contents of each Collection to its .

From 25.2 Canister for Windows can duplicate items when Archiving.

Preferably, use a faster-than-tape source for maximum write speeds to tape and .

LTO drives offer built-in hardware compression. Compression is a property of a tape and is set to use compression during the format process. After the property has been set, it cannot be removed without again erasing the tape. As the compression has zero to no overhead, this is enabled by default. Since compression happens in-device, there's is no feedback on the process, or on how much data is actually saved. If you need to disable compression, use the option.

From 23.2 onward, Canister for Mac supports tape media by MagStor. NanoPure tapes are pre-cleaned, with calibration data recorded to the Cartridge Memory after testing. Canister uses this information to calculate system health at the end of each Archive or Retrieve operation. Each Transfer Log will contain a NanoPure score: Good, Average or Poor.

When Canister for Mac is presented with a source that won't fit on the mounted tape, it enters Spanning mode. Once this happens, you'll be prompted to set a Spanning Label, which makes it easy to find your data later in the Catalog.

In turn, Canister will group the tapes for each Spanning part like this:

From here, rinse and repeat for as many tapes as it takes to complete the Archive.

When Canister for Windows is presented with a source that won't fit on the mounted tape, it will archive as much as possible, then prompt you to load the next tape via the Windows Notification Center.

When prompted, enter the next tape and hit the format button to proceed if required. From here, rinse and repeat for as many tapes as it takes to complete the Archive.

Click Go to Connect ✨, or go to in your web browser.

Once you log into , click the grey bell icon (i.e. the notification button).

Go to the

Android -

For multiple computers with each its own LTO deck, you'll need multiple activations. Adding additional activations to your license can be done in the .

Windows support can be added by simply Extending your existing Canister license in the .

Chances are you have a license that starts with id and ends with ods or uks. This is a legacy license, and cannot be used with versions newer than 20.1. for an upgrade coupon or continue to use the now-legacy Canister .

verify
Netflix-Compatibility
NanoPure
speed up verification
Console
https://connect3.hedge.video
the Connect site
Connect site
Use notifications to get alerts
License Manager
License Manager
Contact us
20.1

Requirements

Canister itself doesn't have any requirements in terms of CPU and RAM, but LTFS does like ample resources.

Which versions of macOS and Windows are supported?

The most recent Canister for Mac requires macOS 10.15 Catalina or newer, and supports both Intel and Apple silicon.

Need to run Canister on an older macOS version? Find your download .

Canister for Windows requires Windows 10 or newer.

here

Need help?

Occasionally, your LTO drive is going to have a bad day. Users that are eligible for updates and support should reach out to the Canister Support Team for assistance - we got you 👊

Forensics

Sometimes, the above won't suffice. In such a case we ask you to send us all forensic data. These files are only used to help diagnose your issue, and are deleted afterwards.

In Terminal, copy/paste this one-line command and hit enter to generate a CanisterForensics.zip file on your Desktop:

zip -ATrq ~/Desktop/CanisterForensics.zip ~/Library/Application\ Support/Canister/.ConsoleHistory ~/Library/Application\ Support/Canister/Transfer\ Logs ~/Library/Application\ Support/Canister/Warning\ Logs

Send us the resulting file, and we'll be able to piece together your LTO history.

Using Explorer, navigate to /Users/Username/AppData/Roaming/Canister and zip both the Catalogs and Logs directory. Send us the resulting files, and we'll be able to piece together your LTO history.

Do you really need all of that? Yes.

LTO issues tend to become very technical very quickly. That's why there's not much we can do without logs files and console output. We're not a strict bunch, but LTO is an exception: if you have an issue that we feel requires us to have a look at these files, we will not help until you send them over. And no, a remote session won't do.

Questions

Which LTO hardware does Canister support?

Canister supports a wide range of LTO configurations from a variety of vendors. For most Macs, SAS-based units tend to be connected via a Thunderbolt, while PCs and Mac Pro's come with the option to install a PCIe HBA directly into the host system's motherboard.

  • LTO Drives: LTO-5 to LTO-9 by IBM, Quantum and HP.

    • Important: different drive vendors cannot be used at the same time.

  • HBAs: most ATTO and Areca models.

    • Highpoint RocketRaid controllers are not suitable for tape usage.

  • Thunderbolt/SAS LTO solutions by Symply, OWC, MagStor, mLogic and more.

  • Ethernet LTO solutions by Symply & MagStor (from Canister 24.1).

  • LTO Drives: IBM LTO-5 to LTO-9, Quantum Rev-C LTO-7 to LTO-9.

    • Important: HP drives are not yet supported on Windows.

  • HBAs: most ATTO and Areca models, plus selected LSI chipsets (eg. SAS2308, onward).

    • Highpoint RocketRaid controllers are not suitable for tape usage.

  • Thunderbolt/SAS LTO solutions by Symply, OWC, MagStor, Unitex, mLogic and more.

  • Ethernet LTO solutions by Symply & MagStor (from Canister 24.1).

Milage may vary with Fibre Channel-based drives. Canister does not detect which driver your FC device requires - you'll have to find that out yourself.

Unitex USB LTO solutions are not fully supported on Mac at this time.

Which macOS versions does Canister support?

Canister supports macOS 10.15 Catalina and newer. Both Intel and Apple silicon are supported.

While legacy downloads are available for older macOS versions, note that legacy means unsupported - if you run into issues, your best bet is to upgrade your OS. Also, your legacy OS might not work with the latest LTFS version - be sure to source a version that works with your OS from the LTO vendor.

Which LTO generations does Canister support?

All generations from LTO-5 and up are supported. As Canister works with LTFS, LTO-4 and older are not supported.

Is Canister compatible with Apple silicon?

My license, starting with id, doesn't work.

What about the mLogic LTFS Utility?

The mLogic LTFS Utility was a light version of Canister 20.1 that used to be included with every mLogic purchase. With the changes Big Sur brought along, the app was end-of-life'd and replaced with Canister.

The mTape app is no longer supported nor available for download. It does not work on Big Sur or newer macOS versions, nor on Windows. The mTape app uses a license provider that is no longer in business, so we can not help with deactivations.

Can I delete files from a tape?

The short answer is, "No, LTFS does not support file deletions." The only way to remove data from a tape is to erase it.

The long answer: it's possible to remove files from the index partition (by accessing a tape with Finder or Terminal and deleting files), but this will only make them vanish from the index; it will not clear the space used by the deleted files. As rolling back a tape will make the deleted files available again, it's not a security mechanism either, so don't bother.

Should I keep any free space, like with a hard disk?

No need to; Canister already does this for you. Canister reserves 5% of a tape's size for the index to ensure there's room for data overflow.

Can I rename a tape?

Yes, as of Canister for Mac 23.1 it's possible to rename tapes without formatting. Changing a tape's serial is not possible without a format.

What is the difference between formatting and erasing?

It's the same thing. People tend to refer to formatting when a tape is new and erasing when a tape is used but needs to be wiped clean. The process itself is identical.

Does Canister perform a "Long Wipe" before erasing?

No, this takes several hours and is not required to reuse a tape. If required, a long wipe can be initiated using this Terminal command: mkltfs -d 0 --long-wipe -f

Why does my LTO drive stop writing periodically?

By default, LTFS, and therefore Canister, will stop to sync the Tape Index every 5 mins. This provides a balance between safety and speed. If you prefer to sync only on unmount, this behavior can be manually overridden using the steps below.

Run the Terminal command below, then remount the tape: defaults write nl.syncfactory.Canister.Mac OverrideMountCommandArguments "-o sync_type=unmount -f"

Locate this file, then open using Notepad with administrator privileges: C:\Program Files\IBM\LTFS\ltfs\ltfs.conf.local

Make sure this is commented out using ###: ###option single-drive sync_type=time@5

Uncomment the following by removing the hashes, then save the file. option single-drive sync_type=unmount Finally, restart the system to apply the change.

Why does my LTO drive sometimes stop and partially eject the tape?

IBM have advised us that this is normal. Your drive's onboard computer works hard to ensure the read/write heads stay “on track”. Sometimes that means adjusting the tape tension to take up slack. Bottom line: as long as there are no error codes on the SCD, it’s situation normal. Until LTO drives landed on the Desktop, nobody noticed their foibles - now they do 🙂

What's the difference between LTFS and TAR?

The difference between TAR and LTFS is that LTFS is a file system. That means your OS already has the tools included to work with LTFS, which in turn means no vendor lock-in for you. With TAR, you're always relying on a vendor's app to work and will be in trouble if that vendor happens to go out of business. With LTFS, that will not happen, and it's why Canister only supports LTFS.

Can tapes made on Windows be read on macOS?

Yes, and vice versa. If a tape was made with LTFS, it's fully useable on both macOS and Windows, with and without Canister.

Is it possible to add multiple folders in one transfer?

Yes, since the release of 23.1 Canister supports Collections: any combination of files and folders (a Collection) can be dragged from Finder into the Source dropzone to be archived to tape. Canister 24.1 adds Pick & Mix, which allows you to update a Collection with more folders and files.

Is it possible to skip or disable verification?

You can safely skip verification by clicking the [X] next to a transfer when the copy part finishes. Disabling verification altogether can be done in the Preferences:

I'm moving to a new computer, what do I need to migrate?

Next, zip and move the Canister directory to your new system. This includes all Catalogs and Transfer Logs.

In Finder, navigate to ~/Library/Application Support/, zip the Canister directory and move it to your new system.

In Explorer, navigate to /Users/Username/AppData/Roaming/, zip the Canister directory and move it to your new system.

Can I daisy chain Thunderbolt LTO devices?

Yes, that's fine to do. You can also add Thunderbolt adapters to it without issue. If your source is also a Thunderbolt storage device try to use a separate Thunderbolt bus for that, to ensure optimal bus usage.

When doing simultaneous backups, can I mix LTO drives?

Yes, as long as they originate from the same LTO drive vendor (IBM, Quantum, HP) and thus use the same LTFS driver.

For example, if you have multiple LTO drives from different manufacturers that support LTO-8, and since LTO-8 cartridges are all made by IBM, as long as you use the same cartridge, you can use all of your LTO drives when doing simultaneous backups.

Can Canister duplicate tapes by copying files directly from tape to tape?

No. This approach is inherently error-prone and can undermine the integrity of what’s written to tape. Instead, use an intermediate SSD or NVMe to retrieve the contents of a tape, then archive those contents to the next tape.

How do I know when my drive needs cleaning?

If your machine shows a C on its display, all you have to do is insert the cleaning cartridge supplied by the manufacturer. The cleaning process will begin automatically, and once complete, the tape will eject by itself. After that, you're good to go. There's no need or usefulness to loading your cleaning cartridge in any other case.

Does Canister connect with any external services while in use?

When Canister launches, it automatically checks for updates and retrieves an updated list of LTO- related dependencies from Hedge's file servers.

My IT dept. doesn't want to lower security when installing macFUSE or HBA drivers

Some opsec teams get scared when they encounter macOS's requirement of reducing security when installing kernel extensions.

The short version: there's no way around it, as LTFS requires FUSE and you'll also need to install a kext for your HBA.

The long version (for your opsec team): it's not a bad thing at all actually, and not about more or less security. As named by Apple, “Reduced security” is a bit misleading, as it does not accurately describe what this kind of change actually represents.

  • Despite the unfortunate wording of “Reduced security,” kexts do not reduce a system’s security. If improperly developed, a kext could only affect system stability and reliability, but not the system’s security.

  • A given kext cannot be installed into the operating system unless it is approved and signed by Apple. It is not possible to run arbitrary code in the form of kext.

  • As noted, LTFS uses a kext called macFUSE, which has been battle-tested for over 15 years and proven to be exceptionally reliable.

  • Enabling kernel extensions simply brings the system on par with any x86-based (i.e. Intel) Mac system. You've been living with "reduced security" for decades already.

  • After changing the setting, and installing FUSE (and likely a kext for your HBA as well), the setting can be changed back.

Disabling SIP

Does your IT department refuse to install macFUSE? Do they insist it requires System Integrity Protection to be disabled on your Mac? Do they say kernel extensions (i.e. KEXTs) are legacy, and there should be a system extension to replace them? Send them this:

System Integrity Protection (SIP) does not block kernel extensions (KEXTs) from running. Also, SIP is not related to whether LTO is working or not and, thus, should never be disabled.

With Big Sur, Apple introduced system extensions as a replacement for kernel extensions. At this stage, those aren't mature enough to replace KEXTs, especially for those used by pro storage devices. If that were so, developers would've ported their KEXTs to system extensions today. Until system extensions are on par with KEXTs, this will be the status quo for the foreseeable future.

Also, Apple did not completely kill off KEXTs. Instead, with Apple silicon, they introduced Security Policies. The default setting prevents even Apple-authorized KEXTs from being installed out of the box. When installing a trusted KEXT like macFUSE, a Mac's Security Policy must be changed to allow signed kernel extensions to load. Changing that Security Policy is also required for every RAID controller and HBA that lives inside storage.

Modifying a Mac's Security Policy is straightforward. It takes one minute, and we documented the process in detail here:

Installing drivers

Troubleshooting

A collection of things any LTO user once in a while runs into. As with all things hardware, from time to time, there will be errors.

"Tape changed to read-only by LTFS"

This error is LTFS's way of reporting something is wrong with either the tape or hardware.

Whenever LTFS drops a tape to Read-Only mode, it does so because too many write errors are reported by the writing part of the tape head in the drive. This results in Canister having to fail the Archive, as there's an external issue that needs solving.

Possible causes

  • Faulty tape media (error code 6)

  • Faulty/dirty/worn LTO drive head (error code 5 or 6)

  • Out-of-date LTO firmware

  • A too-high operating or environmental temperature

When it comes to troubleshooting, the steps below should be followed in order:

  1. Check the Single Character Display (SCD) on the front of the drive. Sometimes all you need to do is insert the cleaning tape, but only if you see a C. Other codes are documented below.

  2. Try with another tape, ideally from a different batch. Every tape surface comes with irreparable faults, with faults often recurring within a batch, so make sure to rule this out.

If the problem persists, the next step is to request a diagnostic from the drive vendor.

My LTO device displays an error code. What does it mean?

Every LTO drive is essentially a computer, and as such follows its own instructions and error handling. Most drives have a single-character display (SCD) to tell you how it's doing. It's behind a black see-through panel so you won't see it except when booting (a countdown shows) or when an error is stated.

Anytime there is a number or letter visible on the front of your LTO drive, the software is not able to communicate with the drive. Refer to this list of SCD error codes to find out how to resolve the issue at hand. As these are hardware errors, get in touch with your vendor to sort out the issue if needed.

SCD Code

Description

0

No Error. Ran successfully.

1

Cooling problem.

2

5V dc power problem. Tape drive detected that the Drive Power Supply is approaching the specified voltage limit (drive is still operating) or is outside the specified voltage range (drive is not operating).

3

Tape drive determined that a microcode error occurred.

4

Microcode or tape drive problem. Tape drive determined that a microcode or tape drive hardware failure occurred.

5

Tape drive problem. Tape drive determined that a hardware failure occurred.

6

Tape drive or media error. Tape drive determined that an error occurred, but it cannot isolate the error due to faulty hardware or to the tape cartridge.

7

Media error.

8

Tape drive, SCSI bus or fibre channel error.

9

Tape drive or RS-422 error.

A

Tape drive hardware problem.

B

No error or message is assigned.

C

Tape drive needs to be cleaned.

D

No error or message is assigned.

J

A too-new tape is loaded into an older-generation LTO drive.

=

The Unload button on the drive was pushed in and did not release.

"Medium consistency check failed"

This error means LTFS has detected the last known tape index is faulty, and thus cannot mount. If mounting does not succeed due to index issues, LTFS will itself do a recovery, and then throw this error if that's unsuccessful.

This error is often caused by a disconnected Thunderbolt cable or a power loss. If this tape has no valuable data on it, it's by far the easiest to just reformat it. If that's not possible, you can try a Repair action in Canister.

Canister's Repair option triggers a full recovery, which can also be done directly in Terminal:

ltfsck -f 0

After a full recovery, a _ltfs_lostandfound folder is created on the tape. LTFS has created binaries of all non-referenced data and added them to the index. This is not really useful stuff, but it's an indicator that a rollback is needed to get to the data.

It's also possible to do a deep recovery. First unmount the tape, then do…

ltfsck --deep-recovery 0

If none of this helps, it's time for a rollback.

Rollbacks

For each change on a tape, LTFS creates a new index. These are called "generations." Consider them snapshots, and it's possible to roll back to a previous snapshot. When you find a snapshot that works, you can continue with that and archive new data to tape.

In Terminal, list the rollback points. Note: this process takes time! Go grab some coffee.

ltfsck -l 0

Creating a rollback list is done top down, starting with the most recent one. Monitor the timestamps to find the desired rollback point, and cancel with Command-C.

Then, roll back to that generation:

ltfsck -g 57 -r 0

Here, 57 is the generation number, and 0 is the drive ID. If you have one LTO drive, it's always 0.

When the process is done, mount the tape and you'll see its contents restored.

My tape mounts, but it suddenly contains a lost_and_found folder

If your tape is showing a lost_and_found folder, the tape has been Repaired, only somewhat unsuccessfully.

When a tape cannot be mounted, LTFS will report if a Repair is needed. If the Repair process locates data on the tape's data partition that is not referenced in the index partition, it's added as "lost and found" data. This is raw data and does not expose file names, so for most purposes, it's quite useless. Only if you know what should be on that tape and what is missing you would be able to cross-reference file sizes and rename the files in that folder through Terminal's mv command.

Releases

Any version of Canister that is older than 1 year is unsupported and considered legacy. Chances are that a legacy version will work completely fine, but if you run into trouble, try to reproduce the issue with the most recent release before requesting support.

Canister 25.2

Verify Duplicates, on Windows. If a file is found to already exist on tape, Canister will use checksum verification to check if the files are identical or not. This is a huge time saver when something goes wrong with your LTO drive, so it's enabled by default.

Canister 25.1

Queuing, Spanning & Independent Transfers for Windows.

Canister 24.2

Introducing Canister Pro for Mac, including an innovative Tape Library Manager, firmware update notification for Windows, Choose files to Skip and more.

  • Fixes a pesky crash during tape indexing and transfer (Thanks, Marty & Tayfun).

  • Fix for edge case involving misplaced checksums vs empty folders (Thanks, Ben).

  • Resolves a crash when a source happens to go MIA before Archive transfers start.

  • Progress bar polish, because details matter.

  • Correct volume name is now used when Cataloging Pro Max tapes (Thanks, Daniel).

  • Improved handling of the "IOCreatePlugin" alert when manually ejecting tapes.

  • Fix for a nasty crash involving filenames with weird emojis.

  • Transfer ETAs no longer disappear on extremely long transfers.

  • Further Connect stability improvements.

  • Various Console tweaks that help our team support you.

  • Improved firmware detection for IBM Full Height LTO drives.

  • Spanned catalogs are updated once again (Thanks, Diego).

  • Skip Cataloging in Retrieve mode (Thanks, Roger).

  • Tidy up various messages in the Console.

  • Several improvements to the Cataloging engine (Thanks, Roger 🙏)

  • The "Retrieve with Full Path"-checkbox works once again

  • Fix for detecting Ethernet-based desktop LTO drives

  • Improved handling of tapes formatted with LTFS by Archiware P5

  • Introducing Canister Pro for macOS!

  • New in Pro: Single Drive Tape Library support (Huge thanks to Magstor for helping with the hardware, and to our Beta Test crew Joe, Henry, and Tom 🙏).

  • Choose which file types Canister should skip during transfer.

  • Fix for a rare item counter issue when Spanning.

  • Various improvements down in the engine room.

  • Minor tweaks to the Catalog Storage Browser.

  • Fix for Canister returning to Preflight Checks screen after 24 hours.

  • Choose which file types Canister should skip.

  • Preflight Checks now notifies you when new LTO firmware is available.

  • Fix for rare Archiving issue when using Pick & Mix Collections.

Canister 24.1

Pick & Mix Collections, Ethernet LTO drive support, plus a swathe of updates for Windows.

  • Fix for multiple compression state messages in the Console.

  • Additional tweaks to keep Connect running smooth.

  • Fix a rare bug causing some HP drives to not show the mount button.

  • Catalog searches now work for everybody once again 🙂

  • Add more items to a Collection using Pick & Mix.

  • Support for Symply's Ethernet-connected LTO drives.

  • Preflight Checks now notifies you when new LTO firmware is available.

  • Catalog support is now bundled with Canister, removing the need for Apple's Command Line Tools 😅

  • Transfer results are logged to the Console to make sure our Support team can help you even faster.

  • Improved handling of incompatible tapes.

  • Get notified when an update is too new for your license

  • Improved LTO drive detection in Preflight Checks

  • Empty folders are now copied (Thanks, Albert!)

  • Improved robustness of indexing

  • Connect improvements, to keep things running smoothly

  • Lots of little UI tweaks because the details matter!

  • Add more items to a Collection using Pick & Mix.

  • Support for Symply's Ethernet-based LTO drives.

  • Make multiple tape copies at the same time, with Simultaneous Transfers.

  • Preflight Checks for Windows, making setting up LTO a breeze.

  • One-Click Support™️ at the touch of a button.

  • Watch Canister's Event Log in real-time using the Log Viewer.

Canister 23.2

Support for Windows, Connect and NanoPure media.

  • Right click anywhere in the Drive node to show the Drive Menu.

  • Moot __MACOSX folders are ignored when Archiving.

  • Console Auto-Scroll improvements.

  • Stop button is now clickable when Spanning is waiting for the next tape.

  • Connect improvements to keep things running smooth.

  • Log LTO compression state when loading a tape.

  • Monitor LTO transfers from anywhere with Connect 🙌

  • Support for MagStor's NanoPure range of premium LTO media.

  • Automatic 10-day trial mode

  • Various stability improvements (Thanks Adnan & Desi 🙏)

  • Transfer Log tweaks for better readability

  • Drive Node now has a nice indexing counter

  • Setting to choose whether tapes are ejected, unmounted or left alone on app close (Roland 🙂)

  • Transfers are now failed automatically if LTFS drops a tape into read-only mode

  • Lots of visual polish 💅

  • First release of Canister for Windows ✨

  • Support for IBM based LTO drives

  • Archive, Retrieve, Catalogs, Dupe Detect, Logs, Connect & more!

Canister 23.1

Collections for Canister, and more.

  • Small improvements to help our support team live their best life.

  • Fix for an annoying crash with some older models of Quantum and HP LTO drives.

  • New Netflix-Compatibility mode, disables LTO hardware compression

  • Improvements for LTO-6 drive behavior

  • Reinstate .txt file extension for Manifests

  • Fix for unnecessary "Completed with Warnings" transfer states (Thanks to Samuel, Andy, and Greg 🙏)

  • When spanning, the Transfer View scrolls to the current tape

  • Displays the amount of files being catalogued after mounting a tape

  • Transfer Logs now take into account files that have been removed from the Source during Archive

  • Fix for a rare crash when mounting tapes without a volume label (Thanks to Joe at The Oscars!)

  • Improved handling of write-protected tapes

  • Lights out and away we go... ETA for Archive & Retrieve is here!

  • Write-protected tapes are no longer selectable for Archiving, to save you from some headaches down the road.

  • Sometimes spanning would not progress to a next tape due to an edge case. Big thanks to Jake, Jonathan, Josh, Ray, Sam, Scott & Yves for helping with hunting down this pesky nuisance 🙏

  • Free space on a tape gets updated properly after archiving without having to unmount a tape first (Thanks, Christiaan & David!)

  • No more endless spanning caused by source files going MIA (Thanks, AJ & Darren!)

  • ...plus lots more little improvements behind the scenes, bonus points if you spot them all!

  • Fix for a rare edge case that would prevent Canister from starting (Thanks, Arturo 🙏)

  • Newly created Destination folders are now automatically selected, saving you some clicks.

  • The Updates Available ribbon works again!

  • Fix for activation state not always showing in Preferences (Thanks, Joe & Cole 🙏)

  • Unresponsive LTO drives no longer cause "something unexpected happened" alerts

  • Fix for the Format button not being visible at all times, when spanning (Thanks, Mattia 🙏)

  • Fixes a crash when Retrieving lots of files (Thanks, Fulvio and Neil 🙏)

  • Choose where to save Manifests

  • Disables Cmd-Q when Spanning is waiting for a next tape

  • Fix for HP drives giving us headaches (Thanks to Rick, Chris, Victor, Perry, and Brice!)

  • Starting Canister after a Force-Quit resets LTFS properly (Thanks to Corentin, Tom, and Fulvio!)

  • Fix for a subtle timing issue causing unnecessary Tape Not Unloaded alerts

  • Tapes are now preselected when you have just one LTO drive

  • Fix for a rounding error in the completed Spanning progress %

  • Mounted tapes now come with a nice icon

  • Improved human-readable units in Transfer Logs

  • Empty folders now have the correct folder icon in the Tape Browser

  • Collections allow you to drag-n-drop any combination of items as a source.

  • Decide whether to eject, unmount, or do nothing with a tape after Archive and Retrieve.

  • Canister will tell you if there's a tape present but not loaded, with a new Load button.

  • macOS Sierra 10.12 is no longer supported.

Canister 22.3

A "Retrieve with Finder" extension, support for Ventura, and more...

  • Early Warning Radar for LTFS errors that cause unsuccessful transfers.

  • One-Click Support™️, for those cases where LTFS goes into a funk 🤪

  • New setting to recreate the full path when retrieving.

  • For your entertainment, indexing now has a nice counter.

  • Command-W now works on the Console and Transfer Log windows.

  • If formatting fails, the tape name and serial are saved for a next attempt.

  • New setting to prepopulate a tape's serial with the date.

  • Detection of files going AWOL on a source during archiving.

  • Fix for Cataloging not always finishing up properly

  • Console improvements that allow us to do even better customer support 🙂

  • Fix for HPE drive detection

  • Workaround for stalling indexes

  • Canister now opens in the last used mode (Archive or Retrieve).

  • The Transfer and Warning logs are merged.

  • Improved Spanning progress bar accuracy.

  • Fix for MagStor B-series HBA download

  • Several spanning percentage improvements

  • Indexing tapes during spanning now shows the number of files indexed.

  • Support for the new MagStor C-series HBAs.

  • Built-in a warning for starting a Repair, as that can be a bit time-consuming.

  • Improved illegal character prevention when setting a serial when formatting a tape.

  • Direct Warning Log access from the Window menu

  • A lot of visual polish; see if you can spot all five improvements!

  • Adds a Force-Quit option for when LTFS is stuck indexing. If you run into this, ping us.

  • New: a Finder extension to Retrieve files directly from the Catalog.

  • Support for macOS 13 Ventura.

  • Selecting or unselecting all files when Retrieving is a lot easier now.

  • Set a custom Catalog location.

Canister 22.2

Official support for MagStor drives, and more.

  • Fixes an issue where sometimes Canister could not mount a fresh tape during spanning.

  • Tape name and serial weren't always added to a Transfer Log after a Transfer.

  • Fixes an issue where Canister could not always fetch the LTO drive vendor.

  • Improved handling of HBAs that don't work well with LTFS.

  • Improved error handling for troublesome tapes.

  • For test purposes, skip all Preflight Checks using the cheatcode idkfa

  • Retrieving files now doesn't preselect everything on a tape.

  • The transfer view now also shows the destination folder(s).

  • Added LTFS version to Transfer Logs

  • Improved handling for tapes with WRITE PERM errors

  • A bunch of small copy changes to improve your well being 😁

  • Detection of HBAs that do not support LTFS

  • Improved macFUSE update flow, for when other FUSE mounts are present.

  • Added legacy ATTO drivers for 10.14 and older macOS versions.

  • As all new FUSE versions work fine with LTFS, the FUSE check now only checks for a minimum version.

  • Fixes an issue where Canister lost its state after hiding in the Dock

  • Fix for endless cataloging after formatting a tape

  • Cosmetic changes, most notably on the Next and Previous labels that were missing some pixels.

  • Fixed a crash that sometimes occurs after checksum creation.

  • Preflight Checks no longer requires ATTO drivers to be up to date all of the time.

  • We finally got rid of that ugly Mount button 😄

  • Fixed a crash that sometimes occurred when Ejecting a tape.

  • Improved the color of the progress bar during Verification.

  • Workaround for the endless "Cleaning Up..." issue, caused by a bug in LTFS. We're still waiting on feedback from IBM and FUSE, but don't want to keep you waiting on a fix in LTFS.

  • New Verification Watchdog, resolving stalling verifications.

  • Empty tapes are no longer cataloged.

  • Preflight Check results are now logged in the console.

Canister 22.1

Spanning allows you to archive more data than fits on a single tape. Canister will ask you to add another tape when the first is full, and continues doing so until all data is archived.

  • Improvement for HP LTFS now requiring FUSE to be installed before anything else.

  • Fix for a rare crash related to the Erase view.

  • Activating Canister would sometimes show an incorrect Upgrade popup, that's fixed.

  • We also fixed a crash when Destinations space runs out during Retrieval.

Canister 21.2

Meet Preflight Checks: each time Canister starts, it runs a full diagnostics of your LTO setup and points out what is missing or needs updating.

  • Polish for some Preflight Checks.

  • Support for archiving Macintosh HD system disks (including /Library folders). NB: restoring macOS directly from tape is not recommended.

  • Support for new ATTO driver for Big Sur and more mTape serials.

Canister 21.1

Canister gains Duplicate Detection, skipping files that already exist on tape. Files with identical names, but different sizes or modification dates will replace the existing file, keeping the original available as a hidden file.

  • Fix for retrieving files with % in their filenames.

  • Our license provider WyDay released a fix for the activation issue present in macOS 10.12, 10.13, and 10.14.

  • Sometimes, the registration for trials didn't go as planned. All good now.

  • Due to a regression in macFUSE, it's no longer allowed to use commas in tape names (Thanks, Jimmy!)

  • Some licensees that got their license through a partner are asked to enter their email so we know who you are in case you need help.

  • Adds support for the new Quantum LTFS driver on M1.

  • Fixes a bug where sometimes a folder in a tape's root couldn't be selected when archiving.

  • Fixes a bug that sometimes occurred when mounting a Catalog.

  • Fixes a crash that sometimes occurred when mounting a tape.

  • Mounting, Indexing, and Cataloging stages are now visible in the interface when mounting a tape.

  • Checks for the new ATTO drivers, as well as for SANLink and Arcsas.

  • Fixes few small bugs.

  • Fixes a bug that caused the tape name to be NONAME.

  • Time Machine sidecar files (.com.apple.timemachine.donotpresent) are no longer archived.

  • The Transfer Log shows the destination root folder again.

  • Some text fields were stuck in dark mode. That's fixed.

  • A brand new icon 🎉

  • Retrieving is again done alphabetically.

  • Proper depicting of the source name instead of always showing the volume name.

  • Added an 'Already Transferred' state when a transfer doesn't contain new files.

  • Selecting a Destination Folder now shows the correct tape name.

Canister 20.2

A new licensing system, and a boatload of improvements.

  • Added support for Fuse 4.

  • Added support for Big Sur.

  • Added support (and a logo) for mLogic users.

  • This update makes Archiving for Discovery Channel a cinch. Simply add a metadata.xml to the root of the folder you want to Archive, and Canister will do the rest.

Canister 20.1

  • Canister now detects when a tape is empty or unformatted, offering you the option to format, and also provides more feedback about drive-related errors.

  • The console has much more output, and timestamps. Timestamps, good.

  • Creating a new destination folder when archiving could sometimes result in Canister ignoring it.

  • El Capitan users reported problems when browsing a tape and not being able to resize the browser. Fixed.

  • Canister handles drives that are disconnected during a transfer more gracefully.

Canister 19.1

  • File sequences are written sequentially to tape, speeding up retrievals.

  • Indexing large sources doesn’t result in spinning beachballs.

  • Huge transfers take up a lot less RAM than they used to.

  • When quitting all mounted tapes are now ejected making sure indexes are up to date.

  • Force-quitting the app doesn't affect tape indexes.

Canister 18.1

First Canister release 🎉

  • Canister 18.1.5 contains some small bug fixes. Thanks for reporting all!

  • Canister now mounts a tape right after erasing/formatting it, so you can start archiving straight away 🚀

  • Improved support for extended attributes, aliases, and bundles.

  • Canister sometimes crashed on quit. Fixed!

Canister 18.1.3 (November 06, 2018)

  • MLU update

  • Canister now mounts a tape right after erasing/formatting it, so you can start archiving straight away 🚀

  • Some Tandberg owners reported that Canister had trouble installing the correct drivers for their machine.

  • You can share your System Information with Support (in case you run into trouble and would like our help).

  • Fixed a crash that occurred when you tried to create a Transfer Log file for an empty transfer.

Beta Track

From time to time, we'd like your feedback on new features before making them available to everyone. This Beta Track is available to all users with a Canister license eligible for updates and support.

Do not use Beta software in production - it's not ready yet!

Getting started

  1. Request beta access via Canister support - we'll give your license key beta superpowers ✨

Feedback & Bug Reports

We like to hear when something is working well, but perhaps more importantly, we need to know when something isn't. Feedback can be sent in-app via the Contact Support button. Bonus points for notes on how to reproduce any unexpected behavior.

Need help?

Can't activate Arctic?

Final Cut Library Manager (FCLM) used a different license key format than Arctic:

  • Arctic - ABCD-EFGH-IJKL...

  • Final Cut Library Manager - FCLM...

You must use an Arctic license key to activate Arctic. You cannot activate Arctic with a license key for FCLM.

Still stuck?

  • The version of macOS you're using:

  • The Arctic version you installed:

  • Screenshots (or a screen recording!) of what you're experiencing

  • Some details on what led up to your experience

Sending us your database

Sometimes, we request you to send us your Arctic database to have a better look. Use this Terminal.app command to generate a zip on your Desktop, which you then can send to us:

Supported Formats

EditReady supports any file in a QuickTime or MXF wrapper plus a wide range of vendor-specific formats, including many RAW codecs:

  • Apple Intermediate

  • ARRIRAW

  • Blackmagic RAW (BRAW)

  • Canon RAW

  • Codex HDE*

  • DNxHD

  • DNxHR

  • DVCProHD

  • H.264

  • H.265 (HEVC)

  • Phantom CineRAW**

  • ProRes

  • ProRes RAW

  • RED RAW (R3D)

  • Sony RAW

  • Sony X-OCN

* ARRI Alexa 35 HDE MXFs are not supported.

Note on Blackmagic Camera Support

Installing

When something unexpected happens, you'll be prompted to Retry or Contact Support.

Alternatively, you can reach out using the Contact Support option in the Help menu:

In both cases, you'll be prompted to tell us what you're running into. All required support files, like Canister's console, are automatically sent along with your request.

When something unexpected happens, use the Contact Support option in the Canister menu. In a few words, describe the problem you're running into (logs are automatically attached).

You can use the latest Canister, available .

Up to and including

  • 10.12 Sierra up to and including

  • 10.11 El Capitan up to and including

Yes - as of version 21.1, Canister is natively compatible with Apple silicon. You can update Canister in-app, or

You have a legacy license key suitable for Canister 20.1 () and older. This version received support until Dec 31 2020, and does not support macOS 11 Big Sur or newer.

To upgrade a legacy Canister license .

Every existing mTape licensee can for a crossgrade discount to Canister.

First of all, deactivate Canister in-app or through the online so you free up your license to be used on the new computer.

Canister also reaches out to our license and crash handling providers, which are documented in the section.

If the LTO drive is running on , perform the relevant upgrade and try again. The success rate of this treatment is very high, so don't skip it.

Canister 25.2 (May 27th, 2025) -

New ✨

  • Instead of just checking for file size and modification date, Duplicate Detection can now verify duplicates.

  • Checksum values are no longer available for transfers done in Trial mode.

Improved

  • Retrieve Transfers again show up in Connect.

  • Various minor tweaks and fixes behind the scenes.

Canister 25.1 (Feb 11th, 2025) -

New ✨

  • Queuing: stack multiple transfers of the same type.

  • Spanning: seamlessly Archive over multiple tapes.

  • Independent Transfers: Use each tape device to be used independently of one another.

Improved

  • Support for System Notifications when a Transfer finishes.

  • Preflight Checks now detects supported LTO drives in the "Other Devices" class.

  • Improved handling of LTFS format failure.

  • Underscores and hyphens are allowed in tape names.

  • Handy option to prepopulate the tape serial number with the date.

  • Canister will ask before cancelling an active transfer.

  • Write protected tapes are greyed out in Archive mode.

  • Set a custom location for your tape Catalogs.

Canister 24.2.6 (Feb 7th, 2025) -

Canister 24.2.5 (Dec 11th, 2024) -

Canister 24.2.4 (Nov 26th, 2024) -

Canister 24.2.3 (Oct 31st, 2024) -

Canister 24.2.2 (July 25th, 2024) -

Canister 24.2.1 (July 4th, 2024) -

Canister 24.2 (May 21st, 2024) -

Canister 24.2.2 (Dec 10th, 2024) -

Canister 24.2.1 (June 11th, 2024) -

Canister 24.2 (May 21st, 2024) -

Canister 24.1.2 (February 28th, 2024) -

Canister 24.1.1 (January 31, 2024) -

Canister 24.1 (January 9, 2024) -

Canister 24.1.1 (March 14, 2024) -

Canister 24.1 (January 9, 2024) -

Canister 23.2.2 (November 8, 2023) -

Canister 23.2.1 (October 26, 2023) -

Canister 23.2 (October 10, 2023) -

Canister 23.2.1 (November 7, 2023) -

Canister 23.2 (October 10, 2023) -

Canister 23.1.8 (October 06, 2023) -

Canister 23.1.7 (September 27, 2023) -

Canister 23.1.6 (July 7, 2023) -

Canister 23.1.5 (June 21, 2023) -

Canister 23.1.4 (Apr 7, 2023) -

Canister 23.1.3 (Mar 16, 2023) -

Canister 23.1.2 (Mar 3, 2023) -

Canister 23.1.1 (Feb 22, 2023) -

Canister 23.1 (Jan 25, 2023) -

Canister 22.3.5 (Jan 13, 2023) -

Canister 22.3.4 (Jan 4, 2023) -

Canister 22.3.3 (Dec 29, 2022) -

Canister 22.3.2 (Dec 14, 2022) -

Canister 22.3.1 (Nov 15, 2022) -

Canister 22.3 (Oct 18, 2022) -

Canister 22.2.11 (Sep 19, 2022) -

Canister 22.2.10 (Aug 10, 2022) -

Canister 22.2.9 (Aug 09, 2022) -

Canister 22.2.8 (July 27, 2022) -

Canister 22.2.7 (July 15, 2022) -

Canister 22.2.6 (June 28, 2022) -

Canister 22.2.5 (June 22, 2022) -

Canister 22.2.4 (May 24, 2022) -

Canister 22.2.3 (May 13, 2022) -

Canister 22.2.2 (May 3, 2022) -

Canister 22.2.1 (Apr 15, 2022) -

Canister 22.2 (Apr 12, 2022) -

Canister 22.1.3 (Apr 8, 2022) -

Canister 22.1.2 (Mar 22, 2022) -

Canister 22.1.1 (Feb 23, 2022) -

Canister 22.1 (Feb 1, 2022) -

Canister 21.2.3 (January 26, 2022) -

Canister 21.2.2 (December 30, 2021) -

Canister 21.2.1 (December 16, 2021) -

Canister 21.2 (December 9, 2021) -

Canister 21.1.10 (November 09, 2021) -

Canister 21.1.9 (October 07, 2021) -

Canister 21.1.8 (July 27, 2021) -

Canister 21.1.7 (July 22, 2021) -

Canister 21.1.6 (July 02, 2021) —

Canister 21.1.5 (June 08, 2021) —

Canister 21.1.4 (March 26, 2021) —

Canister 21.1.3 (March 24, 2021) —

Canister 21.1.2 (March 01, 2021) —

Canister 21.1.1 (February 19, 2021) —

Canister 21.1 (February 12, 2021) —

Canister 20.2.4 (December 21, 2020) -

Canister 20.2.3 (November 10 9, 2020) -

Canister 20.2.2 (November 03, 2020) -

Canister 20.2.1 (October 16, 2020) -

Canister 20.2 (August 19, 2020) -

Canister 20.1 (February 25, 2020) -

Canister 19.1 (July 11, 2019) -

Canister 18.1.5 (November 30, 2018) -

Canister 18.1.4 (September 18, 2018) -

Canister 18.1.2 (October 23, 2018) -

Canister 18.1.1 (October 03, 2018) -

Canister 18.1 (September 18, 2018) -

Queuing Beta 3

All the good stuff from the previous Betas (Queuing, Independent Transfers), plus these fixes:

  • Erase, Rename, and Repair are no longer greyed out when a Tape Library is detected.

  • Connect will update correctly when Queued transfers are removed.

  • Various under-the-hood tweaks you can't see, but will make your LTO life better.

Known issues:

Tape Migration Beta 1

A first look at Tape-to-Tape Migration, plus a dedicated window to show transfer progress.

  • Migrate from one LTFS-formatted tape to another.

  • Intelligent buffering to prevent shoe shining - works best with a flash-based boot drive.

  • New navigation buttons and a dedicated Transfers view.

Download the Beta installer .

Install - full LTO setup instructions can be found .

Request beta access via Canister - we'll give your license key beta superpowers ✨

Download the Beta installer .

Install - full LTO setup instructions can be found .

Make sure you’ve installed , then activate it with your license key for Arctic.

Can’t find your Arctic license key? You can find it in the .

Reach out to Support here – – then send us these details:

** Phantom CineRAW requires an license.

Discovered a file EditReady won't convert? Tell us about it:

When Blackmagic releases new camera models, third party applications often need to release an update to fully support the new model. If you've gotten the latest Blackmagic Camera and we haven't yet shipped an update for EditReady, you can install the on your computer. EditReady will default to using the newer version of the BRAW tools.

EditReady is available as a direct download from . After you've downloaded EditReady from our website, just drag and drop it into your /Applications folder, and it's installed.

Progress bars sometimes redraw themselves. Tell us if you find anything else!

download the latest release here.
download
reach out
reach out
License Manager
old firmware
here
Canister 24.1
Canister 22.3
Canister 20.2
zip ~/Desktop/Arctic.zip ~/Library/Application\ Support/Arctic -r

Getting Started

Clips can be added to EditReady by selecting Open under the File menu, or by dragging clips into the EditReady window. Your clips will appear with thumbnails in the EditReady window. You may toggle between List View and Thumbnail view using the selector in the toolbar.

If you'd like to convert all of your clips, simply click the Convert All button on the right. If you'd only like to convert some clips, you can select them by clicking the flag icon (or selecting Flag Clip from the Clip menu). Then click Convert Flagged.

EditReady includes a variety of presets for popular editing formats like ProRes and DNxHD. You can customize these further by creating custom presets.

Regardless of the preset you select, you have the option of adjusting the destination folder and destination file name. See Naming your Files for details.

Multiple Windows

You can open multiple windows by selecting New Window from the File menu. This allows you to easily queue different batches, with different settings.

Monitoring Progress

After starting a batch, the sidebar will toggle to the Progress tab, which will show you progress information for each clip. The top of the EditReady window will show you progress information for the overall batch (or batches).

Finish Catalog installation

Converting Media

Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
here
here
support
here
here
the latest Arctic release
arctic@hedge.video
EditReady Pro
hello@hedge.video
Blackmagic BRAW SDK
hedge.video/editready

General

The General Settings pane exposes a few common settings that can be used to customize how EditReady processes files. For most users, the default settings will be correct and should not be adjusted.

Parallel Job Count

This setting controls how many files are converted in parallel. By default, EditReady automatically configures itself based on your computer's capabilities and will attempt to fully utilize your Mac's processing power.

Reducing the job count may be helpful in reducing memory consumption on machines with very limited RAM, especially when working with very high-resolution (8K / 12K) footage.

Audio Bit Depth

EditReady produces 24-bit audio by default. This is the industry-wide default for video editing and post-production. However, some workflows or hardware playback devices may require reduced-bit-depth audio.

Hardware Acceleration

All modern Macs have powerful video encoding and decoding hardware, which can speed up video conversion by multiple orders of magnitude. However, this hardware can have trouble decoding the latest video formats. Disabling hardware acceleration and using a purely software-based approach can help process those files in those cases.

Connect

Connect is our companion app that gives you live insight and push notifications about the state and progress of your transfers, transcodes, and archiving.

Connect is available for all licenses that are eligible for updates and support. Pro licenses automatically send their data to Connect, while non-Pro licensees must manually hook up their computers to Connect in-app.

Dashboard

Setting Up

Connect is available in OffShoot, EditReady, and Canister. We have setup guides available for each app:

Requirements

Connect has seen several iterations in the last 10 years, and is currently on its third. That means not every application that shows a Connect panel is still functional. These are the minimum versions required for the current Connect:

  • Canister 23.2

  • EditReady 24.4

  • OffShoot 23.2

EditReady

EditReady provides easy, powerful, and fast transcoding for video professionals.

Modern production pipelines often involve generating a wide mix of QuickTime, MXF, AVCHD, and HDV files. A single production may use a mix of "A-Camera" files in ProRes422, "B-Camera" footage in H.264, as well as archive footage in formats like Apple Intermediate Codec.

EditReady lets you take this mix of files and convert them into a single mezzanine format, offering your post-production pipeline simplicity, reliability, and performance.

Metadata

One of the most powerful features in EditReady is the ability to view and edit the metadata contained in your files. You can access metadata for a clip by selecting the clip and then choosing Edit Metadata from the Clip menu, or by pressing Command-2 on your keyboard.

Browsing Metadata

Metadata may include camera settings like F-Stop, Iris, and Shutter, as well as items like Location (if your camera has GPS), media serial numbers, or even diagnostic data.

In some cases, there may be multiple entries for a single category of metadata. For example, your camera may store a Creation date in a variety of places throughout the file. If the values within the key don't match, EditReady will display Conflicting Values and provide a disclosure triangle to reveal the individual entries. If you'd like to unify all of these entries with a single value, click the checkbox to the right of the value you'd like to preserve. Any other value will be replaced.

If your camera includes GPS data in the metadata, those fields will have a Pin📍 icon, allowing you to view the clip location on a map.

Some metadata is intended only for use by the camera manufacturer during troubleshooting. So it may appear as simply a string of numbers or letters within EditReady.

Editing Metadata

To edit an entry, simply double click and begin typing. Depending on the field, EditReady may enforce requirements on the type of information you can enter (for example, date fields may only contain a valid date).

Adding Metadata

To add a new entry click the add metadata icon in the upper-right corner of the Metadata window. You'll be able to select from a variety of categories and metadata keys. Some metadata keys will restrict the types of data you can enter (for example, timecode entries must be valid timecode values).

Keys that already exist in your file will be disabled from the Add Metadata screen.

Removing Metadata

To remove a metadata entry, click ➖ to the right of the entry.

Global Metadata

EditReady allows you to set metadata across a set of files with a single operation. From the Metadata menu, select either Set Metadata for All or Set Metadata For Flagged. Select a category and metadata key, and then enter a value. This value will be set across all of the target files, and will replace any existing values for that key.

Queuing

Queuing makes it quick and easy to stack up multiple transfers for each tape drive. When queued transfers are made, Canister works its way through the list of queued items until completion.

Queuing also gives you the flexibility to use different LTO drives independently of one another. That means Drive A can be Archiving, whilst Drive B handles a Retrieve.

Tape Library Manager

Tape Library Manager requires a Pro License, and is currently only available on macOS.

From 24.2, it's possible to manage library inventory without leaving the Canister interface - simply drag and drop between your Drive, tape slots, and Mail Slot.

Mail Slots

Most Tape Libraries feature at least one Mail Slot. A Mail Slot allows tapes to be removed and transported without powering down the device. For convenience, Canister's Tape Library Manager shows Mail Slots alongside regular tape slots.

Hardware Support

Canister doesn't currently support multi-drive tape libraries.

Tape Library Manager is validated for use with the following models:

  • Qualstar Q24

  • BDT Flexstor II

  • Quantum Superloader 3

As most libraries are using the same underlying hardware from BDT, there's a good chance tape libraries from other vendors work just as well with Canister. Feel free to reach out when in doubt, or if you'd like to share that your variety of tape library also works.

HPE tape libraries are not (yet) supported.

Firmware

Besides requiring drivers, LTO drives themselves rely on firmware. As a LTO drive is basically a computer, consider the firmware to be its operation system. This firmware is just as much under active development as are the drivers, and should therefore not ignored when troubleshooting. When you run into issue, but all drivers are installed correctly, make sure your firmware is up to date.

Note: firmware is vendor-specific. Most modern LTO drives are made by IBM. For Tandberg drives and older Quantum or HPE drives, please contact your reseller.

Update Notifications

Canister Preflight Checks will notify users of IBM and Quantum drives when a new LTO firmware is available. Firmware updates are advisory and can be skipped if required using the > in the bottom right hand corner of the window.

Updating IBM firmware

To update your IBM LTO drive's firmware, first you install IBM Tape Diagnostic Tool (aka. ITDT), then update the firmware.

Updating Quantum firmware

Most modern Quantum drives are actually IBM drives, so you can use the ITDT process described below to update your firmware.

Updating HPE firmware

Colloquially known as HP, your drive may be either a real HP drive or a rebranded IBM. Preflight Checks will show you the firmware version number which will hold the clue to being an IBM drive or not; if it's four characters long with the first one a letter, chances are it's an IBM. If not, call your reseller as obtaining firmware for older drives is a drag. If it's IBM, you can use continue to read along.

Installing ITDT

Use the steps below to install and run ITDT:

  1. Open the Terminal app, then enter this single command followed by [Enter]:

~/Downloads/install_itdt_macos

  1. An alert will open. Click Cancel.

  1. You'll first need to allow the installation. Go to System Preferences > Security & Privacy > General.

  1. Click the Allow Anyway button (no need to click the Lock icon 🔒 first).

  2. Go back to Terminal, then enter the same command again followed by [Enter]: ~/Downloads/install_itdt_macos

  3. Another alert opens, this time click Open.

  1. Go back to Terminal, and input this command followed by [Enter]: ~/ITDT/itdt

  2. Type L, hit [Enter], then I (to accept the ITDT license agreement) and again [Enter]. ITDT is now set up.

  1. Double Click install_itdt_windows to run extract the installer. This will extract ITDT in the same location as your downloads.

  2. Hit [Enter] to complete close the extraction utility.

  3. Open the ITDT directory, then right click the itdt executable and choose Run as administrator.

  4. Click Yes to the User Access Control prompt.

  5. Type L, hit [Enter], then I (to accept the ITDT license agreement) and again [Enter]. ITDT is now set up.

Updating the firmware

Next, the firmware itself:

1. Download the latest firmware for your drive.

If your LTO drive is housed inside a Thunderbolt device (i.e. mLogic, MagStor, Symply, OWC) use the SAS versions, not the FC (Fiber Channel) versions.

2. Move the downloaded firmware file into the input directory inside the directory containing ITDT.

On macOS the default location is ~/ITDT/input/.

Not sure how to get to that folder? In Finder, hit Shift-Command-H.

On Windows ITDT will extract to wherever your browser downloads go. The input folder for placing firmwares will be something like /Users/Username/Downloads/ITDT/input/.

Next, close ALL apps you use for LTO purposes, and unmount any tapes.

3. ITDT should still be running from the installation steps above. Now enter the following commands to open the connection to your tape device, and upload the firmware:

  • u, then [Enter]

  • 1 (one, not el), then [Enter]

  • If you have just one tape device, tape0 is your device name so just hit [Enter] four times.

If you have multiple LTOs connected, the easiest way to make sure you're updating the correct LTO device is to power off the other units. Alternatively, Mac users can look up device SCSI ID's in System Information > SAS. In this example screenshot, the device ID is 0:

  • 71, then [Enter].

  • If you properly copied the firmware into the input folder, you'll see a view like this listing your firmware file in slot 0:

  • Select the firmware with 0 and an x will appear next to it.

  • Continue with C , then [Enter] and wait until done.

  • A successful upgrade will have a PASSED status:

  • Hit [Enter] to return to the Tape Util menu.

4. When back in the Tape Util menu close the connection to the tape:

  • Type 2, then [Enter] twice.

5. Now you can quit ITDT: q then [Enter]

6. You can safely close the Terminal app.

Joining Files

There are a number of ways in which EditReady can join media, depending on the type of source you're working with.

Manually Joining Files

To manually join files, select the files you wish to join within EditReady, then select Join from the Clip menu. You may also split joins using the Split command in that menu.

EditReady will only allow you to join media if the files all have the same frame size and framerate. If there's a mismatch, the Join menu option will be disabled.

GoPro

EditReady will automatically join files that follow the standard GoPro naming conventions.

AVCHD and HDV

AVCHD and HDV cameras and direct-to-disk recorders automatically split long recordings across multiple files. This split happens at a low level, so the files need to be recombined before they're converted. If you add the root AVCHD folder from a card, or a set of HDV files with a known naming scheme, EditReady will automatically join them.

MXF Files

Most cameras that work with the MXF format do not have limited file sizes. However, some Canon cameras do split long recordings across multiple files. In these cases, EditReady will attempt to automatically join the files.

Additional Features

EditReady provides a set of additional adjustments that can be added to your batch. These are available via Show Additional Options which can be found in the Batch menu. Each library entry has a set of adjustments, and is saved as part of your presets.

Framerate Adjustment

EditReady allows you to adjust the output framerate of your file during conversion. This is sometimes called conforming. This setting adjusts the playback rate of your media, it does not add or remove frames from your footage. This setting is especially useful when creating slow-motion footage with a source that shoots at 60 or 120 frames per second (or higher). Framerate adjustment is not available when using passthrough settings.

That means converting PAL to NTSC and vice versa, 23.97 to 25p, etc, also works - with the caveat that you don't want to do a massive jump. 23.97 to 25 is fine, but 29.97 to 25 is maybe a bit too much.

LUTs

EditReady allows you to load LUTs ("Lookup Table") which can apply color grading looks to your footage during conversion. This can be very powerful if, for example, your camera records in the log space, but you wish to edit with a linear mapping. EditReady supports LUTs in the 3DL and Cube formats. If you attempt to load a LUT in an unsupported format, EditReady will prompt you to submit the file to Hedge, so we can evaluate adding support for that format in the future.

If you save a new preset with a LUT, that LUT will be included in the preset.

Please note, LUTs require additional processing, and will slow the conversion process.

Frame Size Adjustment

This option allows you to resize your source media to match a destination size. Three scaling options are provided.

  1. Source Aspect Maintain the aspect ratio of the source clip, and fit it within the target size. For example, a 4096x2160 source clip with a 1920x1080 target size would be scaled to 1920x1012 in order to maintain the aspect ratio.

  2. Destination Size (pad) Add padding (black bars) to fit the scaled source within the target size. A 4096x2160 source with a 1920x1080 target would have small black bars at the top and bottom.

  3. Destination Size (stretch) Stretch the source to fit the target size, regardless of the aspect ratio.

Scale quality This option allows you to set the scale quality for RAW files and has two options:

  1. Best (slowest)

  2. Good (faster)

When "Best" is selected, EditReady will decode the full resolution RAW file and then scale the frame using a high quality scaling algorithm. When "Good" is selected, EditReady will perform a scaled decode of the source RAW format. This can lead to a very substantial performance increase, but may result in slightly less detail. This is a great option to select for things like proxies and dailies.

Encoder Advanced Options

This entry is specifically for presets that use the H.264 and H.265 codecs. By default, EditReady does a high-quality encode which aims to preserve the image quality of your source. This setting allows you to adjust a variety of H.264 and H.265 parameters. These settings will be disabled if your destination codec is something other than H.264 or H.265.

Target Bitrate

This will instruct EditReady to aim for this bitrate as an average for the file. The automatic setting will adjust automatically to maintain a high quality image.

Keyframes

This is a control for the number of keyframes (I-frames) per second in the output stream.

Profile

H.264 and H.265 have a wide variety of profiles for encoding. EditReady will choose the appropriate sub-profile based on the bitrate, keyframe, entropy coding, and resolution settings.

Entropy

H.264 and H.265 provide two types of entropy coding. In general, CABAC is more efficient, but may require additional CPU power for playback and may not be supported on old devices. In those cases, you may wish you use the CAVLAC setting.

Remove Audio Channels

Remove silent audio channels from output file

Many cameras now record four or eight channels of audio. In almost all cases, only one or two channels are actually used. By enabling this option, EditReady will scan for silent channels and remove them during conversion. EditReady will only remove channels that are truly silent (digital silence - all zeros) and not channels that are just very quiet (for example, an XLR connector without a mic attached).

Preserve audio channels

Some workflows require a specific number of audio channels. This option lets you specify how many channels to keep in the output. EditReady will preserve the first X channels from the source file, maintaining channel layout for compatibility with editing and broadcast systems.

Video Overlays

The Video Overlays option provides a powerful toolset for creating custom overlays on your videos. These can be used to burn in timecode, add watermarking, scene labels, and much more. After enabling the Video Overlays option click Launch Editor to launch the graphical overlay builder. Overlays are saved as part of presets.

Text Overlays

To add custom text to your overlay, click the T icon in the upper-right corner. A new text box will be added to your overlay. You can click and drag to move the text box, or resize it. Click in the box to edit the text. You can use the controls on the right side of the window to adjust your font size, color, background, and more. By default, text will have a black background. Adjust the background opacity to remove the background.

Image Overlays

Image overlays make it easy to add graphical watermarks to your video. To add an image, click the image icon in the upper-right corner, then select any image file from your Mac. EditReady supports transparency in overlay images, which makes it ideal for things like network logos. Click and drag to move or resize your image.

Metadata Overlays

Metadata overlays allow you to customize your overlays based on data from your video files. For example, you can add timecode burns, or include a reel name. To add a metadata overlay, open the Overlay Editor. Then select a clip within EditReady and select Edit Metadata from the Clip Menu. Then simply drag the metadata tag icon from the Metadata Editor to the Overlay Editor. Your metadata key will appear in the Overlay Editor, surrounded by a rounded rectangle. You can adjust the font size and background color just like a text overlay.

Color Conversion

The color conversion option gives you the ability to conform all of your input footage to a single output color space. If your production is working with footage from a variety of cameras, this allows you to standardize your footage going into your edit workflow. When generating proxies from log media, you can use this functionality to convert your footage to a standard video (Rec709) space for wider playback compatibility.

The color conversion is applied prior to the LUT stage, so your LUTs can operate on a single consistent colorspace regardless of your input footage.

EditReady ships with a wide set of industry standard colorspace options, including both log and standard video outputs.

Timecode Overwrite

This option allows you to add or change a time of day timecode track using the file's creation or modification timestamp.

Recreate Source Folders

The Recreate Source Folders option allows you to replicate the directory structure of your source folder. For example, if you've organized your clips by day, camera, and card, you may wish to preserve that structure when generating proxies, without mixing your proxies with your source media.

The text entry field allows you to specify how many folders above the clip to replicate. For example, using the sample directory structure below, entering a value of 1 would replicate just the Card 1 folder, 2 would replicate A Cam/Card 1 and so on.

Media Drive/
├─ Day One/
│  ├─ A Cam/
│  │  ├─ Card 1/
│  │  │  ├─ A00001.mxf
│  │  │  ├─ A00002.mxf

Naming Your Files

EditReady includes powerful file naming features, so that you can keep track of all the files in your post-production pipeline.

The popup menu to the right of the Dest File Name label is pre-populated with a handful of options. For example, you may choose to have your output file names match the input file names, or you may wish to rename your output file names with an automatically incrementing number.

Customizing File Names

Drag that 🏷 to the Dest File Name field to include that metadata element in the destination filename.

For example, you may wish to add the Reel key and the Creation date keys to the existing Auto-increment entry. You can drag and drop to rearrange values within the Dest File Name field, and you can type to add characters like dashes or underscores. So, you could easily have all of your output files named (Reel)-(CreationDate)-(Auto-increment).mov.

You can also use a forward slash / to include folders in your output naming scheme. So you could use (Reel)/(Source Name) to generate a new folder for each reel in your batch.

Overwriting Existing Files

EditReady will not allow you to proceed if your destination files will overwrite your source files. In other cases where files will be overwritten, or where there is insufficient metadata to populate a filename, EditReady will alert you and allow you to continue.

Destination Folder

You can click the icon to the right of Dest Folder to select an output folder for your batch. Within the dialog, you will also have the option to select Same as Source (In OS X 10.11 (El Capitan), click the Options button). That will cause EditReady to store your output files in the same folders as the source files. Please note, EditReady will not allow you to overwrite your source media, so make sure your file naming scheme doesn't conflict with your existing files.

File Format

In most cases, EditReady outputs QuickTime (.mov) files. However, when DNxHD or DNxHR are the destination video formats, you may optionally choose to output in either the OP1a or OP-Atom formats, using the File Format dropdown. In all other cases, that dropdown will be disabled.

In general, when outputting H264 files with AAC audio, the MOV files written by EditReady can safely be renamed ".MP4" if your workflow requires that file extension.

Custom Presets

EditReady is an integral part of a post-production workflow. To make the usage even more seamless, you can create custom presets that match your workflow needs. Begin by selecting the Custom preset in the preset dropdown.

Video Format

EditReady allows you convert to Apple ProRes, Avid DNxHD, and H.264. You may also choose to pass the input video directly to the output file (using the Passthrough option). This is helpful if you only need to adjust the audio track or metadata of your file.

Apple ProRes

Apple ProRes is a popular editing format, whether you're working with Final Cut Pro, Avid Media Composer, Adobe Premiere Pro, or DaVinci Resolve.

EditReady allows you to choose from five different ProRes options: ProRes 422, 422 HQ, 422 LT, 422 Proxy, and 4444. The "right" choice will be different for each workflow. But, in general, if your source is already compressed (e.g. an h264 file from a GoPro camera), the standard ProRes 422 file will be fine.

Avid DNxHD

DNxHD is a popular editing format for workflows involving the Avid ecosystem. EditReady provides three DNxHD choices: Low, Medium, and High.

These choices may be confusing if you're used to seeing DNxHD listed with a variety of bitrates. EditReady selects the correct bitrate automatically, based on your input file's resolution and framerate.

For example, if your source is 1920x1080i60, the Low, Medium, and High settings correspond to DNxHD 100, 145 and 220, respectively. For a 1920x1080p24 file, the bitrates are 36, 80 and 176.

Avid DNxHR

Avid DNxHR is designed for larger-than-HD sources, like 2k and 4k. EditReady suppots DNxHR, but you'll need to create a custom preset in order to use it. Select Custom from the preset dropdown, then select the desired DNxHR codec from the Video Format dropdown. You can save that preset for reuse later by selecting Save Current Preset from the batch menu.

We strongly recommend using PCM audio with DNxHR.

H.264

If you'd like to use EditReady for generating files for distribution, or for creating very small proxy files, the H.264 setting is a good option. This setting will automatically select a bitrate high enough to preserve the quality of your source footage without introducing substantial artifacts.

Audio Formats

EditReady includes three options for audio formats - Uncompressed, AAC, and Passthrough. Passthrough will preserve your source audio. This is useful if you only wish to change the video essence or metadata of your file.

Uncompressed (PCM)

Uncompressed PCM audio is the most common and interoperable method for working with audio on a computer. This is the recommended option for any editing platform.

AAC

AAC compressed audio is an ideal choice if you'll be creating H.264 compressed files for distribution.

None

Remove the audio entirely.

Connect

Get a live overview of conversions in progress – yours and others – plus receive push notifications on completed conversions wherever you are.

Requirements

  1. EditReady 24.4 or newer

  2. A modern web browser

How to use

  1. Go to EditReady > Settings > Connect.

  2. Toggle Enable Connect to ON.

  3. Copy the Connect Code by clicking the clipboard icon.

  1. Enter the Connect Code or request a magic link (requires an EditReady Pro license).

  2. Start a conversion in EditReady, which will then automatically appear on the Connect website.

Automation

EditReady has two levels of automation:

  • EditReady Pro: App URLs

App URLs

You can tell EditReady to do something by calling the app URL: editready://. You can call this from any app or script that can open a URL.

Requirements

  • EditReady 22.4 or newer

Using a browser

Copy/paste the URL below in a web browser, press Enter, and EditReady will open.

Using a shell

Copy/paste the command below in a shell, press Enter, and EditReady will open.

Calls

Activate

Deactivate

Add

Adds a file or folder to the clip view.

Transcode

Transcodes a file or folder (also adds the file to the clip view).

EditReady stores its preset files inside the app bundle with a .erpreset file extension. (e.g. /Applications/EditReady.app/Contents/Resources/Apple ProRes 422 (HQ).erpreset). User presets are saved in: /Users/<your-usename>/Library/Application Support/EditReady

Select the disk and click Security policy
Preflight Checks prompting to install Command Line Tools

Connect offers an online dashboard, available at . Log in with either the email connected to your license key(s), or your license key itself.

EditReady can also generate high-quality proxy media so you can take your media with you on the road or

EditReady interacting with Apple Maps
Adding Metadata Values

Canister for Mac users can preview Queuing via the .

Download IBM's ITDT tool for macOS:

Download IBM's ITDT tool for Windows:

For IBM Half Height LTO firmware, Qualstar maintain a convenient list .

For Quantum LTO firmware, use the list .

Symply maintain an LTO firmware list for their customers , including Full Height models.

SCSI Device ID is 0

If you only have the MTS files, without the rest of the card metadata, . EditReady will attempt to detect whether the files are from a consecutive group, and will take the appropriate action to join them.

EditReady options library
Adding a text overlay
Adding an image overlay
Custom Naming Options

In addition to the presets, you can add additional values from your file's metadata to the file naming scheme. , you will notice a small tag 🏷 icon next to each metadata key.

Dragging in the "Reel" metadata key

If you'd like to see a full chart of the bitrates used by DNxHD, take a look at the from Avid.

For details on the framerates, frame sizes, and bitrates that DNxHR supports, see the .

Click Go to Connect ✨, or go to in your web browser.

EditReady Server:

https://connect.hedge.video
Connect for EditReady
Connect for Canister
Connect for OffShoot
share them with your team using Postlab Drive.
Beta Track
Magstor M2000
https://downloads.hedge.video/canister/firmware/itdt/install_itdt_macos.zip
https://downloads.hedge.video/canister/firmware/itdt/install_itdt_windows.exe
here
here
here
DNxHD whitepaper
DNxHR Codec Bandwidth Specifications table at avid.com
you may still manually join the files
When viewing your file's metadata
editready://open
open 'editready://open'
editready://activate?key=<your-licens-key>
editready://deactivate
editready://add?sourcePath=<file or folder path>
editready://transcode?sourcePath=<file or folder path>&preset=<preset name / path or UUID>&destinationPath=<folder path>

Rewrapping

Media files come in a number of different "wrappers," which define how data is stored. Common wrapper formats include MOV, MP4, MXF, and MTS.

Can any media be rewrapped?

Some video codecs can only exist within certain wrappers. And some wrappers only support certain video codecs. For example, MOV files can contain main historical codecs that are no longer in use, whereas MXF files are limited to a smaller, more modern set of codecs.

Is rewrapping lossless?

Yes, rewrapping does not decompress or recompress your video data. The default rewrap setting in EditReady does decompress your audio to a lossless (LPCM) format. Many editing applications don't deal well with compressed audio, so this makes your rewraps more broadly compatible. If you want to maintain your source audio in its compressed format, you can make a custom preset with Passthrough for both audio and video.

Can I rewrap AVC-Intra footage from MXF to MOV?

One thing to be aware of is that not all NLEs can handle all video codecs in all wrappers. When it comes to AVC-Intra in particular, the Adobe applications (like Premiere Pro) tend to work better with MXF than with MOV. Applications like Final Cut Pro tend to work fine with AVC-Intra rewrapped into MOV.

Advanced

The Advanced Settings pane contains some options that should only be adjusted in response to very specific issues. Generally, you shouldn't make changes here unless our support staff have specifically instructed you. This panel's default is for all options to be unchecked.

Prefer Legacy Color Science for Premiere Pro

When transcoding xvYCC (extended-gamut YCbCr) footage to ProRes, Adobe Premiere Pro can experience color management glitches. While these issues are reduced in newer versions of Premiere Pro, enabling this option may correct color rendering issues if you're using a version from 2023 or earlier.

Ignore H.264/HEVC data levels

Video files can store their brightness information within a couple of different ranges. Historically, all video files were in what was called "video range". To allow for more dynamic range, some cameras allow you to instead record brightness information in "data" or "full" range. By default, EditReady will preserve data range video levels during the transcoding process. However, this can make video content look very high contrast if the playback application isn't taking that range into account. Checking this box will change how EditReady converts those files in those cases.

Disable A/V Synchronization

Cameras often write metadata to files that perform basic synchronization adjustments to account for differences between the frame and audio sample lengths. EditReady preserves these edits (called an edit list or ELST). In some cases, though, cameras incorrectly write ELST data, so it's better to ignore that metadata.

Maintain Source Audio Track Count

Audio is stored in tracks and channels within media files. An audio track stores at least one audio channel but may contain many more. Cameras often record audio with multiple single-channel (mono) tracks. However, converting files to a single track with multiple channels is often better for performance reasons. That's the default behavior for EditReady. Check this box to maintain the original track structure of your source format.

https://connect.hedge.video
headless CLI

FoolCat

Trimming Clips

EditReady has the ability to convert excerpts from clips, using our trimming feature. To mark in and out points on your clip, first open it in the player by double clicking on the clip thumbnail. In the player view, there are "in" and "out" buttons attached to the play controls. Use those to adjust your clip.

After marking "In" and "Out" points, a small scissors icon will appear on the clip thumbnail to indicate that it will be trimmed during conversion.

Requirements

Releases

25.1 - SONY BURANO Version 2.0

24.4 - CODEX HDE & Connect

24.3 - BRAW 4.1

New

  • Convert RAW proxies way faster with the new Scale Quality option “Good (Fastest)”. Find it via “Additional Options > Frame Resizing > Scale Quality”.

  • Support for Blackmagic PYXIS 6K, URSA Cine 12K and URSA Cine 17K, and BRAW recorded by Panasonic GH7 and Fujifilm GFX100S II.

  • Significantly improved processing speed of spanned clip RED clips.

Fixed

  • When applying a LUT some RED clips would show an incorrect results, that’s fixed.

  • Added support for Sony BURANO XAVC HEVC Intra HQ clips.

  • Added support for Blackmagic Design iOS camera app log format.

  • Fixed a rare crash that could happen when saving a presets.

  • Sony FX6 XAVC-I thumbnails were a bit too green, that's fixed too.

24.2 - SDK Updates

New

  • Support for the new RED V-Raptor [X] camera

  • Support for the new Sony BURANO camera

  • Improved processing of ARRI RAW clips

  • Updated Camera SDKs (ARRI v8.2 / RED v8.5.1 / SONY v5.0 / BRAW v3.6.1)

Fixed

  • ProRes RAW footage from an Atomos Ninja recorder was being processed incorrectly, that’s Fixed.

  • Some ARRI RAW clips showed an incorrect Pixel Aspect Ratio, that’s fixed too. </aside>

24.1 - Parallel Transcodes

  • Support for parallel transcodes! Up to 4x speed on Apple silicon 🚀

  • DNxHD OPAtom now automagically links up in Media Composer (Yes, this is a biggie!)

  • New DNxHR LB and DNxHR LB (MXF) presets

  • A new app icon 🤩

23.1 - Folder Mirroring

EditReady 23.1 has a range of updates and enhancements, including performance improvements on Apple Silicon. We've also tackled one of our most requested features - the ability to mirror the folder structure of your source media. Look for the "Recreate Source Folders" feature within the options library.

  • Support for the all-new Apple ProRes Log available on iPhone 15 🥳

  • Parses and applies ARRIRAW aspect ratio metadata in resulting files

  • Speeds up RED transcodes

  • Added a workaround for playing back DJI footage that has faulty metadata (Thanks, Jaakko!)

  • Speeds up decoding for H.264 High Profile on Apple Silicon

  • Fix for transcoding RED footage to H.264/5 (Thanks, Christoph!)

  • Fix for transcoding hang on some M1 Ultra machines (Thanks to Samuel)

  • Recreate the source folder hierarchy on the destination

  • Support for transcoding to 10-bit HEVC

  • Faster transcoding when also scaling, on Apple Silicon (Thanks, Michael!)

  • Reel name metadata is added to MXF files

  • Adds ARRIRAW 1.2 firmware

  • Updates BRAW support

  • Updates Sony X-OCN support

  • Fix for a potential crash transcoding R3D footage on Intel Macs (Thanks, Dorian!)

  • Fix for playing back rewrapped HEVC files in FCP

  • Fixes a crash when opening new BRAW media with accelerometer metadata (Thanks, Akio!)

  • Some MXF files previously transcoded with EditReady wouldn't load properly in EditReady

  • Fix for an issue that truncated the last frame of some MXF files (thanks, David!)

22.4 - CineRAW

The EditReady product line is expanding! With the release of 22.4, we're adding a new Pro tier, and we're starting things off with our first Pro-only feature - Phantom CineRaw (.cine) support. In addition, we're pre-releasing the new EditReady Server; perfect for workflows that require headless command line-driven thumbnailing, metadata extraction, and transcodes.

  • Phantom CineRAW support (requires Pro license)

  • Automatically generate timecode from creation and modification dates

  • Parse and apply scaling for anamorphic RED footage

  • New URL scheme API to add clips and trigger transcodes, to replace the CLI which is now a Server-only feature

  • The retiming tool now supports 100p frame rate

  • Fixed bad transcode progress on some ARRI ProRes MFX clips

  • Fixed failed transcodes of interlaced footage to ProRes on m1 Pro/Ultra

  • Improved memory use during BlackMagic Raw to H264/265 transcodes

  • Improved ARRIRAW decode performance

  • Fix for a rare crash decoding ARRIRAW

22.3 - Canon RAW & ARRI ALEXA 35

  • Create .mp4 files when converting to h.264/5

  • Improved clip playback!

  • Added ProRes 4444 XQ input and output formats

  • Updated RED SDK to v8.3.0. (Bonus: improved performance on M1)

  • Faster thumbnail creation of Canon RAW on M1

  • Fixed possible gamma shift/clipping when applying overlays

  • Fixed doubled first frame for X-OCN MXF sources

  • Adds support for Fujifilm XH2s Blackmagic RAW clips captured by Blackmagic Video Assist

  • Fix for frame stuttering on some transcodes

  • Better fallbacks for bad source colorspace metadata

  • Fix for Canon RAW decode on intel dual GPU systems

  • ARRIRAW now requires 10.15 or newer.

  • Fix for crash when launching EditReady on 10.15

  • Fixes a crash when closing the player while playing back ARRI files

  • "Show in Finder" now works for ARRI files too.

  • Canon Raw Light (CRM) media is now supported!

  • Support for the brand new ARRI ALEXA 35 camera

  • New Log formats and color conversions: Canon's CLog2 and CLog3, and ARRI LogC4

  • Support for Leica SL2-S clips captured through BMD's Video Assist

  • Fix for a crash when parsing some specific non-Sony MXF files

  • Fix for possible black frames when decoding DNxHR 10 bit

22.2 - Color Awareness & X-OCN

  • Support for Sony F65 high frame rate RAW files

  • Improved stability and performance for Sony RAW and X-OCN files

  • New color pipeline improvements to better support media without color tags

  • RAW formats report correctly as progressive in the Info pane

  • Better detection of spanned media on network storage

  • Select a single output colorspace when mixing codecs

  • Convert clips into video or Log formats

  • Convert colorspace prior to LUT application to allow the use of camera manufacturer LUTs

  • Colorspace-aware overlay compositing

  • Higher-quality resizes and blends

  • Sony RAW and X-OCN support

  • Fixes DNxHD and HR 10bit targets

  • Some users experienced DNxHR 4444 color channel swaps

  • Fixes a crash caused by some malformed .mov files

  • Scaling BRAW source files is now again as fast as it should be

  • Fix for ProRes to HEVC transcodes on M1 Max & Ultra

22.1 - RAW Support

  • Improved support for ProRes RAW on 10.14.

  • Support for spanning R3D clips.

  • XAVC clips had a one-frame offset, no longer.

  • BRAW to H.264/5 now works properly too.

  • R3D overlays no longer cause crashes.

  • Fix for a crashing preset

  • Added support for ARRIRAW MXF files and ARI sequences

  • Added support for CODEX-encoded ARX sequences

  • Added support for RED-encoded R3D files

  • Added support for ProRes RAW files

  • Updated Blackmagic RAW support to BRAW 2.1.2

  • Added support for GoPro Hero 10+ HEVC files

  • Licenses now come with a year of free updates 🎉

  • New Metal-based video pipeline for better performance and higher quality on Apple silicon Macs 💪🏽

Legacy Versions

Previewing Files

EditReady allows you to preview your files before conversion. To access the player, select the clip and choose Open Preview from the Clip menu, or press Command-3 on the keyboard.

Applying LUTs During Playback

Keep in mind that LUTs can be compute-intensive, particularly on 4K files. Slower computers (or computers with slower graphics cards) may have trouble with realtime playback.

How can EditReady prep my source media for immediate use in Media Composer?

EditReady can transcode your source media into Avid codec-based MXFs to speed up and simplify your dailies (or rushes) workflow.

There are two types of MXFs Media Composer can use:

  1. OP-Atom

  2. OP1a

OP-Atom

OP-Atom MXFs are the individual video and audio streams Media Composer then combines into one Clip inside a Bin.

When Media Composer transcodes MXFs, it typically names these files like this on your filesystem:

  • Video - V01.(Some Hexadecimal Numbers).MXF

  • Audio - A01.(Some Hexadecimal Numbers).MXF

With EditReady 24.1, you can transcode your source media into DNxHD-based OP-Atom MXFs Media Composer will recognize as one Clip. It also uses the name of your source media for your transcoded MXFs so you can quickly identify them on your filesystem and in your Bin.

Currently, EditReady can only create DNxHD-based OP-Atom MXFs, not DNxHR OP-Atom MXFs

OP1a

OP1a MXFs contain all the video and audio streams captured by a camera or recording device in one container, which Media Composer will see as one Clip inside a Bin.

EditReady can transcode your source media into OP1a MXFs – DNxHD or DNxHR – you can use in an editorial workflow.

How to use

1. Transcode your source media to MXFs

  1. In EditReady, add the clips you wish to transcode.

  2. Transcode your source media to the MXF that's best for your workflow, OP-Atom or OP1a.

  1. In the Preset: dropdown, choose the desired DNxHD... (MXF) preset.

  2. Next, select Custom from the Preset: dropdown. Selecting a Custom preset enables the File Format: dropdown.

    1. From File Format:, choose OPAtom (.mxf).

    2. If needed, customize your transcode settings with:

      1. Dest Folder: - the destination folder where EditReady creates your transcoded files.

      2. Additional Options such as Frame Resizing, Color Conversion, etc.

    3. Go to Batch > Save Current Preset and name your new preset.

  1. In the Preset: dropdown, choose the desired DNxHD... (MXF) or DNxHR… (MXF) preset.

  2. If needed, customize your transcode settings with:

    1. Dest Folder: - the destination folder where EditReady creates your transcoded files.

    2. Additional Options such as Frame Resizing, Color Conversion, etc.

  1. Click Convert All.

Your transcoded MXFs are now available in the Dest Folder: location.

2. Copy the transcoded MXFs into one of Media Composer’s media folders

Copy the transcoded MXFs from the Dest Folder: location to one of these folders:

  • Shared Storage - /(Volume)/Avid MediaFiles/MXF/(Someones Computer).(N)

  • Local Storage - /(Volume)/Avid MediaFiles/MXF/(N)

Copy the transcoded MXFs from the Dest Folder: location to one of these folders:

  • Shared Storage - /(Volume)/Avid MediaFiles/UME/(Someones Computer).(N)

  • Local Storage - /(Volume)/Avid MediaFiles/UME/(N)

Do not mix Shared and Local storage media management folder structures on the same volume.

Media Composer will index and use the MXF and UME folders if they exist inside /(Volume)/Avid MediaFiles on the same volume.

3. Launch Media Composer to index your media folders

The result of Media Composer’s indexing will be a msmMMOB.mdb file in each media folder:

  • ../Avid MediaFiles/MXF/(Folder)

  • ../Avid MediaFiles/UME/(Folder)

4. Use the MDB file to fill your Bin with Clips

  1. In Media Composer, create a new Bin.

  2. In Finder (macOS) or File Explorer (Windows), open one of those media folders – MXF or UME – and locate the msmMMOB.mdb file.

  3. Drag and drop the MDB to your Bin.

You now have a Bin full of Clips ready to use in Media Composer, and those Clips will have the network-connected icon in your Bin.

Questions

Should I rename the folders inside ../Avid MediaFiles/(MXF | UME)/?

Many teams do, but we strongly recommend leaving those folders named as-is.

If identifying those MXFs by filename is important to your workflow, EditReady uses your source media filenames for the transcoded file names so you can easily do so.

What if I add new MXFs to an existing ../Avid MediaFiles/(MXF | UME)/ folder?

If you haven’t renamed those folders to something Media Composer doesn’t expect, Media Composer will reindex that folder, resulting in a new msmMMOB.mdb file. You can drag and drop that MDB file on a new or existing Bin, which will update your Bin with new Clips created from your transcoded MXFs.

Can Media Composer really use OP1a MXFs as media in an editorial workflow?

Yes.

Avid released the Universal Media Engine (UME) to support OP1a MXFs natively in Media Composer 2019.6.

Since 2019, Avid has removed installers for Media Composer versions that do not support UME.

You can read more about the Universal Media Engine and Media Composer’s native OP1a support at Avid’s Knowledge Base:

Questions

Default File Handler

Occasionally, EditReady might become set as the default file handler for some types of video files. That means when you double-click on a file (like an MP4), it opens in EditReady instead of QuickTime Player.

To correct that, follow these steps.

  1. Highlight any movie file in Finder.

  2. Press Command-i on your keyboard.

  3. In the Open with: section, select "QuickTime Player".

  4. Click Change All...

Errors During Conversion

Some issues may be caused by invalid output destinations. To test whether this is the case, try setting the Dest Folder option to your Desktop. You can also try moving your source media to your Desktop to rule out any external or network storage issues.

Transcoding directly from SD cards can be especially problematic, as SD cards can generate errors during the types of sustained reads from transcoding operations.

MXF, HDV (M2T), and AVCHD (MTS) Files

You can test whether your MXF or AVCHD/HDV (MTS/M2T) file is valid by trying to play it with the free video players like:

Can I use EditReady to create dailies/rushes for Media Composer?

Yes. A step-by-step guide is available here:

Need help?

Why can't I activate EditReady?

Legacy EditReady versions (2.72 and older) use a different key format than EditReady 22.1 and newer.

  • EditReady 22.1 and newer - ABCD-EFGH-IJKL...

  • EditReady 2.72 and older - MNOPQRST...

First, verify you're using the desired version of EditReady with the appropriate license key (EditReady > About EditReady). Then activate EditReady accordingly.

How do I know which version of EditReady I can use with my license key?

How can I upgrade my legacy EditReady license key to the new EditReady?

  1. Launch EditReady, then click Activate...

  2. Copy/paste your legacy EditReady license key in the Activation number field, click Activate, then click Buy upgrade...

  3. A personal discount code will be applied. Complete the checkout, and you'll receive a new license key for the latest version of EditReady.

Your legacy EditReady license key cannot be used to activate EditReady 22.1 and newer.

  1. Activate EditReady with that new license key.

I'm not ready to upgrade EditReady yet. Can I use an older version for now?

Upgrades

Users of EditReady 1.x, 2.x, or ClipWrap are entitled to discounted upgrades for EditReady. Just enter your key in the latest release of EditReady, and you'll be prompted with an upgrade link.

Releases

EditReady Server 25.1

EditReady Server 24.4

EditReady Server 24.3

New

  • Convert RAW proxies way faster with the new scalingQuality preset option:

    • "scalingQuality" : 0 // Good (fastest)

    • "scalingQuality" : 1 // Best (slowest)

  • Support for Blackmagic PYXIS 6K, URSA Cine 12K and URSA Cine 17K, and BRAW recorded by Panasonic GH7 and Fujifilm GFX100S II.

  • Significantly improved processing speed of spanned clip RED clips.

Fixed

  • When applying a LUT some RED clips would show an incorrect results, that’s fixed.

  • Added support for Sony BURANO XAVC HEVC Intra HQ clips.

  • Added support for Blackmagic Design iOS camera app log format.

  • The green tint issue in SONY FX6 XAVC-I thumbnails has been fixed.

EditReady Server 24.2

New

  • Use display names for metadata keys with the new --normalizeMetadataKeys flag

  • Support for the new RED V-Raptor [X] camera

  • Support for the new Sony BURANO camera

  • Improved processing of ARRI RAW clips

  • Updated Camera SDKs (ARRI v8.2 / RED v8.5.1 / SONY v5.0 / BRAW v3.6.1)

Fixed

  • ProRes RAW footage from an Atomos Ninja recorder was being processed incorrectly, that’s Fixed.

  • Some ARRI RAW clips showed an incorrect Pixel Aspect Ratio, that’s fixed too.

EditReady Server 23.2

  • Fixes crash when thumbnailing spanned RED clips.

  • Fixes crash exporting metadata JSON of corrupt clips with bad timing data.

  • Adds new clipIndexer (-i) flag - creates json with results of directory parsing and clip span detection

  • Improves R3D decode speeds

  • Improves ProRes speeds when scaling

  • Supports Presets containing the new mirror source option

  • Fixes color rendering of thumbs and proxies from HLG source media

  • Fixes crash transcoding new BRAW media containing timed metadata

  • Supports ARRIRaw firmware 1.1 source files

  • Fixes crash parsing GoPro spans

  • Strips whitespace and bad character padding from serials when registering from commandline

  • Fixes rare hang batch decoding h264 content

  • Fixes crash thumb-nailing clips with no video track

  • Properly applies pixel aspect ratio metadata from ARRIRaw files in both thumbs and transcodes

  • Other changes to improve stability and performance

  • New JSON metadata format (use .json extension on -m path to trigger), XML to be deprecated

  • Support for multiple source files (-s) in a single invocation, allowing for batch processing

  • Removes old CLI flags like showUserInterface, ignoreWarnings, filterFile

  • Fix for a crash when falling back to ffmpeg for thumbnail decompression

  • Supports 10bit HEVC output

  • Additional technical metadata for Sony X-OCN, Canon CRM, ARRI S35

  • Improved argument prechecking

  • Many improvements to prevent hangs on still generation caused by bad inputs and files

EditReady Server 23.1

  • First release 🎉

EditReady Server

EditReady Server enables headless workflows for tasks such as automated ingest and proxy generation for asset managers.

How to use

  1. Activate with your EditReady Server license key (or use the trial mode)

  2. Run your CLI commands

Trial

Activation

Commands

You must have a logged in user session to use EditReady Server.

Convert Media

It's possible to use multiple -s flags in one command.

Progress Example

Additional Options

To save a preset with additional options:

  1. Open EditReady Server.

  2. In the sidebar, configure the additional options.

  3. From the menu bar, go to Batch > Save Current Preset .

The preset will be saved to: ~/Library/Application Support/EditReady and can be referenced by using the -p, --preset flag.

Extract MetaData

Metadata JSON example

Metadata JSON example

Generating Stills

Iconik ISG

Releases

Overview

FoolCat generates camera reports, complete with thumbnails and extended metadata. Available on macOS and Windows.

Creating a Report

Drag and drop your camera footage onto FoolCat's main window, or click the + button to get started.

Hold the Option key to open the PDF report instead of the HTML.

Labels

Change the report name by setting a Label: click the folder or disk name, and enter a new one to be used as the Report name. A label overrides the Report name setting in Preferences.​​

When done, the Report will look something like this:

Customization

FoolCat allows for a lot of customization of your Reports. Add a logo and other project information in the Report Preferences pane:

Thumbnail Creation

By default, FoolCat creates three thumbnails per clip; for the first, middle, and last frame. This amount can be changed in Preferences > Settings.

Don't want any thumbnails? Set it to 0.

Report Location

The default location FoolCat saves Reports into is your Documents folder. You can also save an extra Report on the Source, which will be saved into the root of the folder or drive you set as a Source in FoolCat. Make sure that your source has write permissions for this setting to work properly; some camera cards are set to read-only.

Group PDFs in a separate folder

By default, FoolCat creates a folder for each report containing the HTML, thumbnails, and PDF. Alternatively, you can choose to automatically group the PDFs in a separate folder from the HTML report.

Supported Formats

FoolCat aims to support any file in a QuickTime or MXF wrapper plus a wide range of vendor-specific formats, including many RAW codecs:

  • Apple Intermediate

  • ARRIRAW

  • Blackmagic RAW (BRAW)

  • Canon RAW

  • Codex HDE

  • DNxHD

  • DNxHR

  • DVCProHD

  • H.264

  • H.265 (HEVC)

  • Phantom CineRAW

  • ProRes

  • ProRes RAW

  • RED RAW (R3D)

  • Sony RAW

  • Sony X-OCN

FoolCat aims to support any file in a QuickTime or MXF wrapper plus a wide range of vendor-specific formats, including many RAW codecs:

  • Apple Intermediate

  • ARRIRAW

  • Blackmagic RAW (BRAW)

  • Canon RAW

  • Codex HDE

  • DNxHD

  • DNxHR

  • DVCProHD

  • H.264

  • H.265 (HEVC)

  • Phantom CineRAW

  • ProRes*

  • RED RAW (R3D)

  • Sony RAW

  • Sony X-OCN

*ProRes RAW support is currently being worked on.

Color Conversion

FoolCat can apply a custom look (LUT) to the stills in your reports. Alternatively, you can set FoolCat to convert RAW footage to Rec.709 color space automatically.

When Color Conversion is enabled, the settings used will be shown in the report header.

Requirements

  • FoolCat 24.1 or newer

  • A LUT in the 3D .cube format (33x33x33)

How to use

  1. Go to Settings > Color Conversion.

  2. Click Manage LUTs to open the LUTs folder location in Finder/Explorer.

  3. Copy your LUT files to this location.

  4. Go back to FoolCat and choose your LUT from the dropdown.

    • Alternatively, choose Convert RAW to Rec.709 to automatically convert RAW footage to Rec.709 colorspace. (Currently only available in FoolCat for Mac)

FoolCat supports LUTs in the 3D .cube format (33x33x33).

Convert RAW to Rec.709

When Convert RAW to Rec.709 is enabled, FoolCat automatically detects and converts RAW clips shot in Log colorspace to Rec.709 colorspace. FoolCat performs the conversion based on the clip’s colorspace metadata and will ignore any viewing or creative LUTs encoded within the clip.

The Convert RAW to Rec.709 feature is currently only available in FoolCat for Mac.

Supported formats

  • ARRIRAW

  • RED

  • SONY RAW (Mac only)

  • SONY X-OCN

  • CANON RAW

  • BRAW

  • ProRes RAW

Trimming Controls
Trimmmed Clip

The current release of EditReady supports macOS 12 and newer. This includes macOS 15 and all Apple silicon (M1 and newer) systems.

  • The most recent version of EditReady that works on 10.15 is

  • The most recent version of EditReady that works on 11 is

Legacy versions of EditReady (version 2.* or older) do not work on Apple Silicon.

EditReady is not yet available on Windows.

EditReady 25.1 (Apr 04, 2025) -

New

  • Support for Sony's BURANO Version 2.0 firmware update.

  • The Recreate Source Folders feature released last year can now also work bottom-up instead of just top-down, just like you're used to from Resolve.

  • Specify the exact number of audio channels to keep.

  • Drops support for macOS 10.15 Catalina and macOS 11 Big Sur.

Fixed

  • Audio-only clips no longer appear in EditReady.

EditReady 24.4 (Sept 04, 2024) -

  • Support for CODEX High Density Encoding (HDE) MXF files.

  • Connect! Track conversion progress and receive push notifications wherever you are, via

  • A new Settings window, with General, Connect, License, and Advanced options

EditReady 24.3 (July 02, 2024) -

EditReady 24.3.1 (July 15, 2024) -

EditReady 24.2 (May 07, 2024) -

EditReady 24.1 (March 12, 2024) -

EditReady 23.1.1 (September 26, 2023) -

EditReady 23.1 (June 22, 2023) -

EditReady 22.4 (December 20, 2022) -

Support for Canon RAW Light (CRM), Arri S35, Canon CLog2, CLog 3, and Arri LogC4 color science to colorspace conversions, and support for Leica SL2-S BRAW files.

EditReady 22.3.3 (October 14, 2022) -

EditReady 22.3.2 (August 09, 2022) -

EditReady 22.3.1 (July 15, 2022) -

EditReady 22.3 (July 12, 2022) -

Color Awareness, a new color pipeline, and Sony RAW & X-OCN.

EditReady 22.2.1 (Apr 19, 2022) -

EditReady 22.2 (Apr 13, 2022) -

Easily our biggest upgrade in years! Support for ProRes RAW, RED, ARRIRAW, Blackmagic RAW, and CODEX (with support for Sony's RAW flavors coming soon).

EditReady 22.1.1 (Feb 24, 2022) -

EditReady 22.1 (Feb 01, 2022) -

EditReady licenses can now be managed from the

(Requires macOS 10.12+)

(Requires macOS 10.10+)

(Requires macOS 10.8+)

(Requires macOS 10.8+)

EditReady Player

Click the Add LUT icon to apply a LUT to your file during playback. This allows you to quickly preview any conversions you'd like to apply. For details on LUT support in EditReady, see .

Making QuickTime the default player

If you run into an issue during conversion, begin by confirming that your files play correctly in another application. QuickTime Player or are good general purpose players, but for RAW formats you may need to use a special player from your camera vendor. If your files don't play correctly, they may have been corrupted at some point during your workflow. If possible, re-copy the files from your source media.

If the file plays in one of these apps, but won't open or convert in EditReady, reach out:

If you purchased EditReady after February 1, 2022, you can use the to look up your EditReady license key (version 22.1 or newer).

Otherwise, you likely purchased a legacy EditReady before Divergent Media was acquired by Hedge. You can look up your .

Locate your legacy EditReady license key in your email, or .

Download and install the most recent version of EditReady:

Yes. You can download legacy EditReady versions in under Legacy Versions.

If you purchased ClipWrap from the Mac App Store, contact us for a discount coupon:

EditReady Server 25.1 (Apr 04, 2025) -

New

  • Support for Sony's BURANO Version 2.0 firmware update.

  • The Recreate Source Folders feature released last year can now also work bottom-up instead of just top-down, just like you're used to from Resolve.

  • Specify the exact number of audio channels to keep.

  • Drops support for macOS 10.15 Catalina and macOS 11 Big Sur.

Fixed

  • Audio-only clips no longer get picked up by EditReady.

EditReady Server 24.4 (September 26, 2024) -

  • Support for CODEX High Density Encoding (HDE) MXF files.

  • Connect! Track conversion progress and receive push notifications wherever you are, via .

  • A new Settings window, with General, Connect, License, and Advanced options.

EditReady Server 24.4.1 (Nov 05, 2024) -

  • Fixes an issue that caused transcodes to report as failed in iconik.

EditReady Server 24.4.2 (Feb 19, 2025) -

  • Fixed an issue where disconnecting from Connect could cause the application process to hang.

  • Directory names with _A were not processed correctly, that’s fixed too.

  • Corrupt BRAW files are now handled gracefully.

EditReady Server 24.3 (July 02, 2024) -

EditReady Server 24.3.1 (July 15, 2024) -

EditReady Server 24.2 (May 07, 2024) -

EditReady Server 23.2.2 (November 30, 2023) -

EditReady Server 23.2.1 (August 7, 2023) -

EditReady Server 23.2 (May 11, 2023) -

EditReady Server 23.1 (February 9, 2023) -

EditReady Server supports

Download

Using EditReady Server unlicensed is limited to transcoding the first minute of each clip. Reach out to for a free 10-day trial license.

(De)activation can be managed in the .

EditReady includes many that can be used via the command-line interface (CLI) when configured in a preset.

If you use an , an . Contact us at for details.

Using OffShoot for offloads? You can automatically generate FoolCat reports with the .

generates a report on up to 5 clips so you can quickly see which metadata FoolCat reports based on your source files.

if you need support for a specific camera or codec that isn't currently supported.

Convert RAW to Rec.709 also works with some mxf and mov files, but not all (in which case, they will stay in their original colorspace). Use this feature at your discretion with mxf and mov files. if you encounter any issues.

Download
Download
https://connect.hedge.video
Download
Download
Download
Download
Download
Download
Download
Learn more...
Download
Download
Download
Download
Learn more...
Download
Download
Learn more...
Download
Download
Hedge License Manager
Download v2.7.2
Download v2.6.5
Download v2.5.4
Download v1.4.9
Avid Universal Media Engine FAQ
Avid Media Composer, Apple macOS Catalina Support, and the Universal Media Engine
Media Composer File Type Support Without QuickTime Installed
VLC
IINA
VLC
hello@hedge.video
How can EditReady prep my source media for immediate use in Media Composer?
Hedge License Manager
legacy EditReady license key online
online
https://hedge.video/download/editready/macos
hello@hedge.video
24.4
24.4
Releases
Converting Media > Additional Batch Options > LUTs
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server --registration XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server -h
    
    -r, --registration               Registration string

    -s, --sourceFile                 Path to source file(s)
    -d, --destFile                   Path to output folder
    -p, --preset                     Path to preset file
    -m, --metadataDestination        Path for metadata output
    -k, --normalizeMetadataKeys      Use display names for metadata keys
    -i, --clipIndexerDestination     Path for clip indexing and span detection json output

    -t, --generateThumbs             Create thumbnails
    -x, --thumbSize                  Max dimension for thumbnails (default 320)
    -v, --thumbInterval              Min time between thumbnails (seconds)
    -c, --thumbCount                 Max thumbnail count

    -l, --logginglevel               Logging level {error/warning/info} (default error)
    -h, --help                       Show this help message. Visit https://hedge.video/app/editready/server for more info.
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \
--sourceFile '$FileOrFolderPath' \
--destFile '$folderPath' \
--preset '/Applications/EditReady Server.app/Contents/Resources/Apple ProRes 422 (proxy).erpreset'
STATUS: {"clip": "/Volumes/DRIVE-12TB/_BLACKMAGIC/A001_10031156_C006.braw", "action": "transcode", "destination": "/path/to/destinationFolder", "progress": "0.0000234"}
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \
--sourceFile '$FileOrFolderPath' \
--metadataDestination '$JSONfilePath.'
{
  "format" : "BRAW",
  "timecode" : {
    "drop" : false,
    "frameRate" : {
      "value" : 1001,
      "seconds" : 0.041708331555128098,
      "timescale" : 24000
    },
    "string" : "11:55:35:06",
    "frameCount" : 1030446
  },
  "destinationPath" : "\/Users\/Hedge\/Downloads\/A001_10031156_C006.mov",
  "clipName" : "A001_10031156_C006",
  "duration" : {
    "value" : 130130,
    "seconds" : 5.4220833778381348,
    "timescale" : 24000
  },
  "metaData" : {
    "clip_number" : "A001_10031156_C006",
    "exposure" : "0",
    "file.sourceName" : "A001_10031156_C006",
    ... >> etc
  },
  "audioTracks" : [
    {
      "duration" : {
        "value" : 260260,
        "seconds" : 5.4220833778381348,
        "timescale" : 48000
      },
      "codec" : "Uncompressed (PCM) 2 Channel 24 Bit Signed Integer",
      "timescale" : 48000,
      "fourCC" : "lpcm"
    }
  ],
  "filePath" : "\/Users\/Hedge\/Movies\/A001_10031156_C006.braw",
  "videoTracks" : [
    {
      "fourCC" : "BRAW",
      "displaySize" : {
        "width" : 7680,
        "height" : 4320
      },
      "frameRate" : {
        "value" : 1001,
        "seconds" : 0.041708331555128098,
        "timescale" : 24000
      },
      "codec" : "Blackmagic RAW",
      "duration" : {
        "value" : 130130,
        "seconds" : 5.4220833778381348,
        "timescale" : 24000
      },
      "encodedSize" : {
        "width" : 7680,
        "height" : 4320
      },
      "timescale" : 24000
    }
  ]
}
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \
--sourceFile '$filePath' \
--destFile '$folderPath' \
--generateThumbs \
--thumbSize 1024 \
--thumbInterval 1
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \
--sourceFile '$filePath' \
--destFile '$folderPath' \
--generateThumbs \
--thumbSize 1024 \
--thumbCount 3

Automation

You can automate FoolCat by calling the app URL foolcat://. You can call this URL from any app or script that can open a URL.

Requirements

  • FoolCat 20.1 or newer

Using a browser

Copy/paste the URL below in a web browser, press Enter, and FoolCat will open.

foolcat://open

Using a shell

Copy/paste the command below in a shell, press Enter, and FoolCat will open.

open 'foolcat://open'
start 'foolcat://open'

Calls

Activate

foolcat://activate?key=<your-license-key>

Deactivate

foolcat://deactivate

Create Report

foolcat://create?source=<source-path>&destination=<destination-path>&name=<report-name>&description=<report-description>
Download
Download
https://connect.hedge.video
Download
Download
Download
Download
Download
Download
Download
Download
Download
the same formats as EditReady.
EditReady Server
sales@hedge.video
License Manager
additional options
iconik Storage Gateway (ISG)
EditReady Server integration is available for ISGs
sales@hedge.video
Releases
FoolCat integration in OffShoot
FoolCat's fully functional trial
Let us know
Reach out

Releases

FoolCat 25.1

FoolCat 24.5

FoolCat 24.4

FoolCat 24.3

New

  • Support for new Blackmagic Design cameras:

    • PYXIS 6K, URSA Cine 12K and URSA Cine 17K.

    • BRAW recorded by Panasonic GH7 and Fujifilm GFX100S II.

  • Reports now also show Scene and Take for BRAW clips.

Fixed

  • Fixed a rare issue where the frame count for BRAW clips was off by one.

  • When applying a LUT, some RED clips would show incorrect results.

  • Selecting individual .cine and .crm files is now possible via the file browser.

  • MP4 clips are no longer reported as MOV.

  • Added support for Sony Burano XAVC HEVC Intra HQ clips.

  • The green tint issue in SONY FX6 XAVC-I thumbnails has been fixed.

New

  • Support for all Blackmagic Design cameras, including:

    • PYXIS 6K, URSA Cine 12K and URSA Cine 17K

    • BRAW recorded by Panasonic GH7 and Fujifilm GFX100S II

Fixed

  • Reports created with the FoolCat integration in OffShoot would sometimes be missing the PDF, that's fixed.

FoolCat 24.2

  • Support for the new RED V-Raptor [X] camera and extended highlights.

  • Support for the new SONY Burano camera

  • Improved processing of ARRI RAW clips

  • Updated Camera SDKs (ARRI v8.2 / RED v8.5.1 / SONY v5.0 / BRAW v3.6.1)

  • Support for the new SONY Burano camera

  • Sony RAW clips no longer get reported as X-OCN

FoolCat 24.1

  • Support for Sony X-OCN.

  • A new app icon.

FoolCat 23.1

New codecs

  • Sony X-OCN and Sony RAW

  • Phantom CineRAW

  • ProRes RAW

  • Canon Raw Light (CRM)

New supported cameras/formats

  • ARRI Alexa 35

  • Sony FX3

  • Red V-Raptor XL

  • GoPro Hero 10+ HEVC

  • Sony F65’s high frame rate RAW files

  • ProRes 4444 XQ

  • Canon XF-AVC

  • Fujifilm XH2s BRAW clips captured by BMD’s Video Assist

  • Leica SL2-S clips captured through BMD's Video Assist

  • It’s now possible to create multiple reports at the same time via File > New (Command-N).

  • Reset the FoolCat window after creating a report via Window > Reset (Command-R).

  • Stills in the PDF report now look even better, thanks to Mike.

  • When a still for one clip could not get created, the whole batch would fail. That’s fixed.

  • Panasonic S1H stills did not render correctly; that's fixed.

  • Added support for ARRIRAW SUP1.1.

  • Spanned RED and ARRI clips now report the total byte size and bitrate.

  • Spanned GoPro clips are now properly reported as one clip, with correct file size, duration and bitrate.

  • ARRIRAW thumbnails are now scaled to reflect Lens Squeeze metadata.

  • Fixed a crash when generating multiple reports from the FoolCat integration in OffShoot.

  • Updated support for new camera firmware from Blackmagic, RED, and ARRI.

  • Other changes to improve stability and performance.

  • Fixed a rare crash that could occur when creating a report.

  • Fixed an issue causing spanned RED clips to display incorrectly in the report.

  • Rosetta is no longer required for installing FoolCat.

  • De-squeeze now works for ARRI ProRes and Sony RAW/X-OCN anamorphic clips.

  • Some RED clips showed the FPS value twice; that's now fixed. ARRI ProRes clips now also display the Sensor FPS.

Foolcat 21.2

  • Updated Blackmagic RAW SDK, adds gen 5 color science support (BRAW 2.1)

  • Updated RED RAW SDK, adds support for Komodo Anamorphic.

Foolcat 21.1

  • Set a Label, and it shows up as your Report Name.

  • Report now detect reels and show the reel's folder and file path for every clip (Thanks for suggesting, all).

  • The filenames of generated stills now use the original filename + timestamp (Thanks for suggesting, Jeff).

Foolcat 20.4

  • Change the Report name by adding a Label, just like in Hedge

  • Don't want Foolcat to group PDFs? Prefer the old style? Just uncheck the new 'Group PDFs' option in Preferences.

  • Need direct access to the generated stills?

  • The Report Data folder is now no longer hidden. The 'Go to Report' menu item has been moved to the Window menu and has a shortcut: Command-Shift-R

Foolcat 20.3

  • Added support for RED Komodo camera (R3D SDK V7.3.4)

Foolcat 20.2

  • Camera metadata for RED / ARRI / Blackmagic cameras.

  • RED sequences now show up as one clip.

  • Support for Codex HDE .arx files.

  • Support for ARRI RAW .mxf files.

  • New PDF dark mode and landscape orientation.

  • Thumbnail offset for the last frame.

Foolcat 20.1

  • A brand new version of Foolcat, for both Mac and Windows.

Legacy Downloads

Offload Report Creator

A small AppleScript App that creates an HTML page with links to all FoolCat reports.

  • Supports Light and Dark mode theme

  • Will also adjust the theme of the FoolCat reports

  • Links and paths to local media are disabled/hidden

Requirements

Which OS versions does FoolCat currently support?

Hedge

Looking for the Hedge documentation? Starting October 1, 2023, Hedge version 23.2 is now known as OffShoot.

OffShoot's documentation is applicable for all Hedge versions.

Questions

When I try to activate FoolCat (licensed or a trial), why am I told, “No virtual machine activations allowed.”?

This only concerns Windows users.

Running FoolCat in a VM is a Pro feature.

If you see this error when activating a trial, you're running FoolCat in a VM, or a Hypervisor process must be active in Windows.

If you see this error when activating a purchased license, you have a regular license or a Pro license that needs VM activations allowed on your license.

A step-by-step guide for disabling any-and-all Hypervisor (Hyper-V) and Virtual Machine features on your PC is available here:

FoolCat states error -1004

You're likely on an old version of FoolCat, update to the latest version.

"Invalid activation number"

FoolCat states "Starting Services"

This issue is fixed in FoolCat version 23.1 and newer.

FoolCat's media engine isn't starting correctly. Reboot your computer, and if that doesn't help, reinstall FoolCat.

How can I export/import settings?

To export and import user settings for FoolCat on macOS, using the Terminal app, you can follow these steps:

Export Settings

  1. Quit FoolCat

  2. Open the Terminal app

  3. Export the settings

    Run the following command to export the settings to a .plist file:

    This will create a file named OffShootSettings.plist on your desktop.

Import Settings

The user preferences contain encrypted user information that might cause an issue when doing this offline. A reactivation might be needed.

  1. Open Terminal app

  2. Import the preferences

    Run the following command to import the preferences:

To export and import user settings for FoolCat on Windows, using PowerShell, you can follow these steps:

Export Settings

  1. Quit FoolCat

  2. Open PowerShell as Administrator

    Right-click on the Start menu and select "Terminal (Admin)".

  3. Export the settings Run the following commands to export the registry key to a .reg file:

  1. Prune the registry settings (BuildVersion, LicenseVersion)

This will create a file named FoolCatSettings.reg in C:\Temp

Import Settings

The Registry values contain encrypted user information that might cause an issue when doing this offline. A reactivation might be needed.

  1. Quit FoolCat

  2. Open PowerShell as Administrator

    Right-click on the Start menu and select "Terminal (Admin)"

  3. Import the settings

    Double-click the updated file or run the following command to import the registry settings:

Moving From Hedge to OffShoot

I already have a Hedge license, how do I get OffShoot?

If your license is eligible for updates until or beyond October 1, 2023, your license automatically becomes an OffShoot license. You can update your Hedge to OffShoot, and continue using your existing license key.

What does extending my license cost?

What is OffShoot's floating license?

Do I want a floating license?

If you are working alone, but have multiple computers, a floating license is for you. If you need to use OffShoot on multiple computers at the same time, you will need multiple activations on your license.

What changes for multi-seat licenses?

Nothing, they work the same way in OffShoot as they used to work in Hedge. Your seats are now simply activations. In the future, we'll bring floating to these licenses, allowing you to register more devices than your license has activations.

What happened to the Company License?

Company licenses were Hedge licenses with more than 1 seat. Licenses now simply have one or more activations. If you had a company license, you now have a license with multiple activations.

What about the Emergency Activation?

Each Hedge license came with an additional activation in case of emergency. Thanks to floating that's no longer needed so we promoted all Emergency Activations to full activations, for free.

Why is there a Pro version of OffShoot?

As Hedge matured more and more, we found ourselves working on features that only benefit a small set of our customers, but are expensive to build. We think it's fair that only those that benefit are charged for those features. Here's more on the subject:

What does upgrading to Pro cost?

Can I upgrade and extend at the same time?

Why can't I reduce my activations to 1 in the Extend Checkout?

That likely means you have multiple machines activated with your license.

Will my settings and presets still work?

Yes, all settings and presets are carried over from Hedge to OffShoot.

I'm using Codex, do I need to upgrade to Pro?

How do I upgrade to Pro?

I'm using off-the-shelf scripts, do I need OffShoot Pro?

Yes, you'll need to upgrade OffShoot to OffShoot Pro.

Will my existing scripts work?

Where can I download the last version of Hedge?

Can I run OffShoot and Hedge next to each other?

OffShoot replaces Hedge on install. If you really really really need to use both (never at the same time!) the trick is to move Hedge out of /Applications temporarily, install OffShoot, and move Hedge back into /Applications.

Do so at your own risk.


Releases

23.1 - ProGrade

22.3 - Speed

22.2 - iconik

  • Broken media detection; Hedge will show a warning when zero-byte media files are detected on the Source (You can all thank Judy for the idea!).

  • macOS Ventura has an issue setting timestamps on exFAT drives, so we made a workaround for that. (Thanks for reporting, Ben).

  • Want to run a script immediately when Hedge starts? Now you can, with the new Hedge Started event.

  • Official support for macOS 13 Ventura!

  • Fix for a rare case where preset values would be cleared after a transfer.

  • With this release, we're bringing back a much-requested workflow: Batch Sources. You can now start transferring multiple sources in one go, all using the same preset — with just one click 🚀

  • Hedge now polls for changes like updated system time regularly.

  • Clip Review (a Hedge Pro feature) was not showing any stills, that's fixed.

  • Fixed an edge-case that caused Hedge to crash when adding Transfers (Thanks for sending in those crash reports, all!).

  • Added support for Codex Device Manager 6.1

  • MHL Awareness for ASC MHL: if a source contains ASC MHLs, those checksums are used by Checkpoint rather than regenerating them from the source.

  • ASC MHL history is now fully supported.

  • For some users, the Hedge app icon had a bit of an identity crisis, appearing to be a folder. No longer, thanks to Andy and others.

  • New integration: iconik.

  • Enhance your workflow by automatically launching scripts based on events like added disks and completed transfers.

  • Thanks to Michal, Hedge now warns when files on the source are no longer present at transfer time.

  • Fixed a script error that popped up when running Hedge as a non-admin user (Thanks for reporting, David).

  • Fixed some edge cases that caused Hedge to crash (Thanks for sending in those reports, all).

  • It's now possible to hide disks from the Disk overview (Thanks for requesting this feature, all).

  • Local Transfer Logs are now saved into day folders.

  • Adding Labels for source collections works again (Thanks for reporting, Zac).

  • Hedge could crash when dealing with presets and also when ejecting disks; that's fixed (Thanks for sending in those crash reports Vebjørn, and all others).

  • MHL Awareness for ASC MHL: if a source contains ASC MHLs, those checksums are used by Checkpoint rather than regenerating them from the source.

  • ASC MHL history is now fully supported.

  • Elements would sometimes not make it to iconik sidecar files (Thanks for reporting, Mitchell)

  • Elements could end up twice in iconik sidecar files, that's fixed.

  • New integration: iconik.

  • The Hedge API no longer uses a token, as it's now tied to Pro licenses.

22.1 - Elements

  • The "Preparing..." state, which handles indexing, MHL awareness, and duplicate detection is now much, much faster and less RAM hungry when a Source contains large MHLs and Checkpoint is enabled.

  • Clearing Elements is now also possible to do from the Review pane when not using presets.

  • With Auto Labels, the Source Name element would not always refresh properly.

  • The Review pane now shows more elements without having to scroll.

  • The Counter would sometimes refuse to increment, that's fixed.

  • Some pop-ups were hard to read in light mode, that's fixed too.

  • Clearing Elements is now also possible to do from the Review pane when not using presets.

  • Fixes an issue where the Source Name element didn't update when not using a preset.

  • Some users reported Hedge crashing when using File Date elements, that's fixed!

21.3 - Hedge & Codex

Nov 2, 2021 — Our Codex copy engine gains support for Codex Device Manager 6.0. Built in tight collaboration with Codex to get the most out of your mags.

21.2 - Scratch

July 27, 2021 — Automatically add your media to SCRATCH projects, add metadata, and get your dailies going faster than ever.

21.1 - Labels 2.0

May 12, 2021 - Create Labels automatically, with smart counters, and new timestamps that understand that tomorrow doesn't start at midnight.

20.4 - Sorting, and M1 support

Dec 16, 2020 - Automatically sort your files into folders based on properties like creation date and file type, plus a lot more to help refine what is copied, and how: truly unique file names, ignore bundles, and a "copy only..." filter.

20.3 - Presets

Sep 15, 2020 - Managing a lot of media? Many different settings? Speed up your workflow with Presets. Create one for each job, production, or even a camera - and switch between 'm with one click.

20.2 - Checkpoint 2.0

May 19, 2020 (win Oct 13, 2020) - Create not just Backups but Archives too, with the new Checkpoint source integrity options — Complete with auto-enable, transfer sync, legacy checksums, early warning radar, and of course MHL awareness.

20.1 - Connect

Mar 6, 2020 - An all-new Connect to connect all your Hedge installations and get a live overview of your transfers on both iOS and Android

19.4 - Hedge & Codex

Aug 15, 2019 - A copy engine tailor-made for Codex media, including support for High Density Encoding. Built in tight collaboration with Codex to get the most out of your mags. Hedge 19.4 requires at least macOS 10.12.

Releases older than 19.4.8 are no longer available, as the license provider we previously used has gone offline.

19.3 - Filter & Rename

Jul 23, 2019 - Start organizing like a pro: rename your media, skip unwanted files — all during a transfer.

19.2 - Transfer straight into Frame.io

Apr 25, 2019 - With the new Frame.io integration, use your watch folders directly within Hedge and benefit from Frame.io's accellerated upload.

19.1 - Queuing

Feb 19, 2019 - Sometimes, you need that camera card back as soon as possible. Queuing controls if sources are copied one by one, simultaneously, or even to just one destination at a time.

18.3 - Source Verification

Jul 12, 2018 - Whereas backups are meant to be redundant, sources are not... heat, dust, even a wonky cable can alter what is being read. Detect problematic media and peripherals, with 18.3.

18.2 - Duplicate Detection

Apr 4, 2018 - Save time, copy only what's new. Incremental backups are here! Copy into existing folders, and skip what's already there and identical. Perfect if you continue shooting on a card, without erasing it.

18.1 - The Car Wash

Feb 22, 2018 - Car Wash is not so much a new feature as it is a workflow. It allows for a flexible setup of Sources and Destinations. You can now set any combination of drives, any time. Just reset, set, and go.

17.14 - Create Clip Catalogs with Foolcat

New integration; Foolcat generates clean camera reports with thumbnails and extended metadata in HTML and PDF format.

17.13 - Parashoot

Dec 7, 2017 - New integration; Parashoot. Hedge can tell Parashoot when a Source is ready to be 'erased' and ejected. Parashoot will then ask for your confirmation. Enabling this integration disables Auto-Eject.

17.12 - Labels & Collections

Nov 24, 2017 - Sometimes, instead of offloading a whole disk, you only need to transfer a single clip, or a few folders. With Collections, Hedge can now transfer whatever you need: single or multiple files, multiple folders, and of course combinations

17.1 - Hedge for Windows

Hedge for Windows is here!

1.8 - Duplicate Detect

Jun 27, 2017

1.7 - Recents

Apr 5, 2017

1.6 - Hedge Multilingual

Feb 2, 2017

1.5 - Hedge Connect (iOS)

Nov 15, 2016

1.4 - Transfer Logs & MHLs

Sep 7, 2016

1.3 - Fast Lane transfers

May 24, 2016

1.2 - Source folders

Apr 26, 2016

1.1 - Network transfers

Apr 8, 2016

1.0 - Hedge 🚀

Mar 19, 2016

Drag and Drop camera files to create a Report
Drag and Drop a folder to create a report
Processing images to create a report
Hold Option to open a PDF report instead of the HTML version
Use Labels to set Report Names
Completed report

FoolCat 24.5 for Mac (Apr 04, 2025) -

  • Support for Sony's BURANO Version 2.0 firmware.

  • A fresh lick of paint 🎨

FoolCat 24.5 for Windows (Apr 04, 2025) -

New

  • Support for Sony's BURANO Version 2.0 firmware.

  • Automatic conversion of RAW footage to Rec.709.

  • Automatically ignore in-camera generated proxies now works for Canon cameras too.

  • A fresh lick of paint.

Improved

  • ProRes and H.265 clips now display more metadata.

Fixed

  • Clip file sizes are now reported in MiB/GiB again (thanks, Steven).

  • Some clips would show the same still when applying a LUT (thanks, Courtenay and Kenny).

  • Fixed incorrect duration reporting for ProRes clips from ARRI Alexa 35 (thanks for reporting, Ron).

  • ProRes clips from ARRI Alexa 35 now show more than one still again.

FoolCat 24.5 for Windows (Oct 29, 2024) -

  • Support for Canon RAW

  • Support for RED V-Raptor [X] and extended highlights.

  • Support for Phantom CineRAW

FoolCat 24.4 for Mac (Sept 4, 2024) -

  • Support for Blackmagic Cinema Camera 6K.

  • Support for CODEX High Density Encoding (HDE) MXF files.

FoolCat 24.4.1 for Mac (Sept 5, 2024) -

  • Fixed a crash when indexing a folder containing an unsupported audio file.

FoolCat 24.4 for Windows (Sept 4, 2024) -

  • Support for Blackmagic Cinema Camera 6K.

  • Support for ARRIRAW MXF files.

  • Support for CODEX High Density Encoding (HDE) MXF files.

  • Sony RAW clips now show more metadata.

  • Blackmagic BRAW clips now also show timecode metadata.

FoolCat for Mac 24.3 (July 2, 2024) -

FoolCat for Mac 24.3.1 (July 15, 2024) -

FoolCat for Windows 24.3 (July 2, 2024) -

FoolCat for Mac 24.2 (May 7, 2024) -

FoolCat for Windows 24.2 (May 7, 2024) -

FoolCat for Mac 24.1 (March 12, 2024) -

FoolCat can now apply (LUT) to the stills in your reports. Alternatively, you can set FoolCat to convert RAW footage to Rec.709 color space automatically.

FoolCat for Windows 24.1 (March 12, 2024) -

Apply to the stills in your reports.

May 09, 2023 - A brand-new FoolCat, with many more supported codecs and up to three times faster report generation. ...

FoolCat for Mac 23.1 (May 09, 2023) -

FoolCat for Mac 23.1.1 (May 16, 2023) -

FoolCat for Mac 23.1.2 (May 31, 2023) -

FoolCat for Mac 23.1.3 (August 10, 2023) -

FoolCat for Mac 23.1.4 (November 30, 2023) -

FoolCat for Mac 23.1.5 (February 01, 2024) -

September 01, 2021 - |

May 19, 2021 - |

December 18, 2020 - |

September 25, 2020 - |

July 23, 2020 - |

May 26, 2020 - |

Foolcat 6 -

Foolcat 5 -

The current release of FoolCat supports macOS 10.15 and newer. The most recent version of FoolCat to work on older OSes is .

The current release of FoolCat supports Windows 11 & 10. It is possible to run Hedge on Windows 7, but we cannot guarantee everything will work 100%. The interface experience is especially prone to degradation over time.

If you have a regular license and need VM activations, upgrade your license in the , then .

Already on a Pro license? .

You're likely trying to activate FoolCat using a legacy license key. Legacy license keys start with id or only have a few characters. , or .

If your license is not eligible for updates on October 1, 2023, you'll need to extend your license to be able to update to OffShoot. You can do so in-app, or in the .

That depends on the amount of activations. Log in to the , select your OffShoot license and click Extend.

are licenses with a single activation that "floats" between your computers - when you open OffShoot on one, the activation floats to that computer, temporarily deactivating the others. This way, you don't have to manually move your license between computers.

That depends on the amount of activations. Log in to the , select your OffShoot license and click Upgrade To Pro.

Yes, and it's discounted even more. Log in to the , select your OffShoot license and click Extend to find out what the options are for your license.

Head to the License Manager () and either reset you activations or deactivate Hedge from all of your computer except one. Then you'll be able to drop the license to 1 activation, which enables the floating functionality for your license.

Only if you're using Codex Device Manager 7 or newer. If you're using an older Codex version, you can continue using the latest Hedge version available () with the same license key.

In OffShoot, go to Settings > License and hit Upgrade to Pro, or go to the , log in with your email or license key, select your license, then .

Yes, but you'll need .

All previous releases of Hedge are (and will remain) available under .

Still have questions? Let us know:

Looking for newer releases? Starting with 23.2, Hedge is now called OffShoot:

Hedge for Mac 23.1.2 (September 26, 2023) -

  • Official support for macOS 14 Sonoma!

  • The blue “updates available” ribbon now disappears after 1 minute (Thanks for requesting, all).

Hedge for Mac 23.1.1 (March 29, 2023) -

  • It's now possible to disable the ProGrade integration, to get around a remounting issue when using non-ProGrade cards in ProGrade readers.

Hedge for Mac 23.1 (March 07, 2023) -

  • Sanitize your ProGrade media directly in Hedge with the new .

  • Hedge 23.1 drops support for macOS 10.14 or older, so make sure you are on MacOS 10.15 or newer.

Hedge for Windows 23.1 (March 07, 2023) -

  • Sanitize your ProGrade media directly in Hedge with the new .

  • Broken media detection; Hedge will show a warning when zero-byte media files are detected on the Source.

December 14, 2022 - This update is all about speed; whether you're using regular hard drives, NVMe, 10GE, or doing many-to-many backups — enjoy between 20% and 250% speed gains!

Hedge for Mac 22.3.2 (January 19, 2023) -

  • New Queuing mode: Single Destination. First, offload to your fastest drive to get editing, and then to the slower destinations.

Hedge for Mac 22.3.1 (January 3, 2023) -

  • The Finder Extension now works on macOS 11.

  • Hedge no longer shows a "Does not fit" alert when a Destination fills up with purgeable space, as Hedge can now transfer into that space.

Hedge for Mac 22.3 (December 14, 2022) -

  • Hedge's copy engines got a massive tune-up.

  • Start a transfer directly from Finder, with the new Finder integration.

  • Archive mode is no longer throttled by MD5's lack of speed.

  • Extra checksum generation can now be enabled for all copy modes.

  • C4 checksums are now supported too.

  • Transfer Logs now show the checksum and verification status of each file.

  • Fix for a crash reported by Jon, Hendrik, Wes, Nick, and Hans 🙏

  • Added support for Codex Device Manager 6.2

Hedge for Windows 22.3.1 (January 19, 2022) -

  • New Queuing mode: Single Destination. First, offload to your fastest drive to get editing, and then to the slower destinations.

  • Organizing transfers with the {File Hour} element? Hedge now uses 24h notation.

Hedge for Windows 22.3 (December 14, 2022) -

  • Hedge's copy engines got a massive tune-up.

  • Start a transfer directly from Explorer, with the new Explorer integration.

  • Archive mode is no longer throttled by MD5's lack of speed.

  • Extra checksum generation can now be enabled for all copy modes.

  • C4 checksums are now supported too.

  • Transfer Logs now show the checksum and verification status of each file.

April 13, 2022 - Automatically add metadata to all your iconik assets. Generate sidecars containing all your custom elements, to be processed automatically by iconik’s Storage Gateway app.

Hedge for Mac 22.2.9 (December 07, 2022) -

Hedge for Mac 22.2.8 (October 24, 2022) -

Hedge for Mac 22.2.7 (September 5, 2022) -

Hedge for Mac 22.2.6 (September 1, 2022) -

Custom date elements (available in ) now automatically use the system settings if no value is provided.

Hedge for Mac 22.2.5 (August 30, 2022) -

Hedge for Mac 22.2.4 (August 11, 2022) -

Hedge for Mac 22.2.3 (July, 08, 2022) -

Hedge for Mac 22.2.2 (June, 29, 2022) -

Hedge for Mac 22.2.1 (April 21, 2022) -

Hedge for Mac 22.2 (April 13, 2022) -

Support for ASC MHLs for Pro licenses. if you would like a trial.

The no longer uses a token, as it's now tied to Pro licenses. This also applies to which uses the API. if you need access.

Hedge for Windows 22.2.6 (November 22, 2022) -

Hedge for Windows 22.2.5 (October 20, 2022) -

Hedge for Windows 22.2.4 (August 25, 2022) -

Hedge for Windows 22.2.3 (August 11, 2022) -

Hedge for Windows 22.2.2 (June, 29, 2022) -

Hedge for Windows 22.2.1 (April 21, 2022) -

Hedge for Windows 22.2 (April 13, 2022) -

Support for ASC MHLs for Pro licenses. Let us know at if you would like a trial.

Feb 1, 2022 - You can now organize your offloads using custom metadata elements (i.e Location, Project, etc.). Just pop in a source, review, and transfer ✨

Hedge for Mac 22.1.3 (Feb 22, 2022) -

Hedge for Mac 22.1.2 (Feb 8, 2022) -

Hedge for Mac 22.1.1 (Feb 3, 2022) -

Hedge for Mac 22.1 (Feb 1, 2022) -

Hedge for Windows 22.1.1 (Feb 8, 2022) -

Hedge for Windows 22.1 (Feb 1, 2022) -

Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
a custom look
Download
a custom look (LUT)
Learn more
Download
Download
Download
Download
Download
Download
Foolcat for Mac 21.2.5
Foolcat for Windows 21.2.2
Foolcat for Mac 21.1
Foolcat for Windows 21.1
Foolcat for Mac 20.4
Foolcat for Windows 20.4.1
Foolcat for Mac 20.3.2
Foolcat for Windows 20.3.1
Foolcat for Mac 20.2
Foolcat for Windows 20.2
Foolcat for Mac 20.1.1
Foolcat for Windows 20.1.1
Download
Download
defaults export nl.syncfactory.FoolCat.Mac ~/Desktop/FoolCatSettings.plist
defaults import nl.syncfactory.FoolCat.Mac ~/Desktop/FoolCatSettings.plist 
mkdir C:\\Temp
reg export "HKEY_CURRENT_USER\\Software\\FoolCat" "C:\\Temp\\FoolCatSettings.reg"
(Get-Content "C:\\TEMP\\FoolCatSettings.reg") -notmatch '("BuildVersion"|"LicenseVersion")' | Set-Content "C:\\TEMP\\FoolCatSettings.reg"
reg import "C:\\Temp\\FoolCattSettings.reg"
an OffShoot Pro license
Releases
Hedge Pro

Bin Locking

Bin Locking stops others from overwriting your bins while you're working on them. It allows editors to collaborate, and was introduced by Avid in Media Composer.

With Bin Refresh, when changes occur on a bin locked by another editor, Media Composer will refresh a locked bin's state in your Project, exposing those changes. Bin Refresh also allows you to take command of a bin once it's no longer in use by another editor.

Lock States for Refreshed Bins

Lock Color
Who's using this Bin?
Can you read the Bin?
Can you write to the Bin?

🟢

You

✅

✅

🔴

Someone else

✅

❌

🟡

Someone else

✅

❌

🔵

No one is at the moment

✅

✅

🟢 - You're in control with full read/write access to the Bin.

🔴 - Somebody else is working in this Bin. You have read-only access to it.

🟡 - The locked Bin you have open was updated. Click the Bin's padlock to see the latest version.

🔵 - The user who previously held the lock on this Bin has since released it. Click the padlock to acquire read/write access.

You must open this Bin on your computer while someone else is using it on their computer to see the lock change from 🔴 to 🌕 or 🔵.

Download the FoolCat Offload Report Creator v1.1
You'll find OffShoot's documentation here.
VMs & Hypervisors
License Manager
reach out
Reach out
Upgrade your license
download a legacy version
License Manager
License Manager
Floating licenses
https://blog.hedge.video/meet-offshoot
License Manager
License Manager
https://account.hedge.video
23.1.2
hello@hedge.video
Releases
Download
Download
Download
ProGrade Integration
Download
ProGrade Integration
Learn more...
Download
Download
Download
Download
Download
Learn more...
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Reach out
Hedge API
Hedge Helper
Reach out
Download
Download
Download
Download
Download
Download
Download
hello@hedge.video
Learn more...
Download
Download
Download
Download
Download
Download
Download Hedge for Mac 21.3.2
Learn more...
Download Hedge for Mac 21.2.4
Download Hedge for Windows 21.2
Learn more...
Download Hedge for Mac 21.1.3
Download Hedge for Windows 21.1
Learn more...
Download Hedge for Mac 20.4.9
Download Hedge for Windows 20.4.1
Learn more...
Download Hedge for Mac 20.3.7
Download Hedge for Windows 20.3
Learn more...
Download Hedge for Mac 20.2.7
Download Hedge for Windows 20.2
Learn more...
Download Hedge for Mac 20.1.2
Download Hedge for Windows 20.1.2
Learn more...
Download Hedge for Mac 19.4.8
Learn more...
Learn more...
Learn more...
Learn more...
Learn more...
Read more...
Learn more...
Learn more...
Learn more...
Learn more...
FoolCat 21.2

Installing macFUSE

Installation

When you attempt to add your first Workspace on macOS, Mimiq performs a Preflight Check to confirm macFUSE is installed and loaded on your Mac. If not, Mimiq will prompt you to install macFUSE.

macFUSE

If your Mac is managed through MDM, stop now and contact your System Administrator. The following steps below will not apply when using MDM.

Apple Silicon and Reduced Security

On Apple silicon, you'll first need to set your Mac's security policy to "Reduced Security" to be able to load signed kernel extensions. If you're on Intel, you can skip to Install macFUSE.

Apple's use of "Reduced Security" language is misleading. With it, your Mac's security is on par with the level of security you've come to expect with previous versions of macOS.

  1. Shut down your Apple silicon Mac.

  2. Press and hold down the power button until your Mac boots. Your Mac will either send you directly into macOS' Recovery environment, or you'll see an Options button leading to that.

  3. Log in with your user account and select the disk you want to use.

  4. In the menu bar, go to Utilities, then select Startup Security Utility.

  1. Click Security Policy...

  1. Select Reduced Security, then enable: Allow user management of kernel extensions from identified developers .

  1. Click OK.

  2. In the menu bar, select Shut Down.

  3. Turn your Mac back on (press but don't hold the power button this time), then log in.

Install macFUSE

  1. Click + Add Workspace. If Mimiq can't detect macFUSE on your Mac, Mimiq prompts you to install macFUSE first.

  1. Click Install. Mimiq downloads a DMG with the macFUSE installer, then opens it for you.

  2. In the mounted macFUSE DMG window, double-click Install macFUSE, then follow the prompts to complete installation.

Right before you complete macFUSE installation, a System Extension Blocked or System Extension Updated dialog will appear. Now you'll need to approve macFUSE to load in macOS.

Approving macFUSE in macOS

Confirm which version of macOS you're using with Mimiq, then follow these steps to approve macFUSE to load in macOS:

  1. In the System Extension Blocked or System Extension Updated dialog, click Open System Settings.

    • If you clicked OK instead, click Open Security & Privacy System Preferences in the installer.

  2. System Settings will launch, taking you to Privacy & Security > Security.

  3. Under the System software from developer "Benjamin Fleischer"… prompt, click Allow.

  4. Two Privacy & Security dialogs will appear:

    1. In the first Privacy & Security dialog (Privacy & Security is trying to modify your system settings.), enter the password from a local macOS Administrator account, then click Modify Settings.

    2. In the second Privacy & Security dialog (Privacy & Security needs to authenticate to continue.), enter your macOS account’s password, then click OK.

  5. Restart your Mac. It may restart multiple times.

  1. In the System Extension Blocked or System Extension Updated dialog, click Open Security Preferences.

    • If you clicked OK instead, click Open Security & Privacy System Preferences in the installer.

  2. System Preferences will launch, taking you to Security & Privacy > General.

  3. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  4. Once Security & Privacy > General is unlocked, next to the System software from developer "Benjamin Fleischer"… prompt, click Allow.

  5. Click OK, then Restart your Mac. It may restart multiple times.

  1. Launch System Preferences, then go to Security & Privacy > General.

  2. Click the lock 🔒 in the lower-left corner, then authenticate using a local macOS Administrator account.

  3. Once Security & Privacy > General is unlocked, click Allow.

  4. Click Restart Now.

Still no success?

Try loading the kernel extension manually in Terminal:

sudo /usr/bin/kmutil load -p /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext

kextload /Library/Filesystems/macfuse.fs/Contents/Extensions/10.15/macfuse.kext

If that returns an error like system policy prevents loading and/or doesn't load macFUSE, your computer is very likely under IT management policies that prevent kernel extensions to load. Talk to your IT department first, they'll know what to do.

Getting Started

Install and activate Mimiq

Download and install Mimiq:

Mount any eligible volumes

FUSE-based volumes, such as a LucidLink Filespace, may be connected through their respective apps.

Launch Mimiq

Once the desired volumes are mounted, launch Mimiq, which will be available as a helper app in the menu bar (macOS) or System Tray (Windows).

If you have read and write privileges on those volumes, click the Mimiq helper app, and a list of volumes that report a green 🟢 status will appear.

Launch Media Composer

Launch Media Composer, then create a shared Project (or upload and open one) on the desired volume.

When Media Composer prompts you with the non-Avid storage alert, click Yes.

Then you can start working.

Shared Bins opened from an eligible volume will display:

  • The Team Member's Computer Name currently accessing it.

  • A lock status indicator.

Confirm Bin Locking is Activated in Avid Media Composer

If you need to confirm Bin Locking is activated on your desired volumes, check these preferences and settings in Media Composer:

✅ macOS - Avid Media Composer > About Avid Media Composer > Hardware > Avid NEXIS Drives: (the volumes listed in Mimiq)

✅ Windows - Help > About Avid Media Composer > Hardware > Avid NEXIS Drives: (the volumes listed in Mimiq)

Note: From release 24.2 onwards, users won't have to follow the next step, as Mimiq now has NEXIS Coexistence (Pro) and Bin Refresh for all types of storage.

✅ Settings > Project > General > Enable Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS

Deployment Options

Customize how Mimiq behaves for your facility or environment.

Activating

Activating a license can be done via the API:

mimiq://activate?key=[your license key]

Deactivation works via the same mechanism:

mimiq://deactivate

Autostart

By default, Mimiq launches when you log into your computer, but you can control whether Mimiq autostarts.

  1. In Terminal.app, tell Mimiq whether or not to autostart when you log into macOS.

Disable autostart

defaults write video.hedge.Mimiq.Mac launchAtLogin -bool false

Enable autostart

defaults write video.hedge.Mimiq.Mac launchAtLogin -bool true
  1. Commit the setting in Mimiq.

    • If Mimiq has already launched (i.e. in the menu bar):

      1. Quit Mimiq

      2. Relaunch Mimiq.

      3. Restart your Mac.

    • If Mimiq hasn't launched yet (i.e. not present in the menu bar):

      1. Launch Mimiq.

      2. Quit-then-relaunch Mimiq.

      3. Restart your Mac.

Then, use this Terminal command to check Mimiq's current autostart setting:

defaults read video.hedge.Mimiq.Mac launchAtLogin
  • launchAtLogin = 0 - Mimiq will not autostart when you log into macOS.

  • launchAtLogin = 1 - Mimiq autostarts when you log into macOS.

Use PowerShell to add this Registry key – Mimiq – then set it to the path where Mimiq is installed (likely, C:\Program Files\Mimiq\Mimiq.exe).

New-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run" -Name "Mimiq" -Value "C:\Program Files\Mimiq\Mimiq.exe" -PropertyType STRING -Force

That results in this new Registry key:

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Mimiq

To disable autostart, remove the Mimiq Registry key:

Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run" -Name "Mimiq"

Hide volumes and Workspaces list

Although this suppresses Mimiq from initially displaying the list of volumes and Workspaces after it launches, you can still view that list anytime by clicking the Mimiq icon in the menu bar (macOS) or System Tray (Windows).

  1. In Terminal.app, tell Mimiq whether or not to display the list of volumes and Workspaces after it launches.

Disable displaying the list of volumes and workspaces

defaults write video.hedge.Mimiq.Mac disableWindowPopup -bool true

Enable displaying the list of volumes and workspaces

defaults write video.hedge.Mimiq.Mac disableWindowPopup -bool false
  1. Commit the setting in Mimiq.

    • If Mimiq has already launched (i.e. in the menu bar):

      1. Quit Mimiq

      2. Relaunch Mimiq.

      3. Restart your Mac.

    • If Mimiq hasn't launched yet (i.e. not in the menu bar):

      1. Launch Mimiq.

      2. Quit-then-relaunch Mimiq.

      3. Restart your Mac.

Then, you can use this Terminal command to check whether Mimiq will display its list of volumes and Workspaces after it launches:

defaults read video.hedge.Mimiq.Mac disableWindowPopup
  • disableWindowPopup = 0 - Mimiq will display the list of volumes and Workspaces when you log into macOS.

Use PowerShell to add this Registry key – StartupWindowPopupEnabled – then set it to 0.

New-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "StartupWindowPopupEnabled" -Value 0 -PropertyType DWORD -Force

Which results in this new Registry key:

Computer\HKEY_CURRENT_USER\SOFTWARE\Mimiq\StartupWindowPopupEnabled

You can then use Windows' Registry Editor to set StartupWindowPopupEnabled to:

  • 1 - Mimiq will display the list of volumes and Workspaces when you log into Window.

To remove the StartupWindowPopupEnabled Registry key:

Remove-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "StartupWindowPopupEnabled"

Suppress app updates

Although this suppresses Mimiq from displaying app updates after it launches, you can check for an update anytime by clicking the Mimiq icon in the menu bar (macOS) or System Tray (Windows).

  1. In Terminal.app, tell Mimiq whether or not to display app update notifications after it launches.

Disable app update notifications

defaults write video.hedge.Mimiq.Mac disableUpdateNotifications -bool true

Enable app update notifications

defaults write video.hedge.Mimiq.Mac disableUpdateNotifications -bool false
  1. Commit the setting in Mimiq.

    • If Mimiq has already launched (i.e. in the menu bar):

      1. Quit Mimiq

      2. Relaunch Mimiq.

      3. Restart your Mac.

    • If Mimiq hasn't launched yet (i.e. not in the menu bar):

      1. Launch Mimiq.

      2. Quit-then-relaunch Mimiq.

      3. Restart your Mac.

Then, use this Terminal command to check whether Mimiq will display app update notifications after it launches.

defaults read video.hedge.Mimiq.Mac disableUpdateNotifications
  • disableUpdateNotifications = 1 - Mimiq will not display app update notifications when you log into macOS.

  • disableUpdateNotifications = 0 - Mimiq will display app update notifications when you log into macOS.

Use PowerShell to add this Registry key – CheckForUpdatesOnStartupEnabled – then set it to 0.

New-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "CheckForUpdatesOnStartupEnabled" -Value 0 -PropertyType DWORD -Force

Which results in this new Registry key:

Computer\HKEY_CURRENT_USER\SOFTWARE\Mimiq\CheckForUpdatesOnStartupEnabled

You can then use Windows' Registry Editor to set CheckForUpdatesOnStartupEnabled to:

  • 0 - Mimiq will not display app update notifications when you log into Windows.

  • 1 - Mimiq will display app update notifications when you log into Windows.

To remove the CheckForUpdatesOnStartupEnabled Registry key:

Remove-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "CheckForUpdatesOnStartupEnabled"

Mimiq

Mimiq enables Bin Locking for non-Avid storage. It's a standalone app for teams working with Avid Media Composer, enabling Shared Project workflows on:

  • SMB, NFS, and AFP file shares in your local area network

With Mimiq, Media Composer recognizes these volumes as third-party shared storage so teams of Avid editors can work together using Shared Bins with Bin Locking in Shared Projects.

Mimiq Pro

Mimiq Pro enables remote and hybrid Shared Projects workflows by letting you use non-network volumes alongside SMB, NFS, and AFP file shares.

Mimiq Pro also provides NEXIS Coexistence, allowing one to utilize any type of storage for bin locking simultaneously with a NEXIS.

Avid Requirements

Independent of Mimiq (Mimiq doesn't have many requirements), Avid has very specific requirements for Media Composer to be used successfully. If you haven't done so already, be sure to implement these Requirements for Media Composer on each computer, whether you use Mimiq or not:

Workspaces

Mimiq's Workspaces feature allows you to use non-NAS-type storage with Media Composer. It lets you remount any folder in a Media Composer-compatible way, akin to how NEXIS makes folders on shared storage available. This allows you to use any type of storage for bin locking. This is particularly useful for utilizing non-NAS storage like RAID, SAN (e.g., Quantum StorNext), and local folders as independent NEXIS shares.

Workspaces are only needed when your shared storage is not a NAS or macFUSE volume. Do not use Workspaces to create shares for your NAS, but use your NAS's software instead.

Adding a Workspace

  1. Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), then + Add Workspace.

  1. Select a folder to create a Workspace, then click Select (macOS) or Select Folder (Windows).

  2. Your Workspace will appear in Mimiq with a green 🟢 status, then mount in Finder (macOS) or File Explorer (Windows).

You can access your Workspace through Finder (macOS) or File Explorer (Windows) or double-click a Workspace listed in Mimiq to open it in a new window.

Ideally, you don't have Media Composer open while creating Workspaces, as it will detect your new Workspaces only after a restart of Media Composer.

Practical Limits

Workspaces do not scale indefinitely, it's always best to use as little as possible as each Workspace will add overhead to your overall bandwidth.

macOS

On macOS, the usable amount of simultaneously active Workspaces depends on your system resources.

As Workspaces on macOS rely on macFUSE, there's a limitation on how many Workspaces can be used simultaneously. Our tests have shown that a maximum of eight Workspaces is practical. However, as this number correlates with your hardware and system load, it's possible to increase or decrease this amount.

Override the default Workspaces limit

Using Terminal.app, set the maximum number of Workspaces that can be enabled simultaneously:

defaults write video.hedge.Mimiq.Mac workspacelimit -int [amount]

Then, commit the new setting by starting Mimiq. If Mimiq is already active (i.e. its icon shows in the menu bar), quit and restart Mimiq.

If needed, you can use this command to check the current Workspaces limit:

defaults read video.hedge.Mimiq.Mac workspacelimit

It's just as easy to reset the amount back to the default value of 8:

defaults delete video.hedge.Mimiq.Mac workspacelimit

Windows

On Windows, Workspaces utilize available drive letters for mounting. Due to the limited number of drive letters in Windows, there's a constraint on how many Workspaces can be mounted simultaneously.

By default, Mimiq attempts to mount the first Workspace using the drive letter M:. Subsequent Workspaces are assigned the next available letters in alphabetical order.

If M: is already in use on your system, you can modify the starting drive letter. This can be useful if you want to reserve certain drive letters for other purposes or if you prefer a different range of letters for your Workspace(s).

Using PowerShell, define a different starting drive letter:

Change the starting drive letter

New-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "WorkspaceStartDriveLetter" -Value "[DRIVELETTER]" -PropertyType STRING -Force

Then, commit the new setting by starting Mimiq. If Mimiq is already active (i.e. its icon shows in the menu bar), quit and restart Mimiq.

Resetting the default drive letter is just as straightforward:

Remove-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "WorkspaceStartDriveLetter"

Disabling a Workspace

Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), mouse over the Workspace you wish to disable, then click (⋯) > Disable.

Your Workspace will appear in Mimiq with a grey ⚪️ status.

Disabling a Workspace renders it temporarily unavailable to Media Composer without removing it. You may want to disable a Workspace to simplify media management by reducing the number of volumes Media Composer can read from / write to.

Removing a Workspace

Click the Mimiq icon in the menu bar (macOS) or System Tray (Windows), mouse over the Workspace you wish to remove, then click (⋯) > Remove Workspace.

Once you remove a Workspace, it's ejected from your computer and no longer available in Media Composer until you add it again.

Questions

What happens if I add/remove/disable a Workspace while Media Composer is open?

Media Composer cannot cope with volumes mounting/ejecting (or connecting/disconnecting) while it’s open.

If you need to add/remove/disable a Workspace, quit/exit Media Composer first.

Why does Mimiq say my Workspace is Unreachable?

Either your shared storage is unavailable (e.g. disconnected from the network, powered off), or someone renamed the source folder you selected.

Take the appropriate action to make that source folder available again, then quit-then-relaunch Mimiq.

If Mimiq still says the Workspace is Unreachable, you may have to remove the Workspace and then re-add it.

My SAN is mounted, so why does Mimiq say, No lockable volumes found?

Unlike other eligible volumes, Mimiq will not show the mount point of your SAN share as a lockable volume.

Can I create Workspaces on one computer, then share those same Workspaces with other Mimiq users?

Yes. Mimiq saves paths to Workspaces in a JSON file:

~/Library/Application Support/Mimiq/Workspaces/MimiqWorkspaces.json

C:\Users\(Your Windows Account)\AppData\Roaming\Mimiq\Workspaces.json

You could even sync this JSON file among your local and remote team members using something like Resilio Sync, as long as you sync it among Mimiq users with a matching operating system.

I followed all the steps to install and approve macFUSE to load in macOS, but macOS keeps telling me System Extension Blocked. What can I do?

If your Mac is managed through MDM, stop now and contact your System Administrator.

Starting in macOS Big Sur, the local kernel extension (i.e. kext) database in macOS may not retain your decisions on approving third-party system or kernel extensions to load in macOS. If macOS doesn't load macFUSE despite multiple approvals from you, you can safely reset macOS' kext database, which revokes approval for all third-party kexts installed on your system volume.

Once you reset the local kext database, you can log back into macOS and approve any/all system or kernel extensions installed on your Mac.

  1. Save any open work, then power down your Mac.

  2. Choose your system volume, log in with a macOS Administrator account, then launch Terminal.

  3. Use this command to reset your Mac's Kernel Extension database:

    1. kmutil trigger-panic-medic --volume-root /Volumes/(SYSTEM VOLUME)

      • If your system volume has a space in its name (e.g. Macintosh HD), enclose the volume name in quotation marks (e.g. "/Volumes/Macintosh HD").

    2. Press the (Return) key.

      • If you entered this command correctly, you'll see this response, All third party kexts have been unapproved and uninstalled from /Volumes/(SYSTEM VOLUME).

  4. Restart your Mac.

Once you log into macOS, you'll likely be greeted with multiple dialog boxes saying...

  • System Extension Updated

  • System Extension Blocked

...along with confirmation that you triggered the Panic Medic Boot.

You've successfully reset your local kext database in macOS.

Why are drive labels not displayed in File Explorer for some Workspaces?

This only concerns Windows users.

When you create a Workspace from a local drive, and that drive already has a label in File Explorer, the label of the parent drive takes precedence over the Workspace label assigned by Mimiq. In other words, File Explorer will display the existing label of the parent local drive instead of the Workspace label.

To make the Workspace's label visible in File Explorer, you can remove the label for the parent drive.

Local Drives

To display the Workspace label assigned through Mimiq, follow these steps to remove the label from the parent drive:

  1. In File Explorer, create a new window, then locate the parent drive.

  2. Right-click on the parent drive and select Properties.

  3. In the Properties window, locate the General tab.

  4. In the Label field, delete the existing label text.

  5. Click Apply and then OK to save the changes.

LucidLink Filespaces

For a LucidLink Filespace, use PowerShell to remove the drive label:

  1. Open PowerShell.

  2. Run the following command:

    lucid config --set --local --FileSystem.MountPointWindowsLabel ""

  3. Remount the Filespace.

Requirements

Media Composer

A Media Composer | Ultimate (or beyond) subscription or a Perpetual license is required. If you're not on this year's Media Composer release, we recommend running at least the latest minor version of the year you're on.

Can't find a Mimiq version for a just-released version of Media Composer? Give it a few days, as we typically release a compatible version within a week after Avid releases a new major.

Have you already installed a Media Composer that's too new? Roll back to the last supported Media Composer, reboot your computer, and check your inbox.

Operating Systems

  • macOS 10.15.7 or newer

  • Windows 10 or 11 (64-bit, Pro and Enterprise)

macFUSE

Workspaces on macOS require macFUSE. Mimiq automatically downloads the latest compatible version for the most recent macOS release.

Avid's Requirements

Mimiq has a broader range of supported OSs and Media Composer than Avid. A complete list of qualified combinations of operating systems and Media Composer is available at Avid:

Independent of Mimiq, Avid has very specific requirements for using Media Composer at peak performance. We've gathered a shortlist of these and published them here:

Avid's Requirements

To use Media Composer successfully, you must adhere to Avid's system requirements and implement performance optimizations on each team member's workstation.

Here's a short list of references directly from Avid:

However, we've compiled a list of tried-and-true optimizations so you can quickly elevate your current Media Composer environment to Avid's requirements.

You must complete all optimizations on each workstation before reaching out for support.


1. Use a qualified combination of your operating system and Media Composer

When Avid successfully tests a version of Media Composer against a specific version of an operating system, Avid declares that combination qualified.

Use Avid's documentation to find the qualified combination that is best for you and your team:


2. Update your operating system and Media Composer to the latest possible qualified combination

It's highly probable the latest version of Media Composer won't be qualified for the latest version of an operating system. However, Media Composer may be qualified to run on a more updated version of the operating system you're currently using.

With rare exception, do not update Media Composer or your operating system while working on a Project.


3. Connect your computer to the network using a cable (hard-wired)

Connect over Ethernet or Fibre Channel. Do not use Wi-Fi as your workstation's primary network connection.


4. Disable Fast Scrub

Settings > User > Timeline > Use Fast Scrub: DISABLED


5. Adjust Media Composer's Audio Settings

Settings > User > Audio > ...

  • Play Buffer Size in Samples: 1024 (could be as low as 256)

  • Tool Buffer Size in Samples: 1024 (could be as low as 256)

  • Tool Buffer Size in Samples: 12288 (could be as high as 16384)

  • Play Buffer Size in Samples: 12288 (could be as high as 16384)


6. Increase the Amount of Video Memory Used

You can increase the amount of memory Media Composer uses to cache playback here:

Settings > Site > Media Cache > Video Memory

Then adjust these settings in Video Memory:

  • Desired Video Memory (GB): set to the desired amount (default: 2 GB)

  • Enable Playback Video Frame Cache: ENABLED

  • Enabled FX Editing Video Frame Cache: ENABLED

Since the amount of available RAM varies from computer to computer, we can't say how you should set Desired Video Memory. It's best to increase or decrease the amount of memory by GBs, then test for any improvement in Media Composer (e.g. playback, scrubbing, exporting, etc.)


Additional Performance Optimizations

For macOS

1. Remove OpenIO_VirtIO.acf from Avid Media Composer.app‌

Using Blackmagic Design hardware for video playback? Skip this step.

Starting in Media Composer 7.0.4, Avid packaged this plug-in with Media Composer – OpenIO_VirtIO.acf. Media Composer's installer doesn't let you choose whether to install this or not, so you must take these steps to remove it manually:

  1. Quit Media Composer.

  2. In Finder, locate the Avid Media Composer application bundle (e.g. /Applications/Avid Media Composer/AvidMediaComposer.app).

  3. Control-Click on AvidMediaComposer.app and select Show Package Contents.

  4. Go to ../Contents/SharedSupport/AVX2_Plugins.

    • Note: depending on the version of Media Composer, this folder could be ../Contents/SharedSupport/AVX_Plugins.

  5. Locate the OpenIO_VirtIO.acf file. Hold Option then drag a copy of it to your Desktop. (Your mouse pointer will change into a plus sign inside a green circle.)

  6. Delete OpenIO_VirtIO.acf from the Avid Media Composer app package.

  7. Relaunch Media Composer.

2. Rename your Mac's Computer Name to remove any characters with diacritics.

Take these steps to change your Mac's Computer Name in macOS:

3. Eliminate All Other Performance Inhibitors on Your Mac or Local Area Network

  1. Configure your Mac's Energy Saver settings so your Mac doesn't go to sleep, and none of your disks spins down. Possible Energy Saver settings to modify include:

    1. Computer Sleep: Never

    2. Put hard disks to sleep when possible: DISABLED

  2. Disable the screen saver on your Mac.

For Windows

1. Use the BaseAnalyzer in the Avid Collect Suite app to detect and fix any performance inhibitors in Windows.

  1. Launch Avid Collect Suite, then click CHECK CONFIGURATION.

  2. In the BaseAnalyzer dialog, click Verify All.

  3. Choose Failed from the dropdown menu.

  4. Double-click any 🔴 item in the list, then click Fix.

  5. Click Fix until the button’s disabled or the Reason is passed, then click Cancel.

    • After clicking Fix, Avid Collect Suite may tell you: Depending on the changes made it may be required to reboot the system.

  6. Fix as much as you can, then restart Windows.

  7. Once Windows is back up, go back to Step 2 and repeat these steps.

    • You may notice Avid Collect Suite re-lists certain items as 🔴 once again. Avid Collect Suite is working as expected. Once again, Fix as much as you can.


Questions

What are SFPlayConsumer::Execute TIMEOUT Exceptions?

Why is my Project / Bin getting slower (and slower) to open over time?

The Unity Attic folder is too big.

Zip and archive the existing Unity Attic periodically, then Media Composer will regenerate a new one.

It may be best if all team members are out of the Avid Project before archiving the Unity Attic.

Why do my Bins show ??? as the owner instead of my Team Members' Computer Name?

‌Someone renamed or moved that Bin, and Media Composer isn't showing the Project's current state. Refresh the Project in Media Composer from your location, and you'll see the current owner of each Bin.

  • ‌MC 2021.x and newer: Bins > 🍔 > Refresh

  • ‌MC 2018.12.15: Project > 🍔 > Refresh

Troubleshooting

I can't see any Enable Bin Sharing... features in Media Composer under Settings > General.

‌You're using a standard subscription of Media Composer. An Ultimate subscription or a Perpetual license is required for shared Project workflows:

Why does Media Composer say SYS_ERROR, OSErr:-61 when I try to open a Project on macOS?

Media Composer is trying to write to or create a folder (e.g. the /Unity Attic folder) but you don't have write permissions to the root folder of your volume.

Using a LucidLink Filespace? Try copying a small file into the root folder. If the upload fails and you’re certain you granted write permissions for a user or group to that specific folder, have each user...

  1. Set the Root point in their Lucid app to that folder.

  2. Quit Media Composer.

  3. Quit-then-relaunch Mimiq.

  4. Relaunch Media Composer.

When I open a Project, why do I get this error: File (Project Name).avp not found.?

Media Composer doesn't support all characters. If you're seeing this error, then your Computer Name has a diacritic character or accent in it. Rename your computer, replacing the diacritic with an equivalent character, and Media Composer will be able to open your shared Project.

In this example:

❌ Isaac T - über Mac

✅ Isaac T - uber Mac

If you tried opening a shared Project from Drive before changing your Computer Name, you also need to remove the folder with a matching name from your Project.

Be extra cautious when deleting folders inside your shared Project folder.

  1. Quit Media Composer.

  2. While Drive is connected, go to your shared Project folder and locate the folder named after your computer with the diacritic (e.g. Isaac T - über Mac) within the ../AvidSharedData folder.

Depending on the version of Media Composer you're using, Media Composer may generate that folder named after your computer directly inside your shared Project folder.

  1. Move this folder to the Trash.

  1. Relaunch Media Composer and reopen your shared Project.

I'm getting an "Exception: Resource Temporarily Unavailable, filename:/ ..... .pmr" error

Unfortunately, you've encountered a generic Media Composer error.

Mimiq's sole objective is to tell Media Composer, "That storage right there? That's an 'Avid NEXIS Drive' now." It doesn't alter your folder or file permissions nor impact performance to your storage. This error stems from something happening on your own storage.

It could be that the PMR file in your ../Avid MediaFiles/MXF are corrupt and need to be rebuilt. With Media Composer not yet launched or hidden, try deleting the PMR and MDB in those folders, then relaunch or un-hide Media Composer to rebuild them.

Besides that, there's no official workaround available, but it's always a good thing to confirm:

  1. The permissions on your shared folders are correct.

  2. The hard drives in your server aren't failing.

  3. The network connection to your server isn't failing.

Done all that? Check if your NAS isn't serving both SMB and AFP shares. Even if you only connected to SMB shares, the mere fact that AFP is present can trip up Avid Media Composer.

Why does Media Composer ask me to "Mount All Volumes" when opening a project?

Last time you used Media Composer, one of your volumes likely disconnected while Media Composer was running.

Media Composer tracks any volume disconnects that happen during an editing session or after a crash. The next time you open a project stored on the affected volume, you'll be prompted to "Mount All Volumes." Once you complete this step, you can continue working as usual.

Mimiq says, Media Composer can’t be active when Mimiq starts.

If you launched Media Composer before Mimiq, Mimiq knows it won’t be able to activate Bin Locking on your volumes. Save your work in Media Composer (if needed), quit Media Composer, then click Try again to continue launching Mimiq.

I tried quitting Mimiq while Media Composer was open, but Mimiq says, Quit Media Composer before closing Mimiq.

Launch Mimiq before launching Media Composer to activate Bin Locking. After that, Mimiq must stay open while working on your shared Avid Project in Media Composer.

To prevent any unpredictability entering your Project, Mimiq will try to prevent you from quitting the app. If you know what you’re doing or Support directs you to do so, click Quit.

If I previously used Legacy Mimiq on Windows, what’s the best way to install the latest version of Mimiq?

  1. Use Windows’ Apps & features panel to uninstall Legacy Mimiq (search for “Mimiq”).

  2. Restart your PC.

Questions

When should I use Workspaces?

Only if you're not exclusively using a NAS as shared storage. If you are using a NAS, use the NAS management to create shares. Do not reshare folders on your network share via a Workspace, but create a second share for just the folder you want to share.

When I try to activate Mimiq (licensed or a trial), why am I told, “No virtual machine activations allowed.”?

This only concerns Windows users.

Running Mimiq in a VM is a Pro feature.

If you see this error when activating a trial, you're running Mimiq in a VM, or a Hypervisor process must be active in Windows.

If you see this error when activating a purchased license, you have a regular license or a Pro license that needs VM activations allowed on your license.

A step-by-step guide for disabling any-and-all Hypervisor (Hyper-V) and Virtual Machine features on your PC is available here:

Can I use the same license key to activate Mimiq on a Mac and a PC?

Yes.

What about Indiestor?

Hedge acquired Mimiq from Indiestor in September 2022.

Licenses purchased from Indiestor ("Legacy Mimiq") or its resellers were supported for the duration of your licensing period, which means by now they are all out of support and will no longer receive updates.

Can I transfer a Legacy Mimiq license to another computer?

No. Legacy Mimiq licenses were tied to a specific MAC address which cannot be altered. Instead, crossgrade to a new Mimiq license.

How long was a Legacy Mimiq license valid?

A Legacy Mimiq license was valid for one year from the time your license file was issued.

Do you still offer Legacy Mimiq licenses?

No, Legacy Mimiq is no longer available for purchase. Mimiq has feature parity, and if you need to use Mimiq with MC 2018 and/or macOS 10.14 Mojave a Mimiq Pro license covers your needs.

Can we use Mimiq to work on the same Project from a Mac and a PC?

Can I use Mimiq in an air-gapped environment?

How do I deactivate Mimiq to use on another computer?

You can deactivate Mimiq in-app by clicking the helper app, go to the hamburger, then License > Deactivate...

Does Media Composer support permission management systems like Active Directory or Open Directory?

In short, no. When you're reading this, chances are you have a SAN and thus use permission management like Active Directory or Open Directory. Those permissions do not carry over to Media Composer.

If you already have assets in permission-managed folders that you need to expose to Media Composer, create a new share on your SAN and run a chmod 777 Terminal command on its contents.

From then on, only create new folders through Media Composer.

Will Mimiq work with Media Composer 2018.x and macOS 10.14 or Windows 7?

Your mileage may vary when using Windows 7. We don't officially support it, but Mimiq might work with your workstation's configuration.

Why can’t there be one version of Mimiq for all versions of Windows, macOS, and Media Composer?

In short:

  1. Apple and Avid no longer support all versions in use.

  2. These versions are no longer patched or updated, posing a significant security risk.

  3. Apple silicon requires macOS 10.15.7 or newer.

  4. The new Mimiq uses modern technologies that are too new to work on all previously supported OSs.

Avid’s Chris Bové also maintains a human-readable (but slightly less updated) rendition of that Version Matrix here:

Which on-premise shared storage providers support Mimiq?

Mimiq is compatible with any shared storage that lets you create shared volumes over SMB, NFS, and AFP.

That said, network stack implementations (i.e. SMB, NFS, AFP) vary from vendor to vendor, and there may be differences beyond our control that are incompatible with Mimiq. If you think you’ve found one of these incompatibilities or you’re running in circles, reach out.

How should I configure my SMB, NFS, or AFP share?

Mimiq doesn't have a preference on how to configure your shared storage, but Avid very much does.

If you want to hit the ground running, try setting read and write privileges for any shares used for your Avid Projects and media. Once your shares work as expected, work with IT or experiment with narrowing down permissions for your team or situation.

Also, if you're using SMB shares, look for an OPLOCKS (Opportunistic Locks) setting in your shared storage admin's UI, then disable it. That disables caching on the client workstations, forcing all workstations to always look at the current state of affairs on your shared storage instead of having the OS rely on a locally cached state to make decisions on file operations.

Beyond that, as Hedge isn’t a system integrator or IT support company, we can’t say how best to configure these shares on your particular storage - use an Avid system integrator for that.

Should I mount shared volumes through UNC paths in Windows?

No.

Setting the Mount point of your LucidLink Filespace to a Valid absolute path and separated semicolon drive letter is not supported.

Should I use the AllDrives command in Media Composer's Console?

No, 99% of the time.

However, if you used AllDrives recently, you'll need to make sure AllDrives is correctly set to use with Mimiq:

  1. Use AllDrives -1 to determine the current status. This is the Help file for the command, but the last line reports AllDrives' current status.

  2. Did AllDrives report Only true media drives will be viewed as media drives.? If so, nothing more is needed. Otherwise...

  3. Use AllDrives 2, which will report Only true media drives will be viewed as media drives.

How can I test throughput performance for my network share?

First, check with your shared storage vendor for any docs, bundled utilities, or commands that could assist you.

Where should I store my media?

You can store your media on any volume accessible to your computer. Just make sure you use the appropriate Avid media management folder structure on the desired storage:

  • Shared Storage

    • /(Volume)/Avid MediaFiles/MXF/(Someones Computer).(N)

    • /(Volume)/OMFI MediaFiles/(Someones Computer)

  • Local Storage

    • /(Volume)/Avid MediaFiles/MXF/(N)

    • /(Volume)/OMFI MediaFiles/ - no subfolders

Do not mix Shared and Local storage media management folder structures on the same volume.

Should I rename the folders in ../Avid MediaFiles/MXF | UME/ or ../OMFI MediaFiles?

That depends.

Media Composer expects subfolders in ../Avid MediaFiles/MXF | UME/ or ../OMFI MediaFiles on shared storage to be named this way:

  • ../Avid MediaFiles/MXF/(Someones Computer).(N)

  • ../Avid MediaFiles/UME/(Someones Computer).(N)

  • ../OMFI MediaFiles/(Someones Computer)

When ingesting media, Media Composer generates Media Stream Manager files (MSMs) in these subfolders, then reads those MSMs to connect Clips to their media.

A common practice is to ingest dailies, then rename those subfolders for tracking purposes (e.g. by date or reel). When someone renames this folder, it is now locked off. Media Composer will neither add more media to that folder nor update the MSMs.

If this is part of your workflow and you can stay on top of renaming those folders according to your custom workflow, feel free to rename those folders on your storage.

However, if you don't ‌quickly rename those folders, you introduce unpredictability for the rest of the team. Team Members won't be able to view media in Media Composer until someone renames these subfolders according to your team's custom workflow.

Can both Mimiq and the Avid NEXIS Client be installed on my computer?

Yes. However, since only one NEXIS client can be active on a computer at any given time, once Mimiq launches, it becomes the active NEXIS client.

When you quit/exit Mimiq, your former NEXIS client will resume its place as the active NEXIS client.

Media Composer & Mojave

For teams who must continue working in macOS 10.14 Mojave and/or Avid Media Composer 2018 environments, we have a special build available: Mimiq 18.1

Requirements

  • An Intel Mac (so not Apple silicon)

  • macOS 10.14.x

  • A Media Composer | Ultimate (or beyond) subscription or a Perpetual license

Getting Started

  1. Download Mimiq 18.1:

  1. Launch Mimiq.

  2. Launch Media Composer.

Install and Activate Mimiq 18.1

Once you install Mimiq 18.1, locate your Mimiq Pro license key, copy it, then paste it into the Activate Mimiq dialog by:

  1. Right-clicking the Activation number field.

  2. Click Paste.

    • Note: you cannot paste in your license key using Command-V.

  3. Click Activate.

Need Mimiq to launch in macOS automatically on startup? Add it to System Preferences > Users & Groups > (Your macOS Account) > Login Items

Mount Any Eligible Volumes

Mimiq 18.1 will activate bin locking on the following types of volumes:

  • SMB, NFS, and AFP file shares in your local area network

  • FUSE-based volumes, such as a LucidLink Filespace

Mimiq 18.1's UI does not list the eligible volumes with Bin Locking activated.

Confirm Bin Locking is Activated in Avid Media Composer

If you need to confirm Mimiq 18.1 activated Bin Locking on your desired volumes, check these settings to make sure Media Composer can see those volumes as an Avid NEXIS Drive:

✅‌ MC 2018.12.x: Info > Hardware > Hardware Tool > Avid NEXIS Drives: (your SMB, NFS, AFP, or FUSE-based volume)

✅ MC 2021.x: Avid Media Composer > About Avid Media Composer > Hardware > Avid NEXIS Drives: (your SMB, NFS, AFP, or FUSE-based volume)

You can also open Media Composer's Console (Command-6) and look for this line of text in the output: Avid Shared Storage is installed. (Avid NEXIS)

Questions

Aren't both Mojave and MC 2018 are out of support?

Yes.

That means that if you run into issues with Mimiq 18.1, the cause is either macOS 10.14 and Media Composer 2018. If so, your only option is to migrate away from macOS 10.14 and Media Composer 2018.x.

Why won't Mimiq 18.1 install on my Apple silicon Mac?

Why can't I activate Mimiq 18.1?

A Mimiq Pro license with an available activation is required to activate Mimiq 18.1. You can use the same license key you use to activate other Mimiq versions.

Which file shares are supported in Mimiq 18.1?

  • SMB, NFS, and AFP file shares in your local area network

  • FUSE-based volumes, such as a LucidLink Filespace

Can I use Mimiq 18.1 alongside Mimiq in the same environment?

Yes!

How do I deactivate Mimiq 18.1?

Releases

Mimiq 25.1

Support for Media Composer 2024.12

Mimiq 24.5

Support for Media Composer 2024.10 and LucidLink 3.0.

Mimiq 24.4

Mimiq now supports the brand-new Local License Server for on-prem licensing. Perfect for air-gapped facilities and production houses with strict security requirements.

  • Pro Local License Server support

  • Adds options to hide updates and license information, for MDM deployments

  • Support for macOS 15 Sequoia

  • Pro Local License Server support

  • Adds options to hide updates and license information, for MDM deployments

Mimiq 24.3

  • Support for Media Composer 2024.6

  • Support for Media Composer 2024.6

Mimiq 24.2

  • Bin Refresh for all types of storage

  • Pro NEXIS Coexistence

  • Trials now come with all Pro features

  • Fix for trial extensions

  • Improved activation handling, thanks to Leon!

  • Bin Refresh for all types of storage

  • Pro NEXIS Coexistence

Mimiq 24.1

  • Support for Avid Media Composer 2024.2

  • Pro Workspaces can now be mounted by non-Administrator users

  • Improvements for bin locking on AFP shared storage

  • Support for LucidLink v2.6

  • Support for Avid Media Composer 2024.2

  • Improvements for offline usage

  • Note: does not yet support LucidLink v2.6

Mimiq 23.3

  • Improved support for Media Composer 2023.12

  • Support for Avid Media Composer 2023.12

  • Improved support for Media Composer 2023.12

  • Support for Avid Media Composer 2023.12

Mimiq 23.2

  • Sonoma support, way ahead of Avid 😉

  • Project License support

  • Improved trial handling

  • Support for Avid Media Composer 2023.8

  • Fix for license deactivations when a computer goes offline.

  • Additional bug fixes and performance improvements.

  • Project License support

  • Support for Media Composer 2023.8

  • Mimiq can now be used with non-Administrator accounts.

Mimiq 23.1

Workspaces (Pro) enable you to use any type of block-based storage, like a SAN, RAID, or SSD, with Media Composer.

  • Pro Improved overall performance for Workspaces, particularly when added from a SAN.

  • Adds functionality to hide notifications and prevent the main view from popping up on app-open.

  • Fix for a crash on activation.

  • Pro Workspaces - with Workspaces you can turn any folder on any storage, including Quantum StorNext, into Avid-compatible storage.

  • Support for Media Composer 2023.3

  • Support for AFP is now available for all users.

  • Adds functionality to hide notifications and prevent the main view from popping up on app-open.

  • Pro Workspaces - with Workspaces you can turn any folder on any storage, including Quantum StorNext, into Avid-compatible storage.

  • Support for Media Composer 2023.3

  • Fix for high CPU usage in certain cases.

Mimiq 22.4

A wholly rebuilt Mimiq, with new licensing and support for Apple silicon.

  • Support for Media Composer 2022.12

  • Locking AFP volumes is now available for Pro licenses

  • A 10-day in-app trial is now available.

  • Support for Media Composer 2022.10

  • Fix for an edge case resulting in a memory leak in Media Composer.

  • Fix for auto-locking not persisting.

  • Improve check if Media Composer is installed.

  • First Mimiq release 🎉

  • Support for LucidLink on Windows 11.

  • Fix for volumes showing up twice in Mimiq.

  • Fix for activations not always working.

  • Fix for opening store links.

  • Install Mimiq without having to first install Media Composer.

  • Support for Media Composer 2022.12

  • A 10-day in-app trial is now available.

  • Support for Media Composer 2022.10

  • First Mimiq release 🎉

Mimiq 18.1

A special barebones build of Mimiq for teams that need to use Media Composer on macOS 10.14 Mojave.

Beta Track

From time to time, we have new features that we'd like your feedback on before making them available to all users. The Beta Track is available to all users with a license that's within support and updates. Whenever we open up a Beta for users, we'll email you about how to gain access.

Requirements

A Mimiq or Mimiq Pro license eligible for updates & support.

Downloads

  • Windows: coming soon!

Starting Services
License Manager

macFUSE is a macOS kernel extension used to create virtual filesystems. It's built and maintained by Benjamin Fleischer (). Mimiq automatically downloads the installer for the latest macFUSE release that is confirmed to be compatible with Workspaces.

If you are on older machines, like Intel Macs, you might need to download an older version of macFUSE at .

Select the disk and click Security policy

Once macFUSE is installed, you're ready to . ✅

.

macOS -

Windows -

Connect any local storage to your computer, or mount the desired network shares – SMB, NFS, or AFP – using either Finder (macOS) or File Explorer (Windows). Once those are mounted, any associated will be mounted as well.

NFS in macOS - if you need more control over creating or mounting NFS shares in macOS, you can use something like .

disableWindowPopup = 1 - Mimiq will not display the list of volumes and Workspaces when you log into macOS,

0 - Mimiq will not display the list of volumes and Workspaces when you log into Windows,

FUSE-based volumes, such as a LucidLink Filespace (Available in )

(Available in )

Mimiq Pro allows you to create from any type of storage – such as a RAID, SAN (e.g. Quantum StorNext), LucidLink Filespaces, and even local folders – which Media Composer treats as independent NEXIS shares.

As long as you have read and write permissions to that share, once you , Mimiq will activate Bin Locking on that folder.

Once your Mac is fully powered down, .

, and any other existing system or kernel extensions, to load in macOS.

Media Composer
Supported in Mimiq as of
Media Composer
Supported in Mimiq as of
Media Composer
Supported in Mimiq as of
Media Composer
Supported in Mimiq as of
Media Composer
Supported in Mimiq as of

Media Composer 2019 builds are unsupported.

Support for Media Composer 2018 requires a Mimiq Pro license.

macOS 10.14.6 (requires a Pro license and )

You must use to install or uninstall Mimiq.

As macFUSE releases tend to be backward compatible, installing the latest macFUSE release tends to suffice. If not, you can find older releases at the website.

Our installation and troubleshooting guide for macFUSE is in the section.

This guide is independent of Mimiq, and is only about getting Media Composer deployed successfully. Assisting with Media Composer workflow issues beyond the scope of Mimiq support may require .

Disabling Fast Scrub results in a significant reduction of .

Adjusting Media Composer's Audio settings results in a significant reduction of .

Removing OpenIO_VirtIO.acf results in a significant reduction of .

and install .

2. Complete your Media Composer setup using the that matches the version of Windows you're using.

means some part of your system is too slow for Media Composer to achieve playback. If you open Tools > Console in Media Composer, you'll find these exceptions are logged quite frequently in the background, even with standard operations like playback or scrubbing.

‌ > Collaboration & control > Shared bins & projects

If you don’t have access to IT or need assistance beyond Mimiq support,

First, , replacing the diacritic with another character.

Install

If you have a regular license and need VM activations, upgrade your license in the , then .

Already on a Pro license? .

To crossgrade your Legacy Mimiq license to a new Mimiq license, .

Yes, you can mix any number of Macs and PCs. Just make sure your license has enoughavailable for each computer. Additional activations can be added in the .

Yes. You can either air-gap the Media Composer edit suite after activating Mimiq or use a .

You can also manage your activations and deactivations from anywhere using the .

Yes, see .

If you need guidance on upgrading, use as a starting point, then either consult with an Avid reseller or choose the best qualified combo of operating system and Media Composer for you with Avid's Version Matrix for Media Composer:

If you don’t have access to IT or need assistance beyond Mimiq support,

Avid introduced in Media Composer 2022.12. Our testing reveals their implementation is unpredictable, with erratic OS-level permissions errors. Hence, shared volumes mounted solely through UNC paths are currently not supported by Mimiq.

Otherwise, using something like may help.

Instead, we recommend letting Media Composer put the media wherever it wants within ../Avid MediaFiles/MXF | UME/ or ../OMFI MediaFiles/, then use Media Composer to organize your Clips into Bins. If you need to copy or move any media, use the free helper app to sift media based on Project (or based on a Bin) as needed.

.

Apple discontinued support for macOS Mojave 10.14 in November 2021. The final update for macOS Mojave is , which results in Version 10.14.6 (18G9323).

Avid ended the development of Media Composer 2018.12.15 on December 31, 2020, and on December 31, 2021.

macOS Mojave is incompatible with Apple silicon Macs. If you are on Apple silicon, use the current Mimiq release:

You can and through the Hedge License Manager ().

If you purchased a standard Mimiq license, through the Hedge License Manager.

Mimiq 18.1 cannot be deactivated in-app. If you need to deactivate a computer with Mimiq 18.1, you must do so

Mimiq for Mac 25.1 (Feb 26, 2025) -

  • Support for Media Composer 2024.12

Mimiq for Windows 25.1 (Feb 26, 2025) -

  • Support for Media Composer 2024.12

Mimiq for Windows 25.1.1 (Mar 28, 2025) -

  • Fix for offline usage (Thanks, Mark!)

Mimiq for Mac 24.5 (Oct 30, 2024) -

  • Support for Media Composer 2024.10

  • Pro Pre-release support for LucidLink 3.0

Mimiq for Mac 24.5.1 (Dec 2, 2024) -

  • Fix for switching between multiple Local License Servers

Mimiq for Mac 24.5.2 (Dec 12, 2024) -

  • Support for all Media Composer 2020 releases, not just 2020.12.

Mimiq for Windows 24.5 (Oct 30, 2024) -

  • Support for Media Composer 2024.10

  • Fix for a pesky desktop artifact that was bugging us and also some of you :)

  • Fix for a crash on exit. Thanks for reporting, Paul and Jon!

  • Pro Support for LucidLink 3.0. Currently requires creating a Mimiq Workspace.

Mimiq for Windows 24.5.1 (Dec 12, 2024) -

  • Support for all Media Composer 2020 releases, not just 2020.12.

Mimiq for Windows 24.5.2 (Dec 23, 2024) -

  • ProFix for LucidLink 2.0 users that use Lucid 2.9.6211 or newer.

Mimiq for Mac 24.4 (Sep 12, 2024) -

Mimiq for Windows 24.4 (Sep 12, 2024) -

Mimiq for Mac 24.3 (Jul 4, 2024) -

Mimiq for Windows 24.3 (Jul 4, 2024) -

Mimiq for Mac 24.2 (May 22, 2024) -

Mimiq for Windows 24.2.1 (Jun 14, 2024) -

Mimiq for Windows 24.2 (May 22, 2024) -

Mimiq for Mac 24.1 (March 5, 2024) -

Mimiq for Windows 24.1.1 (March 12, 2024) -

Mimiq for Windows 24.1 (March 5, 2024) -

Mimiq for Mac 23.3.1 (December 21, 2023) -

Mimiq for Mac 23.3 (December 18, 2023) -

Mimiq for Windows 23.3.1 (January 30, 2024) -

Mimiq for Windows 23.3 (December 18, 2023) -

Mimiq for Mac 23.2.1 (October 17, 2023) -

Mimiq for Mac 23.2 (September 4, 2023) -

Mimiq for Windows 23.2.2 (November 29, 2023) -

Mimiq for Windows 23.2.1 (October 26, 2023) -

Mimiq for Windows 23.2 (September 4, 2023) -

Mimiq for Mac 23.1.3 (August 23, 2023) -

Mimiq for Mac 23.1.2 (May 16, 2023) -

Mimiq for Mac 23.1.1 (April 24, 2023) -

Mimiq for Mac 23.1 (April 16, 2023) -

Mimiq for Windows 23.1.2 (May 16, 2023) -

Mimiq for Windows 23.1 (April 16, 2023) -

Mimiq for Mac 22.4 (January 3, 2023) -

Mimiq for Mac 22.3.1 (November 8, 2022) -

Mimiq for Mac 22.3 (October 25, 2022) -

Mimiq for Mac 22.2.2 (September 21, 2022) -

Mimiq for Mac 22.2.1 (September 19, 2022) -

Mimiq for Mac 22.2 (September 8, 2022) -

Mimiq for Windows 22.4.2 (February 7, 2023) -

Mimiq for Windows 22.4.1 (January 24, 2023) -

Mimiq for Windows 22.4 (January 3, 2023) -

Mimiq for Windows 22.3.1 (November 24, 2022) -

Mimiq for Windows 22.3 (October 25, 2022) -

Mimiq for Windows 22.2 - (September 19, 2022) -

Mimiq for Mac 18.1 (Feb 28, 2024) -

macOS:

Media Composer
Mimiq for Mac
Mimiq for Windows
https://osxfuse.github.io
https://github.com/osxfuse/osxfuse/releases
https://hedge.video/download/mimiq/macos
https://hedge.video/download/mimiq/windows
Workspaces
NFS Manager
Workspaces
Avid's Requirements
power up your Mac again in Recovery mode
add your first Workspace
Install and activate Mimiq.
Mount any eligible volumes.
Launch Mimiq.
Launch Media Composer.
Confirm Bin Locking is activated
even if Mimiq launches when you log in.
even if Mimiq launches when you log in.
Mimiq Pro
Workspaces created from any type of storage
Mimiq Pro
add a folder from your SAN as a Workspace
Now you can approve macFUSE

2024.12

25.1

2024.10

24.5

2024.6

24.3

2024.2

24.1

2023.12

23.3

2023.8

23.2

2023.3

23.1

2022.12

22.4

2022.10

22.3

2022.7

22.2

2022.4

22.2

2021.12

22.2

2021.9

22.2

2021.6

22.2

2021.5

22.2

2021.3

22.2

2021.2

22.2

2020.12

22.2

2020.10

24.5.1

2020.9

24.5.1

2020.8

24.5.1

2020.6

24.5.1

2020.5

24.5.1

2020.4

24.5.1

2018.x

18.1

24.2

A complete discussion on this topic is available in Mimiq's documentation.
Media Composer & Mojave

Features

OffShoot has a lot of visible and invisible features.

Mimiq 18.1
Media Composer is not qualified for use on Windows Home or Server editions.
an Administrator account
macFUSE
Workspaces
Avid's Requirements
Professional Services
Media Composer System Requirements
Computer Optimization Guides – Mac and Windows
Media Composer caches playback to RAM. The more memory you have installed on your workstation, the better your playback experience will be.
Download
Avid Collect Suite for Windows
Computer Optimization Guide
SFPlayConsumer::Execute TIMEOUT
https://www.avid.com/media-composer/comparison
Professional Services are available for an additional fee.
change your computer name in macOS
the latest version of Mimiq.
VMs & Hypervisors
License Manager
reach out
Reach out
reach out
activations
License Manager
Local License Server
License Manager
Microsoft ended support for Windows 7 in January 2020.
Apple discontinued support for macOS Mojave 10.14 in November 2021.
Avid declared End of Development of Media Composer 2018.12.x on December 31, 2020, and End of Support for it on December 31, 2021.
Mimiq's Requirements
Professional Services are available for an additional fee.
mounting any shared volume via UNC
iPerf3
Media Database Viewer (MDVx)
A Mimiq Pro license
A version of Media Composer qualified for macOS 10.14.x
Buy a Mimiq Pro license.
https://downloads.hedge.video/mimiq/Mimiq%2018.1.dmg
Security Update 2021-005 (Mojave)
officially ended support
Releases
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
https://hedge.video/download/mimiq/beta/macos
SFPlayConsumer::Execute TIMEOUT exceptions
SFPlayConsumer::Execute TIMEOUT exceptions
SFPlayConsumer::Execute TIMEOUT exceptions
Do not use Wi-Fi as your computer's primary network connection.
Media Composer becomes unpredictable when a Mac's Computer Name contains characters with diacritics (e.g. á, é, í, ö, ü).
Mount any eligible volumes.
Confirm Bin Locking is activated

Overview

OffShoot allows you to create multiple copies, backups, and archives from multiple sources simultaneously. Built with video workflows in mind, OffShoot performs verified transfers using checksums to/from any type of storage medium.

Disks

OffShoot displays all available disks and volumes connected to your computer. You can set any available disk as a Source or a Destination.

Sources

Add any disk or volume listed under Disks to SOURCES. You can transfer files from a single source or multiple sources.

Possible sources may include:

  1. Camera Memory Cards

  2. Local Disks or Folders

  3. Network Volumes or Folders

Is OffShoot able to work with NAS directories both locally and remotely?

OffShoot recognizes all mounted file systems with some exceptions:

  • Time Machine volumes

  • Remote servers

Additional options are available for each disk or volume under the hamburger menu.

Source Folder

By default, OffShoot transfers the entire contents of a disk or volume added to SOURCES. If you only need to transfer a specific folder (along with its subfolders), you can set that as the Source Folder.

You can also use Presets to automate and refine different aspects of a file transfer.

Can I select specific folders as a Source?

Yes, you can select anything as a source. It can be a single file or folder, a collection of files or folders, or both.

Add Label...

Adding a label to a disk or volume listed under Disks automatically adds it to SOURCES.

Set as Unused

Removes a disk or volume from SOURCES, adding it to Disks once again. Any labels will be removed.

Set as Destination

Moves a disk or volume from SOURCES to DESTINATIONS.

Eject Volume Name

Disconnects the disk or volume from your computer.

Rename Volume Name

Renames the disk or volume. Unlike a label, renaming a disk or volume happens at the file system level, persisting beyond its usage in OffShoot.

Destinations

Any disk or volume listed under Disks can be added to DESTINATIONS. Transfer files to a single destination, or multiple destinations.

Possible destinations may include:

  1. Local Disks or Folders

  2. Network Volumes or Folders

Additional options are available for each disk or volume under the hamburger menu.

Destination Folder

By default, OffShoot transfers the entirety of SOURCES to the root folder of disks or volumes added to DESTINATIONS. If you want to transfer files to a specific folder, you can set that as the Destination Folder.

Can I select specific folders as a Destination?

Yes, you can select any folder you have read and write privileges to as a Destination.

Set as Unused

Removes a disk or volume from DESTINATIONS, adding it to Disks once again.

Set as Source

Moves a disk or volume from DESTINATIONS to SOURCES.

Eject Volume Name

Disconnects the disk or volume from your computer.

Rename Volume Name

Renames the disk or volume. Unlike a label, renaming a disk or volume happens at the file system level, persisting beyond its use in OffShoot.

Add Transfers

When SOURCES and DESTINATIONS are selected and configured, OffShoot is ready to perform a file transfer.

Transfers are jobs added to a queue. If you receive a new memory card or drive while a transfer's in progress, you can add it to SOURCES or DESTINATIONS, then add another transfer.

OffShoot multiplies the number of SOURCES by the number of DESTINATIONS, then displays how many transfers you'll make in the Add Transfer button.

  1. Toggle the slider to ☑️.

  2. Select a Preset from the drop-down menu.

Once you've confirmed your transfer settings, click Add 1 Transfer or Add <N> Transfers.

Transfers

In the Transfers view, you can monitor all finished and running transfers.

You can navigate between Disks and Transfers in OffShoot by clicking the arrow on the Transfers section's right-hand side or using the in-app shortcut key combinations for Disks and Transfers.

Progress

When a transfer is in progress, you'll see the following:

  • The name of the transfer job - SOURCE → DESTINATION

  • The name of the transferring file

  • A moving average of the data rate

  • An estimated duration

Progress bars can have the following colors:

  • Grey: the transfer is being indexed and prepared. If MHLs exist on the source, they're indexed too.

  • Dark Blue: copying

  • Light Blue: verification, validation, security, integrity checks, sidecar creation, and logging.

  • Green: all done, no issues found.

  • Red: a hardware issue was detected, like a disconnected storage device, or a checksum error on the source.

  • Orange: a file integrity issue was detected.

Monitoring Progress Remotely with Connect

Connect is a free companion app that runs in your browser and lets you monitor OffShoot transfers. Connect displays live views of transfers in progress, and pushes notifications to your device upon completion.

Need help?

If run into Avid errors that you think are related to Mimiq, please email us a screenshot. Include which Mimiq version you are on, your Media Composer version and license type, and describe your media and storage. That ought to give us enough to go on.

Logs

Verification

Checksums

XXH64BE Checksums are always generated from reading source files and stored in Transfer Logs and MHLs. It's also possible to generate one or all legacy checksums (MD5, SHA1, C4).

Generating legacy checksum can affect overall transfer speed.

Verification modes

Transfer

To enjoy maximum transfer speed, the file sizes of both sources and destinations are checked against each other. Note: do not use this mode if you plan to erase your sources.

Source

To rule out read errors, an independent source checksum verification is done. On destinations, the file size is verified. Use this mode if you’re erasing your sources while creating multiple backups.

When a source verification issue is found, the transfer stops. If a Destination verification issue is found, the transfer will continue and be completed with warnings.

In this mode, OffShoot first performs a pre-read of the file to verify its integrity, then reads it again to perform the actual copy operation.

Source & Destination

All sources and destinations are independently verified for maximum protection by reading back everything and comparing the resulting checksums and file metadata. Typically, it takes twice as long as Transfer Verification.

  • Choose this mode when creating ASC MHLs.

  • When a source or destination verification issue is found, the transfer will continue and complete with warnings.

These modes got a makeover in OffShoot 24.3. For older OffShoot versions, the following legend can be used:

  • Checkpoint OFF -> Transfer

  • Checkpoint ON (Backup) -> Source

  • Checkpoint ON (Archive) -> Source & Destination

MHL awareness

In Source and Source & Destination verification modes, OffShoot will automatically detect (ASC) MHLs on the source, and uses the listed checksums instead of rereading the source file.

OffShoot will only use the (ASC) MHL checksum when the file size and modification date match the referenced file.

Automatic MHL verification

In Transfer and Source verification modes, when transfers are successful and the Destination is idle, OffShoot will automatically reverify the newly created (ASC) MHL on the destination. When an issue is found, OffShoot will try to copy the file again using the Source or another Destination.

Manual MHL verification

Available in OffShoot 24.3 and newer

  • Detects missing files and files with a hash issue.

  • The verification results will be recorded in a log (hint: click the status underneath the progress bar to open the verification log).

  • All ASC MHL files referenced in the ASC MHL chain.xml will be verified.

Source Verification issue event

Fires when a source verification issue is detected.

Broken Media Detection

OffShoot displays an alert when 0-byte media files are detected on the source. This issue typically occurs with ExFAT-formatted cards that have not been ejected properly.

If Broken Media Detection somehow blocks your workflow, you can configure OffShoot to dismiss the alert automatically after 20 seconds. Use the following command in Terminal/PowerShell ( 1 = enabled, 0 = disabled).

defaults write nl.syncfactory.Hedge.Mac SFIDefaultsZeroByteFilesDetectedAutoContinue 1
New-ItemProperty -Path "HKCU:\Software\Hedge" -Name "BrokenMediaAlertAutoContinueEnabled" -Value 1 -PropertyType DWord -Force

Missing files detection

At the end of a transfer, OffShoot checks if all files are present on the destination. If any are missing, an alert is shown and a warning is logged.

OffShoot

Fast, verified data transfers with metadata management for offload and ingest. Formerly known as Hedge, OffShoot is your ideal companion when managing media.

Ingest Browser

Browse a Source and select which folders you want to transfer, each with its own label and preset. Cherrypick folders and label them directly in the browser.

Requirements

  • OffShoot 24.4 or newer

  • A Pro License

How to use

  1. Click the Disk Menu icon and select Source Folder > Ingest...

  1. Select the folders you want to set as Sources.

  2. Click the blue Set Sources button.

Every folder will become an independent Source. By default, OffShoot will add Sources to the transfer queue as a batch. This feature can be disabled in Settings > General > Batch-add Sources to transfer queue.

Setting Labels

To set Labels directly in the Ingest Browser, right-click a folder and choose Add Label... (shortcut: Command-Enter / Control-Enter)

Keyboard shortcuts

Action
Shortcut

Navigate up and down the folder list

Up and Down arrows

Open and close folders

Left and Right arrows

Toggle checkbox

Space

Select or deselect all items in current level

Shift-space / Control-A

Set a Label

Command-Enter / Control-Enter

Set selected Sources

Enter

Dismiss Ingest Browser

Esc

Duplicate Detection

OffShoot will automatically detect duplicates when copying data into an existing folder structure. A file will be not be copied when all of these conditions are met:

  • A file with an identical name exists in the folder the copy will end up

  • That file has the same byte size

  • That file has the same modification date

When a file with an identical name already exists on the destination path, but has a different byte size and/or modification date, it will be copied using a counter following Finder and Explorer's duplicate naming conventions: B002C006_180327_R1ZA.mov becomes B002C006_180327_R1ZA 2.mov.

Logging

Skipped files will be logged in the Transfer Log, under the section:

-- Skipped files (already on destination) --

Duplicates that do not match all criteria are logged as such:

-- Transferred files -- #1: B002C006_180327_R1ZA.mov path: XDROOT/CLIPS/B002C006_180327_R1ZA 2.mov

Finding duplicates without copying

Stop & Resume

Need to stop a transfer? Did a transfer fail? You can stop and resume transfers in OffShoot at your convenience.

Requirements

  • OffShoot 24.1 or newer.

How to use

  • When a transfer is running, stop it with the Stop button.

  • Once stopped, you can resume the transfer with the Resume button.

    • You can also resume Failed transfers, or transfers that report Completed with warnings.

When the destination connection is suddenly lost, OffShoot can't write Transfer logs and (ASC)MHL files on that destination. However, OffShoot will write a local transfer log, which is available in OffShoot > Window > Transfer Log.

Depending on the destination drive and filesystem used, transferred folders and/or files might be missing, incomplete, or show as zero-byte files. Before resuming, make sure to remove any incomplete or zero-byte files from the destination (or all files when a full (ASC)MHL is needed).

When resuming:

  • OffShoot will ensure the correct Source is resumed by comparing the Source index.

  • Partially copied files or files OffShoot did not successfully verify are removed from the destination and transferred again.

  • Changing OffShoot's global application settings will affect restarted transfers. Only Organize, Verification, and MHL-related settings are retained for each transfer.

Limitations

  • Resuming a transfer will result in a new Transfer Log and new (ASC)MHL files containing the newly transferred files.

  • Resuming a partially copied/verified file is not possible.

Labels

With physical memory cards and drives, you'd affix labels to media to stay organized during a shoot. Likewise, OffShoot lets you apply labels to sources, which you can use to build and extend your workflow.

Adding a Label

To add a label to a Disk, click its name, type your label, and hit Return. Doing this will set that Disk as a Source. You can also click the hamburger menu and select Add Label...

Your new label will appear in blue.

To add a label without making that Disk a Source, add the label, then click no some space somewhere outside the Disk. To cancel label creation, press Escape.

Labels do not rename a Source's actual Volume Name.

To remove a label, click the blue label, press Delete or Backspace, and hit Enter. The Source will now revert back to its volume name. You can also click the hamburger menu and select Clear Label.

Labels and your workflow

With your first transfer, you'll notice OffShoot used your label to name the parent folder on the Destination. You can also customize labels to create subfolders and add date-based information to a transfer.

Element

Description

Example

{YYYY}, {YY}

Year

2021, 21

{MM}

Month

03

{DD}

Day

23

{hh}

Hour, in 24-hour format

14

{mm}

Minutes

01

{ss}

Seconds

56

/

When a Label contains a slash, it creates subfolders on the Destination. Useful when you want to have a subfolder for each camera or day.

A/10w

Auto Labels

Auto Label allows you to automatically label a source with a specified format, whether sources are added manually or automatically through the Auto Source setting.

Whereas labels you set manually appear in blue, Auto Labels are shown within a white outline:

Element

Description

Example

{Source Name}

Volume Name

UNTITLED

{Counter}

The Source Counter. Automatically increased with a value of 1. Set the initial value of the Counter in the Organize preference pane, including additional leading zeros if required.

002

{YYYY}, {YY}

Year

2021, 21

{MM}

Month

03

{DD}

Day

23

{hh}

Hour, in 24-hour format

14

{mm}

Minutes

01

{ss}

Seconds

56

/

When a label contains a slash, and the {Source Name} element is used in the folder format so that a label will be part of the folder structure, slashes create subfolders on the destination. Useful when you want to have a subfolder for each camera, or day.

A/10

Auto Labels are auto-updating

Some label elements (e.g. {Counter}, respond dynamically when:

  • Sources are added or removed

  • You change the counter value in Settings

  • Time passes (i.e. when using date-based label elements)

  • You manually override an applied Auto Label

Date-based label elements changed

It's midnight, but it's not the end of the shoot day. Perhaps you're offloading footage from a shoot, but it wasn't shot today. If you're using date-based label elements, go to Preferences > General > Date to set which date Auto Label will use for Today. You can also specify what time tomorrow starts so you can stay organized during those late-night shoots.

Manually changing an applied Auto Label

This is very powerful, and important to understand correctly.

Let's say you're importing cards from camera A, and you use an Auto Label format A{Counter}. Adding three Sources, each gets an Auto Label: A001 A002 and A003. But card two is actually A010, so you alter the second source's Label to give it a manual Label.

What now happens is the Auto Label of the third source detects this change and alters its own label to be A002, as that is the next counter available now that A010 has entered the mix:

Organization

Organize what should be transferred, and how.

Manage which files and folders are to be copied, and how filenames and folder structures are created on the destinations, in OffShoot's Organize settings.

How to use

  1. Go to OffShoot > Settings > Organize.

Selective Copying

If your sources tend to contain files that are not of use to you, filter them by specifying their file extensions or (partial) filenames. If you want to be really strict, for example when importing a Sony card when you might not want anything but the media files copied, you can do the opposite: ignore all files, except the ones defined, by switching fromDo not copy files to Copy only files . Use the latter option with caution, as it's easy to forget you have this setting applied. Pro tip: only use it as part of a Preset.

Ignore Bundles

Don't want to transfer certain bundles like apps, or those empty AVCHD bundles Sony cameras create on every card? For your safety, you need to specify the size as well; by using this feature only for "empty" bundles, you'll be sure that a bundle does get copied if it inadvertently does contain useful data.

Ignore Folders

Some camera cards create a default folder structure that might not be useful to you as it may contain empty folders. To ignore those empty folders when copying, use When empty. If you want to ignore all folders, and only copy files, use Flatten folders.

Auto Label

File Renaming

For each transfer, OffShoot uses the Rename Format to create a new file name.

Folder Creation

For each transfer, OffShoot uses the Folder Format to create a folder structure on the destination.

Use a slash (/) to create multiple folders on a Destination. If you want to add slashes to folder names, you can separate those elements with a colon (:). For example, to format a folder name as a date with slashes, copy/paste this date format into Create Folders - {DD}:{MM}:{YYYY}

Available Elements

The following elements can be used to create a custom format.

Element
Description
Example

{Source Name}

The Source Label, or Volume Name if no Label is set.

UNTITLED

{Counter}

A source counter. Automatically raised by 1. You can set the counter in the Organize preference pane and add additional leading zeros if needed.

002

{YYYY}, {YY}

Year

2021, 21

{MM}

Month

03

{DD}

Day

23

{hh}

Hour, in 24-hour format

14

{mm}

Minutes

01

{ss}

Seconds

56

{Filename}

The name of the file. Can only be used in "Rename Files".

File001.jpg

{File Counter}

A file counter with 5 leading zeros. Automatically raised with 1. Can only be used in "Rename Files".

000001

{File Extension}

The file extension. Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

mov

{File YYYY}, {File YY}

File Creation year Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

2021, 21

{File MM}

File Creation month Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

03

{File DD}

File Creation day Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

23

{File hh}

File Creation hour, in 24-hour format Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

14

{File mm}

File Creation minutes Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

01

{File ss}

File Creation seconds Cannot be used in "Auto Label". Will sort files into folders when used in "Create Folders".

56

{Content *Date*}

Creation Date of the oldest file on the Source. *Use with: YYYY, YY, DD, MM, hh, mm, ss. {Content *Date*} can't be used in the Auto Label field. To exclude specific file extensions, set them as ; separated string (e.g., ".xml;.dat") in the following plist/registry keys*: - macOS: SFIContentDateIgnoreFileExtensions - Windows: ContentDateIgnoreExtensions *Requires v24.4.1 or newer,

{Content YYYY}

Sort files into folders

It is possible to create folders based on file properties. When using {File Extension}, {File YYYY}, {File YY}, {File MM}, {File DD}, {File hh}, {File mm} or {File ss} in "Create Folders", OffShoot will automatically sort all files into folders.

When sorting files into folders, the original folder structure is ignored (Flattens Folders).

Timestamps are set when adding a Source. The Date can be set in General preferences.

Custom elements

Presets

Organization settings can be saved as a preset and selected when adding Transfers.

OffShoot saves Presets as .hedge files in this location:

  • macOS - ~/Library/Preferences/Hedge/Presets

  • Window - C:\Users\(Your Username)\AppData\Roaming\Hedge\Presets

Presets are text files you can rename, edit with a text editor, and share. Once you give someone a .hedge file and they double-click it on their computer, OffShoot opens and installs the preset.

In Settings > Organize, choose Manage Presets in the Preset dropdown to open the preset location in Finder (macOS) or File Explorer (Windows).

Queuing

Queuing allows you to manage how many transfers will run at once:

  • Off - All sources will be transferred at the same time. New transfers start while others are still running.

  • Single Source - Only transfers of a single source run simultaneously. When finished, the next source starts automatically.

  • Single Destination - Each source is transferred to a single destination at a time (requires Hedge for Mac 22.3.2 or newer).

  • Single Transfer - Transfers run one by one, even when from the same source.

Elements

Organize and tag your offloads with custom metadata elements – like Location or Project – to review your added transfers.

Use any elements you create alongside automatically populated elements – such as Source Name, Date, and Counter – to create folder paths, rename files, and set Labels. OffShoot logs all elements and their values in the Transfer Log, Event Log, and Media Hash List.

How to use

  1. Go to Settings > Organize.

  2. Use the ➕ button to create a custom element.

  3. Drag elements to Auto Label, Rename Files, and Create Folders.

  4. Set up a Source and Destination, review your elements, then start your Transfer.

You can also create elements by typing curly brackets { } (e.g. {Project}), then pressing [Enter].

OffShoot lets you review all used elements when you set up a transfer. If you used any custom elements, OffShoot automatically displays the Review panel before a transfer. Didn't use any custom elements? You can still access the Review panel before a transfer. In the Disks menu Command-1, click the up arrow button (⌃) in the lower-right corner to review any auto-populated elements.

If you're using presets, you can toggle the Review panel by choosing Review Preset from the Preset dropdown.

By default, all entered information is saved until you quit OffShoot. Want to start fresh? Right-click anywhere in the Review Preset panel and choose Clear.

Logging & Integrations

All elements and their values are logged in the Transfer Log, Event Log, and Media Hash List. They can also be used in the Foolcat, iconik, and SCRATCH integrations.

OffShoot 23.2 (1481) - macOS 14.0.0

Source: /Untitled
Destination: /T1/Project X/2021_12_24/Amsterdam/A001

Preset: 22.1 CAM A | Review
Counter: 001
Date: 24/12/2021
Location: Amsterdam
Project: PRX

Started: 24/12/2021, 09:15:11
...
24/12/2021, 09:15 - File copy completed: {
    "FileCopyCompleted_bytesCopied" = 232656229;
    "FileCopyCompleted_destinationPath" = "/Volumes/T1/PRX/Amsterdam/2021-12-24/A001";
    "FileCopyCompleted_duration" = "1.180007";
    "FileCopyCompleted_checkpointMode" = Off;
    "FileCopyCompleted_presetName" = "22.1 CAM A | Review";
    "FileCopyCompleted_sourceInfo" = { 
	"Counter" = "001", 
	"Date" = "20211224", 
        "Location" = "Amsterdam", 
        "Project" = "PRX" };
    "FileCopyCompleted_sourcePaths" = "/Volumes/Untitled";
    "FileCopyCompleted_startedAt" = 20211224113108;
    "FileCopyCompleted_state" = Success;
}
<?xml version="1.0" encoding="UTF-8"?>
<hashlist version="1.1">
    <hedge>
        <rootPath>/Volumes/T1</rootPath>
    </hedge>
    <sourceInfo preset="22.1 CAM A | Review">
	<sourceinfofield name="Counter">001</sourceinfofield>
	<sourceinfofield name="Date">2021-12-24</sourceinfofield>
        <sourceinfofield name="Location">Amsterdam</sourceinfofield>
        <sourceinfofield name="Project">PRX</sourceinfofield>
    </sourceInfo>

Pro Preset

Preset Builder

An OffShoot Pro license is required to use presets created by the Preset Builder.

Pro presets let you:

  • Add iconik settings elements

  • Control the order in which elements appear

  • Use dropdown elements

  • Use hidden elements

  • Create one file with multiple presets

  • Give elements default values

  • Save entered values in the preset

Clip Review (beta)

When clipReviewElements are defined in a preset, a Clip Review form is presented per clip.

By default, any entered values are cleared from the Clip Review form. However, you can choose which values will persist by pinning them with 📌. Like Source Review, Clip Review data is logged in the Transfer Log and the (ASC) MHL.

-- Transferred files --
#1: Clip0001.MXF
Path: 2021-09-09__0002_201908231232_000001.MXF
Size: 13729840 bytes
Source hash:	b09fa6763fbd1cf6
Copy hash:	b09fa6763fbd1cf6

Subject: Test shot
Tags: OffShoot, Demo 
Rating: ⭐️⭐️⭐️⭐️⭐️
Info: this is awesome
 <hash>
        <file>2021-09-09__0002_201908231232_000001.MXF</file>
        <size>13729840</size>
        <lastmodificationdate>2019-08-22T11:44:05Z</lastmodificationdate>
        <clipinfo>
            <clipinfofield name="Subject">Test shot</clipinfofield>
            <clipinfofield name="Tags">OffShoot, Demo </clipinfofield>
            <clipinfofield name="Rating">⭐️⭐️⭐️⭐️⭐️</clipinfofield>
            <clipinfofield name="Info">this is awesome</clipinfofield>
        </clipinfo>
        <xxhash64be>b09fa6763fbd1cf6</xxhash64be>
        <xxhash64>f61cbd3f76a69fb0</xxhash64>
        <hashdate>2021-09-09T18:48:03Z</hashdate>
</hash>

iconik

Control per preset which file extensions and metadata elements should end up in iconik sidecar files.

"iconikSidecarElements" : [ "{ProjectID}", "{Project}", "{Season}", "{Date}", "{Camera}", "{Card}", "{Type}" ],
"iconikSidecarExtensions" : [".R3D",".MOV"],
"iconikSidecarDestinations" : ["Backup 1", "Backup 2"]

Pro preset file

A .hedge preset is formatted as a JSON file and can be opened in any text or code editor.

1KB
Production_X_CAM_A.hedge.zip
archive
pro preset example

To install the preset, double-click the .hedge file. OffShoot will launch, and install the preset in ~/Library/Preferences/Hedge/Presets/.

Structure

A .hedge preset file consists of one array with one or more preset objects (in JSON format).

[{
    "name" : "Production X - CAM A",
    "description": "",
    "version" : "1.0",
}]
Name
Required
Description

name

Single preset: no Multiple presets: yes

If you don't specify a name, OffShoot will use the file name as the preset name. Required when defining multiple presets in one file.

description

no

Currently unexposed in OffShoot.

version

yes

Should always be set to 1.0

Elements

The sourceReviewElements array contains all elements that will appear in the Review pane when adding a source.

"sourceReviewElements": [
  { "name": "{Project Name}", "type": "text", "defaultValue": "" },
  { "name": "{Project ID}", "type": "text", "defaultValue": "" },
]

The clipReviewElements array contains all elements that will appear in the Clip Review pane when adding the transfer.

"clipReviewElements": [ 
    { "name": "{Subject}", "type": "text", "defaultValue": "" }, 
    { "name": "{Notes}", "type": "text", "defaultValue": "" }, 
]

Element properties

Name
Required
Description

name

yes

The name of the Element. Must be unique and enclosed in curly brackets { }.

type

yes

The type of the Element: text, date, select, counter, or hidden.

defaultValue

yes

The default value of the Element.

value

no

Holds the value that has been entered in OffShoot when adding tranfers.

options

required for select elements

Holds an array of select objects.

Element types

There are five Element types:

Type
Description

text

A normal text input field.

date

A date picker. Uses the Language & Region set in System Preferences. The value will be formatted as {YYYY}-{MM}-{DD}. To use a different format in labelPattern , renamePattern or folderPattern use {YYYY},{MM} and {DD} elements.

select

A dropdown with multiple values.

counter

A text input field with a number that auto increments every time the preset is used.

number

A text input field that accepts only numerical values.

hidden

A hidden field that does not show up in the form.

    "sourceReviewElements" : [
      { "name" : "{Project Name}", "type" : "text", "defaultValue" : ""},
      { "name" : "{Date}", "type": "date", "defaultValue" : ""},
      { "name" : "{Location}", "type" : "select", "defaultValue" : "",
        "options" : [
          { "name" : "", "value" : "" },
          { "name" : "Adam", "value" : "Adam" },
          { "name" : "Rome", "value" : "Rome" }
        ]
      },
      { "name" : "{Reel}", "type" : "counter", "defaultValue" : "0001" },
      { "name" : "{Preset ID}", "type" : "hidden", "defaultValue" : "0293840293" }
    ],

All Element types can have a defaultValue set, with the exception of date . The defaultValue displays when the Source Review form's first used or when clearing the form. By default, the date element uses the date set in Preferences > General > Date:.

Values entered when tranfers are added are saved as a value property in the preset file..

{ "name" : "{Project Name}", "type" : "text", "value": "Project X, "defaultValue" : ""},

Dropdown

select Elements have an extra options property that holds all the dropdown options.

  { "name" : "{Location}", "type" : "select", "defaultValue" : "", "value" : "",
    "options" : [
      { "name" : "", "value" : "" },
      { "name" : "Adam", "value" : "Adam" },
      { "name" : "NY", "value" : "030" }
    ]

Tip: Leave the first option blank to make selecting a value an active choice.

Organize settings

You can define the following organize settings in a preset:

Setting
Type
Required
Description and example

doNotCopyFiles

Array

no

Files with these file extensions will be transferred. e.g. [".thumbs", "XML"] cannot be combined with copyOnlyFiles.

copyOnlyFiles

Array

no

Only files with these file extensions will be transferred. e.g. [".mp4", "mov"] cannot be combined with doNotCopyFiles. When both properties are defined, doNotCopyFiles will be used.

ignoreEmptyFolders

Boolean

no

When true, empty folders will not be transferred.

ignoreBundles

Array

no

Bundles with these names have their file size checked. If the name matches and they're larger or smaller than the size specified, they won't be transferred. e.g. [ "AVCHD<2MB" ]

flattenFolders

Boolean

no

When true, the Source's folder structure is flattened. Duplicate filenames will be renamed with a counter.

labelPattern

String

no

Sets the Auto Label pattern for this preset. {Metadata} elements, excluding {Filename} and {File date} elements, can be used. This label will be used in the transfer log name and picked up by the {Source Name} element.

renamePattern

String

no

Renames all files with the specified format. {Metadata} elements including {Filename} can be used here.

folderPattern

String

no

Create destination folders with a specified format. {Metadata} elements, excluding {Filename} and {File date}elements, can be used. Use / to create a folder path.

dontAllowRepetitionAndTrim

Array

no

Specify characters that should be trimmed and checked for repetition in labelPattern, renamePattern, and folderPattern. Especially useful when not all elements have a value.

    "doNotCopyFiles": ["xml", ".thumb"],
    "copyOnlyFiles": ["mov", "mp4", "mxf"],

    "ignoreEmptyFolders" : false,
    "ignoreBundles": ["AVCHD<1MB"],
    "flattenFolders" : true,
    
    
    "labelPattern" : "{Location}_{Card}",
    "renamePattern" : "{Project Name}_{Date}__{Location}_{Card}__{Clip Location}_{Rating}_{File YYYY}{File MM}{File DD}{File hh}{File ss}__{File Counter}",
    "folderPattern" : "{Project Name}/{Date}/{Location}/{Card}",
    
    "dontAllowRepetitionAndTrim" : ["_", "/"],

Multiple presets in one file

It is also possible to create one .hedge file with multiple presets. See the example below.

[
    {
        "name": "preset 1",
        ...
    },
    {
        "name": "preset 2",
        ...
    },
    {
        "name": "preset 3",
        ...
    }
]

Cascading Copies

By utilizing Cascading, you can offload faster. If one of your destinations is faster than the others, Cascading allows you to copy to your fastest destination and then copy from that destination to other destinations. This lets you free up the source earlier, independent of the verification mode used.

Requirements

How To Set Up

  1. First, set your fastest disk as Destination. This is typically an SSD or RAID. Using a NAS as the primary destination is not recommended, as this will bog down your network bandwidth.

  2. Drag the next disk you want as a Destination onto the primary Destination and release when a blue outline appears (Figure 1). Repeat for additional Destinations.

  1. A Cascading Group will be created, with an arrow indicating the flow (Figure 2).

  2. When you've added a Source and then hit Add Transfers, transfers will be created for each destination. The transfers that cascade from the primary destination will start when the primary transfer has been completed. The Source can be ejected as soon as the cascading transfers start (Figure 3).

Alternatively, you can set up Cascading via the Disk Menu (or right-click a disk); select Cascade from... and choose a Destination (Figure 4).

Advanced Workflows

With an OffShoot Pro license, advanced Cascading workflows are possible.

Copy from your primary destinations to multiple other destinations (Figure 5), or switch to continue to cascade, where each previous destination becomes the source for the next destination (Figure 6).

It's also possible to create multiple Cascading Groups with multiple primary disks acting as sources for secondary disks (see Figure 7).

Limitations

  • To modify your cascading setup, you must drag disks out of Destinations.

  • Cascading transfers won't show up in Connect yet.

  • Cascading from S3 is not supported.

Connect

Get a live overview of OffShoot transfers in progress – yours and others – plus receive push notifications on completed transfers wherever you are.

Requirements

  1. OffShoot 23.2 or newer

  2. A modern web browser

How to use

  1. Go to Settings > Connect.

  2. Toggle Enable Connect to ON.

  3. Copy the Connect Code by clicking the clipboard icon.

  1. Enter the Connect Code or request a magic link (requires an OffShoot Pro license).

  1. Start a transfer in OffShoot, and your transfers will appear on the Connect site.

Monitor multiple computers

Connect can list multiple workstations with OffShoot transfers in-progress if someone enables Connect in OffShoot on their workstation and they send you their Connect Code.

  1. Under Add new connection, enter the Connect Code of another computer using OffShoot with Connect enabled.

  2. Click Connect.

  3. That computer will appear on the Connect site with any live transfer progress.

Receive Notifications

Connect can send push notifications about completed OffShoot transfers to a network-connected device.

  1. Click Allow in the notifications popup on your device.

  2. When the grey bell turns blue, Connect will send you notifications for completed transfers.

Enable Push Notifications from the Connect site on mobile devices

  • iOS 16.4 and newer:

    1. Save Connect as a web app by tapping the share button in the iOS toolbar, scrolling to the bottom of the menu, and tapping Add to Home Screen.

    2. Open the web app and click the notification bell icon.

    3. Enable Notifications for this website when prompted.

If the notification button is disabled, your browser does not support notifications, or you rejected notifications to appear in your web browser.

Change connection name

By default, Connect will display the Computer Name as the connection name.

You can change the connection name in OffShoot > Settings > Connect > Computer Name.

Revoke access

An OffShoot user can revoke access to Connect by clicking the Revoke Access button in OffShoot. This cancels all connections to the Connect site and creates a new Connect Code.

On the Connect site, you can delete a connection to a device by hovering over the device listed under Connections, then clicking X next to it.

Auto Connect (Pro)

With an OffShoot Pro license, there's no need to Add new connection's with a Connect Code since:

  • Enable Connect will be toggled ON by default.

  • OffShoot automatically adds your device's connection to the Connect site.

  • You can log in to the Connect site using your email address or license key.

Date & Time

Sometimes, you want to offload yesterday's material and obviously not use today's timestamps. OffShoot allows you to control such metadata without having to reset your computer's time and date (which will lead to a bunch of trouble).

In OffShoot's Settings > General page, you can control date and time. Here, we've set the timestamp to Jan 1st:

You can reset the timestamp to again follow the system time by hitting the Now button. Until that button is changed, the date is static; in this example, it doesn't roll over into Jan 2nd.

For shoots that run late into the night, it's possible to automatically keep OffShoot from disregarding what is technically a new day. In this setting, OffShoot will switch to tomorrow at 4am (04:00)

S3 Transfers

simultaneouslyPerform verified file transfers directly to an S3 bucket using OffShoot.

Currently, you can only set S3 disks as a Destination.

Requirements

  • OffShoot 23.2 or newer

  • A Pro License

  • Access to an S3 bucket with at least write, delete and listBucket permissions

How to use

  1. Go to Settings > Cloud.

  2. Click Add... to create a new S3 connection.

  1. Enter your S3 credentials – the Address, Bucket Name, Access Key, and Secret.

The AWS S3 address is constructed as follows: https://s3. followed by <bucket region>, and ending with .amazonaws.com.

  1. Click Connect.

  2. The S3 bucket will now be available as a Disk in OffShoot.

AWS S3 Transfer acceleration

Configuring the S3 Connection

Connecting to a path

You can also define an Optional Path as part of your S3 bucket's Location, which OffShoot will mount as your S3 bucket's "root point".

Hover over the disk with your mouse in OffShoot, and OffShoot will display the Bucket name and Optional Path as a tooltip.

Using a Label

By default, OffShoot uses the Bucket name as the disk name. As with other disks in OffShoot, you can rename it with a Label when creating or configuring the connection.

Configuring an S3 connection via CLI (macOS only)

Browsing a Bucket

Once your S3 bucket is connected, you can browse it in OffShoot by:

  • Double-clicking the S3 bucket's disk icon.

  • Choosing Browse... from the Disk's menu.

Editing / Removing a Connection

You can edit or remove an existing S3 connection by:

  • Double-clicking the connection.

  • Clicking the ellipses ⋯, then choosing Edit or Remove.

Setting a Destination Folder

It's possible to set a Destination folder via Disk menu > Destination Folder > Browse...

New folder creation is also possible, but OffShoot only creates those at transfer time.

Verification

S3 transfers are always verified using multi-part MD5 checksums. This is done server-side and does not require a readback of the files or Checkpoint being ON.

Concurrency

OffShoot uploads multiple files (in parts) to S3 at the same time. To adjust these settings, you can modify the following defaults:

API

Limitations

  • Setting an S3 bucket as a Source is currently unsupported.

  • Transfers will use the Standard storage class.

  • Local S3 connections using self-signed certificates are currently unsupported.

  • Due to S3 limitations, OffShoot cannot transfer:

    • Empty folders

    • File aliases/symlinks

    • Zero byte files

    • Files larger than 5TiB

  • Due to S3 limitations, the FoolCat, EditReady, and iconik integrations are unsupported.

Generic S3

If you don't have an AWS S3 bucket, you can try the generic S3 integration. Use at your own discretion.

Configuring Connections

On macOS, configuring connections is also possible via the Terminal app.

You'll need to restart OffShoot to apply any changes made with these commands.

Connections are stored in these keys:

  • S3AwsConnections

  • S3GenericConnections

A connection is structured using the following JSON format:

Creating a connection

You can create an AWS S3 connection from a JSON file using the structure listed above with the following Terminal command:

The connection's Secret Access Key is stored in the login Keychain as an Application password item, which you can create with the following command:

Although OffShoot was allowed access when creating the keychain item, permissions must be allowed again. Please let us know if you discover how to fix this issue.

Checking existing AWS S3 locations

Write current S3 connections to a JSON file

(For backing up or editing the JSON file.)

System Preferences > Sharing > Computer Name
Avid Media Composer Documentation and Version Matrix
Avid Media Composer Documentation and Version Matrix
Avid Media Composer Documentation and Version Matrix
AlwaysEditing.comAlwaysEditing.com
From Chris Bové, Online Community Manager and Customer Advocate, Avid Technology
AlwaysEditing.comAlwaysEditing.com
From Chris Bové, Online Community Manager and Customer Advocate, Avid Technology
Change your computer’s name or local hostname on MacApple Support
https://account.hedge.video
Disks

During a shoot, adding temporary labels to memory cards or drives helps you stay organized. Similarly,

To send us your log files, open the Mimiq app, click the hamburger, then Help > Collect log files for support. Save that log somewhere convenient (e.g. your Desktop) and email it to .

All transfers in OffShoot are always verified, so you can be sure your files are copied safely. By default, this is done using the method. If you need more thorough verification and protection, you can set a different mode in OffShoot > Settings > Transfers > Verification

It's possible to verify data without doing a transfer. Just double-click and then click Verify.

If an identical file exists in a different folder on your destination, the source file will be copied. If you are looking for a way to find duplicates on an existing drive, have a look at or .

OffShoot will resume by restarting the transfer and skipping files that are already on the destination based on rules.

A Label has been set
Two sources with Auto Labels applied.

If an Auto Label format is part of , all new Sources will be labeled accordingly.

Auto Label elements
Preferences > General > Date
Auto Labels auto-update when a manual Label is set.

Auto Label allows you to automatically label a source with a specified format. Each disk automatically gets a Label when set as a Source, whether it's done manually or automatically through the Auto Source setting. Read more on how to use Labels .

It is possible to create custom elements like Location and Project. Read more on how to use custom elements .

Set the Transfer Queuing to Off, Single Source or Single Transfer
Create a new element
Remove an element by clicking the ⌄ down arrow button and choose "Remove"
Use elements in Auto Label, Rename Files and Create Folders

Clicking an also opens the Review pane.

Click the ⌃ up arrow button to open the Review panel

This feature requires an OffShoot Pro license. Upgrade via the , or via OffShoot > Settings > License. Check out all Pro features .

Create more powerful presets, with custom elements and settings, using the online .

(Beta - not available in OffShoot 23.2 or newer)

Read more about the iconik integration .

Cascading transfers are not yet.

The is incompatible with OffShoot. As of February 2025, Connect 2.0 will no longer work with Hedge 23.1.2 or older versions.

Click Go to Connect ✨, or go to in your web browser.

Once you log into , click Add + .

Once you log into , click the grey bell icon (i.e. the notification button).

Go to the

Android -

This feature requires an OffShoot Pro license. Upgrade via the , or via OffShoot > Settings > License. Check out all Pro features .

This feature requires an OffShoot Pro license. Upgrade via the , or via OffShoot > Settings > License. Check out all Pro features .

Choose an S3 provider from the list or .

On Mac, if you encounter an ‘Could not create S3 connection’ error, hover over the error message for more details. If you need further assistance, contact us at .

AWS S3 buckets with are supported in OffShoot 24.1 and newer.

It's possible to create a connection via the command line. .

To set an S3 bucket with the API, use the call with Bucket Name and Optional Path as the path parameter's value:

OffShoot logs any files or folders that couldn't be transferred in the .

Looking for a vendor-specific S3 implementation? Let us know:

OffShoot lets you add temporary labels to a Source to differentiate between multiple sources with the same disk or volume name.
If you want to use a transfer Preset:
mimiq@hedge.co
Duplicate Detective
Gemini
Duplicate Detect
here
here
License Manager
here
Preset Builder
here
Transfer Verification
the active Preset
Auto Label
Add Clip Review elements
multi-part// sets the multi-part size in MB; default = 64 (min 5 MB, max 5GB)
defaults write nl.syncfactory.Hedge.Mac "S3MultipartSize" -int <size in MB>

// sets the maximum amount of parts uploaded simultaneously; default = 10
defaults write nl.syncfactory.Hedge.Mac "S3MultipartConcurrencyLimit" -int <amount in parts>

// delete these keys if you want the reset to the default values
defaults delete nl.syncfactory.Hedge.Mac "S3MultipartSize"
defaults delete nl.syncfactory.Hedge.Mac "S3MultipartConcurrencyLimit"
Location - Computer\HKEY_CURRENT_USER\Software\Hedge
Key - CloudIntegrationConcurrency and CloudIntegrationPartSize
Type - DWORD (Hex)

CloudIntegrationConcurrency // maximum amount of parts uploaded simultaneously, default = 10
CloudIntegrationPartSize // multi-part size in bytes, default = 15728640 (min 5MiB, max 5GiB)
offshoot://setDestination?path=hedge-s3-test
[
  {
    "path" : "",
    "label" : "",
    "endpoint" : "https://s3.eu-central-1.amazonaws.com",
    "bucket_name" : "bucket-name",
    "accessKey" : "ACCESSKEY"
  }
]
defaults write nl.syncfactory.Hedge.Mac S3AwsConnections -string "$(cat /path/to/file.json)"
sudo security add-generic-password -a "ACCESSKEY" -s "https://s3.eu-central-1.amazonaws.com/bucket-name" -l "https://s3.eu-central-1.amazonaws.com" -w "secret-access-key" -T "/Applications/OffShoot.app"
defaults read nl.syncfactory.Hedge.Mac S3AwsConnections
defaults read nl.syncfactory.Hedge.Mac S3AwsConnections > `/path/to/jsonname.json`
Figure 1 Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
https://connect.hedge.video/connect.hedge.video
OffShoot for Mac 25.1 Beta 2
Hedge Connect app for iOS and Android
https://connect.hedge.video
the Connect site
the Connect site
Connect site
Use notifications to get alerts
License Manager
here
License Manager
here
offshoot@hedge.video
Transfer Acceleration
Learn more
offshoot@hedge.video
(ASC) MHL aware
Generic S3
network requirements
Hedge License Manager
hit Upgrade to Pro
locate your Mimiq Pro license key
confirm the number of available activations on your license
you can upgrade your license to Mimiq Pro
through the Hedge License Manager.
an (ASC) MHL file
Transfer Logs
Logo
Logo
Logo
Logo

Logging

Transfer Logs

For each transfer, OffShoot creates a Transfer Log with details about the transfer and transferred files. Transfer Logs are always saved locally and optionally also on the Destination.

You can access OffShoot's Transfer Logs via the menu: Window > Transfer Logs (or Command-L), or by going to this location in Finder:

~/Library/Application Support/Hedge/Transfer Logs

Transfer Logs can be accessed via the menu: Transfer Logs or (Control-L) , or by going to this location in Explorer:

C:\Users\(Your Username)\AppData\Roaming\Hedge\Transfer Logs

Force Underscores

OffShoot has a hidden feature that allows for forcing underscores in the file name of the logs:

Set using Terminal command:

defaults write nl.syncfactory.Hedge.Mac SFIDefaultsForceUnderscores "1"

Set via the Registry:

  • Location - Computer\HKEY_CURRENT_USER\Software\Hedge

  • Key - ForceUnderscrores

  • Type - String

  • Value - 1

Extra Log Location

OffShoot has a hidden feature that allows for setting a secondary transfer log location:

Set using Terminal command:

defaults write nl.syncfactory.Hedge.Mac SFIDefaultsExtraLogLocation "/path/of/your/choice"

Set via the Registry:

  • Location - Computer\HKEY_CURRENT_USER\Software\Hedge

  • Key - ExtraLogLocation

  • Type - String

  • Value - C:\the_path_you_choose

Media Hash Lists

When enabled, OffShoot creates a Media Hash List for each transfer (.mhl file) with the checksums (i.e. hashes) of all transferred files. The .mhl is included in the root of the folder that you transferred into.

Don't want Transfer Logs and Media Hash Lists on your destination? You can turn this feature off in Settings > Transfers > Paper Trail > Create Transfer Logs and (MHLs) on Destinations.

When OffShoot's Checkpoint feature detects a Media Hash List on your Source, it will use those checksums as a reference instead of doing an extra Source Verification source read.

ASC MHLs (Pro)

OffShoot Pro users can choose between creating legacy MHLs and ASC MHLs .

The Tranfer Log viewer

More information on media hash lists can be found on .

This feature requires an OffShoot Pro license. Upgrade via the , or via OffShoot > Settings > License. Check out all Pro features .

ASC MHL creation is only available when Checkpoint is ON and in Archive mode. More information on the ASC MHL standard can be found on website.

MHLs and ASC MHLs options
https://mediahashlist.org
License Manager
here
American Society of Cinematographers
setDestination
OffShoot for Windows 25.1
Logo
Logo