# Welcome 👋 Welcome to the documentation for all of Hedge's products. Can't find what you need? Or just plain stuck? Reach out, we're always happy to help: ## Office Hours You can [email](mailto:hello@hedge.video) 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. We don't guarantee a reply within 24 hours on working days, but it has rarely happened that we were unable to send a reply within a fraction of that time. 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 now 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. 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 :wink: Remember, support outside office hours is a courtesy, not a privilege. {% hint style="info" %} Live status of our online services: {% endhint %} # Arctic {% hint style="info" %} Before April 2024, Arctic was known as Final Cut Library Manager. [Read more...](https://blog.hedge.video/a-new-home-for-final-cut-library-manager) {% endhint %} 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 {% hint style="info" %} Your user must be able to `read` and `write` to a `Source`. {% endhint %} 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`. {% hint style="success" %} You can temporarily remove the scan results from a `Source` by unchecking it in the list. {% endhint %} ## 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. {% hint style="info" %} To remove the same category of data across multiple Events in a Library, click the multi-select checkbox under Arctic’s scan results. {% endhint %} 3. 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. {% hint style="success" %} 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). {% endhint %} ## 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. {% hint style="success" %} 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). {% endhint %} ## 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…`. # Requirements ## macOS macOS 11.x (Big Sur) and newer ## Final Cut Pro FCP 10.3.x and newer # Upgrades Final Cut Library Manager customers can receive a discounted upgrade for Arctic. If you didn't receive your upgrade coupon when Arctic was released, email us – [arctic@hedge.video](mailto:arctic@hedge.video?subject=Upgrade%20Discount%20for%20Arctic) – and we'll send you an upgrade discount. # Releases ## Arctic 26.1 Support for Final Cut Pro 12 {% tabs %} {% tab title="macOS" %} **Arctic 26.1** (Jan 20, 2026) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20260120060303_v26.1.0b66/Arctic_20260120060303_v26.1.0b66.dmg) * Support for Final Cut Pro 12 **Arctic 26.1.1** (Jul 9, 2026) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20260709162100_v26.1.1b71/Arctic_20260709162100_v26.1.1b71.dmg) * Support for Final Cut Pro 12.3 {% endtab %} {% endtabs %} ## Arctic 25.2 Support for Final Cut Pro 11.2 {% tabs %} {% tab title="macOS" %} **Arctic 25.2** (Sep 26, 2025) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20250926102928_v25.2.0b56/Arctic_20250926102928_v25.2.0b56.dmg) * Support for Final Cut Pro 11.2 * Fixes for some crashes already present in FCLM {% endtab %} {% endtabs %} ## Arctic 25.1 Send to PostLab! {% tabs %} {% tab title="macOS" %} **Arctic 25.1** (Apr 23, 2025) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20250403030623_v25.1.0b50/Arctic_20250403030623_v25.1.0b50.dmg) * Send to PostLab, from within Arctic {% endtab %} {% endtabs %} ## Arctic 24.3 Final Cut Pro 11 {% tabs %} {% tab title="macOS" %} **Arctic 24.3** (Nov 14, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20241110055239_v24.3.0b43/Arctic_20241110055239_v24.3.0b43.dmg) * Support for Final Cut Pro 11 :tada: * A spiffy new UI **Arctic 24.3.1** (Dec 19, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20241218003246_v24.3.1b45/Arctic_20241218003246_v24.3.1b45.dmg) * Improvements for migrating FCLM data * Fixes for some UI render issues * Fixes for some old crashes **Arctic 24.3.2** (Mar 28, 2025) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20250328004217_v24.3.2b47/Arctic_20250328004217_v24.3.2b47.dmg) * Support for Final Cut Pro 11.1 {% endtab %} {% endtabs %} ## Arctic 24.2 Final Cut Pro 10.8 & Importing from FCLM {% tabs %} {% tab title="macOS" %} **Arctic 24.2.3** (Aug 22, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240821090753_v24.2.3b33/Arctic_20240821090753_v24.2.3b33.dmg) * Improved migration flow from FCLM to Arctic * Fix for some background crashes lingering in FCLM's codebase **Arctic 24.2.2** (Jul 17, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240717024427_v24.2.2b30/Arctic_20240717024427_v24.2.2b30.dmg) * If FCLM data is found, Arctic now offers to copy it over. * It's now easier to add additional activations to your license. **Arctic 24.2.1** (Jul 3, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240702025314_v24.2.1b27/Arctic_20240702025314_v24.2.1b27.dmg) * 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. **Arctic 24.2** (Jun 21, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240621044501_v24.2.0b25/Arctic_20240621044501_v24.2.0b25.dmg) * Support for Final Cut Pro 10.8 {% endtab %} {% endtabs %} ## Arctic 24.1 {% tabs %} {% tab title="macOS" %} **Arctic 24.1.3** (May 22, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240521092113_v24.1.3b23/Arctic_20240521092113_v24.1.3b23.dmg) * 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 **Arctic 24.1.2** (May 7, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240502224923_v24.1.2b21/Arctic_20240502224923_v24.1.2b21.dmg) * Opening settings now remembers the last panel selected * Improved handling of offline usage * Improved activating directly from the license email **Arctic 24.1.1** (April 3, 2024) - [Download](https://updates.hedge.video/arctic/macos/updates/production/Arctic_20240403132247_v24.1.1b19/Arctic_20240403132247_v24.1.1b19.dmg) * Fix for a crash on Monterey (Thanks for reporting, Niek, Dave, Yarrow, Thomas, and Manuel!) **Arctic 24.1** (April 2, 2024) * First Arctic release 🎉 {% endtab %} {% endtabs %} ## Legacy Versions * [Final Cut Library Manager v3.98](https://hedge.video/download/arctic/legacy) (Dec 4, 2023) # Questions ## Why is there a hand icon over a Library? That Library is open and 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. {% hint style="success" %} Resetting Arctic’s database will not endanger your Final Cut Pro Libraries. {% endhint %} ## Why do I need to reindex Spotlight? If some Libraries are still missing from an Arctic scan, you may need to reindex Spotlight on your Mac. {% embed url="" %} ## How can I reset Arctic’s preferences? If all else fails, you can reset Arctic’s preferences using this command in `Terminal.app`: ```bash 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. If you can’t locate your license key for Arctic, you an look it up online in the [Hedge License Manager](/general/licenses/the-license-manager). ## 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? {% hint style="success" %} There is no need to remove Final Cut Library Manager before installing Arctic, you can keep both apps installed at any time. {% endhint %} 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. Download AppCleaner - 2. Drag-and-drop Final Cut Library Manager from `/Applications` to AppCleaner then click `Remove`. 3. In Finder, empty your Trash. If needed, you can also use these steps to uninstall Arctic. ## Need help? {% content-ref url="/pages/vqXGfqv332nfB3bWVh6j" %} [Need help?](/arctic/need-help) {% endcontent-ref %} # 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. Make sure you’ve installed [the latest Arctic release](https://hedge.video/download/arctic/macos), then activate it with your license key for Arctic. {% hint style="info" %} Can’t find your Arctic license key? You can find it in the [Hedge License Manager](/general/licenses/the-license-manager#locating-activation-numbers-license-keys). {% endhint %} ## Still stuck? Reach out to Support here – [arctic@hedge.video](mailto:arctic@hedge.video?body=Hello%20there%21%0D%0A%0D%0ACan%20you%20send%20us%20these%20details%20so%20we%20can%20investigate%3F%0D%0A%0D%0A-%20The%20version%20of%20macOS%20you%27re%20using%3A%20%0D%0A-%20The%20Arctic%20version%20you%20installed%3A%0D%0A-%20Screenshots%20%28or%20a%20screen%20recording%21%29%20of%20what%20you%27re%20experiencing%0D%0A-%20Some%20details%20on%20what%20led%20up%20to%20your%20experience%0D%0A%0D%0AThank%20you%21%0D%0A%0D%0A%E2%80%93%20The%20Hedge%20Team) – then send us these details: * 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: ``` zip ~/Desktop/Arctic.zip ~/Library/Application\ Support/Arctic -r ``` # 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:
{% embed url="" %} {% hint style="info" %} Troubleshooting LTO can be a pain, so please don't hesitate to use the in-app [Contact Support](/canister/need-help) option. {% endhint %} # Installation Canister supports both macOS and Windows, each with its setup instructions. * [Installing Canister on macOS](/canister/installation/installation) * [Installing Canister on Windows](/canister/installation/windows) # macOS ## Installers The latest installer for macOS is available here:\ ## 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 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 {% hint style="info" %} From Canister `26.1` a cross-vendor release of LTFS is shipped inside the installer. To run vendor LTFS instead use the documentation [here](https://docs.hedge.video/canister/faq#how-do-i-tell-canister-to-prefer-vendor-ltfs). {% endhint %} 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. {% tabs %} {% tab title="HBAs" %} (ATTO 6xx series, PCI-3)\ (ATTO 12xx series, PCI-3)\ (ATTO 12xx series, PCI-4)\ [https://hedge.video/external/canister/hba/arecaArcSAS](https://hedge.video/external/canister/hba/arecaM1) (Areca 1330 series)\ [https://hedge.video/external/canister/hba/arecaArcMSRu](https://hedge.video/external/canister/hba/areca1886-apple) (Areca 1686/1886 series) {% endtab %} {% tab title="macFUSE" %} (macOS 10.15 to macOS 15)\ (macOS 26) {% endtab %} {% tab title="LTFS" %} Vendor specific LTFS downloads: \ \ {% endtab %} {% tab title="ICU" %} Vendor specific ICU downloads: \ \ {% endtab %} {% endtabs %} ## Hardware {% hint style="info" %} A full list of compatible hardware is available [here](https://docs.hedge.video/canister/faq#which-lto-hardware-does-canister-support) {% endhint %} Each Thunderbolt-based LTO drive consists of 3 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 some may also use ATTO. * Old mTape units also house Areca cards (eg. ARC-1320). These tend to be incompatible with newer builds of LTFS. * Some brands use HighPoint "RocketStor" HBAs which are not recommended for use with LTO. * Older LSI HBAs are not compatible with Macs. These cards are also sold under HP's brand name. ### Symply 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 [SymplyATOM](https://support.gosymply.com/support/solutions/articles/80000979589-symplyatom-for-macos) tool to get started. ### OWC Other World Computing's Mercury Pro & Archive Pro solutions typically use ATTO HBAs. Refer to their documentation [here](https://eshop.macsales.com/support/owc-archive-pro) for guidance on which driver to install. ### 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 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 [Help Center](https://www.mlogic.com/apps/help-center). ### 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. {% hint style="danger" %} If your Mac is managed through MDM, stop now and contact your System Administrator.\ The following steps below will not apply when using MDM. {% endhint %} #### 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 [macOS](/canister/installation/installation#installing-the-hba-driver). {% hint style="info" %} 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. {% endhint %} 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`. ![](/files/iQpWVTttFHTixPFsVTRG) 5. Click `Security Policy...` ![Select the disk and click Security policy](/files/VIYqdNeq42huzbXa5emf) 6. Select `Reduced Security`, then enable:\ `Allow user management of kernel extensions from identified developers` . ![](/files/94ztFND4lKt7Er40H2IK) 7. Click `OK`. 8. In the menu bar, select `Shut Down`. 9. 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: {% tabs %} {% tab title="macOS 13 and newer" %} 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. {% endtab %} {% tab title="macOS 12" %} 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. {% endtab %} {% tab title="macOS 11 and older" %} 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`. {% endtab %} {% endtabs %} 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 the [#software](#software "mention") 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 Try installing macFUSE 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. #### Manually load the kernel extension {% hint style="info" %} Since most people use ATTO HBAs, we'll use those as an example. But you can use these steps with any kext. {% endhint %} 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: {% tabs %} {% tab title="macOS 11 and newer" %} `sudo /usr/bin/kmutil load -p /Library/Extensions/ATTOExpressSASHBA2.kext` {% endtab %} {% tab title="macOS 10.15.7 and older" %} `sudo kextload /Library/Extensions/ATTOExpressSASHBA2.kext` {% endtab %} {% endtabs %} 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. Once your Mac is fully powered down, [power up your Mac again in Recovery mode](https://support.apple.com/guide/mac-help/intro-to-macos-recovery-mchl46d531d6/mac). 4. Choose your system volume, log in with a macOS Administrator account, then launch Terminal. 5. 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)`.` 6. 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. Now you can approve [the HBA driver](#installing-the-hba-driver), [macFUSE](#macfuse), and any other existing system or kernel extensions to load 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: {% tabs %} {% tab title="macOS 13 and newer" %} 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. {% endtab %} {% tab title="macOS 12" %} 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. {% endtab %} {% tab title="macOS 11 and older" %} 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`. {% endtab %} {% endtabs %} #### Not getting that `Allow` button? Use this command in Terminal (all on one line): {% tabs %} {% tab title="macOS 11 and newer" %} `sudo /usr/bin/kmutil load -p /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext` {% endtab %} {% tab title="macOS 10.15.7 and older" %} `kextload /Library/Filesystems/macfuse.fs/Contents/Extensions/10.15/macfuse.kext` {% endtab %} {% endtabs %} Again, you'll need to enter your password, then open the Security & Privacy pane – it should show you the `Allow` button. ### Installing LTFS {% hint style="info" %} From Canister `26.1` a cross-vendor release of LTFS is bundled with the installer. That means you can skip this step altogether. {% endhint %} When an older release of Canister detects your LTO drive, it will deduce which vendor specific LTFS release 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 {% hint style="info" %} From `24.1` Catalog support is bundled with the Canister installer. This section is retained for legacy purposes, but no longer supported. {% endhint %} Up until `23.2`, Catalogs requires additional drivers. Preflight Checks will prompt you to install Apple's Command Line Tools ("CLT") first: ![Preflight Checks prompting to install Command Line Tools](/files/Iq9VeRVpJdfT5wh2Evwo) {% hint style="success" %} If CLT doesn't download (it happens, as Apple hosts it themselves), you can do so manually with this Terminal command: `xcode-select --install` {% endhint %} Then, continue with the Catalog install either by clicking "finish installation" or by downloading the Catalog installer from [here](https://hedge.video/external/canister/catalog). ![Finish Catalog installation](/files/kNxhJXKArEmkLuU6cYpb) #### 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): {% code overflow="wrap" lineNumbers="true" %} ``` PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec"; export PATH; m4 --version ``` {% endcode %} 4. 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. 5. 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`. 3. Locate the `canister-catalog-installer.log` file, and [email](mailto:canister@hedge.video) that to us. ## "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? 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 [Canister's Preflight Checks](#preflight-checks). We won't give up on you :thumbsup: # Windows ## Installers The latest installer for Windows is available here:\ ## 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. {% tabs %} {% tab title="HBAs" %} (6xx series, PCI-3)\ (12xx series, PCI-3)\ (12xx series, PCI-4) {% endtab %} {% tab title="Visual C++" %} {% endtab %} {% tab title="LTFS" %} {% endtab %} {% endtabs %} ## Hardware {% hint style="info" %} A full list of compatible hardware is available [here](https://docs.hedge.video/canister/faq#which-lto-hardware-does-canister-support). {% endhint %} 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 {% hint style="info" %} Pro Tip: Device Manager can be located by searching in the Windows `Start` menu. {% endhint %} 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. 1. Install [Microsoft Visual C++ 2015-2022 Runtime](https://hedge.video/external/canister/vcredist_x64_2015-2022) 2. Install [IBM LTFS for Windows 2.4.8.1](https://hedge.video/external/canister/ltfs/ibm/windows_2.4.8.1) ## "I give up" Can't get up and running? Running in circles? 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 [Canister's Preflight Checks](#preflight-checks). We won't give up on you :thumbsup: # 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.
LTOAdvertisedMaximumRealistic
1030 TB29.2 TB27.7 TB
918 TB17.5 TB16.7 TB
812 TB11.7 TB11.1 TB
76 TB5.73 TB5.4 TB
62.5 TB2.45 TB2.3 TB
51.5 TB1.43 TB1.4 TB
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%. {% hint style="warning" %} 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. {% endhint %} ## 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 {% hint style="info" %} Canister for Windows does not support NanoPure tape media. {% endhint %} From `23.2` onward, Canister for Mac supports [NanoPure](https://magstor.com/pages/nanopure) 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`. 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: | From | To LTO-8 | To LTO-9 | | ----- | -------- | -------- | | LTO-5 | 8 | 12 | | LTO-6 | 4 or 5 | 7 | | LTO-7 | 2 | 3 | # Features Canister has a lot of visible and invisible features. # 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 {% hint style="info" %} LTFS requires a tape to be unmounted before erasing a tape. If `Erase` is disabled, first eject the tape. {% endhint %} 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 {% hint style="info" %} This feature is not supported on Canister for Windows, yet. {% endhint %} 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 {% hint style="info" %} Canister for Windows does not support NanoPure tape media. {% endhint %} From `23.2` onward, Canister for Mac supports [NanoPure](https://magstor.com/pages/nanopure) 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`. In the event of a poor result you might consider retiring the tape, or contacting your hardware vendor for a thorough diagnostic check. # 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/Explorer 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. Collections can be further expanded by "Picking and Mixing" items in any order. Canister outputs the contents of each Collection to its [Console](/canister/features/logs-and-manifests#canisters-console).
## Duplicate Detection {% hint style="info" %} From `25.2` Canister for Windows can [verify](/offshoot/features/verification) duplicate items when Archiving. {% endhint %} 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. ## Independent Transfers Canister allows multiple LTO drives to be used independently of one another. That means `Drive A` can be Archiving, whilst `Drive B` handles a Retrieve. ## Simultaneous Transfers {% hint style="info" %} Preferably, use a faster-than-tape source for maximum write speeds to tape and [speed up verification](#verification). {% endhint %} 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 consecutive and part of the same folder are not actually stored in consecutive order on disk. When working with LTO, the goal is to line up and write files in consecutive order to prevent shoeshining 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 LTO drives offer built-in hardware compression. Compression is a property of a tape that is applied during the format process. Once set, it cannot be removed without 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 [Netflix-Compatibility](https://docs.hedge.video/canister/features/erasing#netflix-compatibility) option.
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. If your data is of a sensitive nature, Encrypted Sparse Bundles are a practical solution, providing the bundle isn't bigger than the uncompressed capacity of a single tape. # 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 {% tabs %} {% tab title="macOS" %} When Canister for Mac is presented with a source that won't fit on the mounted tape, it enters Spanning mode. You'll be prompted to set a Spanning Label, making it easy to locate your data later in the Catalog.
In turn, Canister will group the tapes for each Spanning part like this: ![](/files/EeJjMZSUMJcywWxVI5V6) From here, rinse and repeat for as many tapes as it takes to complete the Archive. {% endtab %} {% tab title="Windows" %} When Canister for Windows is presented with a source that won't fit on the mounted tape, it archives as much as will fit, then prompts you to load the next tape via the Windows Notification Center.
Enter the next tape and hit the format button to proceed. Rinse and repeat for as many tapes as it takes to complete the Archive. {% endtab %} {% endtabs %} ## 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 reenter the Spanning flow described above. {% hint style="info" %} **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 is grouped in the same Catalog. {% endhint %} ## 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 a source dataset that requires between 2-3 tapes. Why? Because Spanning requires Canister keeping the entire source index in memory, which is a heavy lift. Also, the chance of something going wrong on the hardware side increases exponentially the longer your LTO drive operates. As an upper limit we recommend Spanned Archives contain 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. With Spanning, the chance that a tape runs into an issue due to a hardware trouble 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 previously finished, then let Duplicate Detection skip items already existing on each part. #### Can I incrementally update a Spanned Archive? Although Canister supports Dupe Detection, due to LTO's linear nature, we don't recommend making 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. Tape compression can also play a part here, so it's best to disable at the point of formatting for the best results. #### 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. # 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. ![](/files/-MiQSd_kdON3MH0dpdVD) Hover over the drive to see the size of your selection:
When done, click `Next` then select a Destination:
Then add the Transfer...
When done, the progress bar turns green:
Open the accompanying Transfer Log if needed:
## Independent Transfers Canister allows multiple LTO drives to be used independently of one another. That means `Drive A` can be Archiving, whilst `Drive B` handles a Retrieve. ## Retrieve with Finder {% hint style="info" %} This feature requires macOS Big Sur or newer. {% endhint %} Canister for Mac makes it easy to retrieve files using Catalogs. First mount the relevant tape, then locate it the LTO Archive. Finally, select the file or folder you wish to retrieve, right-click and select the "Retrieve..." Finder extension.
## Retrieve with Full Path {% hint style="info" %} Retrieve with Full Path cannot be disabled in Canister for Windows. {% endhint %} 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`. # Queuing ## Setting up Queued Transfers Queuing makes it quick and easy to stack up multiple transfers of the same type to each tape. {% tabs %} {% tab title="macOS" %} {% hint style="info" %} Canister for Mac disables Spanning mode when there is a queue and vice versa, Queuing when there is an active Spanning transfer. {% endhint %} Canister for Mac uses a separate Transfer List for Queued Archives and Retrieves. To add a new transfer click the Transfer List "+" button in the bottom left hand corner of the window, then work through the steps to add each additional transfer. Rinse and repeat as many times as required. Canister will work its way through the each item in the queue until completion.
{% endtab %} {% tab title="Windows" %} {% hint style="info" %} Canister for Windows will seamlessly segue from processing Queued Transfers into Spanning mode. {% endhint %} Canister for Windows uses the same Transfer List for Queued Archives and Retrieves. To add transfers click either Archive or Retrieve, then work through the steps to add each additional transfer. Rinse and repeat as many times as required. Canister will work its way through the each item in the queue until completion.
{% endtab %} {% endtabs %} # Migrating {% hint style="info" %} Tape Migration requires a Pro License, and is currently only available on Windows. {% endhint %} Tape Migration allows you to safely migrate data from older-generation LTO tapes to newer-generation LTO tapes with a larger capacity. ## Setting up a Migrate Transfer 1. Mount both the source and destination tapes. 2. Choose the source tape. By default, the whole tape will be migrated. To transfer specific items, click Select Files from the hamburger menu. 3. Choose the destination tape. By default, Canister will migrate to the top level of the destination. You can select or create a new Destination Folder if required, using the hamburger menu. 4. Click `Migrate` to start the transfer.
## Read-ahead Cache By default, Canister will use the boot drive as read-ahead cache. This prevents the slower source LTO drive from stalling the faster destination LTO drive, also known as Shoe-shining. For this reason, we strongly recommend using a solid-state boot drive. Ideally, your boot drive will have more free space than the largest file on your source tape. Files that are too large for the read-ahead cache will be skipped and clearly mentioned in the Transfer Log. This situation can be easily resolved by connecting a larger cache device, then rerunning the Migrate job which leans on Canister's Duplicate Detection engine to skip items already on the destination. ## Cache Location Canister's read-ahead cache Location can be specified using the Windows Registry switch below. For the best results, we recommend using a good-quality SSD connected over USB-C or Thunderbolt. {% tabs %} {% tab title="Windows" %} To change the Migrate Cache location:
1. Open Registry Editor. 2. Locate Canister here: `Computer\HKEY_CURRENT_USER\Software\Canister` 3. Right-click to create a new String Value called `AlternativeBufferCacheLocation` 4. Define the full path, including the drive letter. 5. Restart Canister. {% endtab %} {% endtabs %} # Catalogs Each time a tape is mounted, Canister will create a Catalog of its contents. This makes it easy to find what's on a tape without having to mount it first. ## The LTO Archive volume 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 to install it. You can also [download the installer](https://downloads.hedge.video/canister/catalog/Canister%20Catalog.pkg) directly from our servers. {% hint style="info" %} Don't see the LTO Archive volume? Check if your user has administrator permissions. {% endhint %} ## Creating Catalogs Canister automatically creates a Catalog the first time it mounts each tape and updates existing Catalogs on subsequent mounting of the tape. Also, after each Archive transfer, the Catalog for that tape is updated automatically. ## Finding files using Catalogs {% tabs %} {% tab title="macOS" %} 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": ![](/files/jpdyQycmHeDjW2vGFlwe) {% endtab %} {% tab title="Windows" %} On Windows, Catalogs can be accessed by clicking the Catalog button pictured below.
The Storage Browser will open. It provides a useful overview of all tapes in the Catalog. Folders can be expanded by clicking the `>` button.
{% endtab %} {% endtabs %} ## 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. ![](/files/RR4DCurnbIUNEOT2imHe) ## Catalog History Canister creates a Catalog when mounting a tape and updates it after each Archive. Catalog history is stored for safekeeping as described below. {% tabs %} {% tab title="macOS" %} Old Catalogs are moved into a *hidden* folder named `Tapename (serial).history`, essentially archiving them. {% hint style="info" %} To see previous generations of your Catalogs, enable Show Hidden Files in Finder with the shortcut `Shift-Command-.` {% endhint %} {% endtab %} {% tab title="Windows" %} 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` {% endtab %} {% endtabs %} ## Editing and removing Catalogs Use the steps below to clean up the Catalog, or remove test entries: {% tabs %} {% tab title="macOS" %} 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. {% endtab %} {% tab title="Windows" %} Navigate to`/Users/Username/AppData/Roaming/Canister/Catalogs` using Explorer, then either delete the folder representing tape you wish to remove. {% endtab %} {% endtabs %} ## Changing the Catalog location {% tabs %} {% tab title="macOS" %} 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` {% hint style="info" %} Pro-tip: don't type the folder path, but drag the folder you want as location for Catalogs from Finder into the Terminal. {% endhint %} **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. {% endtab %} {% tab title="Windows" %} 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. {% endtab %} {% endtabs %} ## Migrating to a new system In the event you need to move to a new computer, Catalogs can be moved as follows: {% tabs %} {% tab title="Mac" %} 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: ``` tar -cvzf ~/Desktop/catalogs.tar.gz ~/Library/Application\ Support/Canister/Catalogs ``` You can copy this archive to a new machine, then unpack it with a free app like [Unarchiver](https://apps.apple.com/us/app/the-unarchiver/id425424353?mt=12). {% endtab %} {% tab title="Windows" %} 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. {% endtab %} {% endtabs %} ## Converting with NeoFinder NeoFinder for Mac offers integrations between many other LTO-focused apps (eg. YoYotta, PreRoll Post) and Canister, making it a breeze to convert your old databases to Catalogs. For more information, refer to NeoFinder's [documentation](https://www.cdfinder.de/guide/10/10.2/hedge_canister_export.html). ## Importing StorageDNA Catalogs Users with StorageDNA LTFS Catalogs can use [this script](https://downloads.hedge.video/canister/scripts/migrate_sdna_to_canister.sh) to convert them into Canister Catalogs. {% hint style="info" %} This script requires the `fileicon` utility to be installed first, via [brew](https://brew.sh/). {% endhint %} 1. Zip the `archive.xml` and `catalog.tgz` files representing each of your SDNA Catalogs, then place the resulting zip file into a folder named after the Catalog. 2. Place the converter script on the same level as the folders containing your zip files, e.g.,
3. Run the script in `Terminal.app`:\ `./migrate_sdna_to_canister.sh` 4. Copy the newly created Canister Catalogs stubs from the `_processed` directory to\ `~/Library/Application Support/Canister/Catalogs` # Library Manager {% hint style="info" %} Library Manager requires a Pro License, and is currently only available on macOS. {% endhint %} From Canister for Mac `24.2`, it's possible to manage library inventory without leaving the Canister interface. The Library Manager is accessed via the hamburger menu:
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 Library Manager shows mail slots alongside regular tape slots. ## Hardware Support {% hint style="info" %} Canister doesn't currently support multi-drive tape libraries. {% endhint %} Library Manager is validated for use with the following models: * [Magstor M2000](https://magstor.com/collections/m2000-tape-libraries) * [Qualstar Q24](https://www.qualstar.com/q24-tape-library) * 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 specific tape library model also works. HPE tape libraries are not (yet) supported. # 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. {% tabs %} {% tab title="macOS" %} Transfer Logs are accessible through the Transfer Log viewer (Command-L) or directly in Finder: `~/Library/Application Support/Canister/Transfer Logs` {% endtab %} {% tab title="Windows" %} Transfer Logs are accessible via the Canister menu or in Explorer: `/Users/Username/AppData/Roaming/Canister/Logs/Transfer Logs` {% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} To access the Console on macOS, use `Shift-Command-C`. Text is selectable, and also searchable (Command-F). ![](/files/y1KhZlmKuMWFUPXR9AGQ) {% endtab %} {% tab title="Windows" %} To view the Session Log in real time, click the Canister menu -> `Log Viewer`.
{% endtab %} {% endtabs %} # Connect Get a live overview of Canister transfers in progress – plus receive push notifications on completed transfers, wherever you are. ## How to use 1. Go to `Settings` > `Connect`. 2. Toggle `Enable Connect` to `ON`. 3. Copy the `Connect Code` by clicking the clipboard icon. 4. Click `Go to Connect ✨`, or go to in your web browser. {% tabs %} {% tab title="macOS" %}
{% endtab %} {% tab title="Windows" %}
{% endtab %} {% endtabs %} 5. Enter the `Connect Code` into the Connect site. 6. 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. Once you log into [the Connect site](https://connect3.hedge.video), click the grey bell icon (i.e. the notification button). 2. Click `Allow` in the notifications popup on your device. 3. 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. Go to the [Connect site](https://connect3.hedge.video) 2. 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`. 3. Open the web app and click the notification bell icon. 4. Enable Notifications for this website when prompted. * Android - [Use notifications to get alerts](https://support.google.com/chrome/answer/3220216?hl=en\&co=GENIE.Platform%3DAndroid)
{% hint style="warning" %} If the notification button is disabled, your browser does not support notifications, or notifications are disabled. {% endhint %} ## 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. ## Connect Pro {% hint style="info" %} This feature requires a Canister Pro license. Upgrade via the [License Manager](https://account.hedge.video/), or via Canister > Settings > License. {% endhint %} Connect Pro allows your team to log in to the Connect site using the registered Canister email address. This allows multiple team members to follow the progress of each active LTO transfer, on each computer that's using your Canister license. # Deployment Canister supports deployment URL calls, helping administrators manage installations at scale. ## How it works Canister responds to URLs beginning with `canister://`. These can be triggered from a browser, a shell, an MDM, or a script. **Using a browser** Paste the URL call below into a web browser, press `Enter`, and Canister will open. ``` canister://open ``` **Using a shell** Paste the command below into a shell, press `Enter`, and Canister will open. {% tabs %} {% tab title="Mac" %} Using a Terminal: ``` open "canister://open" ``` {% endtab %} {% tab title="Windows" %} Using PowerShell: ``` start canister://open ``` {% endtab %} {% endtabs %} ## Calls The following calls are intended for deployment and administration purposes: #### Open Launches Canister: ``` canister://open ``` #### Quit Closes Canister: ``` canister://quit ``` #### Restart Restarts Canister: ``` canister://restart ``` #### Check for updates Triggers an update check: ``` canister://update ``` #### Activate Activates Canister using your license key: ``` canister://activate?key=xxxx-xxxx-xxxx-xxxx ``` | URL Parameter | Type | Required? | | ------------- | ------ | --------- | | key | string | mandatory | #### Deactivate Deactivate Canister: ``` canister://deactivate ``` # Automation Automate transfers and fetch information about mounted tapes using Canister's API. ## How it works The Canister API responds to URLs beginning with `canister://`. These can be triggered from a browser, shell, or script. [Deployment calls](https://docs.hedge.video/canister/features/deployment) can be included in your automated workflows. \ **Example script usage** {% tabs %} {% tab title="Mac" %} From the Terminal: ``` open "canister://open" ``` {% endtab %} {% tab title="Windows" %} Using Python: ``` import os os.system("start canister://open") ``` {% endtab %} {% endtabs %} #### Add Archive Archive a source to all mounted tapes: {% tabs %} {% tab title="Mac" %} ``` canister://addarchive?sources=/Volumes/X9 SSD/Important Footage ``` {% endtab %} {% tab title="Windows" %} ``` canister://addarchive?sources="E:\Important footage" ``` {% endtab %} {% endtabs %} The parameters below are supported: | URL Parameter | Type | Required? | | ----------------- | ------ | --------- | | sources | String | Mandatory | | destinationtape | String | optional | | destinationfolder | String | optional | A Collection of different sources, files, or folders can be combined using the `|` (pipe) operator. {% tabs %} {% tab title="Mac" %} {% code overflow="wrap" %} ``` canister://addarchive?sources=/Volumes/X9 SSD/Important Footage 1|/Volumes/X9 SSD/Important Footage 2 ``` {% endcode %} {% endtab %} {% tab title="Windows" %} {% code overflow="wrap" %} ``` canister://addarchive?sources="E:\Important footage 1"|"F:\Important footage 2" ``` {% endcode %} {% endtab %} {% endtabs %} Putting it together: {% tabs %} {% tab title="Mac" %} {% code overflow="wrap" %} ``` canister://addarchive?sources=/Volumes/X9 SSD/Important Footage&destinationtape=Archive 01&destinationfolder=260304 ``` {% endcode %} {% endtab %} {% tab title="Windows" %} {% code overflow="wrap" %} ``` canister://addarchive?sources="E:\Important footage 1"&destinationtape="Archive 01"&destinationfolder="260304" ``` {% endcode %} {% endtab %} {% endtabs %} #### Add Retrieve Retrieve folders or files from tape: {% tabs %} {% tab title="Mac" %} {% code overflow="wrap" %} ``` canister://addretrieve?sources=260304/Important Footage 1&sourcetape=Archive 01&destinationpath=/Volumes/X9 SSD/Retrieved Footage ``` {% endcode %} {% endtab %} {% tab title="Windows" %} {% code overflow="wrap" %} ``` canister://addretrieve?sources="260304\Important footage 1"&sourcetape="Archive 01"&destinationpath="E:\Retrieved Footage" ``` {% endcode %} {% endtab %} {% endtabs %} The parameters below are supported: | URL Parameter | Type | Required? | | --------------- | ------ | --------- | | sources | string | mandatory | | sourcetape | string | mandatory | | destinationpath | string | mandatory | #### Get Tapes Generate a JSON list of mounted tapes using `gettapes`. {% tabs %} {% tab title="Mac" %} \ On Mac a path and filename must be supplied to the `gettapes` call. {% code overflow="wrap" %} ``` canister://gettapes?path=/Users/Username/Desktop/gettapes.json ``` {% endcode %} | URL Parameter | Type | Required? | | ------------- | ------ | ------------------------- | | path | String | mandatory (inc. filename) | | {% endtab %} | | | {% tab title="Windows" %} \ On Windows the path can be omitted from the `gettapes` call. This will dump a `tapes.json` file to the Canister `AppData` folder. A filename should not be supplied for the output. {% code overflow="wrap" %} ``` canister://gettapes?path="c:\path\to\scripts" ``` {% endcode %} | URL Parameter | Type | Required? | | ------------- | ------ | --------- | | path | String | optional | | {% endtab %} | | | | {% endtabs %} | | | Sample output: {% tabs %} {% tab title="Mac" %} ```json [ { "name" : "Archive 01", "serial" : "19WT134678", "mountPath" : "/Users/LTO Mac/Library/Application Support/Canister/.MountIndexData/146498582", "status" : "Mounted", "totalCapacityBytes" : 5732142415872, "freeBytes" : 3994656406 } ] ``` {% endtab %} {% tab title="Windows" %} ```json [ { "name" : "Archive 01", "serial" : "19WT134678", "driveLetter" : "Z", "status" : "READY", "totalCapacityBytes" : 2408088338432, "freeBytes" : 2408085192704 } ] ``` {% endtab %} {% endtabs %} # Standard vs. Pro Canister has two license types: Standard and Pro.
FeatureStandardPro
Preflight Checks✓✓
Archive✓✓
Retrieve✓✓
Simultaneous Transfers✓✓
Spanning✓✓
Queuing✓✓
Migration-available on Windows
Catalogs✓✓
Logs & Manifests✓✓
Tape Library Manager-available on macOS
NanoPure Supportavailable on macOSavailable on macOS
Connect✓✓
Connect Pro-✓
Deployment✓✓
Automation-available on Windows
Offline Activation-available on Windows
Priority Support-✓
# 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. 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 [License Manager](https://account.hedge.video). ## How do I add Windows Support to my License? Windows support can be added by simply Extending your existing Canister license in the [License Manager](https://account.hedge.video). ## 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 currently limited to macOS. ## My license key won't activate the latest Canister 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. [Contact us ](mailto:canister@hedge.video)for an upgrade coupon or continue to use the now-legacy Canister [20.1](https://hedge.video/download/canister/legacy). ## Can I activate Canister Offline? Yes, since Canister for Windows 25.4, users with a Pro License eligible for support can request an offline activation file. # Firmware Besides requiring drivers, LTO drives themselves rely on firmware. As a LTO drive is basically a computer, consider the firmware to be its operating system. This firmware is just as much under active development as are the drivers, and should not be ignored when troubleshooting. When you run into an issue, but all drivers are installed correctly, make sure your firmware is up to date. ## 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.
## Downloading LTO firmware LTO firmware is specific to each LTO vendor. Below you'll find links for IBM and Quantum firmware downloads. Users with HP and Tandberg drives are advised to contact their drive vendor for assistance. Brands such as Symply, Magstor, OWC and mLogic generally use stock IBM LTO drives inside their products, but not always, so be sure to check Preflight Checks. Once you have downloaded the latest firmware, the next step is to install IBM Tape Diagnostic Tools ("ITDT"), then perform the update. {% tabs %} {% tab title="IBM" %} Official IBM LTO firmwares can be obtained from [Fix Central](https://www.ibm.com/support/fixcentral), which requires an account. For convenience, you can find the same downloads here on the [Qualstar firmware index](https://www.qualstar.com/drivers-directories/tape-drive-firmware). Both [Symply](https://support.gosymply.com/support/solutions/articles/80001035913-lto-firmware-downloads) and [Magstor](https://support.magstor.com/portal/en/kb/articles/lto-firmware) each maintain a handy list of IBM firmware downloads for their customers. {% endtab %} {% tab title="Quantum" %} Quantum drive firmwares can be obtained the firmware index [here](https://www.quantum.com/en/service-support/downloads-and-firmware/lto-std/). Although IBM firmwares will technically run on a Quantum drive, for warranty/support reasons we recommend using the latest version recommended by Quantum who are often slower to qualify updates. {% endtab %} {% tab title="HP" %} HP LTO drives, aka. HPE or Hewlett Packard Enterprise, are a bit of a mixed bag. While their older drives were manufactured in house, later units come direct from the IBM factory. In all cases, HP LTO drives require special vendor-locked firmwares, which are only available with an active HP support contract. If your drive is new and you think it requires a firmware update, try speaking to your vendor as a next step. To add to the headache, HP also use a custom update utility known as HP LTT ([Library & Tape Tools](https://support.hpe.com/connect/s/softwaredetails?language=en_US\&collectionId=MTX-6d5d29b8407d4250\&tab=releaseNotes)), which means ITDT won't work. HP LTT runs on Windows or Linux, only. {% endtab %} {% tab title="Tandberg" %} Most Tandberg drives were rebadged HP/HPE units, so the same rules apply. {% endtab %} {% endtabs %} ## Installing ITDT Use the steps below to install and run ITDT, aka. IBM Tape Diagnostic Tools: {% tabs %} {% tab title="macOS" %} ITDT can be downloaded [here](https://downloads.hedge.video/canister/firmware/itdt/install_itdt_macos.zip). Since installation is a bit fiddly, we've put a script together that drops ITDT into your home directory:
1. Open Applications > Utilities > `Terminal.app` 2. Copy, then paste the following prompt, then hit enter to install ITDT:\ `curl -fsSL "https://downloads.hedge.video/canister/scripts/itdt_install.sh" | bash` 3. Run ITDT using:\ `~/ITDT/itdt` 4. Accept the ITDT license agreement by typing `L`, `[Enter]`, then `I` and again `[Enter]`. ITDT is now set up. {% endtab %} {% tab title="Windows" %} 1. Download IBM's `ITDT` tool for Windows:\ 2. Double Click `install_itdt_windows` to run extract the installer. This will extract ITDT in the same location as your downloads. 3. Hit `[Enter]` to complete close the extraction utility. 4. Open the `ITDT` directory, then right click the `itdt` executable and choose `Run as administrator`. 5. Click `Yes` to the `User Access Control` prompt. 6. Accept the ITDT license agreement by typing `L`, `[Enter]`, then `I` and again `[Enter]`. ITDT is now set up. {% endtab %} {% endtabs %} ## Updating the firmware Next, the firmware itself: 1\. Download the [latest firmware](#downloading-lto-firmware) for your drive. {% hint style="success" %} 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. {% endhint %} 2\. Move the firmware package (a `.fmrz` file) into the `input` directory inside `ITDT` install location. {% tabs %} {% tab title="Mac" %} On macOS, the default location is `~/ITDT/input/`. Not sure how to get to that folder? In Finder, hit `Shift-Command-H` and enter the above path. {% endtab %} {% tab title="Windows" %} 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/`. {% endtab %} {% endtabs %} {% hint style="danger" %} Next, quit ALL apps you use for LTO purposes, and unmount any tapes. {% endhint %} 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*. {% hint style="info" %} 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 IDs in `System Information` > `SAS`. In this example screenshot, the device ID is `0:` {% endhint %} ![SCSI Device ID is 0](/files/lqt65TCqJNM5sk8m6JgZ) * `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. # Releases {% hint style="info" %} 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. If that resolves the problem, [extend](https://account.hedge.video/) your license. {% endhint %} ## Canister 26.1 Mix and match LTO vendors on Mac, plus an API to automate LTO transfers from scripts, apps, or pipelines. {% tabs %} {% tab title="Mac" %} **Canister 26.1** (June 16th, 2026) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20260617102202_v26.1b1175/Canister_20260617102202_v26.1b1175.dmg) **New ✨** * LTFS `2.4.8.2`: mix and match IBM, HP, and Quantum drives * IBM LTO-10 support! * Deployment API to help admins roll out Canister at scale * `Pro` Set up LTO transfers and fetch tape info using Canister's API **Improved** * Destination checksum failures are now listed in the Failed Items section of each Transfer Log **Fixed** * The Finder Extension works once again (Thanks, Christiaan!) **Canister 26.1.1** (June 18th, 2026) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20260618150218_v26.1.1b1177/Canister_20260618150218_v26.1.1b1177.dmg) * Fixes an edge case that could cause the installer to hang (Thanks, John!) {% endtab %} {% tab title="Windows" %} **Canister 26.1** (March 16th, 2026) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-26.1.0.228.exe) **New ✨** * Deployment API to help admins roll out Canister at scale * `Pro` Set up LTO transfers and fetch tape info using Canister's API \ **Canister 26.1.1** (April 28th, 2026) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-26.1.1.230.exe) * Improved offline support for Preflight Checks when using too-new dependencies (Thanks, Simon) * Improved logging when LTFS drops the tape to read-only and a transfer fails as a result (Thanks, Vincent) **Canister 26.1.2** (July 24th, 2026) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-26.1.2.234.exe) * The `addtransfer` API call can now be used while indexing * Transfer buffer tweaks to ensure efficient tape usage **Canister 26.1.3** (July 27th, 2026) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-26.1.3.235.exe) * A small tweak to ensure the installer runs smoothly on all systems {% endtab %} {% endtabs %} ## Canister 25.4 Introducing Canister Pro for Windows, including Tape Migration, and more. {% tabs %} {% tab title="Windows" %} **Canister 25.4** (December 17th, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.4.0.209.exe) **New ✨** * Introducing Canister Pro for Windows * `Pro` Tape-to-Tape Migration * `Pro` Support for Offline Activation and Project Licenses * A lick of paint to keep things super-fresh 🧼 **Improved** * The Console Log viewer is much smoother to scroll * Canister won't let the system go to sleep during a transfer * Session Logs have been tidied up **Canister 25.4.1** (December 19th, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.4.1.210.exe) * Fixed a bug that stopped Canister from launching when used offline **Canister 25.4.2** (March 10th, 2026) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.4.2.225.exe) * Improved support for LTO-10 drive detection (Thanks, Zhe) * Failing transfers due to hardware errors have improved logging {% endtab %} {% endtabs %} ## Canister 25.3 Support for LTFS 2.4.8.1 and LTO-10 on Windows. {% tabs %} {% tab title="Windows" %} **Canister 25.3** (October 8th, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.3.0.190.exe) **New ✨** * Support for LTFS 2.4.8.1 and LTO-10 on Windows **Canister 25.3.1** (October 29, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.3.1.196.exe) * Fix for partial progress bars caused by files gone missing from the source * Dot underscore files are now skipped * Connect now shows the correct tape names for all spanning parts * Transfers will gracefully fail if a Win32 error code "31" is encountered * Transfer Logs are even generated if a LTO drive goes MIA **Canister 25.3.2** (November 10, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.3.2.198.exe) * Fix for Canister not finding its license when disconnected from the internet (Thanks, James!) {% endtab %} {% endtabs %} ## Canister 25.2 Canister for Windows gets support for verifying duplicate items, a huge time saver when something goes wrong with your LTO drive. Canister for Mac gets support for macOS 26 Tahoe. {% tabs %} {% tab title="macOS" %} **Canister 25.2** (September 15th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250910095125_v25.2b1109/Canister_20250910095125_v25.2b1109.dmg) **New ✨** * Support for macOS 26 Tahoe
**Canister 25.2.1** (November 11th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20251111143759_v25.2.1b1120/Canister_20251111143759_v25.2.1b1120.dmg) * Fix for an intermittent indexing bug that stopped Archiving from starting ("unknown error 1002") * Fix for unnecessary tape unloads while the queue is being processed * No more endless spinning if loading a tape, without one being present
**Canister 25.2.2** (December 23rd, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20251222113246_v25.2.2b1124/Canister_20251222113246_v25.2.2b1124.dmg) * Long item names are neaty truncated so they don't overlap the ETA * Throw a handy alert when a tape needs Deep Recovery * Holding option to show free space works again in Retrieve mode * Console now logs additional information when Spanning * By default LTFS now mounts with a 600 second macFUSE daemon timeout {% endtab %} {% tab title="Windows" %} **Canister 25.2** (May 27th, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.2.0.170.exe) **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 {% endtab %} {% endtabs %} ## Canister 25.1 Queuing and Independent Transfers for both platforms, and Spanning is now available on Windows as well. {% tabs %} {% tab title="macOS" %} **Canister 25.1** (July 22nd, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250714143825_v25.1b1098/Canister_20250714143825_v25.1b1098.dmg)\ \ **New ✨** * Queuing: stack multiple transfers of the same type * Independent Transfers: Use each tape device independently of one another * Support for Project Licenses **Improved** * As usual, lots of small improvements behind the scenes that you can't see **Canister 25.1.1** (July 23rd, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250723114949_v25.1.1b1100/Canister_20250723114949_v25.1.1b1100.dmg) * Fix for an annoying crash when entering the Connect panel in Settings * Small UI tweaks to the activation form that requests your details **Canister 25.1.2** (July 30th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250729161547_v25.1.2b1102/Canister_20250729161547_v25.1.2b1102.dmg) * Fix for activation error "15" after a clean install of macOS and Canister **Canister 25.1.3** (August 7th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250806103600_v25.1.3b1105/Canister_20250806103600_v25.1.3b1105.dmg) * Fix for potential intermittent crashes during Verification **Canister 25.1.4** (September 5, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250905093816_v25.1.4b1106/Canister_20250905093816_v25.1.4b1106.dmg) * Adds compatibility alert for users attempting to do an early upgrade to macOS 26 Tahoe {% endtab %} {% tab title="Windows" %} **Canister 25.1** (February 11th, 2025) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-25.1.0.143.exe) **New ✨** * Queuing: stack multiple transfers of the same type * Independent Transfers: Use each tape device independently of one another * Spanning: seamlessly Archive over multiple tapes **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 {% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} **Canister 24.2.7** (June 17th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250617092328_v24.2.7b1089/Canister_20250617092328_v24.2.7b1089.dmg)
* Minor tweak to improve unmount handling * Tape Libraries can be disabled with a user default * Checksum values are no longer available for transfers done in Trial mode * Hotfix for memory usage problem in initial release (Thanks, Christoph 🙏)
**Canister 24.2.6** (February 7th, 2025) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20250207113428_v24.2.6b1060/Canister_20250207113428_v24.2.6b1060.dmg) * Fixes a pesky crash during tape indexing and transfer (Thanks, Marty & Tayfun) **Canister 24.2.5** (December 11th, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20241210203835_v24.2.5b1056/Canister_20241210203835_v24.2.5b1056.dmg) * 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 **Canister 24.2.4** (November 26th, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20241126095206_v24.2.4b1052/Canister_20241126095206_v24.2.4b1052.dmg) * 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
**Canister 24.2.3** (October 31st, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20241031122202_v24.2.3b1042/Canister_20241031122202_v24.2.3b1042.dmg) * 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
**Canister 24.2.2** (July 25th, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240725101129_v24.2.2b1018/Canister_20240725101129_v24.2.2b1018.dmg) * 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 **Canister 24.2.1** (July 4th, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240703124648_v24.2.1b1009/Canister_20240703124648_v24.2.1b1009.dmg) * 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 **Canister 24.2** (May 21st, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240527131109_v24.2b978/Canister_20240527131109_v24.2b978.dmg) * 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 {% endtab %} {% tab title="Windows" %} **Canister 24.2.2** (December 10th, 2024) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-24.2.2.114.exe) * Minor tweaks to the Catalog Storage Browser
**Canister 24.2.1** (June 11th, 2024) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-24.2.1.86.exe) * Fix for Canister returning to Preflight Checks screen after 24 hours **Canister 24.2** (May 21st, 2024) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-24.2.0.85.exe) * 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 {% endtab %} {% endtabs %} ## Canister 24.1 Pick & Mix Collections, Ethernet LTO drive support, plus a swathe of updates for Windows. {% tabs %} {% tab title="macOS" %} **Canister 24.1.2** (February 28th, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240223051417_v24.1.2b907/Canister_20240223051417_v24.1.2b907.dmg) * Fix for multiple compression state messages in the Console * Additional tweaks to keep Connect running smooth
**Canister 24.1.1** (January 31, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240127043239_v24.1.1b873/Canister_20240127043239_v24.1.1b873.dmg) * Fix a rare bug causing some HP drives to not show the mount button * Catalog searches now work for everybody once again 🙂 **Canister 24.1** (January 9, 2024) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20240104200230_v24.1b868/Canister_20240104200230_v24.1b868.dmg) * 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 {% endtab %} {% tab title="Windows" %} **Canister 24.1.1** (March 14, 2024) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-24.1.1.75.exe) * 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! **Canister 24.1** (January 9, 2024) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-24.1.0.61.exe) * 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 {% endtab %} {% endtabs %} ## **Canister 23.2** Support for Windows, Connect and NanoPure media. {% tabs %} {% tab title="macOS" %} **Canister 23.2.2** (November 8, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20231107193328_v23.2.2b848/Canister_20231107193328_v23.2.2b848.dmg) * 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 **Canister 23.2.1** (October 26, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20231026111245_v23.2.1b833/Canister_20231026111245_v23.2.1b833.dmg) * Connect improvements to keep things running smooth * Log LTO compression state when loading a tape **Canister 23.2** (October 10, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20231008175422_v23.2b812/Canister_20231008175422_v23.2b812.dmg) * Monitor LTO transfers from anywhere with Connect 🙌 * Support for MagStor's NanoPure range of premium LTO media {% endtab %} {% tab title="Windows" %} **Canister 23.2.1** (November 7, 2023) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-23.2.1.49.exe) * 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 💅
**Canister 23.2** (October 10, 2023) - [Download](https://updates.hedge.video/canister/windows/updates/CanisterSetup-23.2.0.43.exe) * First release of Canister for Windows ✨ * Support for IBM based LTO drives * Archive, Retrieve, Catalogs, Dupe Detect, Logs, Connect & more! {% endtab %} {% endtabs %} ## **Canister 23.1** Collections for Canister, and more. {% tabs %} {% tab title="macOS" %} **Canister 23.1.8** (October 06, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20231006111556_v23.1.8b805/Canister_20231006111556_v23.1.8b805.dmg) * 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 **Canister 23.1.7** (September 27, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/production/Canister_20230927093651_v23.1.7b793/Canister_20230927093651_v23.1.7b793.dmg) * 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 🙏) **Canister 23.1.6** (July 7, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-724.dmg) * 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 \ \ **Canister 23.1.5** (June 21, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-705.dmg) * 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! **Canister 23.1.4** (Apr 7, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-622.dmg) * Fix for a rare edge case that would prevent Canister from starting (Thanks, Arturo 🙏) **Canister 23.1.3** (Mar 16, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-599.dmg) * 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 🙏) **Canister 23.1.2** (Mar 3, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-594.dmg) * 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 **Canister 23.1.1** (Feb 22, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-582.dmg) * 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 **Canister 23.1** (Jan 25, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-539.dmg) * 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 {% endtab %} {% endtabs %} ## **Canister 22.3** A "Retrieve with Finder" extension, support for Ventura, and more... {% tabs %} {% tab title="macOS" %} **Canister 22.3.5** (Jan 13, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-529.dmg) * 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. **Canister 22.3.4** (Jan 4, 2023) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-513.dmg) * Fix for Cataloging not always finishing up properly * Console improvements that allow us to do even better customer support 🙂 **Canister 22.3.3** (Dec 29, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-506.dmg) * Fix for HPE drive detection * Workaround for stalling indexes **Canister 22.3.2** (Dec 14, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-492.dmg) * 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. **Canister 22.3.1** (Nov 15, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-455.dmg) * 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. **Canister 22.3** (Oct 18, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-411.dmg) * 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. {% endtab %} {% endtabs %} ## **Canister 22.2** Official support for MagStor drives, and more. {% tabs %} {% tab title="macOS" %} **Canister 22.2.11** (Sep 19, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-397.dmg) * 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. **Canister 22.2.10** (Aug 10, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-385.dmg) * Fixes an issue where Canister could not always fetch the LTO drive vendor. **Canister 22.2.9** (Aug 09, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-383.dmg) * Improved handling of HBAs that don't work well with LTFS. **Canister 22.2.8** (July 27, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-377.dmg) * Improved error handling for troublesome tapes. * For test purposes, skip all Preflight Checks using the cheatcode *idkfa* **Canister 22.2.7** (July 15, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-364.dmg) * 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. **Canister 22.2.6** (June 28, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-349.dmg) * 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. **Canister 22.2.5** (June 22, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-344.dmg) * Fixed a crash that sometimes occurs after checksum creation. **Canister 22.2.4** (May 24, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-339.dmg) * Preflight Checks no longer requires ATTO drivers to be up to date all of the time. **Canister 22.2.3** (May 13, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-338.dmg) * We finally got rid of that ugly Mount button 😄 **Canister 22.2.2** (May 3, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-337.dmg) * Fixed a crash that sometimes occurred when Ejecting a tape. * Improved the color of the progress bar during Verification. **Canister 22.2.1** (Apr 15, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-336.dmg) * 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. **Canister 22.2** (Apr 12, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-330.dmg) * Preflight Check results are now logged in the console. {% endtab %} {% endtabs %} ## **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. {% tabs %} {% tab title="macOS" %} **Canister 22.1.3** (Apr 8, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-329.dmg) * Improvement for HP LTFS now requiring FUSE to be installed before anything else. **Canister 22.1.2** (Mar 22, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-318.dmg) * Fix for a rare crash related to the Erase view. **Canister 22.1.1** (Feb 23, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-313.dmg) * 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 22.1** (Feb 1, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-309.dmg) {% endtab %} {% endtabs %} ## **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. {% tabs %} {% tab title="macOS" %} **Canister 21.2.3** (January 26, 2022) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-300.dmg) * Polish for some Preflight Checks. **Canister 21.2.2** (December 30, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-296.dmg) * Support for archiving Macintosh HD system disks (including /Library folders). NB: restoring macOS directly from tape is not recommended. **Canister 21.2.1** (December 16, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-292.dmg) * Support for new ATTO driver for Big Sur and more mTape serials. **Canister 21.2** (December 9, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-289.dmg) {% endtab %} {% endtabs %} ## **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. {% tabs %} {% tab title="macOS" %} **Canister 21.1.10** (November 09, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-284.zip) * Fix for retrieving files with % in their filenames. **Canister 21.1.9** (October 07, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-277.dmg) * Our license provider WyDay released a fix for the activation issue present in macOS 10.12, 10.13, and 10.14. **Canister 21.1.8** (July 27, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-270.dmg) * Sometimes, the registration for trials didn't go as planned. All good now. **Canister 21.1.7** (July 22, 2021) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-269.dmg) * 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. **Canister 21.1.6** (July 02, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-263.zip) * Adds support for the new Quantum LTFS driver on M1. **Canister 21.1.5** (June 08, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-257.zip) * Fixes a bug where sometimes a folder in a tape's root couldn't be selected when archiving. **Canister 21.1.4 (**March 26, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-249.zip) * Fixes a bug that sometimes occurred when mounting a Catalog. **Canister 21.1.3** (March 24, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-244.zip) * 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. **Canister 21.1.2** (March 01, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-238.zip) * Checks for the new ATTO drivers, as well as for SANLink and Arcsas. * Fixes few small bugs. **Canister 21.1.1** (February 19, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-230.zip) * 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. **Canister 21.1** (February 12, 2021) — [Download](https://updates.hedge.video/canister/macos/updates/Canister-225.zip) * 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. {% endtab %} {% endtabs %} ## **Canister 20.2** A new licensing system, and a boatload of improvements. {% tabs %} {% tab title="macOS" %} **Canister 20.2.4** (December 21, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-218.dmg) * Added support for Fuse 4. **Canister 20.2.3** (November 10 9, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-214.dmg) * Added support for Big Sur. **Canister 20.2.2** (November 03, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-212.dmg) * Added support (and a logo) for mLogic users. **Canister 20.2.1** (October 16, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-208.dmg) * 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.2** (August 19, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-202.dmg) {% endtab %} {% endtabs %} ## **Canister 20.1** {% tabs %} {% tab title="macOS" %} **Canister 20.1** (February 25, 2020) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-172.dmg) * 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. {% endtab %} {% endtabs %} ## **Canister 19.1** {% tabs %} {% tab title="macOS" %} **Canister 19.1** (July 11, 2019) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-151.dmg) * 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. {% endtab %} {% endtabs %} ## Canister 18.1 First Canister release 🎉 {% tabs %} {% tab title="macOS" %} **Canister 18.1.5** (November 30, 2018) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-118.dmg) * Canister 18.1.5 contains some small bug fixes. Thanks for reporting all! **Canister 18.1.4** (September 18, 2018) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-117.dmg) * 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 18.1.2** (October 23, 2018) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-109.dmg) * 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. **Canister 18.1.1** (October 03, 2018) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-107.dmg) * 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. **Canister 18.1** (September 18, 2018) - [Download](https://updates.hedge.video/canister/macos/updates/Canister-102.dmg) {% endtab %} {% endtabs %} # Requirements Canister itself doesn't have any requirements in terms of CPU and RAM, but LTFS does like ample resources. As a rough guide, any Apple Silicon Mac or recent PC with 16G memory, and a solid state system drive, will be sufficient. ## Which LTO hardware does Canister support? Canister supports a wide range of standalone LTO drives, from a variety of vendors. For most Macs, SAS-based units tend to be connected via a Thunderbolt, while PCs and Mac Pros come with the option to install a PCIe HBA directly into the host system's motherboard. {% tabs %} {% tab title="macOS" %} * LTO Drives * IBM LTO-5 to LTO-10 * HP and Quantum LTO-5 to LTO-9 * Tandberg drives (using HP LTFS) * HBAs * Most ATTO and Areca SAS models * TLR support is required * Highpoint RocketRaid controllers are not recommended for LTO * Thunderbolt/SAS LTO solutions by Symply, OWC, MagStor, mLogic etc * Ethernet-based LTO solutions by Symply & MagStor (from Canister `24.1`) * USB-based LTO solutions by Unitex are not supported on Mac at this time {% endtab %} {% tab title="Windows" %} * LTO Drives * IBM LTO-5 to LTO-10 * Quantum Rev-C LTO-7 to LTO-9 * HP (and thus Tandberg) LTO drives are not currently supported on Windows * HBAs * Most ATTO and Areca SAS models * Selected LSI chipsets (eg. `SAS2308`, onward) * TLR support is required * Highpoint RocketRaid controllers are not recommended for LTO * Thunderbolt/SAS LTO solutions by Symply, OWC, MagStor, mLogic and more * Ethernet-based LTO solutions by Symply & MagStor (from Canister `24.1`) * USB-based LTO solutions by Unitex {% endtab %} {% endtabs %} {% hint style="info" %} Mileage may vary with Fibre Channel-based drives. Canister does not detect which driver your FC device requires - contact your vendor for that. {% endhint %} ## Which versions of macOS, Windows and LTFS are supported? {% tabs %} {% tab title="macOS" %} The latest version of Canister for Mac requires macOS `12` or newer, and supports both Intel and Apple silicon. As with all things LTO, it's essential to pair your operating system with a compatible LTFS version. The table below documents which versions of IBM LTFS are suitable for which macOS and Canister release.
macOSNameSupported sinceSupported up toLTFS Version
26TahoeCanister 25.2Latest release2.4.8.2
15SequoiaCanister 24.2Latest release2.4.8.2
14SonomaCanister 23.2Latest release2.4.8.2
13VenturaCanister 22.1Latest release2.4.8.2
12MontereyCanister 21.1Latest release2.4.8.2
11Big SurCanister 20.2Canister 25.22.4.5.1
10.15CatalinaCanister 19.1Canister 25.22.4.5.1
10.14MojaveCanister 18.1Canister 24.12.4.5.1
10.13High SierraCanister 18.1Canister 24.12.4.5.1
10.12SierraCanister 18.1Canister 22.32.4.5.1
{% endtab %} {% tab title="Windows" %} Canister for Windows supports Windows `10`, onward. We do not officially test or support Windows Server, so your milage may vary. As with all things LTO, it's essential to pair your operating system with a compatible version of LTFS. The table below documents which versions of IBM LTFS are suitable.
WindowsSupported sinceSupported up toLTFS Version
11Canister 23.2Latest release2.4.8.3 onward
10Canister 23.2Latest release2.4.8.3 onward
{% endtab %} {% endtabs %} # Troubleshooting A collection of problems any LTO user will run into at some point. {% hint style="info" %} Troubleshooting LTO can be a pain, so please don't hesitate to use the in-app [Contact Support](/canister/need-help) option. {% endhint %} ## "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. If the LTO drive is running on [old firmware](https://docs.hedge.video/canister/firmware), perform the relevant upgrade and try again. The success rate of this treatment is very high, so don't skip it. 3. 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 CodeDescription
0No Error. Ran successfully.
1Cooling problem.
25V 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).
3Tape drive determined that a microcode error occurred.
4Microcode or tape drive problem. Tape drive determined that a microcode or tape drive hardware failure occurred.
5Tape drive problem. Tape drive determined that a hardware failure occurred.
6Tape 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.
7Media error.
8 Tape drive, SCSI bus or fibre channel error.
9Tape drive or RS-422 error.
ATape drive hardware problem.
BNo error or message is assigned.
CTape drive needs to be cleaned.
DNo error or message is assigned.
JA too-new tape is loaded into an older-generation LTO drive.
=The Unload button on the drive was pushed in and did not release.
## Why won't my tape mount? {% hint style="info" %} This often happens when your LTO drive loses power or connectivity mid transfer, or when the host system crashes. If the tape doesn’t contain valuable data, the simplest solution is to reformat it and start again. {% endhint %} LTFS will automatically repair minor consistency issues between the index and data partition as part of the mount process. Most of the time you won't even know this has happened. However, if the LTFS index is corrupt, Canister will prompt you to perform a Repair, which attempts to rebuild or rollback to the last usable index. This action can be performed in app by clicking the Repair button, or manually using the command line: {% tabs %} {% tab title="Mac (Canister LTFS)" %} From Canister for Mac 26.1 onwards, the `ltfsck` utility is located on this path: {% code overflow="wrap" %} ``` /usr/local/canister/bin/ltfsck ``` {% endcode %} To repair drive `0`, open Applications → Utilities → Terminal and run: ``` /usr/local/canister/bin/ltfsck -f 0 ``` {% endtab %} {% tab title="Mac (Vendor LTFS)" %} With vendor LTFS installed, you can use the `ltfsck` utility to repair tapes. To repair drive `0`, open Applications → Utilities → Terminal and run: ``` ltfsck -f 0 ``` {% endtab %} {% tab title="Windows" %} Open a Command Prompt, then change directory into IBM LTFS: ``` cd c:\ProgramFiles\IBM\LTFS ``` Note down the drive address by running: ``` LtfsCmdDrives.exe ``` Assign the drive to an available letter: ``` LtfsCmdAssign.exe y 1.0.0.0 ``` Start the repair process: ``` LtfsCmdCheck.exe y ``` {% endtab %} {% endtabs %} Providing the Repair operation completes without error, you can attempt to mount your tape. ## Deep Recovery {% hint style="info" %} Deep Recovery is not currently available in IBM LTFS for Windows. {% endhint %} If the tape is in worse condition than a normal Repair can handle, LTFS may be unable to find a usable index or a valid End of Data (EOD) marker. When that happens, you’ll be prompted to perform a Deep Recovery operation. This process walks the tape block-by-block, which can take a long time to complete. For this reason, Canister does not offer this option in app. To perform a Deep Recovery, open Utilities > Terminal, then run: {% tabs %} {% tab title="Canister LTFS" %} {% code overflow="wrap" %} ``` /usr/local/canister/bin/ltfsck --deep-recovery 0 ``` {% endcode %} {% endtab %} {% tab title="Vendor LTFS" %} {% code overflow="wrap" %} ``` ltfsck --deep-recovery 0 ``` {% endcode %} {% endtab %} {% endtabs %} After Deep Recovery completes, you can attempt to mount the tape. ## **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. {% tabs %} {% tab title="Canister LTFS" %} {% code overflow="wrap" %} ``` /usr/local/canister/bin/ltfsck -l 0 ``` {% endcode %} {% endtab %} {% tab title="Vendor LTFS" %} {% code overflow="wrap" %} ``` ltfsck -l 0 ``` {% endcode %} {% endtab %} {% endtabs %} 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 (eg. `57`): {% tabs %} {% tab title="Canister LTFS" %} {% code overflow="wrap" %} ``` /usr/local/canister/bin/ltfsck -g 57 -r 0 ``` {% endcode %} {% endtab %} {% tab title="Vendor LTFS" %} {% code overflow="wrap" %} ``` ltfsck -g 57 -r 0 ``` {% endcode %} {% endtab %} {% endtabs %} 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 contains a "lost\_and\_found" folder after performing a repair If you notice a `lost_and_found` folder at the top level of your tape, it means the tape has undergone a Repair operation. During this process, LTFS discovered orphaned files that exist in the data partition but are not referenced in the index. This is raw data and does not expose file names, so for most purposes, it's pretty useless. Unless you really, *really* need to retrieve this data, you are likely better off formatting the tape. # Questions ## 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. ## Can I mix and match different LTO vendors? Yes, as of Canister for Mac `26.1` you can mix and match IBM, HP and Quantum drives. Tandberg drives require the HP vendor release. Windows users should check the [hardware compatibility list](/canister/requirements#which-lto-hardware-does-canister-support). ## How do I tell Canister to prefer vendor LTFS? If you are on Canister for Mac `26.1` and need to run vendor LTFS, use this Terminal command: {% code overflow="wrap" %} ``` defaults write nl.syncfactory.Canister.Mac PreferVendorLTFS 1 ``` {% endcode %} ## Is Canister compatible with Apple Silicon? Yes - as of version `21.1`, Canister is natively compatible with Apple silicon. ## What about the mLogic LTFS Utility? The mLogic LTFS Utility was a lightweight version of Canister `20.1` that was included with every mLogic purchase. With the changes Big Sur and Apple silicon brought along, the app was end-of-life'd and replaced with Canister. The mTape app is no longer supported or 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. Every existing mTape licensee can [reach out](mailto:canister@hedge.video) for a crossgrade discount to Canister. ## 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. ## Can I move/rename files and folders on tape? Files can be moved and renamed. Folders can be renamed, but moving them is not supported. ## 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 overheads and LTFS indexes. ## 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 syncs the Tape Index every 5 minutes. This conservative default, chosen by IBM, causes the drive to pause writing and reposition the tape whenever the timer expires, which is sometimes mistaken for shoeshining. If you prefer less frequent index updates, for example every 30 minutes, you can override this setting using the steps below. For large files and media & entertainment workflows, 30 minutes is generally a sensible balance. {% tabs %} {% tab title="macOS" %} Run the Terminal command below, then remount the tape: {% code overflow="wrap" %} ``` defaults write nl.syncfactory.Canister.Mac OverrideMountCommandArguments "-o sync_type=time@30 -f" ``` {% endcode %} {% endtab %} {% tab title="Windows" %} Locate the LTFS config on this path, then open it using Notepad with administrator privileges: ``` C:\Program Files\IBM\LTFS\ltfs\ltfs.conf.local ``` Find this line: ``` option single-drive sync_type=time@5 ``` Modify it as follows then save the change: ``` option single-drive sync_type=time@30 ``` Finally, restart the system to apply the change. {% endtab %} {% endtabs %} ## 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. ## Why does Canister offer to format LTFS tapes created using Archiware P5 or ProMax? If an LTFS tape created by Archiware P5 or ProMax appears unformatted when you load it, this is because Canister has not detected LTFS attributes in the tape’s Media Auxiliary Memory (MAM). Canister uses the MAM to quickly check whether a tape is LTFS-formatted or not. However, some (often Linux-based) systems do not bother to write LTFS attributes to the MAM, causing the check to fail, even if the tape is correctly LTFS formatted. As a workaround, you can force Canister to mount without first checking for MAM attributes using this Terminal command: ```defaults defaults write nl.syncfactory.Canister.Mac MountWithoutMAMAttributes -int 1 ``` ## 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:
## Can I disable Tape Library detection? Tape Library detection can be disabled with this user default:\ `defaults write nl.syncfactory.Canister.Mac IgnoreTapeLibrary 1` ## I'm moving to a new computer, what do I need to migrate? First of all, deactivate Canister in-app or through the online [License Manager](https://account.hedge.video) so you free up your license to be used on the new computer. Next, zip and move the Canister directory to your new system. This includes all Catalogs and Transfer Logs. {% tabs %} {% tab title="macOS" %} In Finder, navigate to `~/Library/Application Support/`, zip the Canister directory and move it to your new system. {% endtab %} {% tab title="Windows" %} In Explorer, navigate to `/Users/Username/AppData/Roaming/`, zip the Canister directory and move it to your new system. {% endtab %} {% endtabs %} ## 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. ## 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. Canister also reaches out to our license and crash handling providers, which are documented in the [network requirements](/general/licenses/network-requirements#network-requirements) section. ## 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 anyway. 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? They're wrong. 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: [macOS](/canister/installation/installation#installing-drivers) # 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. {% hint style="warning" %} Do not use Beta software in production - it's not ready yet! {% endhint %} ## Getting started {% tabs %} {% tab title="Windows" %} 1. Request beta access via Canister [support](mailto:canister+beta@hedge.co) - we'll give your license key beta superpowers ✨ 2. Download the Beta installer [here](https://downloads.hedge.video/canister/beta/CanisterSetup-25.3.0.171%CE%B2.exe). 3. Install - full LTO setup instructions can be found [here](https://docs.hedge.video/canister/installation/installation). {% endtab %} {% endtabs %} ## 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? 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 👊 {% tabs %} {% tab title="macOS" %} 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.
{% endtab %} {% tab title="Windows" %} 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).
{% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} In Terminal, copy/paste this one-line command and hit enter to generate a `CanisterForensics.zip` file on your Desktop: {% code overflow="wrap" %} ``` zip -ATrq ~/Desktop/CanisterForensics.zip ~/Library/Application\ Support/Canister/.ConsoleHistory ~/Library/Application\ Support/Canister/Transfer\ Logs ~/Library/Application\ Support/Canister/Warning\ Logs ``` {% endcode %} Send us the resulting file, and we'll be able to piece together your LTO history. {% endtab %} {% tab title="Windows" %} 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. {% endtab %} {% endtabs %} ## 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 cannot help until we have received them. And no, a remote session won't do - we need to be able to run our in-house developed analysis tools. # 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 Connect offers an online dashboard, available at . Log in with either the email connected to your license key(s), or your license key itself. ## Setting Up Connect is available in OffShoot, EditReady, and Canister. We have setup guides available for each app: * [Connect for EditReady](/editready/connect) * [Connect for Canister](/canister/features/connect) * [Connect for OffShoot](/offshoot/features/connect) ## 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 # Webhooks Webhooks let you get notified when events happen in Connect. {% hint style="success" %} Webhooks is a `Pro` feature. {% endhint %} {% hint style="warning" %} This feature is currently in Public Beta. Feedback? Mail us at . {% endhint %} Webhooks let you subscribe to events in Connect. When an event occurs, Connect sends a notification to your webhook endpoint that includes a JSON payload with the updated entity. You can use webhooks in several ways: * Notify your colleagues when a transfer has finished * Enrich your media asset management system (MAM) with transfer status * Start downstream processing when files have been processed or transferred ## Getting started 1. In your back end, create a webhook endpoint handler to receive POST requests with event data. 2. [Log in to Connect](https://connect.hedge.co) using your email or license key 3. Register your webhook endpoint 4. Securing your endpoint ### 1. Create a handler Set up an HTTP or HTTPS endpoint function that can accept webhook requests with a POST method. If you’re still developing your endpoint, you can use something like [Hootdeck CLI](https://hookdeck.com/docs/cli#installation) to forward the webhook requests to your local development server (see local development). 1. Handles POST requests with a JSON payload consisting of an event object. 2. Quickly returns a successful status code (`2xx`) prior to any complex logic that might cause a timeout. {% hint style="info" %} You can use services like Zapier to create webhooks handlers, and connect that to other systems. {% endhint %} ### 2. Log into Connect Head on over to the [Connect login page](https://connect.hedge.co) with the email address or license key. Webhooks are only available for events originating from computers using a `Pro` license. ### 3. Register your secure webhook endpoint After testing your webhook endpoint function and logging into Connect, you can now register your webhook endpoint’s accessible URL so Connect knows where to deliver events. To create a new webhook endpoint in the Dashboard: 1. Open the settings modal by clicking the `Settings` button at the top 2. Fill in your full webhook endpoint URL and hit the `Save` button ### **4. Securing your endpoint** Coming soon. ### Testing with local environments Webhooks require public-facing URLs. If you're developing locally, you can expose your local development server to the internet using a service like [Hookdeck CLI](https://hookdeck.com/docs/cli): 1. Install [Hookdeck CLI](https://hookdeck.com/docs/cli#installation). 2. Run your local server. Note the port your local server is running on. 3. Run `hookdeck listen {PORT} connect --path {WEBHOOK_ENDPOINT_PATH}`, where `{PORT}` is the port where your local server is running and `{WEBHOOK_ENDPOINT_PATH}` is the path to your webhook handler. For example: ``` $ hookdeck listen 3000 connect --path /api/webhook ``` 4. Use the unique URL generated by Hookdeck CLI as your webhook endpoint URL when [registering a webhook endpoint](#id-3.-register-your-secure-webhook-endpoint). ## Event Delivery behaviours This section helps you understand different behaviours to expect regarding how Connect sends events to your webhook endpoint. ### Respond to events The server that you set to receive events from Connect should respond with an HTTP `200` status code within three seconds. This lets Connect know that you successfully received the message. We can't guarantee the order of delivery for webhooks. They may be delivered in a different order to the order they're generated. ### Automatic retries Connect attempts to deliver events to your destination up to three times with an exponential backoff. Connect will retry three times, with a 10-second delay between the first and second attempts, and a 100-second delay for the third attempt. # transfer\_created Occurs when an overall transfer is created. Different applications decide at different times when transfers are created, but generally: a `transfer_created` event is sent when a transfer or job has been started (e.g. transferring 2 sources to one destination sends two `transfer_created` events). ### Example event This example event is showing OffShoot finishing the transfer of one source (in this example: `A001`) to two destinations (`RAID`, `NAS` ). ```json { "version": 1, "event": "transfer_created", "transfer": { "id": "y7opjyv9jl4w", "external_id": "de1efd56-7d53-4211-b798-21f5eb2db2be", "client_id": "e85j1l6r13nq", "uploaded_size": 0, "total_size": 10000000000, "progress": 0, "time_remaining": 0, "state": "queued", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "transfers": [ { "id": "6g5vq8lojolp", "external_id": "51d1707f-fd3d-413b-9e51-f4e15de31160", "client_id": "e85j1l6r13nq", "parent_id": "y7opjyv9jl4w", "uploaded_size": 0, "total_size": 5000000000, "upload_speed": 0, "progress": 0, "time_remaining": 0, "state": "queued", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "destination": { "id": "dqxj87mn83k6", "external_id": "e5ea51a0-aa3d-4664-b40b-a662db546c41", "client_id": "e85j1l6r13nq", "name": "NAS", "kind": "HDD", "type": "destination" }, "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:28:36.000000Z" }, { "id": "4nx1q78lj853", "external_id": "0b84a53f-ae25-4869-99ea-e19426bf2696", "client_id": "e85j1l6r13nq", "parent_id": "y7opjyv9jl4w", "uploaded_size": 0, "total_size": 5000000000, "upload_speed": 0, "progress": 0, "time_remaining": 0, "state": "queued", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "destination": { "id": "0ogpvg77vqjn", "external_id": "08b2432f-a898-418e-a539-8051f7c2d3b9", "client_id": "e85j1l6r13nq", "name": "RAID", "kind": "HDD", "type": "destination" }, "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:28:36.000000Z" } ], "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:28:36.000000Z" } } ``` ### Event data
FieldTypeDescription
versionintThe version number of the event (for future changes)
eventenumThe type of event, in this case: transfer_created
transferobjectSee Transfer Group data
### Transfer Group data The transfer group wraps the transfers that are coming from the same source. This object looks similar to the transfer data below, but summarizes the stats from all transfers from the same source.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
uploaded_sizeintThe total summary of the size in bytes transferred by all the transfers within this group
total_sizeintThe total summary of the total size in bytes by all the transfers within this group
progressfloatThe total summary of the progress percentage by all the transfers within this group
time_remainingintThe time remaining of the highest time remaining by al the transfers within this group
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
transfersTransfer[]An array of Transfer data
created_atstringThe creation timestamp of the given transfer group in ISO8601 format
updated_atstringThe updated timestamp of the given transfer group in ISO8601 format
### Transfer data The individual transfers from one source to one destination.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
parent_idstring|nullThe unique identifier for the Transfer Group this transfer belongs to
uploaded_sizeintThe total size in bytes that has been transferred
total_sizeintThe total size in bytes for the given transfer
upload_speedintThe upload speed in bytes per second
progressfloatThe percentage of progress for the given transfer
time_remainingintThe estimated amount of seconds remaining from now until the transfer has been completed
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
sourceobjectOptional. See Source & Destination
destinationobjectOptional. See Source & Destination
created_atstringThe creation timestamp of the given transfer in ISO8601 format
updated_atstringThe last updated at timestamp of the given transfer in ISO8601 format
### Source & Destination
FieldTypeDescription
idstringThe unique identifier of the source or destination
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
namestringThe display name of the source or destination
kindstringThe kind of source or destination
typeenumPossible values of: source, destination
# transfer\_finished Occurs when a transfer is considered finished, which could be either failed or successful. ### Example event This example event is showing OffShoot finishing the transfer of one source (in this example: `A001`) to two destinations (`RAID`, `NAS`). ```json { "version": 1, "event": "transfer_finished", "transfer": { "id": "y7opjyv9jl4w", "external_id": "de1efd56-7d53-4211-b798-21f5eb2db2be", "client_id": "e85j1l6r13nq", "uploaded_size": 15000000000, "total_size": 15000000000, "progress": 1, "time_remaining": 0, "state": "completed", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "transfers": [ { "id": "6g5vq8lojolp", "external_id": "51d1707f-fd3d-413b-9e51-f4e15de31160", "client_id": "e85j1l6r13nq", "parent_id": "y7opjyv9jl4w", "uploaded_size": 10000000000, "total_size": 10000000000, "upload_speed": 50000000, "progress": 1, "time_remaining": 0, "state": "completed", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "destination": { "id": "dqxj87mn83k6", "external_id": "e5ea51a0-aa3d-4664-b40b-a662db546c41", "client_id": "e85j1l6r13nq", "name": "NAS", "kind": "HDD", "type": "destination" }, "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:28:36.000000Z" }, { "id": "4nx1q78lj853", "external_id": "0b84a53f-ae25-4869-99ea-e19426bf2696", "client_id": "e85j1l6r13nq", "parent_id": "y7opjyv9jl4w", "uploaded_size": 5000000000, "total_size": 5000000000, "upload_speed": 0, "progress": 1, "time_remaining": 0, "state": "completed", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "destination": { "id": "0ogpvg77vqjn", "external_id": "08b2432f-a898-418e-a539-8051f7c2d3b9", "client_id": "e85j1l6r13nq", "name": "RAID", "kind": "HDD", "type": "destination" }, "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:30:36.000000Z" } ], "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:30:36.000000Z" } } ``` ### Event data
FieldTypeDescription
versionintThe version number of the event (for future changes)
eventenumThe type of event, in this case: transfer_finished
transferobjectSee Transfer Group data
### Transfer Group data The transfer group wraps the transfers that are coming from the same source. This object looks similar to the transfer data below, but summarizes the stats from all transfers from the same source.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
uploaded_sizeintThe total summary of the size in bytes transferred by all the transfers within this group
total_sizeintThe total summary of the total size in bytes by all the transfers within this group
progressfloatThe total summary of the progress percentage by all the transfers within this group
time_remainingintThe time remaining of the highest time remaining by al the transfers within this group
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
transfersTransfer[]An array of Transfer data
created_atstringThe creation timestamp of the given transfer group, in ISO8601 format
updated_atstringThe updated timestamp of the given transfer group, in ISO8601 format
### Transfer data The individual transfers from one source to one destination.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
parent_idstring|nullThe unique identifier for the Transfer Group this transfer belongs to
uploaded_sizeintThe total size in bytes that has been transferred
total_sizeintThe total size in bytes for the given transfer
upload_speedintThe upload speed in bytes per second
progressfloatThe percentage of progress for the given transfer
time_remainingintThe estimated amount of seconds remaining from now until the transfer has been completed
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
sourceobjectOptional. See Source & Destination
destinationobjectOptional. See Source & Destination
created_atstringThe creation timestamp of the given transfer in ISO8601 format
updated_atstringThe last updated at timestamp of the given transfer in ISO8601 format
### Source & Destination
FieldTypeDescription
idstringThe unique identifier of the source or destination
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
namestringThe display name of the source or destination
kindstringThe kind of source or destination
typeenumPossible values of: source, destination
# transfer\_deleted Occurs when a stale transfer is deleted from Connect. This can happen when the application loses connection mid-transfer and can't report its status to Connect. ### Example event ```json { "version": 1, "event": "transfer_deleted", "transfer": { "id": "y7opjyv9jl4w", "external_id": "de1efd56-7d53-4211-b798-21f5eb2db2be", "client_id": "e85j1l6r13nq", "uploaded_size": 15000000000, "total_size": 15000000000, "progress": 1, "time_remaining": 0, "state": "stale", "source": { "id": "35qwe2eqwzdo", "external_id": "22f844e2-657c-3efe-8105-ce035d196288", "client_id": "e85j1l6r13nq", "name": "A001", "kind": "SD", "type": "source" }, "created_at": "2025-08-25T15:28:36.000000Z", "updated_at": "2025-08-25T15:30:36.000000Z" } } ``` ### Event data
FieldTypeDescription
versionintThe version number of the event (for future changes)
eventenumThe type of event, in this case: transfer_deleted
transferobjectSee Transfer Group data
### Transfer Group data The transfer group wraps the transfers that are coming from the same source. This object looks similar to the transfer data below, but summarizes the stats from all transfers from the same source.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
uploaded_sizeintThe total summary of the size in bytes transferred by all the transfers within this group
total_sizeintThe total summary of the total size in bytes by all the transfers within this group
progressfloatThe total summary of the progress percentage by all the transfers within this group
time_remainingintThe time remaining of the highest time remaining by al the transfers within this group
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
transfersTransfer[]An array of Transfer data
created_atstringThe creation timestamp of the given transfer group in ISO8601 format
updated_atstringThe updated timestamp of the given transfer group in ISO8601 format
### Transfer data The individual transfers from one source to one destination.
FieldTypeDescription
idstringThe unique identifier for the given transfer
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
parent_idstring|nullThe unique identifier for the Transfer Group this transfer belongs to
uploaded_sizeintThe total size in bytes that has been transferred
total_sizeintThe total size in bytes for the given transfer
upload_speedintThe upload speed in bytes per second
progressfloatThe percentage of progress for the given transfer
time_remainingintThe estimated amount of seconds remaining from now until the transfer has been completed
stateenumPossible values of: unknown, queued, preparing, waiting_for_codex, transferring, canceling, canceled, finishing, completed, completed_with_warnings, stopped, failed, stale
sourceobjectOptional. See Source & Destination
destinationobjectOptional. See Source & Destination
created_atstringThe creation timestamp of the given transfer in ISO8601 format
updated_atstringThe last updated at timestamp of the given transfer in ISO8601 format
### Source & Destination
FieldTypeDescription
idstringThe unique identifier of the source or destination
external_idstringThe unique identifier given by the application
client_idstringThe unique identifier for the Connect client
namestringThe display name of the source or destination
kindstringThe kind of source or destination
typeenumPossible values of: source, destination
# DropOff DropOff lets others drop off and pick up files through your LucidLink Filespace. You can achieve this by means of creating `Receive` and `Send` links from [https://dropoff.cloud](https://dropoff.cloud/). Once someone receives a DropOff link, they can use a web browser on their desktop computer or mobile device to upload or download files to/from your Filespace. {% hint style="info" %} **A Note to PostLab Users** [Drop Off and Pick Up are still available as a part of PostLab](/postlab-classic/drive/drop-off) but will be removed from PostLab in an upcoming release. The standalone release of our DropOff service will replace it. Have questions on how DropOff can improve your workflow? Reach out: {% endhint %} ## Initial Setup Go to and click `Don’t have an account? Sign up`. Once you fill in your account details, your next step is connecting your LucidLink Filespace to DropOff.
#### LucidLink Credentials * `Username` - this is the username you use to authenticate to your Filespace through the Lucid app. * `Password` - this is the password you use to authenticate to your Filespace through the Lucid app. {% hint style="success" %} Due to technical limitations, it's currently not possible to connect to a LucidLink Filespace with a SSO account. If your Filespace uses SSO, ask the person in your organization to create a non-SSO user to use with DropOff. {% endhint %} #### Storage Details {% hint style="warning" %} You must use a version 2.x Filespace with DropOff. If you need to upgrade your 1.x Filespace, [contact LucidLink Support](https://www.lucidlink.com/contact-us). {% endhint %} * `Filespace` - this is the name of your Filespace as displayed in the Lucid app. * The Lucid app displays your Filespace name both under the “FILESPACES” list and after you successfully connect to your Filespace. * `DropOff Folder` - this is the folder on your Filespace where DropOff will upload files. DropOff will create a new folder in this location named “DropOff” after the first successful upload. * You can define a `DropOff Folder` as: 1. A path to a folder that starts at the top level of your Filespace’s `Mount point`. This path must begin with a forward slash (`/`). 2. [A path to a folder derived from using the Lucid app’s `Copy link` action.](https://support.lucidlink.com/hc/en-us/articles/5464117977357-Direct-link-to-Filespace-resources) This path will start with `lucid://`. {% hint style="info" %} The `Username` you’re using must have Read and Write permissions to the `DropOff Folder`. {% endhint %} Once you’ve filled in your `LucidLink Credentials`, click `Connect`, and you’ll see DropOff’s dashboard. You’re now ready to create DropOff links to `Receive` or `Send` files via your LucidLink Filespace.
## Receiving Files From Others ### Adding a `Receive` Link 1. In DropOff’s dashboard, click `Receive`, then `Add +`. 2. In the `Create Link` dialog, give your `Receive` link a `Title`, a time period for when the link `Expires`, then click `Create`. A new link will appear under `Receive`.
3. Click the copy icon next to the `…/dropoff/abcd1234` URL and send someone this DropOff link so they can upload files directly to your LucidLink Filespace.
### Uploading Files Through DropOff If you received a DropOff link to upload files using DropOff: 1. Click the DropOff link (e.g. `https://dropoff.cloud/dropoff/...`), which will launch in your web browser. 2. You can drag and drop the files to upload onto the `Drop your files` region or click that region to launch a file selector. * Did you change your mind about uploading a file? Hover over the file and click `X` to remove it from the list. 3. When you’re ready, click `Upload Files`.
4. When your upload completes: 1. DropOff will notify you in your web browser. 2. DropOff will send an email notification to the person who created the DropOff link. ### Accessing Files Uploaded Through `Receive` Links After a DropOff link recipient successfully uploads their files and your `Receive` link reports a `Completed` status, those uploaded files are stored in a folder called `../DropOff` inside the `DropOff Folder` location on your LucidLink Filespace. Inside the `../DropOff` folder you’ll find subfolders corresponding to each `Receive` link. You can identify which subfolders belong to a specific `Receive` link by matching the `abcd1234` portion of the `Receive` link’s URL with the subfolder name. ## Sending Files to Others ### Adding a `Send` Link 1. In DropOff’s dashboard, click `Send`, then `Add +`. 2. In the `Send files via download links` dialog, give your `Send` link a `Title`, a time period for when the `Files expires`, then click `Next`.
3. In your Send link, click `Upload Files`. {% hint style="info" %} Files uploaded for `Send` links are stored on a LucidLink Filespace owned by Hedge, not your Filespace. [More details are available here.](/dropoff/questions#where-are-uploaded-files-stored-on-my-filespace) {% endhint %} 4. You can drag and drop the files to upload onto the `Drop your files` region or click that region to launch a file selector. * Did you change your mind about uploading a file? Hover over the file and click `X` to remove it from the list.
5. When your upload is complete, DropOff will notify you in your web browser. To send someone a link to download these files: 1. Click `Share`. 2. Click the copy icon next to the `https://dropoff.cloud/pickup…` URL and send this DropOff link so they can download files directly from your LucidLink Filespace. ### Downloading Files From DropOff If you received a DropOff link to download files: 1. Click the DropOff link (e.g. `https://dropoff.cloud/pickup…`), which will launch in your web browser. 2. In the `Download Files` page, click `📥` next to each file you wish to download.
## DropOff Dashboards ### Main * `Top Up` - DropOff is billed by the amount of data uploaded through DropOff. When you run out of data, click `Top Up` and purchase the desired amount of data to use with DropOff. * `Settings`: * `Storage` - edit and update the settings for the LucidLink Filespace you’re using with DropOff. * `Default upload bucket` - DropOff chooses a default upload bucket region for you. But if another region would speed up your uploads based on your current geographic location, you can select another region here. * `Sign out` ### `Receive` * 🗑️ - delete this `Receive` link. * 📝 - edit and update a `Receive` link’s `Title` and `Expires` period. #### `Receive` Link Options * `Copy Link` - copy a `Receive` link to paste into an email, message, et cetera. * `Edit` - edit and update a `Receive` link’s `Title` and `Expires` period. ### `Send` * 🗑️ - delete this `Send` link. * 📝 - edit and update a `Send` link’s `Title`. #### `Send` Link Options * `Share` - copy a `Send` link to paste into an email, message, etc. * `Upload Files` - upload files to share with someone. * `Edit` - edit and update a `Send` link’s `Title`. ### Monitoring File Upload Status If you click the `Title` of a `Receive` or`Send` link, you can monitor the status of a file upload which reports one of three stages: 1. `Uploading` - the file is uploading through DropOff in a web browser. 2. `Processing` - the file successfully uploaded through DropOff and is en route to a LucidLink Filespace. 3. `Completed` - the uploaded file is now available on the destination Filespace. When an upload has `Completed`, DropOff will also display: * `Receive` - how many files were uploaded using this link. * `Send` - the name of each uploaded file, its size, and the time stamp of when that file was uploaded. {% tabs %} {% tab title="Receive" %}
{% endtab %} {% tab title="Send" %}
{% endtab %} {% endtabs %} ## Questions? {% content-ref url="/pages/7pFvQ4NdrY212tfIJhQO" %} [Questions](/dropoff/questions) {% endcontent-ref %} # Questions ### Can I use my LucidLink SSO to log in to DropOff? Due to technical limitations, it's currently not possible to connect to a LucidLink Filespace with a SSO account. If your Filespace uses SSO, ask the person in your organization to create a non-SSO user to use with DropOff. ### Someone uploaded files with a `Receive` link, but I can’t see them on my LucidLink Filespace. Why? Confirm the `LucidLink Credentials` you entered are correct, particularly your `DropOff Folder` path. Once you correct your `LucidLink Credentials`, within 30 minutes: * The status of each transfer will change from `Processing` to `Completed`. * Any previous attempts to transfer files with Receive links will appear in your `DropOff Folder`. ### Why is my DropOff link invalid? Likely, your DropOff link expired. If you *received* a DropOff link, email the person who sent you the DropOff link for assistance. If you *created* the DropOff link: * `Receive` - you can update the `Expires` period for an existing `Receive` link. * `Send` - add a new `Send` link and send it to your recipient. ### How is DropOff billed? You’re billed by the amount of data uploaded through DropOff, which includes: 1. Files uploaded by you and any link recipients using a `Receive` link. 2. Files you upload using a `Send` link. Once you’ve exhausted the data on your account, you can `Top Up` on more data from DropOff’s dashboard. ### Where are uploaded files stored on my Filespace? For `Receive` links, uploads are stored in individual job folders within the `../DropOff` folder defined by your `DropOff Folder` path of your LucidLink Credentials. For `Send` links, files are stored on a LucidLink Filespace owned by Hedge. `Send` link uploads are deleted once the `Send` link expires and are governed by [our privacy and information security policies](/general/policies). # Need help? ## Forgot your password? ## Encountered a hurdle in DropOff? ### 1. Confirm your LucidLink Credentials are correct. Still having trouble? ### 2. Contact Support 1. Gather these details: * The URL of the DropOff link. * The date and time when you experienced difficulty in DropOff. 2. Email those details to us: # 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. EditReady can also generate high-quality proxy media so you can take your media with you on the road or [share them with your team using Postlab Drive.](/postlab-classic/drive) # Installing EditReady is available as a direct download from [hedge.video/editready](https://hedge.video/editready). After you've downloaded EditReady from our website, just drag and drop it into your `/Applications` folder, and it's installed. # Standard vs. Pro EditReady has two license types: Standard and Pro.
FeatureStandardPro
Custom Presets✓✓
Trimming Clips✓✓
Joining Files✓✓
Naming Files✓✓
Rewrapping✓✓
Additional features✓✓
Connect✓✓
Converting non-RAW formats✓✓
Converting RAW formats-✓
Automation (API and Scripting) -✓
# 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 * DNxHD (Op-Atom and OP1a) * DNxHR (OP1A) * DVCProHD * H.264 * H.265 ("HEVC") * ProRes **RAW codecs** (requires a `Pro` license) * ARRIRAW / ARRICORE * Blackmagic RA * Canon RAW * Codex HDE * Nikon * Phantom CineRAW * ProRes RAW * R3D NE * RED RAW * Sony RAW * Sony X-OCN {% hint style="info" %} [EditReady's fully functional trial](/general/trials) converts clips up to 1 minute so you can quickly see if EditReady works with your source files. \ \ Did you discover a file that EditReady can't convert to your liking? [Email us](mailto:editready@hedge.video) about it! {% endhint %} ## Chunked files Due to FAT32's file size limit of 4GB, in the not-too-distant past, some cameras and recorders would split files into 4GB chunks. EditReady automatically detects these for all formats and stitches them together during transcoding. [More…](/editready/converting-media/joining-files) ## New Blackmagic Design cameras Blackmagic Design regularly releases new camera models and accompanying codec updates, requiring an EditReady update for each. That tends to take a bit of time, so if you find yourself in possession of the latest Blackmagic Camera and we haven't yet shipped an update for EditReady, we've made it possible to override EditReady's baked-in BRAW support by manually installing the [Blackmagic BRAW SDK](https://www.blackmagicdesign.com/event/blackmagicrawinstaller) on your computer. EditReady will default to using the newer version. # 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). # 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. ![EditReady Player ](/files/9Zh9wnn4OnK2HDXvzvzA) ### Applying LUTs During Playback 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 [Converting Media > Additional Batch Options > LUTs](/editready/converting-media/additional-features#luts). 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. # 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. ![](/files/TQ6oBrIGCs7a8FsoHUsx)![](/files/nusnAliwHJ47dNQxqD9b) 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. ![EditReady interacting with Apple Maps](/files/TGclSM8X9osxpMCizzTt) 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. ![Adding Metadata Values](/files/qqulcoBpzYZq01DlcV4t) ### 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. # Converting Media # 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. ![EditReady options library](/files/3CA9hCrvcTxAdJ4UiQxT) ## 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. ![Adding a text overlay](/files/jQITZGqZjxAdEaCqQpVv) #### 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. ![Adding an image overlay](/files/JSCW6uXD9ytxR9oBXJi7) #### 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 ``` ## Chunked files Due to FAT32's file size limit of 4GB, in the not too distant past some cameras and recorders would split files into 4GB chunks. EditReady automatically detects these for all formats, and stitches them together during transcoding. # 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. If you'd like to see a full chart of the bitrates used by DNxHD, take a look at the [DNxHD whitepaper](https://www.avid.com/de/~/media/avid/files/whitepaper-pdf/dnxhd.pdf?la=en) from Avid. #### 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. {% hint style="success" %} We strongly recommend using PCM audio with DNxHR. {% endhint %} For details on the framerates, frame sizes, and bitrates that DNxHR supports, see the [DNxHR Codec Bandwidth Specifications table at avid.com](https://avid.secure.force.com/pkb/articles/en_US/White_Paper/DNxHR-Codec-Bandwidth-Specifications). #### 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. # 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. ![Trimming Controls](/files/D6xb9XxhLaLNZT6iNdxd) 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. ![Trimmmed Clip](/files/2p9J5N3lukaWeDuHEV1F) # Joining Files There are a number of ways in which EditReady can join clips, 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, 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. If you find yourself ending up with a bunch of non-joined AVCHD files, likely the .mpl file residing inside the AVCHD bundle (in the PLAYLIST folder) is missing. This can for instance happen when uploading clips to cloud drives that do not have bundle support. \ To get around this, see [#manually-joining-files](#manually-joining-files "mention") If you only have the MTS files, without the rest of the card metadata, [you may still manually join the files](#manually-joining-files). EditReady will attempt to detect whether the files are from a consecutive group and will take the appropriate action to 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 join the files automatically. # 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. ![Custom Naming Options](/files/4ZjEnZu89KlE7KZqFIdr) ### Customizing File Names In addition to the presets, you can add additional values from your file's metadata to the file naming scheme. [When viewing your file's metadata](/editready/metadata#browsing-metadata), you will notice a small tag `🏷` icon next to each metadata key. Drag that `🏷` to the `Dest File Name` field to include that metadata element in the destination filename. ![Dragging in the "Reel" metadata key](/files/gLbTuLT03XZRgaqMvTX7) 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. # 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. # 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. 4. Click `Go to Connect ✨`, or go to [https://connect.hedge.video](https://connect.hedge.video/) in your web browser.
5. Enter the `Connect Code` or request a magic link (requires an EditReady Pro license). 6. Start a conversion in EditReady, which will then automatically appear on the Connect website.
## Connect Pro With an EditReady Pro license, you don’t need to connect each computer using a Connect code. Instead, simply request a magic link with your license key or the email associated with your license. Once you’re logged in, all of your EditReady activations will automatically appear as connections. {% hint style="info" %} When you activate EditReady with a Pro license, Connect is enabled by default. {% endhint %} # Settings
## 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. #### Write ALE Files When enabled, EditReady generates an Avid Log Exchange (ALE) file for each transcoding batch. The ALE file contains metadata about all media files included in the batch. This file can be imported directly into Avid Media Composer to recreate bin metadata and organize clips alongside the transcoded media. #### 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. ## 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. # 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. ### Write ALE Files When enabled, EditReady generates an Avid Log Exchange (ALE) file for each transcoding batch. The ALE file contains metadata about all media files included in the batch. ### 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. # 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 has specifically instructed you. This panel's default is for all options to be unchecked. ### Always write video range ProRes clips Remaps full range (data range) source content to video range when writing ProRes outputs. There's inconsistent handling of ProRes range mapping across applications, which can cause issues when between different applications, which can cause issues mixing ProRes proxies with camera originals. Premiere Pro and DaVinci Resolve tend to treat ProRes as video range exclusively, whereas Final Cut Pro X will treat files differently depending on the project settings. ### 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. # Automation Automate conversions, remotely set settings, and control licenses with the EditReady API. You can also trigger custom scripts on specific events, and run custom processes, other apps, or integrate EditReady into an existing workflow. {% hint style="info" %} EditReady is also available as a [headless CLI](/editready-server). {% endhint %} ## Requirements * EditReady Pro license * API: EditReady 22.4 or newer * Scripting: EditReady 25.4 or newer ## API 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. Copy/paste the URL below in a web browser, press `Enter`, and EditReady will open. ``` editready://open ``` You can also use a shell, copy/paste the command below, press `Enter`, and EditReady will open. ``` open 'editready://open' ``` ### Activate & Deactivate License ``` editready://activate?key= ``` ``` editready://deactivate ``` ### Add Clips Adds a file or folder to the clip view. ``` editready://add?sourcePath= ``` ### Transcode Transcodes a file or folder (also adds the file to the clip view). ``` editready://transcode?sourcePath=&preset=&destinationPath= ``` {% hint style="info" %} 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//Library/Application Support/EditReady` {% endhint %} ## Scripting You can attach scripts (AppleScript or Python) to the following events: * [EditReady Started](#editready-started) * [File Conversion Completed](#file-conversion-completed)
{% hint style="danger" %} Scripting is a powerful tool. Easy to learn, but even easier to screw up. Always test your script with disposable data, and then test again. And again. Hedge does not offer support or assume responsibility for problems with or due to examples or any other script. If you’re new to scripting, find someone to help you out, or use the example scripts available here. Remember: you are solely responsible. {% endhint %} ### EditReady Started Fires once when launching EditReady. Has no payload. ### File Conversion Completed Fires when a conversion has completed, and has the following payload: {% code overflow="wrap" %} ``` 03/10/2025, 15:18:11 - File Conversion Completed: { "FileConversionCompleted_destinationPath" = "/Volumes/Hedge/Clip-0001.braw"; "FileConversionCompleted_status" = "Success"; "FileConversionCompleted_sourcePath" = "/Volumes/G-DRIVE I/TEST"; "FileConversionCompleted_error" = "none"; } ``` {% endcode %} ### Python When a Python script is executed, the event payload is passed as a JSON string in the first command-line argument (sys.argv\[1]). You can parse it into a dictionary as follows: ``` import sys import json # Load the event payload from the first argument payload = json.loads(sys.argv[1]) # Example: access fields from the payload print(payload.get("FileConversionCompleted_status")) ``` ### AppleScript When an AppleScript script is executed, the event payload is injected into the script by identifying key names, such as "{FileConversionCompleted\_status}", and replacing them with corresponding values. You can test this as follows: ``` display alert "{FileConversionCompleted_status}" ``` ### Event Log All events and script execution results are recorded in the Event Log. You can find the log file at: {% code overflow="wrap" %} ``` /Users/[your-username]/Library/Application Support/EditReady/Event Log/EditReadyEvents.log ``` {% endcode %} # Media Composer Guide EditReady can converrt your source media into Avid codec-based MXFs to speed up and simplify your dailies (or rushes) workflow. There are two types of MXF that Media Composer supports: 1. OP-Atom 2. OP1a ## OP-Atom With OP-Atom, there are separate MXFs for the individual video and audio streams. Media Composer then combines these 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, 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. ## 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. {% tabs %} {% tab title="OP-Atom" %} 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. (Optional) Go to `Batch > Save Current Preset` and name your new preset. {% endtab %} {% tab title="OP1a" %} 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. {% endtab %} {% endtabs %} 3. Click `Convert All.` Your transcoded MXFs are now available in the `Dest Folder:` location, alongside the corresponding `*.aaf` files for each clip. ### **2. Copy the transcoded MXFs into one of Media Composer’s media folders** {% tabs %} {% tab title="OP-Atom" %} 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)` {% endtab %} {% tab title="OP1a" %} 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)` {% endtab %} {% endtabs %} {% hint style="danger" %} Do not mix Shared and Local storage media management folder structures on the same volume. {% endhint %} {% hint style="info" %} Media Composer will index and use the `MXF` and `UME` folders if they exist inside `/(Volume)/Avid MediaFiles` on the same volume. {% endhint %} ### **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 associated `*.aaf` file to import a specific clip into a Bin** 1. In Media Composer, create a new Bin. 2. In Finder (macOS) or File Explorer (Windows), open the destination folder from your transcodes and locate the `*.aaf` file for the specific clip you want to import. 3. Drag and drop the `*.aaf` to your Bin. ### **5. (Optional ) 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 with the exported Clips - ready to use in Media Composer.
## 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. [A complete discussion on this topic is available in Mimiq's documentation.](https://docs.hedge.video/editready/pages/PfT531SlVaikfqfaAC5r#should-i-rename-the-folders-in-..-avid-mediafiles-mxf-or-..-omfi-mediafiles) ### 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: * [Avid Universal Media Engine FAQ](https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/Knowledge/Avid-Universal-Media-Engine-FAQ) * [Avid Media Composer, Apple macOS Catalina Support, and the Universal Media Engine](https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/Knowledge/MC-macOS-Catalina-Support-Universal-Media-Engine) * [Media Composer File Type Support Without QuickTime Installed](https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/Knowledge/Media-Composer-File-Type-Support-on-macOS-Catalina) # 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. If you purchased ClipWrap from the Mac App Store, contact us for a discount coupon: # Requirements ## Which versions of macOS and Windows are supported? {% tabs %} {% tab title="Mac" %} 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 [`24.4`](https://docs.hedge.video/editready/pages/CZBbZpEEwcQNlXDNNAJW#id-24.4-codex-hde-and-connect) * The most recent version of EditReady that works on `11` is [`24.4`](https://docs.hedge.video/editready/pages/CZBbZpEEwcQNlXDNNAJW#id-24.4-codex-hde-and-connect) Legacy versions of EditReady (version 2.\* or older) do not work on Apple Silicon. {% endtab %} {% tab title="Windows" %} EditReady is not yet available on Windows. {% endtab %} {% endtabs %} # Releases ## 26.2 - Sony BURANO V3 {% tabs %} {% tab title="macOS" %} **EditReady 26.2** (June 23 2026) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20260612190408_v26.2b1722/EditReady_20260612190408_v26.2b1722.dmg) * Support for Sony BURANO Version 3.0 {% endtab %} {% endtabs %} ## 26.1 - ALE & SDK Updates {% tabs %} {% tab title="macOS" %} **EditReady 26.1** (Apr 1, 2026) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20260314052935_v26.1b1707/EditReady_20260314052935_v26.1b1707.dmg) **New** * Support for R3D NE * Support for Blackmagic URSA Cine Immersive and PYXIS 12K * Option to create Avid ALE files for each transcoding batch (enable in EditReady > Settings > General). * Advanced option to always write video range for ProRes clips. **Fixed & Improved** * Clips are now sorted alphabetically when added to EditReady. * Intra-frame formats sometimes failed to generate a thumbnail. * "Remove Audio Channels" is now supported for AAC mixdowns. {% endtab %} {% endtabs %} ## 25.4 - Nikon, ARRICORE, and Scripting {% tabs %} {% tab title="macOS" %} **EditReady 25.4** (Nov 4, 2025) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20251006155101_v25.4b1675/EditReady_20251006155101_v25.4b1675.dmg) **New** * A free upgrade to FoolCat Pro - [learn more](https://hedge.co/blog/back-to-basics) * ARRICORE and Nikon RAW support * Automate your workflow with the new Scripting feature, now supporting AppleScript and Python. * Transcodes will now detect and include ARRI audio sidecar tracks. {% endtab %} {% endtabs %} ## 25.3 - DNxHR OPAtom {% tabs %} {% tab title="macOS" %} **EditReady 25.3** (August 5th, 2025) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20250804200030_v25.3b1657/EditReady_20250804200030_v25.3b1657.dmg) * Official support for DNxHR OPAtom ✨ * Fixed an issue where thumbnails for ARRI Alexa LF and Mini LF MXF HDE clips were not appearing. * Increased the max bitrate for constant bit rate HEVC and H.264 transcodes to 1 Gb/s {% endtab %} {% endtabs %} ## 25.2 - Camera updates {% tabs %} {% tab title="macOS" %} **EditReady 25.2** (Jul 02, 2025) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20250625160229_v25.2b1636/EditReady_20250625160229_v25.2b1636.dmg) **New** * Support for DJI D-Log/D-Gamut color space * Support for Blackmagic Design SDK 4.6 * Support for RED SDK 9.0.1 * Support for Panasonic S1II and S1IIE clips recorded by the Blackmagic Video Assist 12G HDR * Enhanced performance for URSA Cine 12K LF and URSA Cine 17K 65 clips **Fixed** * Canon AVC-Intra 10-bit clips could display a green thumbnail * Some ARRIRAW clips made with an Alexa 65 could not be transcoded {% endtab %} {% endtabs %} ## 25.1 - SONY BURANO Version 2.0 {% tabs %} {% tab title="macOS" %} **EditReady 25.1** (Apr 04, 2025) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20250404185749_v25.1b1619/EditReady_20250404185749_v25.1b1619.dmg) **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. {% endtab %} {% endtabs %} ## 24.4 - CODEX HDE & Connect {% tabs %} {% tab title="macOS" %} **EditReady 24.4** (Sept 04, 2024) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20240903212724_v24.4b1603/EditReady_20240903212724_v24.4b1603.dmg) * Support for CODEX High Density Encoding (HDE) MXF files. * Connect! Track conversion progress and receive push notifications wherever you are, via [https://connect.hedge.video](https://connect.hedge.video/) * A new Settings window, with General, Connect, License, and Advanced options {% endtab %} {% endtabs %} ## 24.3 - BRAW 4.1 {% tabs %} {% tab title="macOS" %} \ **EditReady 24.3** (July 02, 2024) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20240701225116_v24.3b1584/EditReady_20240701225116_v24.3b1584.dmg) 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. **EditReady 24.3.1** (July 15, 2024) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20240711220544_v24.3.1b1592/EditReady_20240711220544_v24.3.1b1592.dmg) * 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. {% endtab %} {% endtabs %} ## 24.2 - SDK Updates {% tabs %} {% tab title="macOS" %} **EditReady 24.2** (May 07, 2024) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20240507102104_v24.2b1562/EditReady_20240507102104_v24.2b1562.dmg) **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. \ {% endtab %} {% endtabs %} ## 24.1 - Parallel Transcodes {% tabs %} {% tab title="macOS" %} **EditReady 24.1** (March 12, 2024) - [Download](https://updates.hedge.video/editready/macos/updates/production/EditReady_20240311221951_v24.1b1555/EditReady_20240311221951_v24.1b1555.dmg) * 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 🤩 {% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} **EditReady 23.1.1** (September 26, 2023) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1446.dmg) * 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) **EditReady 23.1** (June 22, 2023) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1436.dmg) * 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!) {% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} **EditReady 22.4** (December 20, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1404.dmg) * 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 {% endtab %} {% endtabs %} ## 22.3 - Canon RAW & ARRI ALEXA 35 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. [Learn more...](https://blog.hedge.video/editready-canon-raw-and-arri-alexa-35) {% tabs %} {% tab title="macOS" %} **EditReady 22.3.3** (October 14, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1393.dmg) * 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 **EditReady 22.3.2** (August 09, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1384.dmg) * 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 **EditReady 22.3.1** (July 15, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1376.dmg) * 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. **EditReady 22.3** (July 12, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1375.dmg) * 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 {% endtab %} {% endtabs %} ## 22.2 - Color Awareness & X-OCN Color Awareness, a new color pipeline, and Sony RAW & X-OCN. [Learn more...](https://blog.hedge.video/editready22-2/) {% tabs %} {% tab title="macOS" %} **EditReady 22.2.1** (Apr 19, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1364.dmg) * 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 **EditReady 22.2** (Apr 13, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1361.dmg) * 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 {% endtab %} {% endtabs %} ## 22.1 - RAW Support 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). [Learn more...](https://blog.hedge.video/editready-raw/) {% tabs %} {% tab title="macOS" %} **EditReady 22.1.1** (Feb 24, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1354.dmg) * 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 **EditReady 22.1** (Feb 01, 2022) - [Download](https://updates.hedge.video/editready/macos/updates/EditReady-1348.dmg) * 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 * EditReady licenses can now be managed from the [Hedge License Manager](https://account.hedge.video) * Licenses now come with a year of free updates 🎉 * New Metal-based video pipeline for better performance and higher quality on Apple silicon Macs 💪🏽 {% endtab %} {% endtabs %} ## Legacy Versions * [Download v2.7.2](https://downloads.hedge.video/editready/legacy/EditReady%202.7.2.dmg) (Requires macOS 10.12+) * [Download v2.6.5](https://downloads.hedge.video/editready/legacy/EditReady%202.6.5.dmg) (Requires macOS 10.10+) * [Download v2.5.4](https://downloads.hedge.video/editready/legacy/EditReady%202.5.4.dmg) (Requires macOS 10.8+) * [Download v1.4.9](https://downloads.hedge.video/editready/legacy/EditReady%201.4.9.dmg) (Requires macOS 10.8+) # Questions ## Why is EditReady suddenly the default app for video files? Occasionally, EditReady might become set as the default app 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...` ![Making QuickTime the default player](/files/jnmiLjOPmeyUOyCOULiM) ## My chunked video files aren't stitched together during transcoding Likely, a required file is missing. More info [here](/editready/converting-media/joining-files). ## I'm running into errors If you run into an issue during conversion, begin by confirming that your files play correctly in another application. QuickTime Player or [VLC](http://www.videolan.org/vlc/index.html) 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. 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: * [IINA](https://iina.io) * [VLC](https://www.videolan.org) If the file plays in one of these apps, but won't open or convert in EditReady, reach out: ## Can I use EditReady to create dailies/rushes for Media Composer? Yes. A step-by-step guide is available here: {% content-ref url="/pages/1skMhcr5hM7AgRl86qWp" %} [Media Composer Guide](/editready/media-composer-guide) {% endcontent-ref %} # 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? If you purchased EditReady after February 1, 2022, you can use the [Hedge License Manager](https://account.hedge.video/) 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 [legacy EditReady license key online](http://divergent-licensing.hedge.video/keylookup). ## How can I upgrade my legacy EditReady license key to the new EditReady? 1. Locate your legacy EditReady license key in your email, or [online](http://divergent-licensing.hedge.video/keylookup). 2. Download and install the most recent version of EditReady: 3. Launch EditReady, then click `Activate...` 4. Copy/paste your legacy EditReady license key in the `Activation number` field, click `Activate`, then click `Buy upgrade...` 5. A personal discount code will be applied. Complete the checkout, and you'll receive a new license key for the latest version of EditReady. {% hint style="warning" %} Your legacy EditReady license key cannot be used to activate EditReady 22.1 and newer. {% endhint %} 6. Activate EditReady with that new license key. ## I'm not ready to upgrade EditReady yet. Can I use an older version for now? Yes. You can download legacy EditReady versions in [Releases](/editready/releases#legacy-versions) under [Releases](/editready/releases#legacy-versions). # EditReady Server EditReady Server enables headless workflows for tasks such as automated ingest and proxy generation for asset managers. {% hint style="info" %} EditReady Server supports [the same formats as EditReady](/editready/supported-formats), and the same [API calls](/editready/automation). {% endhint %} ## How to use 1. Download [EditReady Server](https://hedge.video/download/editready-server/macos) 2. Activate with your EditReady Server license key (or use the trial mode) 3. Run your CLI commands ## Trial Using EditReady Server unlicensed is limited to transcoding the first minute of each clip. Reach out to for a free 10-day trial license. ## Activation {% code lineNumbers="true" %} ``` /Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server --registration XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX ``` {% endcode %} (De)activation can be managed in the [License Manager](https://account.hedge.video/). ## Commands {% hint style="info" %} You must have a logged-in user session to use EditReady Server. {% endhint %} 
/Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server -h
    
Usage: /Applications/EditReady Server.app/Contents/MacOS/EditReady Server
    -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
    -a, --aleDestination             Path for ALE file 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
    -7, --rec709                     Apply rec709 transform to thumbnail

    -l, --logginglevel               Logging level {error/warning/info} (default error)
    -I, --iconik                     Enable iconik-specific multichannel AAC handling for CLI conversions
    -h, --help                       Show this help message. Visit https://hedge.video/app/editready/server for more info.
## Convert Media ```bash /Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \ --sourceFile '$FileOrFolderPath' \ --destFile '$folderPath' \ --preset '/Applications/EditReady Server.app/Contents/Resources/Apple ProRes 422 (proxy).erpreset' ``` {% hint style="info" %} It's possible to use multiple -s flags in one command. {% endhint %} **Progress Example** {% code overflow="wrap" %} ```bash STATUS: {"clip": "/Volumes/DRIVE-12TB/_BLACKMAGIC/A001_10031156_C006.braw", "action": "transcode", "destination": "/path/to/destinationFolder", "progress": "0.0000234"} ``` {% endcode %} ## **Additional Options** EditReady Server includes many [additional options](/editready/converting-media/additional-features) that can be used via the command-line interface (CLI) when configured in a preset. 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** ``` /Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \ --sourceFile '$FileOrFolderPath' \ --metadataDestination '$JSONfilePath.' ``` **Metadata JSON example** ```xml { "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 } ] } ``` ## Generating Stills ```bash /Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \ --sourceFile '$filePath' \ --destFile '$folderPath' \ --generateThumbs \ --thumbSize 1024 \ --thumbInterval 1 ``` ```bash /Applications/EditReady\ Server.app/Contents/MacOS/EditReady\ Server \ --sourceFile '$filePath' \ --destFile '$folderPath' \ --generateThumbs \ --thumbSize 1024 \ --thumbCount 3 ``` ## Releases {% content-ref url="/pages/JZrfyIJI1mKgVvdWRx9i" %} [Releases](/editready-server/releases) {% endcontent-ref %} # Iconik Storage Gateway For iconik customers, an [EditReady Server integration is available](https://help.iconik.backlight.co/hc/en-us/articles/25027479882647-EditReady). {% hint style="info" %} Manually creating multichannel web proxies for iconik? Use the `--iconik` overwrite flag. {% endhint %} # Mistika Workflows Mistika Workflows users can integrate EditReady Server directly: # Releases ## EditReady Server 26.2 {% tabs %} {% tab title="macOS" %} **EditReady Server 26.2** (June 23, 2026) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20260612190349_v26.2b1722/EditReady_Server_20260612190349_v26.2b1722.dmg) * Support for Sony BURANO Version 3.0 * Support for iconik multichannel audio web proxies {% endtab %} {% endtabs %} ## EditReady Server 26.1 {% tabs %} {% tab title="macOS" %} **EditReady Server 26.1** (April 1, 2026) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20260314052600_v26.1b1707/EditReady_Server_20260314052600_v26.1b1707.dmg) **New** * Support for R3D NE * Support for Blackmagic URSA Cine Immersive and PYXIS 12K * Option to create Avid ALE files for each transcoding batch (enable in EditReady Server> Settings > General). * Advanced option to always write video range for ProRes clips. **Fixed & Improved** * Support for rotated thumbnails. * Intra-frame formats sometimes failed to generate a thumbnail. * "Remove Audio Channels" is now supported for AAC mixdowns. {% endtab %} {% endtabs %} ## EditReady Server 25.4 {% tabs %} {% tab title="macOS" %} **EditReady Server 25.4** (Nov 4, 2025) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20251003175715_v25.4b1674/EditReady_Server_20251003175715_v25.4b1674.dmg) **New** * ARRICORE and Nikon RAW support * Automate your workflow with the new Scripting feature, now supporting AppleScript and Python. * Transcodes will now detect and include ARRI audio sidecar tracks. {% endtab %} {% endtabs %} ## EditReady Server 25.3 {% tabs %} {% tab title="macOS" %} **EditReady Server 25.3** (Sep 23, 2025) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20250813191303_v25.3b1663/EditReady_Server_20250813191303_v25.3b1663.dmg) **New** * Official support for DNxHR OPAtom ✨ * Fixed an issue where thumbnails for ARRI Alexa LF and Mini LF MXF HDE clips were not appearing. * Increased the max bitrate for constant bit rate HEVC and H.264 transcodes to 1 Gb/s. * Support for DJI D-Log/D-Gamut color space * Support for Blackmagic Design SDK 4.6 * Support for RED SDK 9.0.1 * Support for Panasonic S1II and S1IIE clips recorded by the Blackmagic Video Assist 12G HDR * Enhanced performance for URSA Cine 12K LF and URSA Cine 17K 65 clips **Fixed** * Canon AVC-Intra 10-bit clips could display a green thumbnail * Some ARRIRAW clips made with an Alexa 65 could not be transcoded {% endtab %} {% endtabs %} ## EditReady Server 25.1 {% tabs %} {% tab title="macOS" %} **EditReady Server 25.1** (Apr 04, 2025) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20250404191506_v25.1b1620/EditReady_Server_20250404191506_v25.1b1620.dmg) **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. {% endtab %} {% endtabs %} ## EditReady Server 24.4 {% tabs %} {% tab title="macOS" %} **EditReady Server 24.4** (September 26, 2024) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20240925224310_v24.4b1605/EditReady_Server_20240925224310_v24.4b1605.dmg) * Support for CODEX High Density Encoding (HDE) MXF files. * Connect! Track conversion progress and receive push notifications wherever you are, via [https://connect.hedge.video](https://connect.hedge.video/). * A new Settings window, with General, Connect, License, and Advanced options. **EditReady Server 24.4.1** (Nov 05, 2024) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20241031220618_v24.4.1b1606/EditReady_Server_20241031220618_v24.4.1b1606.dmg) * Fixes an issue that caused transcodes to report as failed in iconik. **EditReady Server 24.4.2** (Feb 19, 2025) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20250214233518_v24.4.2b1612/EditReady_Server_20250214233518_v24.4.2b1612.dmg) * 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. {% endtab %} {% endtabs %} ## EditReady Server 24.3 {% tabs %} {% tab title="macOS" %} **EditReady Server 24.3** (July 02, 2024) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20240701221907_v24.3b1583/EditReady_Server_20240701221907_v24.3b1583.dmg) **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.
**EditReady Server 24.3.1** (July 15, 2024) - [Download](https://updates.hedge.video/editready-server/macos/updates/production/EditReady_Server_20240715204812_v24.3.1b1595/EditReady_Server_20240715204812_v24.3.1b1595.dmg) * 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. {% endtab %} {% endtabs %} ## EditReady Server 24.2 {% tabs %} {% tab title="macOS" %} #### EditReady Server 24.2 (May 07, 2024) - [Download](https://updates.hedge.video/editready-server/macos/updates/EditReady_Server-1471.dmg) **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. {% endtab %} {% endtabs %} ## EditReady Server 23.2 {% tabs %} {% tab title="macOS" %} #### EditReady Server 23.2.2 (November 30, 2023) - [Download](https://updates.hedge.video/editready-server/macos/updates/EditReady_Server-1450.dmg) * Fixes crash when thumbnailing spanned RED clips. * Fixes crash exporting metadata JSON of corrupt clips with bad timing data. #### EditReady Server 23.2.1 (August 7, 2023) - [Download](https://updates.hedge.video/editready-server/macos/updates/EditReady_Server-1444.dmg) * 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 #### EditReady Server 23.2 (May 11, 2023) - [Download](https://updates.hedge.video/editready-server/macos/updates/EditReady_Server-1423.dmg) * 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 {% endtab %} {% endtabs %} ## EditReady Server 23.1 {% tabs %} {% tab title="macOS" %} #### EditReady Server 23.1 (February 9, 2023) - [Download](https://updates.hedge.video/editready-server/macos/updates/EditReady_Server-1407.dmg) * First release 🎉 {% endtab %} {% endtabs %} # FoolCat # Overview FoolCat generates camera reports, complete with thumbnails and extended metadata. Available on macOS and Windows. {% hint style="info" %} Using OffShoot for offloads? You can automatically generate FoolCat reports with the [FoolCat integration in OffShoot](https://docs.hedge.video/hedge/integrations/foolcat). {% endhint %} ### Creating a Report Drag and drop your camera footage onto FoolCat's main window, or click the `+` button to get started. ![Drag and Drop camera files to create a Report](/files/kVdzQHI5V2Xp34QlkbZE) ![Drag and Drop a folder to create a report](/files/yhiwHoeIk4u8IrgIgCyg) ![Processing images to create a report](/files/voBmgYEW00oTRkG5sEkV) {% hint style="info" %} Hold the `Option` key to open the PDF report instead of the HTML. {% endhint %} ![Hold Option to open a PDF report instead of the HTML version](/files/waa9z3S3lVVbEuqiz3ii) #### 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.​​
![Use Labels to set Report Names](/files/Tp7wNRZ7QcQWZCq7IbEp) When done, the Report will look something like this: ![Completed report](/files/-Me9ttqkEWre4obv9U8O) ### Customization FoolCat allows for a lot of customization of your Reports. Add a logo and other project information in the `Report` Preferences pane: ![](/files/SRpRnoB0WNKhRbsQgo1O) ![](/files/y3nZkWGaMrEqLqOXshgX) ### 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`. {% hint style="info" %} Don't want any thumbnails? Set it to 0. {% endhint %} ### 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. ![](/files/OFrzPY3VXwudBpp3sNbQ) # Standard vs. Pro FoolCat has two license types: Standard and Pro.
FeatureStandardPro
PDF and HTML Reports✓✓
Custom Reports✓✓
non-RAW formats✓✓
RAW formats-✓
Color Conversion (Rec. 709 and LUTs) -✓
Automation (API and Scripting)-✓
# 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. {% hint style="info" %} When Color Conversion is enabled, the settings used will be shown in the report header. {% endhint %}
## 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) {% hint style="info" %} FoolCat supports LUTs in the 3D `.cube` format (33x33x33). {% endhint %} ## 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. {% hint style="info" %} `The Convert RAW to Rec.709` feature is currently only available in FoolCat for Mac. {% endhint %} ### Supported formats * ARRIRAW * RED * SONY RAW (Mac only) * SONY X-OCN * CANON RAW * BRAW * ProRes RAW {% hint style="warning" %} `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. [Reach out]() if you encounter any issues. {% endhint %} # 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 * DNxHD (Op-Atom and OP1a) * DNxHR (OP1A) * DVCProHD * H.264 * H.265 ("HEVC") * ProRes **RAW codecs** (requires a `Pro` license) * ARRIRAW / ARRICORE * Blackmagic RA * Canon RAW * CinemaDNG * Codex HDE * Nikon * Phantom CineRAW * ProRes RAW * R3D NE * RED RAW * Sony RAW * Sony X-OCN {% hint style="info" %} [FoolCat's fully functional trial](/general/trials) generates reports up to 5 clips so you can quickly see which metadata FoolCat reports based on your source files. \ \ [Let us know](mailto:foolcat@hedge.video) if you need support for a specific camera, metadata key, or codec that isn't currently supported. {% endhint %} # Automation Automate Report creation, remotely set settings, and control licenses with the FoolCat API. You can also trigger custom scripts on specific events, start run custom processes or other apps, and integrate FoolCat into existing workflows. ## Requirements * FoolCat Pro license * API: FoolCat 20.1 or newer * Scripting: FoolCat 25.3 or newer ## API You can tell FoolCat to do something by calling the app URL: `foolcat://`. You can call this from any app or script that can open a URL. Copy/paste the URL below in a web browser, press `Enter`, and EditReady will open. ``` editready://open ``` You can also use a shell, copy/paste the command below, press `Enter`, and EditReady will open. {% tabs %} {% tab title="macOS" %} ``` open 'foolcat://open' ``` {% endtab %} {% tab title="Windows" %} ``` start 'foolcat://open' ``` {% endtab %} {% endtabs %} ### Activate ``` foolcat://activate?key= ``` ### Deactivate ``` foolcat://deactivate ``` ### Create Report {% code overflow="wrap" %} ``` foolcat://create?source=&destination=&name=&description= ``` {% endcode %} ## Scripting You can attach scripts (AppleScript or Python) to the following events: * FoolCat Started * Report Created
{% hint style="danger" %} Scripting is a powerful tool. Easy to learn, but even easier to screw up. Always test your script with disposable data, and then test again. And again. Hedge does not offer support or assume responsibility for problems with or due to examples or any other script. If you’re new to scripting, find someone to help you out, or use the example scripts available here. Remember: you are solely responsible. {% endhint %} ### FoolCat Started Fires once when launching FoolCat. Has no payload. ### Report Created Fires when a Report has been created, and has the following payload: {% code overflow="wrap" %} ``` 03/10/2025, 10:55:21 - Report Created: { "ReportCreated_status" = "Success"; "ReportCreated_error" = "none"; "ReportCreated_pdfPath" = "/Volumes/Hedge/A001/Reports.pdf"; "ReportCreated_htmlPath" = "/Volumes/Hedge/A001/Reports.html"; } ``` {% endcode %} ### Python When a Python script is executed, the event payload is passed as a JSON string in the first command-line argument (sys.argv\[1]). You can parse it into a dictionary as follows: ``` import sys import json # Load the event payload from the first argument payload = json.loads(sys.argv[1]) # Example: access fields from the payload print(payload.get("FileConversionCompleted_status")) ``` ### AppleScript When an AppleScript script is executed, the event payload is injected into the script by finding key names, e.g. "{FileConversionCompleted\_status}" , and replacing them with values. You can test this as follows: ``` display alert "{ReportCreated_status}" ``` ### Event Log All events and script execution results are recorded in the Event Log. You can find the log file at: {% code overflow="wrap" %} ``` /Users/[your-username]/Library/Application Support/FoolCat/Event Log/FoolCatEvents.log ``` {% endcode %} # 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 {% hint style="info" %} [Download the FoolCat Offload Report Creator v1.1](http://downloads.hedge.video/foolcat/Foolcat_Offload_Report_Creator_1.1.zip) {% endhint %} ![](/files/8cj2SF6w8A5phWXsjPmH)![](/files/WwIIv0G4xSez5gCVBVl4) ![](/files/VDxCG4CKG43yrAF2MROz)![](/files/DS8AuxBfTmuDsOPMP8p7) # Questions ## When I try to activate FoolCat (licensed or a trial), why am I told, “No virtual machine activations allowed.”? {% hint style="info" %} This only concerns Windows users. {% endhint %} 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: {% content-ref url="/pages/UIBxiHJMUBHr8aURYDew" %} [VMs & Hypervisors](/general/licenses/vms-and-hypervisors) {% endcontent-ref %} If you have a regular license and need VM activations, upgrade your license in the [License Manager](https://account.hedge.video/), then [reach out](mailto:hello@hedge.video). Already on a Pro license? [Reach out](mailto:hello@hedge.video). ## FoolCat states error -1004 You're likely on an old version of FoolCat, update to the latest version. ## "Invalid activation number" You're likely trying to activate FoolCat using a legacy license key. Legacy license keys start with `id` or only have a few characters. [Upgrade your license](https://hedge.video/store/foolcat?coupon=FOOL6GRADE-C7B230BC), or [download a legacy version](https://docs.hedge.video/foolcat/releases#legacy-downloads). ## FoolCat states "Starting Services" {% hint style="info" %} This issue is fixed in FoolCat version 23.1 and newer. {% endhint %} FoolCat's media engine isn't starting correctly. Reboot your computer, and if that doesn't help, reinstall FoolCat. ![Starting Services](/files/FBRVrOJw6x7M6K0qgArF) ## How can I export/import settings? {% tabs %} {% tab title="macOS" %} 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: ``` defaults export nl.syncfactory.FoolCat.Mac ~/Desktop/FoolCatSettings.plist ``` 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: ``` defaults import nl.syncfactory.FoolCat.Mac ~/Desktop/FoolCatSettings.plist ``` {% endtab %} {% tab title="Windows" %} 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: ``` mkdir C:\\Temp ``` ``` reg export "HKEY_CURRENT_USER\\Software\\FoolCat" "C:\\Temp\\FoolCatSettings.reg" ``` 4. Prune the registry settings (BuildVersion, LicenseVersion) ``` (Get-Content "C:\\TEMP\\FoolCatSettings.reg") -notmatch '("BuildVersion"|"LicenseVersion")' | Set-Content "C:\\TEMP\\FoolCatSettings.reg" ``` 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: ``` reg import "C:\\Temp\\FoolCattSettings.reg" ``` {% endtab %} {% endtabs %} ## Can I change the size of stills FoolCat creates? {% tabs %} {% tab title="macOS" %} Yes, you can change the size of the stills with the following Terminal command: {% code overflow="wrap" %} ``` defaults write nl.syncfactory.Foolcat.Mac kFFMDefaultsPreferencesCatalogThumbSize -int 1024 ``` {% endcode %} The value sets the maximum dimension of the still’s longest edge. For example, a value of 1024 means the still will fit within a 1024×128 box while preserving its original aspect ratio. {% endtab %} {% tab title="Windows" %} Yes, you can change the size of the stills with the following Terminal (PowerShell) command: {% code overflow="wrap" %} ``` Set-ItemProperty -Path "HKCU:\Software\FoolCat" -Name "SettingsStillResolution" -Type DWord -Value 1024 ``` {% endcode %} The value sets the maximum dimension of the still’s longest edge. For example, a value of 1024 means the still will fit within a 1024×128 box while preserving its original aspect ratio. {% endtab %} {% endtabs %} # Requirements ## Which versions of macOS and Windows are supported? {% tabs %} {% tab title="macOS" %} The [current release](/foolcat/releases) of FoolCat supports macOS `14` and newer.
macOSFoolCat
26 Tahoe Latest release
15 SequoiaLatest release
14 SonomaLatest release
13 Ventura25.1
12 Monterey25.1
11 Big Sur25.1
10.15 Catalina24.1
{% endtab %} {% tab title="Windows" %} 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. {% endtab %} {% endtabs %} # Releases ## FoolCat 26.1 {% tabs %} {% tab title="macOS" %} **FoolCat 26.1 for Mac** (Apr 02, 2026) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20260402180505_v26.1b247/FoolCat_20260402180505_v26.1b247.dmg) **New** * Support for CinemaDNG * Support for R3D NE * Support for Blackmagic URSA Cine Immersive and PYXIS 12K **Improves** * Brings back the fresh lick of paint and support for larger reports introduced in FoolCat 25.3 * Reports now use a simplified HTML structure that loads faster and is more preview- and post-processing-friendly. * Improved support for Canon RAW * The Report theme is now applied to both HTMLs and PDFs **Fixes** * Editing report information is now immediately reflected when generating a report. * Audio tracks were incorrectly counted as audio channels. *** **FoolCat 26.1.1 for Mac** (Apr 10, 2026) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20260410155252_v26.1.1b263/FoolCat_20260410155252_v26.1.1b263.dmg) * Fixes an issue that prevented FoolCat from creating reports (Error 0). {% endtab %} {% tab title="Windows" %} **FoolCat 26.1 for Windows** (Apr 02, 2026) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-26.1.0.120.exe) **New** * Support for CinemaDNG * Support for R3D NE * Support for Blackmagic URSA Cine Immersive and PYXIS 12K **Improves** * Reports now use a simplified HTML structure that loads faster and is more preview- and post-processing-friendly. * Improved support for Canon RAW * The Report theme is now applied to both HTMLs and PDFs **Fixes** * Editing report information is now immediately reflected when generating a report. * Audio tracks were incorrectly counted as audio channels. *** **FoolCat 26.1.1 for Windows** (Apr 09, 2026) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-26.1.1.121.exe) * Fixed a bug that stopped FoolCat from launching when used offline {% endtab %} {% endtabs %} ## FoolCat 25.3 {% tabs %} {% tab title="macOS" %} **FoolCat 25.3 for Mac** (Nov 4, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20251031191214_v25.3b203/FoolCat_20251031191214_v25.3b203.dmg) **New** * FoolCat Pro - [learn more](https://hedge.co/blog/back-to-basics) * The HTML and PDF reports got a fresh lick of paint 🎨 * Support for reports with 100+ clips * ARRICORE and Nikon RAW support * Automate your workflow with the new Scripting feature, with support for both AppleScript and Python. **Fixes** * Some H.264 clips were missing stills — that's fixed. *** **FoolCat 25.3.1 for Mac** (Dec 3, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20251202140448_v25.3.1b207/FoolCat_20251202140448_v25.3.1b207.dmg) * AVC Intra MXFs are showing stills again. * Spanned Sony clips now show the entire duration instead of the duration of the first part. * The FoolCat integration in OffShoot now works correctly again when FoolCat is not also open. *** **FoolCat 25.3.2 for Mac** (Jan 21, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20260121145408_v25.3.2b212/FoolCat_20260121145408_v25.3.2b212.dmg) * Fix for a PDF rendering issue specific to Tahoe 26.2 (Thanks for reporting, everyone).\ This update temporarily reverts the fresh lick of paint and support for larger reports introduced in FoolCat 25.3. We’ll bring those back once everything plays nicely again.\ \ Note: If you’re not on Tahoe, you can skip this update. {% endtab %} {% tab title="Windows" %} **FoolCat 25.3 for Windows** (Nov 4, 2025) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-25.3.0.107.exe) **New** * FoolCat Pro - [learn more](https://hedge.co/blog/back-to-basics) * The HTML and PDF reports got a fresh lick of paint 🎨 * Support for reports with 100+ clips * ARRICORE and Nikon RAW support * Automate your workflow with the new Scripting feature. **Fixes** * Some H.264 clips were missing stills — that's fixed. *** **FoolCat 25.3.1 for Windows** (Dec 23, 2025) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-25.3.1.111.exe) * Fixed a bug that stopped FoolCat from launching when used offline * AVC Intra MXFs are showing stills again (Thanks for reporting, all). * Spanned Sony clips now show the entire duration instead of the duration of the first part (Thanks, Anne-Sophie!). {% endtab %} {% endtabs %} ## FoolCat 25.2 {% tabs %} {% tab title="macOS" %} **FoolCat 25.2 for Mac** (Jul 02, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20250627233935_v25.2b176/FoolCat_20250627233935_v25.2b176.dmg) **New** * Support for DJI D-Log/D-Gamut color space * Support for BlackMagic Design SDK 4.6 * Support for RED SDK 9.0.1 * Support for Panasonic S1II and S1IIE clips recorded by the Blackmagic Video Assist 12G HDR * Enhanced performance for URSA Cine 12K LF and URSA Cine 17K 65 clips **Improved** * Improved tone mapping for Rec.709 and LUT-based color conversions, getting rid of blown out highlights. * Apple-certified support for ProRes and ProRes RAW * Additional metadata (Lens, Sensor FPS, Shutter, White Balance, ISO, Tint) for Canon RAW clips * Anamorphic clip resolution is now reported as de-squeezed. **Fixed** * Some Canon AVC-Intra 10-bit clips displayed a green thumbnail (Thanks, Jamey!) * Incorrect timecode for some ProRes RAW clips (Thanks, Colin!) * Incorrect ISO for some ProRes clips *** **FoolCat 25.2.1 for Mac** (Jul 22, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20250717162734_v25.2.1b186/FoolCat_20250717162734_v25.2.1b186.dmg) * Support for HDE-compressed MXF files from ARRI ALEXA Mini and ALEXA Mini LF cameras * Shutter angle is now displayed for ARRI MXF clips * Fixed a crash that could occur during report creation (thanks for reporting, Joshua and others!) *** **FoolCat 25.2.2 for Mac** (Sep 5, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20250811183459_v25.2.2b190/FoolCat_20250811183459_v25.2.2b190.dmg) * Fixes an issue where FoolCat fails to find clips on Intel Macs.
{% endtab %} {% tab title="Windows" %} **FoolCat 25.2 for Windows** (Jul 02, 2025) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-25.2.0.93.exe) **New** * Support for DJI D-Log/D-Gamut color space * Support for BlackMagic Design SDK 4.6 * Support for RED SDK 9.0.1 * Support for Panasonic S1II and S1IIE clips recorded by the Blackmagic Video Assist 12G HDR * Enhanced performance for URSA Cine 12K LF and URSA Cine 17K 65 clips *** **FoolCat 25.2.1 for Windows** (Jul 22, 2025) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-25.2.1.94.exe) * Support for HDE-compressed MXF files from ARRI ALEXA Mini and ALEXA Mini LF cameras * Shutter angle is now displayed for ARRI MXF clips * Fixed a crash that could occur during report creation (thanks for reporting, Joshua and others!) {% endtab %} {% endtabs %} ## FoolCat 25.1 {% tabs %} {% tab title="macOS" %} **FoolCat 25.1 for Mac** (Apr 04, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20250404182952_v25.1b159/FoolCat_20250404182952_v25.1b159.dmg) * Support for Sony's BURANO Version 2.0 firmware. * A fresh lick of paint 🎨 *** **FoolCat 25.1.1 for Mac** (Jun 04, 2025) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20250529201310_v25.1.1b172/FoolCat_20250529201310_v25.1.1b172.dmg) * Fixed an issue where 10-bit AVC Intra clips displayed green thumbnails. {% endtab %} {% tab title="Windows" %} **FoolCat 25.1 for Windows** (Apr 04, 2025) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-25.1.0.88.exe) **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. {% endtab %} {% endtabs %} ## FoolCat 24.5 {% tabs %} {% tab title="Windows" %} **FoolCat 24.5 for Windows** (Oct 29, 2024) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-24.5.0.65.exe) * Support for Canon RAW * Support for RED V-Raptor \[X] and extended highlights. * Support for Phantom CineRAW {% endtab %} {% endtabs %} ## FoolCat 24.4 {% tabs %} {% tab title="macOS" %} **FoolCat 24.4 for Mac** (Sept 4, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20240902173342_v24.4b148/FoolCat_20240902173342_v24.4b148.dmg) * Support for Blackmagic Cinema Camera 6K. * Support for CODEX High Density Encoding (HDE) MXF files. **FoolCat 24.4.1 for Mac** (Sept 5, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20240904214358_v24.4.1b149/FoolCat_20240904214358_v24.4.1b149.dmg) * Fixed a crash when indexing a folder containing an unsupported audio file.
{% endtab %} {% tab title="Windows" %} **FoolCat 24.4 for Windows** (Sept 4, 2024) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-24.4.0.61.exe) * 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.
{% endtab %} {% endtabs %} ## FoolCat 24.3 {% tabs %} {% tab title="macOS" %} **FoolCat for Mac 24.3** (July 2, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20240702001425_v24.3b144/FoolCat_20240702001425_v24.3b144.dmg) **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. *** **FoolCat for Mac 24.3.1** (July 15, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20240711201906_v24.3.1b145/FoolCat_20240711201906_v24.3.1b145.dmg) * Added support for Sony Burano XAVC HEVC Intra HQ clips. * The green tint issue in SONY FX6 XAVC-I thumbnails has been fixed.
{% endtab %} {% tab title="Windows" %} **FoolCat for Windows 24.3** (July 2, 2024) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-24.3.0.54.exe) **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.
{% endtab %} {% endtabs %} ## FoolCat 24.2 {% tabs %} {% tab title="macOS" %} **FoolCat for Mac 24.2** (May 7, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/production/FoolCat_20240507093023_v24.2b138/FoolCat_20240507093023_v24.2b138.dmg) * 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)
{% endtab %} {% tab title="Windows" %} **FoolCat for Windows 24.2** (May 7, 2024) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-24.2.0.50.exe) * Support for the new SONY Burano camera * Sony RAW clips no longer get reported as X-OCN
{% endtab %} {% endtabs %} ## FoolCat 24.1 {% tabs %} {% tab title="macOS" %} **FoolCat for Mac 24.1** (March 12, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-132.dmg) * FoolCat can now apply [a custom look](/foolcat/color-conversion) (LUT) to the stills in your reports. Alternatively, you can set FoolCat to convert RAW footage to Rec.709 color space automatically.
{% endtab %} {% tab title="Windows" %} **FoolCat for Windows 24.1** (March 12, 2024) - [Download](https://updates.hedge.video/foolcat/windows/updates/FoolCatSetup-24.1.0.48.exe) * Support for Sony X-OCN. * Apply[ a custom look (LUT)](/foolcat/color-conversion) to the stills in your reports. * A new app icon.
{% endtab %} {% endtabs %} ## FoolCat 23.1 May 09, 2023 - A brand-new FoolCat, with many more supported codecs and up to three times faster report generation. [Learn more](https://blog.hedge.video/the-new-foolcat?ref=docs)... {% tabs %} {% tab title="macOS" %} **FoolCat for Mac 23.1** (May 09, 2023) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-95.dmg) 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 *** **FoolCat for Mac 23.1.1** (May 16, 2023) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-101.dmg) * 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. *** **FoolCat for Mac 23.1.2** (May 31, 2023) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-105.dmg) * 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. *** **FoolCat for Mac 23.1.3** (August 10, 2023) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-113.dmg) * 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. *** **FoolCat for Mac 23.1.4** (November 30, 2023) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-118.dmg) * 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. *** **FoolCat for Mac 23.1.5** (February 01, 2024) - [Download](https://updates.hedge.video/foolcat/macos/updates/FoolCat-125.dmg) * 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. {% endtab %} {% endtabs %} ## Foolcat 21.2 September 01, 2021 - [Foolcat for Mac 21.2.5](https://updates.hedge.video/foolcat/macos/updates/Foolcat-70.dmg) | [Foolcat for Windows 21.2.2](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-21.2.2.35.exe) * 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 May 19, 2021 - [Foolcat for Mac 21.1](https://updates.hedge.video/foolcat/macos/updates/Foolcat-63.dmg) | [Foolcat for Windows 21.1](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-21.1.0.26.exe) * 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 December 18, 2020 - [Foolcat for Mac 20.4](https://updates.hedge.video/foolcat/macos/updates/Foolcat-58.dmg) | [Foolcat for Windows 20.4.1](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-20.4.1.23.exe) * 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 September 25, 2020 - [Foolcat for Mac 20.3.2](https://updates.hedge.video/foolcat/macos/updates/Foolcat-56.) | [Foolcat for Windows 20.3.1](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-20.3.1.21.exe) * Added support for RED Komodo camera (R3D SDK V7.3.4) ## Foolcat 20.2 July 23, 2020 - [Foolcat for Mac 20.2](https://updates.hedge.video/foolcat/macos/updates/Foolcat-51.dmg) | [Foolcat for Windows 20.2](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-20.2.0.16.exe) * 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 May 26, 2020 - [Foolcat for Mac 20.1.1](https://updates.hedge.video/foolcat/macos/updates/Foolcat-40.dmg) | [Foolcat for Windows 20.1.1](https://updates.hedge.video/foolcat/windows/updates/FoolcatSetup-20.1.1.11.exe) * A brand new version of Foolcat, for both Mac and Windows. ## Legacy Downloads Foolcat 6 - [Download](https://updates.hedge.video/foolcat/macos/updates/Foolcat-v6.zip) Foolcat 5 - [Download](http://foolcolor.net/foolcat.zip) # Hedge Looking for the Hedge documentation? Starting October 1, 2023, Hedge version 23.2 is now known as OffShoot. [You'll find OffShoot's documentation here.](/offshoot) {% hint style="info" %} OffShoot's documentation is applicable for all Hedge versions. {% endhint %} # Releases {% hint style="info" %} Looking for newer releases? Starting with 23.2, Hedge is now called OffShoot: [Releases](/offshoot/releases) {% endhint %} ## 23.1 - ProGrade {% tabs %} {% tab title="macOS" %} **Hedge for Mac 23.1.2** (September 26, 2023) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1478.dmg) * 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) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1376.dmg) * 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) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1370.dmg) * Sanitize your ProGrade media directly in Hedge with the new [ProGrade Integration](/offshoot/integrations/prograde). * Hedge 23.1 drops support for macOS 10.14 or older, so make sure you are on MacOS 10.15 or newer. {% endtab %} {% tab title="Windows" %} **Hedge for Windows 23.1** (March 07, 2023) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-23.1.0.729.msi) * Sanitize your ProGrade media directly in Hedge with the new [ProGrade Integration](/offshoot/integrations/prograde). * Broken media detection; Hedge will show a warning when zero-byte media files are detected on the Source. {% endtab %} {% endtabs %} ## 22.3 - Speed 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! [Learn more...](https://blog.hedge.video/speed-2dot0?ref=docs) {% tabs %} {% tab title="macOS" %} **Hedge for Mac 22.3.2** (January 19, 2023) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1357.dmg) * 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) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1351.dmg) * 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) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1339.dmg) * 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 {% endtab %} {% tab title="Windows" %} **Hedge for Windows 22.3.1** (January 19, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.3.1.721.msi) * 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) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.3.0.717.msi) * 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. {% endtab %} {% endtabs %} ## 22.2 - iconik 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. [Learn more...](https://blog.hedge.video/iconik/) {% tabs %} {% tab title="macOS" %} **Hedge for Mac 22.2.9** (December 07, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1336.dmg) * 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.
**Hedge for Mac 22.2.8** (October 24, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1316.dmg) * Official support for macOS 13 Ventura!\ **Hedge for Mac 22.2.7** (September 5, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1303.dmg) * Fix for a rare case where preset values would be cleared after a transfer.
**Hedge for Mac 22.2.6** (September 1, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1299.dmg) * Custom date elements (available in [Hedge Pro](broken://pages/1k3C8g6nCJPPZOqAi7ax)) now automatically use the system settings if no value is provided. **Hedge for Mac 22.2.5** (August 30, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1294.dmg) * 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.
**Hedge for Mac 22.2.4** (August 11, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1282.dmg) * Clip Review (a Hedge Pro feature) was not showing any stills, that's fixed.
**Hedge for Mac 22.2.3** (July, 08, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1278.dmg) * Fixed an edge-case that caused Hedge to crash when adding Transfers (Thanks for sending in those crash reports, all!).
**Hedge for Mac 22.2.2** (June, 29, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1272.dmg) * 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.
**Hedge for Mac 22.2.1** (April 21, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1238.dmg) * 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.
**Hedge for Mac 22.2** (April 13, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1232.dmg) * New integration: iconik. * Support for ASC MHLs for Pro licenses. [Reach out](mailto:hello@hedge.video) if you would like a trial. * The [Hedge API](https://docs.hedge.video/hedge/features/automation/api) no longer uses a token, as it's now tied to Pro licenses. This also applies to [Hedge Helper](https://docs.hedge.video/hedge/features/automation/hedge-helper) which uses the API. [Reach out](mailto:hello@hedge.video) if you need access. {% endtab %} {% tab title="Windows" %} **Hedge for Windows 22.2.6** (November 22, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.6.709.msi) * Enhance your workflow by automatically launching scripts based on events like added disks and completed transfers.
**Hedge for Windows 22.2.5** (October 20, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.5.704.msi) * 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). **Hedge for Windows 22.2.4** (August 25, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.4.702.msi) * 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.
**Hedge for Windows 22.2.3** (August 11, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.3.697.msi) * 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).
**Hedge for Windows 22.2.2** (June, 29, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.1.695.msi) * 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. **Hedge for Windows 22.2.1** (April 21, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.1.679.msi) * 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.
**Hedge for Windows 22.2** (April 13, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.2.0.678.msi) * New integration: iconik. * Support for ASC MHLs for Pro licenses. Let us know at if you would like a trial. * The Hedge API no longer uses a token, as it's now tied to Pro licenses. {% endtab %} {% endtabs %} ## 22.1 - Elements 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 ✨ [Learn more...](https://blog.hedge.video/elements?ref=whatsnew) {% tabs %} {% tab title="macOS" %} **Hedge for Mac 22.1.3** (Feb 22, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1207.dmg) * 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. **Hedge for Mac 22.1.2** (Feb 8, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1202.dmg) * 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.
**Hedge for Mac 22.1.1** (Feb 3, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1197.dmg) * 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.
**Hedge for Mac 22.1** (Feb 1, 2022) - [Download](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1195.dmg) {% endtab %} {% tab title="Windows" %} **Hedge for Windows 22.1.1** (Feb 8, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.1.1.668.msi) * 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! **Hedge for Windows 22.1** (Feb 1, 2022) - [Download](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-22.1.0.658.msi) {% endtab %} {% endtabs %} ## 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. * [Download Hedge for Mac 21.3.2](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1178.dmg) ## 21.2 - Scratch July 27, 2021 — Automatically add your media to SCRATCH projects, add metadata, and get your dailies going faster than ever. * [Learn more...](https://blog.hedge.video/scratch?ref=docs) * [Download Hedge for Mac 21.2.4](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1140.dmg) * [Download Hedge for Windows 21.2](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-21.2.0.642.msi) ## 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. * [Learn more...](https://blog.hedge.video/auto-label?ref=whatsnew) * [Download Hedge for Mac 21.1.3](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1102.dmg) * [Download Hedge for Windows 21.1](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-21.1.0.629.msi) ## 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. * [Learn more...](https://blog.hedge.video/sorting?ref=docs) * [Download Hedge for Mac 20.4.9](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-1058.dmg) * [Download Hedge for Windows 20.4.1](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-20.4.1.614.msi) ## 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. * [Learn more...](https://blog.hedge.video/presets?ref=docs) * [Download Hedge for Mac 20.3.7](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-992.dmg) * [Download Hedge for Windows 20.3](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-20.3.0.608.msi) ## 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. * [Learn more...](https://blog.hedge.video/checkpoint-2-0-f86cb4fd5031/) * [Download Hedge for Mac 20.2.7](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-960.dmg) * [Download Hedge for Windows 20.2](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-20.2.0.593.msi) ## 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 * [Learn more...](https://blog.hedge.video/the-all-new-connect-15ae83d0b54b/) * [Download Hedge for Mac 20.1.2](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-913.dmg) * [Download Hedge for Windows 20.1.2](https://updates.hedge.video/hedge/windows/updates/HedgeForWindows-20.1.2.590.msi) ## 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. * [Learn more...](https://blog.hedge.video/hedge-codex-e74d3ce82797/) * [Download Hedge for Mac 19.4.8](https://updates.hedge.video/hedge/macos/updates/HedgeForMac-902.dmg) {% hint style="info" %} Releases older than 19.4.8 are no longer available, as the license provider we previously used has gone offline. {% endhint %} ## 19.3 - Filter & Rename Jul 23, 2019 － Start organizing like a pro: rename your media, skip unwanted files — all during a transfer. * [Learn more...](https://blog.hedge.video/filter-rename-7f68cdf5c267?ref=docs) ## 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. * [Learn more...](https://blog.hedge.video/transfer-straight-into-frame-io-65d422640b7c?ref=docs) ## 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. * [Learn more...](https://blog.hedge.video/queueing-transfers/?ref=docs) ## 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. * [Learn more...](https://blog.hedge.video/it-s-all-about-the-source/?ref=docs) ## 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. * [Learn more...](https://blog.hedge.video/save-time-copy-just-what-s-new/?ref=docs) ## 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. * [Read more...](https://blog.hedge.video/hedge-18-1---the--car-wash--update/?ref=docs) ## 17.14 - Create Clip Catalogs with Foolcat New integration; Foolcat generates clean camera reports with thumbnails and extended metadata in HTML and PDF format. * [Learn more...](https://blog.hedge.video/integration--2--foolcat/?ref=docs) ## 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. * [Learn more...](https://blog.hedge.video/hedge-integrations-parashoot/?ref=docs) ## 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 * [Learn more...](https://blog.hedge.video/labels-and-collections-4b9e727b08d8/?ref=docs) ## 17.1 - Hedge for Windows *Hedge for Windows* is here! * [Learn more...](https://blog.hedge.video/hedge-for-windows-is-here-/?ref=docs) ## 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 # 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. 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 [License Manager](https://account.hedge.video/). ## What does extending my license cost? That depends on the amount of activations. Log in to the [License Manager](https://account.hedge.video), select your OffShoot license and click Extend. ## What is OffShoot's floating license? [Floating licenses](/offshoot/features/floating-licenses) 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. ## 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? That depends on the amount of activations. Log in to the [License Manager](https://account.hedge.video), select your OffShoot license and click Upgrade To Pro. ## Can I upgrade and extend at the same time? Yes, and it's discounted even more. Log in to the [License Manager](https://account.hedge.video), select your OffShoot license and click Extend to find out what the options are for your license. ## Why can't I reduce my activations to 1 in the Extend Checkout? That likely means you have multiple machines activated with 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. ## 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? 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 ([23.1.2](https://docs.hedge.video/hedge/releases)) with the same license key. ## How do I upgrade to Pro? In OffShoot, go to `Settings > License` and hit `Upgrade to Pro`, or go to the [License Manager](https://account.hedge.video/?ref=blog.hedge.video), log in with your email or license key, select your license, then [hit `Upgrade to Pro`](/general/licenses/the-license-manager#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? Yes, but you'll need [an OffShoot Pro license](broken://pages/1k3C8g6nCJPPZOqAi7ax). ## Where can I download the last version of Hedge? All previous releases of Hedge are (and will remain) available under [Releases](/hedge/releases). ## 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`. {% hint style="danger" %} Do so at your own risk. {% endhint %} *** Still have questions? Let us know: # Mimiq Mimiq enables Bin Locking for non-Avid storage. It's a standalone app for teams working with Avid Media Composer, enabling collaborative workflows on: * SMB, NFS, and AFP shares on your NAS * Cloud drives, such as a LucidLink Filespaces and Suite Studios (Available in [Mimiq Pro](#mimiq-pro)) * [Workspaces created from any type of storage](/mimiq/workspaces) (Available in [Mimiq Pro](#mimiq-pro)) With Mimiq, Media Composer recognizes these drives as *third-party shared storage* so teams of Avid editors can work together using the same projects, bins and media. ## Mimiq Pro Mimiq Pro enables remote and hybrid collaborative workflows by letting you use non-network drives alongside SMB, NFS, and AFP shares. Mimiq Pro allows you to create [Workspaces](/mimiq/workspaces) from any type of storage – such as a RAID, SAN (e.g. Quantum StorNext), LucidLink Filespaces, Suite Studios and even local folders – which Media Composer treats as independent NEXIS volumes. Mimiq Pro also provides NEXIS Coexistence, allowing one to utilize any type of storage for Bin Locking while simultaneously using a NEXIS. ## Avid Requirements Independent of Mimiq (Mimiq doesn't have many requirements aside from fast storage), 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: {% content-ref url="/pages/atKCPoJF8dftKHkAHLWj" %} [Avid's Requirements](/mimiq/requirements/avids-requirements) {% endcontent-ref %} # 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. Mimiq offers both Bin Locking and Bin Refresh for a multitude of [storage options](/mimiq/supported-storage). ## Lock States in Media Composer
Lock ColorWho'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. {% hint style="info" %} 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 🔵. {% endhint %} # Supported Storage ## NAS With Mimiq, Bin Locking works out of the box on network shares that use SMB (including DFS-backed SMB paths), AFP, or NFS protocols. These are typically NAS shares, but can also be a Mac or PC that shares drives or folders. ## SAN Through the [Workspaces](/mimiq/workspaces) feature, Mimiq can enable any folder on a SAN or other block-based volumes to work with Media Composer. Workspaces is a [Pro](https://docs.hedge.video/mimiq/standard-vs.-pro) feature. ## StorNext StorNext is fully supported and usable with Avid Media Composer through the [Workspaces](/mimiq/workspaces)feature. Also useful: [StorNext Permissions](/mimiq/workspaces/stornext-permissions) ## NEXIS Mimiq packs a technology dubbed NEXIS Coexistence, which allows you to use any combination of NEXIS and third-party storage at the same time. NEXIS Coexistence is a [Pro](/mimiq/standard-vs.-pro) feature. ## Facilis Mimiq fully supports Facilis' bin locking technology, allowing you to use non-Facilis storage simultaneously. Facilis Coexistence is a [Pro](/mimiq/standard-vs.-pro) feature. ## Qumulo Both Qumulo's on-premise and AWS offerings are fully supported by Mimiq. As Qumulo shares connect via SMB or NFS, a non-Pro license suffices, with no additional setup requirements. ## Cloud Drives {% hint style="info" %} Cloud Drives require a [Pro](https://docs.hedge.video/mimiq/standard-vs.-pro) license. {% endhint %} Remote workflows often use cloud providers like LucidLink and Suite Studios. Mimiq supports both of these providers by recognizing their mount points and enabling them for Media Composer. All cloud drive providers regularly release updates for their macOS and Windows clients. A new Mimiq release typically accompanies each update. Most client updates don't require much work on our end; in such cases, we'll release a minor Mimiq update. When a client update does require elbow grease, it's made available as a major update, which might require a license extension. To avoid being caught out, before updating your cloud drive client, verify that your Mimiq license is eligible for the corresponding Mimiq release. You can track which client update is supported by which version of Mimiq in the [Releases](/mimiq/releases) section. \ \ In the rare case that a cloud provider releases an update without prior notice (e.g., emergency security updates), you can safely install their update, provided *your license is eligible for updates and support*. In such cases, we will opt to release a minor update to Mimiq, thereby avoiding the need for a license extension. ## Local Drives Although it's an esoteric workflow, Mimiq Pro can be utilized to turn a local folder living on an SSD or RAID into a volume that works with Media Composer. This can for instance be used when a separate syncing mechanism is employed between computers, like Resilio. As the biggest bottleneck here will be your connection and not Mimiq, test rigorously. Your mileage may vary a lot. # Standard vs. Pro Mimiq has two license types: Standard and Pro. | Bin Locking & Bin Refresh | Standard | Pro | | ---------------------------------------------------------- | -------- | --- | | [SMB, AFP, NFS](/mimiq/bin-locking#smb-nfs-and-afp) | ✓ | ✓ | | [RAID, SSD, SAN](/mimiq/bin-locking#raid-ssd-and-san) | - | ✓ | | [Quantum StorNext](/mimiq/workspaces/stornext-permissions) | - | ✓ | | [LucidLink](/mimiq/bin-locking#cloud-drives) | - | ✓ | | [Suite Studios](/mimiq/bin-locking#cloud-drives) | - | ✓ | | Features | Standard | Pro | | ----------------------------------------------------------------------------------------------------------- | -------- | --- | | [Remote Deactivations](/general/licenses/the-license-manager#managing-activations) | ✓ | ✓ | | [Online License Manager](/general/licenses/the-license-manager) | ✓ | ✓ | | [Managed Workspaces](https://docs.hedge.video/mimiq/pages/pYQIoJdaHk7kRcdJCwTV#local-vs.-shared-workspaces) | - | ✓ | | [NEXIS Coexistence](/mimiq/bin-locking#nexis) | - | ✓ | | [Facilis Coexistence](/mimiq/bin-locking#facilis) | - | ✓ | | [Remote Deployment](/mimiq/deployment) | - | ✓ | | [Local License Server](/general/licenses/local-license-server) | - | ✓ | | [macOS Mojave ](/mimiq/mc-2018-and-mojave) | - | ✓ | | [MC 2018 ](/mimiq/mc-2018-and-mojave) | - | ✓ | | Priority Support | - | ✓ | # Getting Started 1. [Install and activate Mimiq.](#install-and-activate-mimiq) 2. [Mount any eligible volumes.](#mount-any-eligible-volumes) 3. [Launch Mimiq.](#launch-mimiq) 4. [Launch Media Composer.](#launch-media-composer) 5. [Confirm Bin Locking is activated](#confirm-bin-locking-is-activated-in-avid-media-composer). ## Install and activate Mimiq Download and install Mimiq: * macOS - * Windows - ## Mount any eligible volumes 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 [Workspaces](/mimiq/workspaces) will be mounted as well. Cloud volumes, such as LucidLink or Suite Studios, are connected using their respective apps. {% hint style="info" %} NFS in macOS - if you need more control over creating or mounting NFS shares in macOS, you can use something like [NFS Manager](https://www.bresink.com/osx/NFSManager.html). {% endhint %} ## 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)
{% hint style="info" %} 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. {% endhint %} ✅ `Settings > Project > General > Enable Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS`
# Workspaces Mimiq Workspaces allows you to quickly remount any folder as a drive that Media Composer can use for Bin Locking. This is especially useful when collaborating with Avid on a SAN (e.g. Quantum StorNext), or when working with cloud storage like LucidLink or Suite Studios. {% hint style="info" %} While Workspaces can be used with NAS systems, shares accessed over SMB, AFP, or NFS are automatically detected for Bin Locking. As a best practice, export multiple shares using your NAS management software. {% endhint %} ## Adding a Workspace 1. Click the Mimiq icon in the Menu Bar (macOS) or System Tray (Windows), then `+ Add Workspace`.
2. Select a folder to create a Workspace, then click `Select` (macOS) or `Select Folder` (Windows). 3. 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, Media Composer will not be running while you creating Workspaces, as this can cause unexpected behaviour. ## Local vs. Shared Workspaces Mimiq supports both local and shared Workspace configurations. The local Workspace configuration applies to you, as an individual user, and is stored in a JSON on your computer at one of these locations: **macOS**\ `~/Library/Application Support/Mimiq/Workspaces/MimiqWorkspaces.json` **Win**\ `C:\Users\\AppData\Roaming\Mimiq\Workspaces.json` \ \ This is used to remember your Workspace list and to auto-mount chosen Workspaces on app start. Shared Workspaces extend this concept by storing a centralized JSON on the root level of the parent volume. This allows everybody in a team to use the same Workspace definitions. On the parent volume you'll find the Mimiq Enabled JSON here:\ `/Mimiq Settings/MimiqEnabled.json` ## Workspaces on Cloud Drives Remote workflows utilizing cloud drives like LucidLink and Suite Studios can also use Workspaces. However, keep in mind that Media Composer won't work well if it sees your storage twice. If you use a Workspace on a folder somewhere on your cloud drive, be sure to [disable](#disabling-a-workspace) the main volume in Mimiq. ## Search, Sort and Filter Search, sort, and filter helps teams quickly find the right lockable network share or Workspace. Type to search, then hit escape to clear. Sort and filter are available via the pop-out menu.
## Sharing a Workspace {% hint style="info" %} This only needs to be done once by one team member. {% endhint %} To share a Workspace with your team: 1. Ensure you have top-level write access to the storage volume. 2. Add the Workspace using Mimiq. 3. Click **Share**, then **Enable for Everyone**.
## Workspace Groups Workspace Groups make it easy to locate and mount the Workspaces associated with a particular project or job. Grouping is especially useful when your team has a large number of Workspaces.
1. Click the context menu for the Workspace you wish to group. 2. Click `Add to Group` then `New Group...` or choose an existing group.
2. Choose a name for the new group. 3. Assign more Workspaces to the group, as required. 4. Optional: share the group to your team.
Administrator notes: * Workspaces can be a member of one group at once. * Groups can span multiple parent volumes. * Group membership emerges from the presence of the group key in all visible config files. * Removing a group will not affect or delete Workspaces associated with it. ## Config Files Mimiq saves all information about Shared Workspaces in a JSON file on your storage, in a folder in the root of your drive. This folder is named `Mimiq Settings` , and contains a file named `MimiqEnabled.json` . {% hint style="info" %} If there are no write permissions for the root of your drive, Mimiq won't be able to Share Workspaces. You can manually create the `Mimiq Settings` folder to enable Shared Workspaces on your storage. {% endhint %} This JSON file is human-readable and can be manually edited by experienced users (e.g. System Administrators or Post Supervisors), though it's usually managed automatically by Mimiq. The example below shows two Workspaces. One is disabled, the other is not. Both are members of the same group. ```json { "version": "26.2.0", "ignore": false, "workspaces": [ { "path": "workspace1", "group": "example group", "disabled": true }, { "path": "workspace2", "group": "example group", "disabled": false } ] } ``` The table below explains the usage of each key:
NameRequiredDescription
versionYesThe version string of Mimiq used to write the workspace config.
ignoreYesBoolean, defines if the root of the volume should be ignored by Mimiq. This is useful when working with LucidLink Classic.
workspacesYesThe list of workspace objects.
pathYesThe relative path to the workspace, not including the volume name.
groupNoUsed to specify the workspace group.
nameNoIf defined, this value will be used for the name of the Workspace. If undefined, the last component of the path is used (i.e. the folder name). This key is supported on macOS only.
## Practical Limits Workspaces are powerful, but should be used sparingly. On macOS, each active Workspace introduces a small overhead to your system's bandwidth. On Windows, you're limited by the number of free drive letters. {% tabs %} {% tab title="macOS" %} The usable amount of simultaneously active Workspaces depends on your system resources. As Workspaces on macOS rely on macFUSE as an intermediate, there's a limitation to how many Workspaces can be used simultaneously. Our tests have shown a maximum of 8 Workspaces is practical. However, as this number is dependent on your hardware and system load, it's possible to increase or decrease this amount. Using `Terminal.app`, set the maximum number of Workspaces that can be enabled simultaneously: #### Override the default Workspaces limit ```sh defaults write video.hedge.Mimiq.Mac workspacelimit -int 8 ``` Then, load the new setting by relaunching Mimiq. Use this command to check the current Workspaces limit: ```sh defaults read video.hedge.Mimiq.Mac workspacelimit ``` It's just as easy to reset the amount back to the default value of 8: ```sh defaults delete video.hedge.Mimiq.Mac workspacelimit ``` {% endtab %} {% tab title="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" ``` {% endtab %} {% endtabs %} ## Disabling a Workspace Sometimes, you don't want Media Composer to interact with every Lockable Volume. In that case, you can `Disable` a Workspace. Here, it's in the context of a Workspace, but `Disable` is available for all lockable volumes. 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 temporarily renders it unavailable in Media Composer without removing it from altogether. You may want to disable a Workspace to simplify media management by reducing the number of volumes Media Composer can read from or 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. ## Workspace Discovery From the hamburger menu, click `Scan for workspaces...` then locate the volume or folder you wish to scan. Mimiq will treat any parent folder containing `Avid MediaFiles` as a Workspace candidate. When the scan completes, select the Workspaces you want to add.
## SANFusion Detection Workspace Discovery is trained to automatically detect `SFWS` bundles. You can easily spot a SANFusion bundle by the pink icon displayed on the right-hand side.
# 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 macFUSE is a macOS kernel extension used to create virtual filesystems. It's built and maintained by **Benjamin Fleischer** ([https://osxfuse.github.io](https://osxfuse.github.io/)). Mimiq automatically downloads the correct macFUSE installer for your OS. Newer systems running macOS 26 Tahoe require [macFUSE 5](https://hedge.video/external/mimiq/fuse26), or newer. Older systems, like Intel Macs, you might need to download an older version of macFUSE at . {% hint style="danger" %} If your Mac is managed through MDM, stop now and contact your System Administrator. The following steps below will not apply when using MDM. {% endhint %} #### 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](#install-macfuse "mention"). {% hint style="info" %} 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. {% endhint %} 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`. ![](/files/iQpWVTttFHTixPFsVTRG) 5. Click `Security Policy...` ![Select the disk and click Security policy](/files/VIYqdNeq42huzbXa5emf) 6. Select `Reduced Security`, then enable:\ `Allow user management of kernel extensions from identified developers` . ![](/files/94ztFND4lKt7Er40H2IK) 7. Click `OK`. 8. In the menu bar, select `Shut Down`. 9. 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.
2. Click `Install`. Mimiq downloads a DMG with the macFUSE installer, then opens it for you. 3. 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: {% tabs %} {% tab title="macOS 13 and newer" %} 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. {% endtab %} {% tab title="macOS 12" %} 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. {% endtab %} {% tab title="macOS 11 and older" %} 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`. {% endtab %} {% endtabs %} Once macFUSE is installed, you're ready to [add your first Workspace](#add-a-workspace). ✅ #### Still no success? Try loading the kernel extension manually in Terminal: {% tabs %} {% tab title="macOS 11 and newer" %} `sudo /usr/bin/kmutil load -p /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext` {% endtab %} {% tab title="macOS 10.15.7" %} `kextload /Library/Filesystems/macfuse.fs/Contents/Extensions/10.15/macfuse.kext` {% endtab %} {% endtabs %} 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. # StorNext Permissions Avid has strict expectations when it comes to permissions, which is not always obvious when working with SAN storage like StorNext. While there are multiple ways to skin this cat, here's a proven permissions model when using Stornext with Media Composer. ## Folder Structure In this folder structure example, the Project Folder is the folder you turn into a [Workspace](/mimiq/workspaces). * SAN volume * Avid Folder * [Project Folder](/mimiq/workspaces) * Avid Projects * Avid MediaFiles ## Client Permissions Set the `umask` settings of each computer to `002` so that the default permissions of a newly created file will be `775`, which means the `owner` and `group` will be able to edit. ## Server Permissions | Folder | Other ("others", "world") | Assigned Users | | --------------- | ------------------------- | -------------- | | SAN volume | Read | | | Avid Folder | No Access | Read | | Project Folder | Read/Write\* | | | Avid Projects | Read/Write | | | Avid MediaFiles | Read/Write | | An alternative for the `Project Folder` permission is to set a group sticky bit on the group folder with `chmod g+s Project Folder` . This will cause all files and folders to have the same group id. That way, you don’t have to work with the `Other` permissions, and it will also open up the possibility to use StorNext’s quota system if required. (Big thanks to Nathan Fleming for the help) # Workspace 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`? A SAN volume as is, is not compatible with Avid. You must add a folder on the SAN as a Workspace instead. As long as you have `read` and `write` permissions to that share, once you [add a folder from your SAN as a Workspace](#add-a-workspace), Mimiq will enable Bin Locking for that folder. ### Why is the option to Share a Workspace disabled? Your Workspace is likely created on a volume where you do not have write permissions for the root. That makes it impossible for Mimiq to create a `Mimiq Settings` folder to store the Workspaces JSON files in. Either create the `Mimiq Settings` folder manually (easiest) or ensure you gain write permissions for the root folder of your storage (preferred). ### Why can't a Workspace be created using the root of a drive? Because Avid volumes require write permissions, and the root of shared storage very often doesn't allow for that. Therefore, each Workspace should be staged from a subfolder—not from the parent volume (or "root") itself. ### Why is some of my media appearing in the wrong folder? Is your media intermittently appearing in a `1` folder, instead of a `hostname.1` folder? It is likely that you created a Workspace from the root of an external drive, which is a no-go, especially if it's already home to an Avid MediaFiles directory. Although Media Composer should always honour your Media Creation preferences, in this specific case that won't always happen. Some background: Avid media can be stored on many types of drive, including direct-attached storage formatted with HFS+, APFS, or NTFS. In some workflows, we've seen users create a Workspace of the root of the drive, then layer a sync service on top, syncing the whole drive to their co-editors. This will trip up Media Composer into seeing an Avid-compatible volume (the Workspace) and the same volume as local storage. You want to avoid that by all means, as now all media exists twice. If you need to sync two drives, sync the Workspace folders, and [don't create Workspaces using the root of the drive](#why-cant-a-workspace-be-created-using-the-root-of-a-drive). ### Why do Workspaces need to be staged from a subfolder on the parent volume? Avid media can be stored on many types of storage, including direct-attached devices formatted with HFS+, APFS, or NTFS. In some workflows, users choose to stage their Mimiq Workspace on this kind of storage, with a sync service layered on top. This works well, but there’s a caveat. Each Mimiq Workspace must be staged from a subfolder on the parent volume. If not, Media Composer (especially on macOS) will detect two volumes with the same name and Avid MediaFiles directory. This can cause unexpected behavior when importing, consolidating, or transcoding clips. ### Why am I asked to extend Mimiq when using LucidLink or Suite Studios? You have a too-new LucidLink client installed, one that's not compatible with your installed version of Mimiq. First, check if you are eligible for updates. If not, you'll have to either extend your Mimiq license, or downgrade your LucidLink client. Before updating your LucidLink client, always check the [Releases](https://docs.hedge.video/mimiq/releases) page to check which version of Mimiq is required. ### macOS keeps telling me `System Extension Blocked` after installing macFUSE. What can I do? {% hint style="danger" %} If your Mac is managed through MDM, stop now and contact your System Administrator. {% endhint %} Starting with 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. Once your Mac is fully powered down, [power up your Mac again in Recovery mode](https://support.apple.com/guide/mac-help/intro-to-macos-recovery-mchl46d531d6/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. [Now you can approve macFUSE](#approving-macfuse-in-macos), and any other existing system or kernel extensions, to load in macOS. ### Why are drive labels not displayed in File Explorer for some Workspaces? {% hint style="info" %} This only concerns Windows users. {% endhint %} 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. # Deployment Mimiq is in use by a lot of facilities with hundreds of edit suites, so we made it easy to deploy Mimiq at scale. We strongly suggest using an MDM solution to set up automated deployment of license keys, to use [Shared Licenses](/general/licenses/shared-licenses), or to set up a [Local License Server](/general/licenses/local-license-server). ## Activating Mimiq Activating a license can be done via the API: ``` mimiq://activate?key=[your license key] ``` Deactivation works via the same mechanism: ``` mimiq://deactivate ``` ## Autostart Mimiq By default, Mimiq launches when you log into your computer, but you can control whether Mimiq autostarts. {% tabs %} {% tab title="macOS" %} 1. In `Terminal.app`, tell Mimiq whether or not to autostart when you log into macOS. #### Disable autostart ```sh defaults write video.hedge.Mimiq.Mac launchAtLogin -bool false ``` #### Enable autostart ```sh defaults write video.hedge.Mimiq.Mac launchAtLogin -bool true ``` 2. 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: ```sh 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. {% endtab %} {% tab title="Windows" %} 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`). ```powershell 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: ```powershell Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run" -Name "Mimiq" ``` {% endtab %} {% endtabs %} ## Don't show the Mimiq UI {% hint style="info" %} 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). {% endhint %} {% tabs %} {% tab title="macOS" %} 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 ```sh defaults write video.hedge.Mimiq.Mac disableWindowPopup -bool true ``` #### Enable displaying the list of volumes and workspaces ```sh defaults write video.hedge.Mimiq.Mac disableWindowPopup -bool false ``` 2. 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: ```sh defaults read video.hedge.Mimiq.Mac disableWindowPopup ``` * `disableWindowPopup = 1` - Mimiq will not display the list of volumes and Workspaces when you log into macOS, [even if Mimiq launches when you log in.](#autostart) * `disableWindowPopup = 0` - Mimiq will display the list of volumes and Workspaces when you log into macOS. {% endtab %} {% tab title="Windows" %} Use PowerShell to add this Registry key – `StartupWindowPopupEnabled` – then set it to `0`. ```powershell 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: * `0` - Mimiq will not display the list of volumes and Workspaces when you log into Windows, [even if Mimiq launches when you log in.](#autostart) * `1` - Mimiq will display the list of volumes and Workspaces when you log into Window. To remove the `StartupWindowPopupEnabled` Registry key: ```powershell Remove-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "StartupWindowPopupEnabled" ``` {% endtab %} {% endtabs %} ## Suppress App Updates {% hint style="info" %} 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). {% endhint %} {% tabs %} {% tab title="macOS" %} 1. In `Terminal.app`, tell Mimiq whether or not to display app update notifications after it launches. #### Disable app update notifications ```sh defaults write video.hedge.Mimiq.Mac disableUpdateNotifications -bool true ``` #### Enable app update notifications ```sh defaults write video.hedge.Mimiq.Mac disableUpdateNotifications -bool false ``` 2. 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. ```sh 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. {% endtab %} {% tab title="Windows" %} Use PowerShell to add this Registry key – `CheckForUpdatesOnStartupEnabled` – then set it to `0`. ```powershell 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: ```powershell Remove-ItemProperty -Path "HKCU:\Software\Mimiq" -Name "CheckForUpdatesOnStartupEnabled" ``` {% endtab %} {% endtabs %} ## Managing Workspaces Full docs on Workspace Management can be found [here](https://docs.hedge.video/mimiq/pages/pYQIoJdaHk7kRcdJCwTV#local-vs.-shared-workspaces). # MC 2018 & 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 * [A Mimiq Pro license](http://hedge.video/mimiq/pricing) * An Intel Mac (*not* Apple silicon) * macOS 10.14.x * [A version of Media Composer qualified for macOS 10.14.x](https://kb.avid.com/pkb/articles/en_US/Compatibility/en267087) * A `Media Composer | Ultimate` (or beyond) subscription or a `Perpetual` license ## Getting Started 1. [Get a Mimiq Pro license](http://hedge.video/mimiq/pricing) 2. Download Mimiq 18.1: {% hint style="success" %} {% endhint %} 3. [Mount any eligible volumes.](#mount-any-eligible-volumes) 4. Launch Mimiq. 5. Launch Media Composer. 6. [Confirm Bin Locking is activated](#confirm-bin-locking-is-activated-in-avid-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`. {% hint style="success" %} Need Mimiq to launch in macOS automatically on startup? Add it to `System Preferences > Users & Groups > (Your macOS Account) > Login Items` {% endhint %} ### 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 {% hint style="info" %} Mimiq 18.1's UI does not list the eligible volumes with Bin Locking activated. {% endhint %} ### 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. Apple discontinued support for macOS Mojave `10.14` in November 2021. The final update for macOS Mojave is [Security Update 2021-005 (Mojave)](https://support.apple.com/kb/DL2078?locale=en_US), which results in `Version 10.14.6 (18G9323)`. Avid ended the development of Media Composer 2018.12.15 on December 31, 2020, and [officially ended support](https://kb.avid.com/pkb/articles/en_US/faq/Avid-Supported-Software-Releases#MediaComposer) on December 31, 2021. 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? macOS Mojave is incompatible with Apple silicon Macs. If you are on Apple silicon, use the current Mimiq release: [Releases](/mimiq/releases) ### 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. You can [locate your Mimiq Pro license key](/general/licenses/the-license-manager#locating-activation-numbers-license-keys) and [confirm the number of available activations on your license](/general/licenses/the-license-manager#viewing-activations) through the Hedge License Manager (). If you purchased a standard Mimiq license, [you can upgrade your license to Mimiq Pro](/general/licenses/the-license-manager#upgrade-to-pro) through the Hedge License Manager. ### 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? Mimiq 18.1 cannot be deactivated in-app. If you need to deactivate a computer with Mimiq 18.1, you must do so [through the Hedge License Manager.](/general/licenses/the-license-manager#resetting-activations) # 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. {% tabs %} {% tab title="25" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 2025.12 | 26.1 | | 2025.6 | 25.3 | | {% endtab %} | | {% tab title="24" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 2024.12 | 25.1 | | 2024.10 | 24.5 | | 2024.6 | 24.3 | | 2024.2 | 24.1 | | {% endtab %} | | {% tab title="23" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 2023.12 | 23.3 | | 2023.8 | 23.2 | | 2023.3 | 23.1 | | {% endtab %} | | {% tab title="22" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 2022.12 | 22.4 | | 2022.10 | 22.3 | | 2022.7 | 22.2 | | 2022.4 | 22.2 | | {% endtab %} | | {% tab title="21" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 2021.12 | 22.2 | | 2021.9 | 22.2 | | 2021.6 | 22.2 | | 2021.5 | 22.2 | | 2021.3 | 22.2 | | 2021.2 | 22.2 | | {% endtab %} | | {% tab title="20" %} | Media Composer | Supported in Mimiq as of | | -------------- | ------------------------ | | 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 | | {% endtab %} | | {% tab title="19" %} Media Composer 2019 builds are unsupported. {% endtab %} {% tab title="18" %} | Media Composer | Mimiq for Mac | Mimiq for Windows | | -------------- | ------------- | ----------------- | | 2018.x | 18.1 | 24.2 | Support for Media Composer 2018 requires a Mimiq Pro license. {% endtab %} {% endtabs %} {% hint style="info" %} 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. {% endhint %} ## Operating Systems * macOS 10.14.6 (requires a Pro license and [Mimiq 18.1](/mimiq/mc-2018-and-mojave)) * macOS 10.15.7 or newer * Windows 10 or 11 (64-bit, Pro and Enterprise) * [Media Composer is not qualified for use on Windows Home or Server editions.](https://kb.avid.com/pkb/articles/en_US/Compatibility/en267087) * You must use [an Administrator account](https://support.microsoft.com/en-us/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) to install or uninstall Mimiq. ## macFUSE Workspaces on macOS require macFUSE. Mimiq automatically downloads the latest compatible version for the most recent macOS release. 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 [macFUSE](https://github.com/osxfuse/osxfuse/releases) website. {% hint style="info" %} Our installation and troubleshooting guide for macFUSE is in the [Workspaces](/mimiq/workspaces) section. {% endhint %} ## 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: {% embed url="" %} 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: {% content-ref url="/pages/atKCPoJF8dftKHkAHLWj" %} [Avid's Requirements](/mimiq/requirements/avids-requirements) {% endcontent-ref %} # Avid's Requirements {% hint style="warning" %} 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 [Professional Services](/general/purchasing/professional-services). {% endhint %} 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: * [Media Composer System Requirements](https://kb.avid.com/pkb/articles/en_US/Knowledge/Media-Composer-System-Requirements) * [Computer Optimization Guides – Mac and Windows](https://kb.avid.com/pkb/articles/en_US/Knowledge/en367983) 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. {% hint style="success" %} You must complete all optimizations on each workstation before reaching out for support. {% endhint %} *** ### 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: {% embed url="" %} {% embed url="" %} From Chris Bové, Online Community Manager and Customer Advocate, Avid Technology {% endembed %} *** ### 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. {% hint style="danger" %} With rare exception, *do not* update Media Composer or your operating system while working on a Project. {% endhint %} *** ### 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 Disabling Fast Scrub results in a significant reduction of [`SFPlayConsumer::Execute TIMEOUT` exceptions](#what-are-sfplayconsumer-execute-timeout-exceptions). *** ### 5. Adjust Media Composer's Audio Settings `Settings > User > Audio >` ... {% tabs %} {% tab title="macOS" %} * `Play Buffer Size in Samples:` 1024 (could be as low as 256) * `Tool Buffer Size in Samples:` 1024 (could be as low as 256) {% endtab %} {% tab title="Windows" %} * `Play Buffer Size in Samples:` 12288 (could be as high as 16384) * `Tool Buffer Size in Samples:` 12288 (could be as high as 16384) {% endtab %} {% endtabs %} Adjusting Media Composer's Audio settings results in a significant reduction of [`SFPlayConsumer::Execute TIMEOUT` exceptions](#what-are-sfplayconsumer-execute-timeout-exceptions). *** ### 6. Increase the Amount of Video Memory Used [Media Composer caches playback to RAM. The more memory you have installed on your workstation, the better your playback experience will be.](https://kb.avid.com/pkb/articles/en_US/How_To/Correct-interactive-frame-cache-or-Media-Cache-settings-in-Media-Composer) 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 {% hint style="success" %} 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.) {% endhint %} *** ## Additional Performance Optimizations ### For macOS #### 1. Remove OpenIO\_VirtIO.acf from Avid Media Composer.app‌ {% hint style="success" %} Using Blackmagic Design hardware for video playback? Skip this step. {% endhint %} 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. Removing `OpenIO_VirtIO.acf` results in a significant reduction of [`SFPlayConsumer::Execute TIMEOUT` exceptions](#what-are-sfplayconsumer-execute-timeout-exceptions). #### 2. Rename your Mac's Computer Name to remove any characters with diacritics. [Media Composer becomes unpredictable when a Mac's `Computer Name` contains characters with diacritics (e.g. á, é, í, ö, ü).](https://docs.hedge.video/mimiq/requirements/pages/PfT531SlVaikfqfaAC5r#when-i-open-a-project-why-do-i-get-this-error-file-project-name-.avp-not-found) Take these steps to change your Mac's `Computer Name` in macOS: {% embed url="" %} #### 3. Eliminate All Other Performance Inhibitors on Your Mac or Local Area Network 1. [Do not use Wi-Fi as your computer's primary network connection.](#3.-connect-your-computer-to-the-network-using-a-cable-hard-wired) 2. 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 3. 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. [Download](https://kb.avid.com/pkb/sfc/servlet.shepherd/document/download/0696e00000SgmhFAAR?operationContext=S1) and install [Avid Collect Suite for Windows](https://kb.avid.com/pkb/articles/en_US/troubleshooting/Avid-Collect-Suite-for-Windows). 2. Launch Avid Collect Suite, then click `CHECK CONFIGURATION`. 3. In the `BaseAnalyzer` dialog, click `Verify All`. 4. Choose `Failed` from the dropdown menu. 5. Double-click any 🔴 item in the list, then click `Fix`. 6. 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.` 7. `Fix` as much as you can, then restart Windows. 8. 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. #### 2. Complete your Media Composer setup using the [Computer Optimization Guide](https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/Knowledge/en367983?retURL=%2Fpkb%2Farticles%2Fen_US%2FKnowledge%2FWindows-11-Guide\&popup=true) that matches the version of Windows you're using. *** ## Questions ### What are `SFPlayConsumer::Execute TIMEOUT` Exceptions? [`SFPlayConsumer::Execute TIMEOUT`](https://duckduckgo.com/?va=e\&t=hq\&q=SFPlayConsumer%3A%3AExecute+TIMEOUT\&ia=web) 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. ![](/files/0VOD4sZySziWpgYXdK51) ![](/files/hUUCcUeEcl1WC7E8X8BD) ### 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. {% hint style="info" %} It may be best if all team members are out of the Avid Project before archiving the `Unity Attic`. {% endhint %} ### 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` # Releases ## Mimiq 26.2 Introducing Workspace Groups. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 26.2** (May 5th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260505135920_v26.2b197/Mimiq_20260505135920_v26.2b197.dmg) New ✨ * `Pro` Workspace Groups: keep your Mimiq Workspaces organized Cloud Drives ☁️ * `Pro` Support for LucidLink Classic `2.9` build `8131` * `Pro` Support for LucidLink `3.7` build `8178` **Mimiq for Mac 26.2.1** (Jun 11th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260611113929_v26.2.1b203/Mimiq_20260611113929_v26.2.1b203.dmg) Improved * If LucidLink is disconnected, Mimiq will now auto-unmount related Workspaces (Thanks, Andrew!) Cloud Drives ☁️ * `Pro` Support for Suite build `66.42.0` * `Pro` Support for LucidLink `3.7` build `8283` * `Pro` Support for LucidLink `2.10` build `8237` \ **Mimiq for Mac 26.2.2** (Jul 28th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260728142311_v26.2.2b204/Mimiq_20260728142311_v26.2.2b204.dmg) Cloud Drives ☁️ * `Pro` Support for Suite build `67.146.0` * `Pro` Support for LucidLink `3.7` build `8540` * `Pro` Support for LucidLink `2.10` build `8388` {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 26.2** (May 5th, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.2.0.176.exe) New ✨ * `Pro` Workspace Groups: keep your Mimiq Workspaces organized Cloud Drives ☁️ * `Pro` Support for LucidLink Classic `2.9` build `8131` * `Pro` Support for LucidLink `3.7` build `8178` **Mimiq for Windows 26.2.1** (Jun 11th, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.2.1.178.exe) Improved * Mimiq now correctly reports that there are "no updates available" when there are none Cloud Drives ☁️ * `Pro` Support for Suite build `66.42.0` * `Pro` Support for LucidLink `3.7` build `8283` * `Pro` Support for LucidLink `2.10` build `8237` **Mimiq for Windows 26.2.2** (Jul 28th, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.2.2.179.exe) Cloud Drives ☁️ * `Pro` Support for Suite build `67.146.0` * `Pro` Support for LucidLink `3.7` build `8540` * `Pro` Support for LucidLink `2.10` build `8388` {% endtab %} {% endtabs %} ## Mimiq 26.1 Support for Media Composer 25.12. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 26.1** (Dec 23rd, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20251223104917_v26.1b180/Mimiq_20251223104917_v26.1b180.dmg) New ✨ * Support for Media Composer 2025.12 Cloud Drives ☁️ * `Pro` Support for Suite Studios build `63.2.0` * `Pro` Support for LucidLink Classic `2.9` build `7246` * `Pro` Support for LucidLink `3.3` build `7638` **Mimiq for Mac 26.1.1** (Jan 20th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260120101521_v26.1.1b186/Mimiq_20260120101521_v26.1.1b186.dmg) * The Mimiq installer now also packs an uninstaller * Additional guard rails and logging when Workspaces are unmounted Cloud Drives ☁️ * `Pro` Support for LucidLink `3.3` build `7727` **Mimiq for Mac 26.1.2** (Feb 19th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260219123345_v26.1.2b190/Mimiq_20260219123345_v26.1.2b190.dmg) Cloud Drives ☁️ * `Pro` Support for Suite Studios build `65.8.0` * `Pro` Support for LucidLink Classic `2.9` build `7722` * `Pro` Support for LucidLink `3.6` build `7820` **Mimiq for Mac 26.1.3** (Mar 30th, 2026) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20260330110507_v26.1.3b191/Mimiq_20260330110507_v26.1.3b191.dmg) Cloud Drives ☁️ * `Pro` Support for Suite Studios build `65.36.0` * `Pro` Support for LucidLink `3.7` build `8012` {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 26.1** (Dec 23rd, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.1.0.161.exe) New ✨ * Support for Media Composer 2025.12 Cloud Drives ☁️ * `Pro` Support for Suite Studios build `63.2.0` * `Pro` Support for LucidLink Classic `2.9` build `7246` * `Pro` Support for LucidLink `3.3` build `7638` **Mimiq for Windows 26.1.1** (Feb 19th, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.1.1.166.exe) Cloud Drives ☁️ * `Pro` Support for Suite Studios build `65.8.0` * `Pro` Support for LucidLink Classic `2.9` build `7722` \ **Mimiq for Windows 26.1.2** (Feb 23rd, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.1.2.167.exe) Cloud Drives ☁️ * `Pro` Support for LucidLink `3.6` build `7820` \ **Mimiq for Windows 26.1.3** (Mar 30th, 2026) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-26.1.3.172.exe) Cloud Drives ☁️ * `Pro` Support for Suite Studios build `65.36.0` * `Pro` Support for LucidLink `3.7` build `8012` {% endtab %} {% endtabs %} ## Mimiq 25.6 Search, sort, and filter lockable network shares and Workspaces, plus Workspace Discovery for Mac. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.6** (Dec 9th, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20251208144231_v25.6b179/Mimiq_20251208144231_v25.6b179.dmg) New ✨ * Search, sort, and filter lockable network shares and Workspaces * Workspace Discovery - quickly find and import folders containing Avid MediaFiles * SANFusion bundle detection (Thanks to the Picture Head team) Cloud Drives ☁️ * `Pro` Support for Suite Studios Build `61.24.0` * `Pro` Support for LucidLink Classic `2.9` Build `7246` * `Pro` Support for LucidLink `3.3` Build `7564` {% endtab %} {% endtabs %} ## Mimiq 25.5 Support for macOS 26 Tahoe. Search, sort and filter lockable network shares and Workspaces, plus Workspace Discovery for Windows. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.5** (Sept 15, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250915120945_v25.5b171/Mimiq_20250915120945_v25.5b171.dmg) New ✨ * Support for macOS 26 Tahoe Cloud Drives ☁️ * `Pro` Support for Suite Studios Build `60.1.0` * `Pro` Support for LucidLink Classic `2.9` Build `7246` * `Pro` Support for LucidLink `3.3` Build `7265` {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 25.5** (Dec 9th, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.5.0.159.exe) New ✨ * Search, sort, and filter lockable network shares and Workspaces * Workspace Discovery - quickly find and import folders containing Avid MediaFiles * SANFusion bundle detection (Thanks to the Picture Head team) * Support for DFS-backed SMB paths (Thanks to the RodeoFX team & Alan) Cloud Drives ☁️ * `Pro` Support for Suite Studios Build `61.24.0` * `Pro` Support for LucidLink Classic `2.9` Build `7246` * `Pro` Support for LucidLink `3.3` Build `7564`
**Mimiq for Windows 25.5.1** (Dec 19th, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.5.1.160.exe) * Fixed a bug that stopped Mimiq from launching when used offline {% endtab %} {% endtabs %} ## Mimiq 25.4 Support for Suite Studios. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.4** (Sept 8, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250908102246_v25.4b166/Mimiq_20250908102246_v25.4b166.dmg) * `Pro` Official support for Suite Studios! Build `59.20.0` * `Pro` Support for LucidLink `3.3` Build `7142` * `Pro` Facilis Coexistence {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 25.4** (Sept 8, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.4.0.142.exe) * `Pro` Official support for Suite Studios! Build `59.20.0` * `Pro` Support for LucidLink `3.3` Build `7142` **Mimiq for Windows 25.4.1** (Sept 30, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.4.1.144.exe) * Fix for duplicate volumes showing up in the UI * `Pro` Support for Suite Studios `60.37.0` * `Pro` Support for LucidLink Classic `2.9` Build `2.9.7246` * `Pro` Support for LucidLink `3.3` Build `3.3.7297`
**Mimiq for Windows 25.4.2** (Nov 17, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.4.2.151.exe) * Fix for intermittent locking when using more than one LucidLink Classic Filespaces (Thanks, James) * Pro Support for Suite Studios `61.24.0` * Pro Support for LucidLink Classic `2.9` Build `7246` * Pro Support for LucidLink `3.3` Build `7410` {% endtab %} {% endtabs %} ## Mimiq 25.3 Support for Media Composer 2025.6. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.3** (Jul 3, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250702101742_v25.3b154/Mimiq_20250702101742_v25.3b154.dmg) * Support for Media Composer 2025.6 * `Pro` Support for LucidLink Classic `2.9` Build `6811` * `Pro` Support for LucidLink `3.3` Build `6885`
**Mimiq for Mac 25.3.1** (Jul 31, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250731133114_v25.3.1b157/Mimiq_20250731133114_v25.3.1b157.dmg) * LucidLink can again be used in trials! * Fix for auto-starting Mimiq after a clean install * `Pro` Support for LucidLink Classic `2.9` Build `6983` * `Pro` Support for LucidLink `3.3` Build `6919`
**Mimiq for Mac 25.3.2** (Aug 28, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250827134906_v25.3.2b160/Mimiq_20250827134906_v25.3.2b160.dmg) * `Pro` Support for LucidLink Classic `2.9` Build `6983` * `Pro` Support for LucidLink `3.3` Build `6919` * Fix for intermittent locking with fast Apple Silicon-based systems (Thanks Eric & the Salon team) \ **Mimiq for Mac 25.3.3** (Sept 4, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250903174226_v25.3.3b164/Mimiq_20250903174226_v25.3.3b164.dmg) * Workspaces can once again be created on any volume type, not just cloud volumes (Thanks, Moe!) {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 25.3** (Jul 3, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.3.0.129.exe) * Support for Media Composer 2025.6 * `Pro` Support for LucidLink Classic `2.9` Build `6811` * `Pro` Support for LucidLink `3.0` Build `6885` \ **Mimiq for Windows 25.3.1** (Aug 6, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.3.1.134.exe) * Minimum MC version is now handled correctly when unlicensed (Thanks to the Salon team!) * Fix for rare "bin locking error" on startup when using the Local License Server (Thanks, Ronan) * `Pro` Support for LucidLink Classic `2.9` Build `6983` * `Pro` Support for LucidLink `3.0` Build `6919` \ **Mimiq for Windows 25.3.2** (Aug 28, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.3.2.137.exe) * `Pro` Support for LucidLink Classic `2.9` Build `6983` * `Pro` Support for LucidLink `3.3` Build `6919` {% endtab %} {% endtabs %} ## Mimiq 25.2 Support for Shared Workspace configs, Auto-mounting, Ignore Volumes and MC Beta Releases. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.2** (Jun 11, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250609151514_v25.2b150/Mimiq_20250609151514_v25.2b150.dmg) * Ignore Volumes, so that not all network shares show up in Media Composer * Support for Media Composer beta releases (requires an active license) * `Pro` Create and share workspaces for all team members, not just yourself * `Pro` Automatically mount Workspaces created by other team members * `Pro` Support for LucidLink Classic `2.9` Build `6222` * `Pro` Support for LucidLink `3.0` Build `6757` {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 25.2** (Jun 11, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.2.0.127.exe) * Ignore Volumes, so that not all network shares show up in Media Composer. * Support for Media Composer beta releases (requires an active license). * `Pro` Create and share workspaces for all team members, not just yourself. * `Pro` Automatically mount Workspaces created by other team members. * `Pro` Support for LucidLink Classic `2.9` Build `6222`. * `Pro` Support for LucidLink `3.0` Build `6757`. {% endtab %} {% endtabs %} ## Mimiq 25.1 Support for Media Composer 2024.12. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 25.1** (Feb 26, 2025) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20250226103641_v25.1.0b139/Mimiq_20250226103641_v25.1.0b139.dmg) * Support for Media Composer 2024.12 * `Pro` Support for LucidLink 3.0 * `Pro` Support for LucidLink 2.9 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 25.1** (Feb 26, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.1.0.105.exe) * Support for Media Composer 2024.12 * `Pro` Support for LucidLink 3.0 * `Pro` Support for LucidLink 2.9 **Mimiq for Windows 25.1.1** (Mar 28, 2025) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-25.1.1.114.exe) * Fix for offline usage (Thanks, Mark!) {% endtab %} {% endtabs %} ## Mimiq 24.5 Support for Media Composer 2024.10 and LucidLink 3.0. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 24.5** (Oct 30, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20241030163107_v24.5b124/Mimiq_20241030163107_v24.5b124.dmg) * Support for Media Composer 2024.10 **Mimiq for Mac 24.5.1** (Dec 2, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20241127123113_v24.5.1b132/Mimiq_20241127123113_v24.5.1b132.dmg) * Fix for switching between multiple Local License Servers * `Pro` Support for LucidLink 2.8 **Mimiq for Mac 24.5.2** (Dec 12, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20241212094729_v24.5.2b134/Mimiq_20241212094729_v24.5.2b134.dmg) * Support for all Media Composer 2020 releases, not just 2020.12 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 24.5** (Oct 30, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.5.0.99.exe) * 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! **Mimiq for Windows 24.5.1** (Dec 12, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.5.1.101.exe) * Support for all Media Composer 2020 releases, not just 2020.12. * `Pro` Support for LucidLink 2.8 **Mimiq for Windows 24.5.2** (Dec 23, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.5.2.102.exe) * `Pro`Improvements for LucidLink {% endtab %} {% endtabs %} ## 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. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 24.4** (Sep 12, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20240912142810_v24.4b120/Mimiq_20240912142810_v24.4b120.dmg) * `Pro` Local License Server support * `Pro` Support for LucidLink 2.7 * Adds options to hide updates and license information, for MDM deployments * Support for macOS 15 Sequoia {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 24.4** (Sep 12, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.4.0.96.exe) * `Pro` Local License Server support * `Pro` Support for LucidLink 2.7 * Adds options to hide updates and license information, for MDM deployments {% endtab %} {% endtabs %} ## Mimiq 24.3 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 24.3** (Jul 4, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20240702120213_v24.3b111/Mimiq_20240702120213_v24.3b111.dmg) * Support for Media Composer 2024.6 * `Pro` Support for LucidLink 2.6 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 24.3** (Jul 4, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.3.0.85.exe)[ ](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.3.0.85.exe) * Support for Media Composer 2024.6 * `Pro` Support for LucidLink 2.6 {% endtab %} {% endtabs %} ## Mimiq 24.2 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 24.2** (May 22, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20240522113831_v24.2b110/Mimiq_20240522113831_v24.2b110.dmg) * Bin Refresh for all types of storage * `Pro` NEXIS Coexistence * `Pro` Support for LucidLink 2.5 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 24.2.1** (Jun 14, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.2.1.82.exe) * Trials now come with all Pro features * Fix for trial extensions * Improved activation handling, thanks to Leon! **Mimiq for Windows 24.2** (May 22, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.2.0.62.exe) * Bin Refresh for all types of storage * `Pro` NEXIS Coexistence * `Pro` Support for LucidLink 2.5 {% endtab %} {% endtabs %} ## Mimiq 24.1 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 24.1** (March 5, 2024) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20240229124155_v24.1b100/Mimiq_20240229124155_v24.1b100.dmg) * 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 * `Pro` Support for LucidLink 2.4 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 24.1.1** (March 12, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.1.1.56.exe) * Support for LucidLink v2.6 **Mimiq for Windows 24.1** (March 5, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-24.1.0.55.exe) * Support for Avid Media Composer 2024.2 * Improvements for offline usage * `Pro` Support for LucidLink 2.4 {% endtab %} {% endtabs %} ## Mimiq 23.3 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 23.3.1** (December 21, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20231221145735_v23.3.1b97/Mimiq_20231221145735_v23.3.1b97.dmg) * Improved support for Media Composer 2023.12 * `Pro` Support for LucidLink 2.3 **Mimiq for Mac 23.3** (December 18, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20231218133129_v23.3b96/Mimiq_20231218133129_v23.3b96.dmg) * Support for Avid Media Composer 2023.12 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 23.3.1** (January 30, 2024) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.3.1.52.exe) * Improved support for Media Composer 2023.12 * `Pro` Support for LucidLink 2.3 **Mimiq for Windows 23.3** (December 18, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.3.0.39.exe) * Support for Avid Media Composer 2023.12 {% endtab %} {% endtabs %} ## Mimiq 23.2 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 23.2.1** (October 17, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/production/Mimiq_20231026130657_v23.2.1b93/Mimiq_20231026130657_v23.2.1b93.dmg) * Sonoma support, way ahead of Avid 😉 * Project License support * Improved trial handling * `Pro` Support for LucidLink 2.2 **Mimiq for Mac 23.2** (September 4, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-72.dmg) * Support for Avid Media Composer 2023.8 * `Pro` Support for LucidLink 2.1 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 23.2.2** (November 29, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.2.2.37.exe) * Fix for license deactivations when a computer goes offline. * Additional bug fixes and performance improvements. **Mimiq for Windows 23.2.1** (October 26, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.2.1.34.exe) * Project License support * `Pro` Support for LucidLink 2.2 **Mimiq for Windows 23.2** (September 4, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.2.0.32.exe) * Support for Media Composer 2023.8 * `Pro` Support for LucidLink 2.1 * Mimiq can now be used with non-`Administrator` accounts. {% endtab %} {% endtabs %} ## Mimiq 23.1 Workspaces (`Pro`) enable you to use any type of block-based storage, like a SAN, RAID, or SSD, with Media Composer. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 23.1.3** (August 23, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-70.dmg) * `Pro` Improved overall performance for Workspaces, particularly when added from a SAN **Mimiq for Mac 23.1.2** (May 16, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-62.dmg) * Adds functionality to hide notifications and prevent the main view from popping up on app-open **Mimiq for Mac 23.1.1** (April 24, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-60.dmg) * Fix for a crash on activation **Mimiq for Mac 23.1** (April 16, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-59.dmg) * `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. * `Pro` Support for LucidLink 2.0 {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 23.1.2** (May 16, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.1.2.30.exe) * Adds functionality to hide notifications and prevent the main view from popping up on app-open. **Mimiq for Windows 23.1** (April 16, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-23.1.0.28.exe) * `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. * `Pro` Support for LucidLink 2.0
{% endtab %} {% endtabs %} ## Mimiq 22.4 A wholly rebuilt Mimiq, with new licensing and support for Apple silicon. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 22.4** (January 3, 2023) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-48.dmg) * Support for Media Composer 2022.12 * Locking AFP volumes is now available for `Pro` licenses {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 22.4.2** (February 7, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.4.2.21.exe) * 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.
**Mimiq for Windows 22.4.1** (January 24, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.4.1.17.exe) * Install Mimiq without having to first install Media Composer.
**Mimiq for Windows 22.4** (January 3, 2023) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.4.0.16.exe) * Support for Media Composer 2022.12
{% endtab %} {% endtabs %} ## Mimiq 22.3 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 22.3** (October 25, 2022) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-28.dmg) * Support for Media Composer 2022.10 \ **Mimiq for Mac 22.3.1** (November 8, 2022) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-36.dmg) * A 10-day in-app trial is now available. {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 22.3** (October 25, 2022) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.3.0.10.exe) * Support for Media Composer 2022.10
**Mimiq for Windows 22.3.1** (November 24, 2022) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.3.1.12.exe) * A 10-day in-app trial is now available. {% endtab %} {% endtabs %} ## Mimiq 22.2 {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 22.2** (September 8, 2022) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-20.dmg) * First Mimiq release 🎉
**Mimiq for Mac 22.2.1** (September 19, 2022) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-23.dmg) * Fix for auto-locking not persisting. * Improve check if Media Composer is installed.
**Mimiq for Mac 22.2.2** (September 21, 2022) - [Download](https://updates.hedge.video/mimiq/macos/updates/MimiqForMac-24.dmg) * Fix for an edge case resulting in a memory leak in Media Composer. {% endtab %} {% tab title="Windows" %} **Mimiq for Windows 22.2** - (September 19, 2022) - [Download](https://updates.hedge.video/mimiq/windows/updates/MimiqSetup-22.2.0.9.exe) * First Mimiq release 🎉 {% endtab %} {% endtabs %} ## Mimiq 18.1 A special barebones build of Mimiq for teams that need to use Media Composer on macOS 10.14 Mojave. {% tabs %} {% tab title="macOS" %} **Mimiq for Mac 18.1** (Feb 28, 2024) - [Download](https://downloads.hedge.video/mimiq/Mimiq%2018.1.dmg) {% endtab %} {% endtabs %} # 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: ‌ `> Collaboration & control > Shared bins & projects` ## My volume doesn't enable, shows a link icon?
The client version of your clour provider is too new for your version of Mimiq Pro. Click the 🔗 icon, and extend your license. [More info…](/mimiq/supported-storage#cloud-drives) ## My bins are disappearing? 99% chance you're using SMB and haven't disabled `OPLOCKS` (Opportunistic Locks) on your NAS. Read more about it [here](/mimiq/questions#how-should-i-configure-my-smb-nfs-or-afp-share). If disabling `OPLOCKS` doesn't help, get in touch. ## My shares randomly disconnect and lose bin locking This issue often indicates a misconfigured network share. If you're using StorNext, check if your group policies are set to `update`, not `replace`. ## 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. If you don’t have access to IT or need assistance beyond Mimiq support, [Professional Services are available for an additional fee.](/general/purchasing/professional-services) ## When I open a Project, why do I get this error: `File (Project Name).avp not found.`? ![](/files/iimpbt8BKU58nzvcROHJ) 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. ![System Preferences > Sharing > Computer Name](/files/k8XoqryWA3pUxvR0MmVR) First, [change your computer name in macOS](https://support.apple.com/guide/mac-help/change-computers-local-hostname-mac-mchlp2322/mac), replacing the diacritic with another character. 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. {% hint style="danger" %} Be extra cautious when deleting folders inside your shared Project folder. {% endhint %} 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. {% hint style="info" %} 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. {% endhint %} 3. Move this folder to the Trash. ![](/files/Hq4OM2v9V7IjaFoT1fZj) 4. 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. 3. Install [the latest version of Mimiq.](https://hedge.video/download/mimiq/windows) # Questions ## Why am I shown a "Security Alert" in Media Composer? This alert is Avid's way of telling you that you are not using NEXIS storage with Media Composer. It shows up when creating or first opening a project. This behaviour is consistent across all third-party Bin Locking solutions from Mimiq to EditShare, ELEMENTS, or Facilis. This alert has been around for years in various forms, and does not indicate a problem — it has no functional impact.
## 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 I'm getting a “No virtual machine activations allowed”-alert. {% hint style="info" %} This only concerns Windows users. {% endhint %} 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: {% content-ref url="/pages/UIBxiHJMUBHr8aURYDew" %} [VMs & Hypervisors](/general/licenses/vms-and-hypervisors) {% endcontent-ref %} If you have a regular license and need VM activations, upgrade your license in the [License Manager](https://account.hedge.video/), then [reach out](mailto:hello@hedge.co). Already on a Pro license? [Reach out](mailto:hello@hedge.co). ## 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. To crossgrade your Legacy Mimiq license to a new Mimiq license, [reach out](mailto:mimiqlegacy@hedge.co). ## 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. ## 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? Yes, you can mix any number of Macs and PCs. Just make sure your license has enough[ activations ](https://docs.hedge.video/general/licensing/hedge-license-manager#managing-activations)available for each computer. Additional activations can be added in the [License Manager](https://account.hedge.video). ## Can I use Mimiq in an air-gapped environment? Yes. You can either air-gap the Media Composer edit suite after activating Mimiq or use a [Local License Server](/general/licenses/local-license-server). ## Why does Mimiq Pro no longer enable my cloud drive for MC? You likely have installed a version of LucidLink or Suite Studios that was released after your Mimiq Pro license's eligibility for support and updates expired. You can either extend your Mimiq license, then update your Mimiq to the latest release, or downgrade your cloud drive application. Which version of Mimiq supports which version of a cloud drive client app is documented in [Releases](/mimiq/releases). {% hint style="info" %} If you solely use Mimiq Pro for remote workflows using cloud drives, our yearly licenses are a more economical option than a perpetual license. If you have a perpetual license, reach out to discuss migrating to a yearly license. {% endhint %} ## 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...` You can also manage your activations and deactivations from anywhere using the [License Manager](/general/licenses/the-license-manager). ## 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? Yes, see [MC 2018 & Mojave](/mimiq/mc-2018-and-mojave). 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. [Microsoft ended support for Windows 7 in January 2020.](https://support.microsoft.com/en-us/windows/windows-7-support-ended-on-january-14-2020-b75d4580-2cc7-895a-2c9c-1466d9a53962) [Apple discontinued support for macOS Mojave `10.14` in November 2021.](https://support.apple.com/kb/DL2078?locale=en_US) [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.](https://kb.avid.com/pkb/articles/en_US/faq/Avid-Supported-Software-Releases) If you need guidance on upgrading, use [Mimiq's Requirements](/mimiq/requirements) 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: {% embed url="" %} Avid’s Chris Bové also maintains a human-readable (but slightly less updated) rendition of that Version Matrix here: {% embed url="" %} From Chris Bové, Online Community Manager and Customer Advocate, Avid Technology {% endembed %} ## 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. If you don’t have access to IT or need assistance beyond Mimiq support, [Professional Services are available for an additional fee.](/general/purchasing/professional-services) ## Should I mount shared volumes through UNC paths in Windows? No. Avid introduced [mounting any shared volume via UNC](https://resources.avid.com/SupportFiles/attach/WhatsNew_MediaComposer_v22.12.pdf) 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. {% hint style="danger" %} Setting the `Mount point` of your LucidLink Filespace to a `Valid absolute path and separated semicolon drive letter` is not supported. {% endhint %} ## Should I use the `AllDrives` command in Media Composer's Console? No, `AllDrives` is not required for Bin Locking and shared media to work with Mimiq. ## 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. Second, use a benchmarking utility to perform a throughput test. Benchmarking utilities should only be used as a rough guide. For further assistance, it may be necessary to contact an experienced storage specialist. ## 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 {% hint style="danger" %} Do not mix Shared and Local storage media management folder structures on the same volume. {% endhint %} ## 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. 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 [Media Database Viewer (MDVx)](http://djfio.com/mdv/) helper app to sift media based on Project (or based on a Bin) as needed. ## Can both Mimiq and the Avid NEXIS Client be installed on my computer? Yes. Since Mimiq 24.2, the NEXIS client and Mimiq Pro can coexist. In context, the NEXIS client is used to mount NEXIS type shares, while Mimiq is used to handle Bin Locking on third party storage. --- [Next Page](/llms-full.txt/1)