Comment on page
Questions
In Media Composer, go to
Avid Media Composer > About Avid Media Composer > Hardware > Avid NEXIS Drives and confirm your Team's Drive or Workspace is listed.
Avid Media Composer > About Avid Media Composer > Hardware > Avid NEXIS Drives
This involves Team Owners. When in doubt, make sure each Team Member...
- 2.Has
Enable Remote Locking on this computerchecked on their local Mac inPreferences > Integrations > Remote Locking.
Preferences... > Integrations > Remote Locking > Enable Remote Locking on this computer
Once you enable Remote Locking for Avid Media Composer on your Team, PostLab automatically enables Remote Locking for each LucidLink filespace connected through the LucidLink app.
Connect your LucidLink filespace, then head to
POSTLAB CLOUD > Drive. You'll see your LucidLink filespace listed with a new status: /Volumes/(Mount point) is enabled for Remote LockingThen, launch Media Composer and create an Avid Project on your LucidLink filespace.
Avid Media Composer requires
read and write permissions to each disk's root folder. Therefore, make sure your LucidLink user has both read and write privileges to the full Filespace; i.e the
/ share. Without that, Media Composer is sure to crash on start-up, or during project creation — without any warning or errors.Yes. Workspaces let you create multiple volumes from folders on your PostLab Drive. More details are available here.
What if you need to use Media Composer alongside other NLEs? In this instance, Remote Locking is available as a paid add-on option with a Team or Enterprise plan. Like a PostLab for Media Composer trial, Remote Locking is enabled during your trial. Once the trial expires, the Team Owner (and no one else) must purchase Remote Locking, then enable it for each Team Member.
To purchase Remote Locking, go to
Preferences > Integrations > Remote Locking. Click Enable, then complete the checkout.
Remote Locking for Avid Media Composer > Checkout
Enable Remote Locking for all Team Members who need it, and your billing will be adjusted accordingly.
You're using a standard subscription of Media Composer. An Ultimate subscription or a Perpetual license is required for shared Project workflows:
First confirm Remote Locking is enabled for your Team Member in PostLab. If it isn't, ask your Team Owner to enable it for you.
From time to time, you may need to disable-then-re-enable
Enable Bin Sharing... In Media Composer (Settings > General > Enable Bin Sharing...). This is a long-standing known issue in Media Composer.Avid Media Composer Documentation and Version Matrix > Documentation > (Media Composer Version) > README > Limitations:
If you launch a project and receive an “Enable 3rd Party Emulation” warning, even if you select Enable in the warning dialog, you should also perform the following: Select File > Settings and click the Project tab. Click General Settings and select “Enable Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS.”
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
The
Unity Attic folder is too big.Zip and archive the existing
Unity Attic periodically, then Media Composer will regenerate a new one.It may be best if all Team Members are out of the Avid Project before archiving the
Unity Attic.When Remote Locking is enabled, another NEXIS client cannot be active at the same time. However, you can use Remote Locking alongside your Avid or compatible third-party shared storage by:
- 1.Mounting your Avid or compatible third-party shared storage folders as network shares in Finder.
- 2.Telling Media Composer to treat those network shares as Avid media storage volumes.
This reverts the Avid media management folder structure from the shared storage method back to the local storage method.
- Shared Storage
- MXFs - folders are created based on the source Mac's Computer Name (
System Preferences > Sharing > Computer Name) and a number:/(Volume)/Avid MediaFiles/MXF/(Someones Mac).(N) - OMFs - folders are created based on the source Mac's Computer Name (
System Preferences > Sharing > Computer Name) :/(Volume)/OMFI MediaFiles/(Someones Mac)
- Local Storage
- MXFs - subfolders are created with a number (
/(Volume)/Avid MediaFiles/MXF/1) - OMFs - (
/(Volume)/OMFI MediaFiles/); no subfolders
No. If you're using PostLab Drive with Remote Locking, the media must be stored with the Shared Storage media management folder scheme.
❌ Local Storage -
Avid MediaFiles/MXF/1✅ Shared Storage
../Avid MediaFiles/MXF/(Someones Mac).(N)../OMFI MediaFiles/(Someones Mac)
That depends.
Media Composer expects subfolders in
../Avid MediaFiles/MXF/ or ../OMFI MediaFiles on shared storage to be named this way:../Avid MediaFiles/MXF/(Someones Mac).(N)../OMFI MediaFiles/(Someones Mac)
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 the subfolders in
../Avid MediaFiles/MXF/ or ../OMFI MediaFiles 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 Drive.
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/ 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) helper app to sift media based on Project (or based on a Bin) as needed.
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
First, go to
System Preferences > Sharing, and replace the diacritic with another character in Computer Name.In this example:
❌ Isaac T - über Mac ✅
Isaac T - uber MacIf you tried opening a shared Project from Drive before changing your Computer Name, you also need to remove the folder with a matching name from your Project.
Be extra cautious when deleting folders inside your shared Project folder.
- 1.Quit Media Composer.
- 2.While Drive is connected, go to your shared Project folder and locate the folder named after your computer with the diacritic. (e.g.
Isaac T - über Mac) - 3.Move this folder to the Trash.
- 4.Relaunch Media Composer, and open your shared Project from Drive.
SFPlayConsumer::Execute TIMEOUT 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.
You reviewed the Initial Workflow Checklist, enabled Remote Locking, double-checked you fulfilled all Requirements, and couldn't find an answer to your question. What's next?
Last modified 2mo ago