Questions
Last updated
Last updated
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.
Running Mimiq in a VM is a Pro feature.
If you see this error when activating a trial, you're running Mimiq in a VM, or a Hypervisor process must be active in Windows.
If you see this error when activating a purchased license, you have a regular license or a Pro license that needs VM activations allowed on your license.
A step-by-step guide for disabling any-and-all Hypervisor (Hyper-V) and Virtual Machine features on your PC is available here:
If you have a regular license and need VM activations, upgrade your license in the , then .
Already on a Pro license? .
Yes.
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.
No. Legacy Mimiq licenses were tied to a specific MAC address which cannot be altered. Instead, crossgrade to a new Mimiq license.
A Legacy Mimiq license was valid for one year from the time your license file was issued.
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.
You can deactivate Mimiq in-app by clicking the helper app, go to the hamburger, then License > Deactivate...
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.
Yes, see Media Composer & Mojave.
Your mileage may vary when using Windows 7. We don't officially support it, but Mimiq might work with your workstation's configuration.
In short:
Apple and Avid no longer support all versions in use.
These versions are no longer patched or updated, posing a significant security risk.
Apple silicon requires macOS 10.15.7 or newer.
The new Mimiq uses modern technologies that are too new to work on all previously supported OSs.
Avid’s Chris Bové also maintains a human-readable (but slightly less updated) rendition of that Version Matrix here:
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.
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.
No.
Setting the Mount point of your LucidLink Filespace to a Valid absolute path and separated semicolon drive letter is not supported.
AllDrives command in Media Composer's Console?No, 99% of the time.
However, if you used AllDrives recently, you'll need to make sure AllDrives is correctly set to use with Mimiq:
Use AllDrives -1 to determine the current status. This is the Help file for the command, but the last line reports AllDrives' current status.
Did AllDrives report Only true media drives will be viewed as media drives.? If so, nothing more is needed. Otherwise...
Use AllDrives 2, which will report Only true media drives will be viewed as media drives.
First, check with your shared storage vendor for any docs, bundled utilities, or commands that could assist you.
You can store your media on any volume accessible to your computer. Just make sure you use the appropriate Avid media management folder structure on the desired storage:
Shared Storage
/(Volume)/Avid MediaFiles/MXF/(Someones Computer).(N)
/(Volume)/OMFI MediaFiles/(Someones Computer)
Local Storage
/(Volume)/Avid MediaFiles/MXF/(N)
/(Volume)/OMFI MediaFiles/ - no subfolders
Do not mix Shared and Local storage media management folder structures on the same volume.
../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.
Yes. However, since only one NEXIS client can be active on a computer at any given time, once Mimiq launches, it becomes the active NEXIS client.
When you quit/exit Mimiq, your former NEXIS client will resume its place as the active NEXIS client.
To crossgrade your Legacy Mimiq license to a new Mimiq license, .
Yes, you can mix any number of Macs and PCs. Just make sure your license has enoughavailable for each computer. Additional activations can be added in the .
Yes. You can either air-gap the Media Composer edit suite after activating Mimiq or use a .
You can also manage your activations and deactivations from anywhere using the .
If you need guidance on upgrading, use as a starting point, then either consult with an Avid reseller or choose the best qualified combo of operating system and Media Composer for you with Avid's Version Matrix for Media Composer:
If you don’t have access to IT or need assistance beyond Mimiq support,
Avid introduced in Media Composer 2022.12. Our testing reveals their implementation is unpredictable, with erratic OS-level permissions errors. Hence, shared volumes mounted solely through UNC paths are currently not supported by Mimiq.
Otherwise, using something like may help.
Instead, we recommend letting Media Composer put the media wherever it wants within ../Avid MediaFiles/MXF | UME/ or ../OMFI MediaFiles/, then use Media Composer to organize your Clips into Bins. If you need to copy or move any media, use the free helper app to sift media based on Project (or based on a Bin) as needed.
