For Avid Media Composer, Bin Locking is the preferred mechanism. Once Remote Locking is enabled for your Postlab Team, Avid Media Composer recognizes Postlab Drive as third-party shared storage. Teams of Avid editors can then work together using Shared Bins with Bin Locking in shared Avid Projects.
In Postlab, go to Preferences... → Integrations → Remote Locking.
Avid Media Composer expectsread 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.
Can I use existing Avid and third-party shared storage alongside Postlab Drive?
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:
Mounting your Avid or compatible third-party shared storage folders as network shares in Finder.
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 - folders are created based on the source Mac's Computer Name (System Preferences → Sharing → Computer Name) and a number (/<Volume>/Avid MediaFiles/MXF/<Computer Name>.1)
Local Storage - subfolders with media are created with a number (/<Volume>/Avid MediaFiles/MXF/1)