Troubleshooting
Last updated
Last updated
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:
https://www.avid.com/media-composer/comparison > Collaboration & control > Shared bins & projects
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...
Set the Root point
in their Lucid app to that folder.
Quit Media Composer.
Quit-then-relaunch Mimiq.
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.
File (Project Name).avp not found.
?Media Composer doesn't support all characters. If you're seeing this error, then your Computer Name
has a diacritic character or accent in it. Rename your computer, replacing the diacritic with an equivalent character, and Media Composer will be able to open your shared Project.
First, change your computer name in macOS, 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.
Be extra cautious when deleting folders inside your shared Project folder.
Quit Media Composer.
While Drive is connected, go to your shared Project folder and locate the folder named after your computer with the diacritic (e.g. Isaac T - über Mac
) within the ../AvidSharedData
folder.
Depending on the version of Media Composer you're using, Media Composer may generate that folder named after your computer directly inside your shared Project folder.
Move this folder to the Trash.
Relaunch Media Composer and reopen your shared Project.
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:
The permissions on your shared folders are correct.
The hard drives in your server aren't failing.
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.
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.
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
.
Use Windows’ Apps & features
panel to uninstall Legacy Mimiq (search for “Mimiq”).
Restart your PC.
Install the latest version of Mimiq.