Facilis Technology Avid Post Workflows
Facilis Shared File System unlocks Avid project and media sharing features.
Avid post workgroups need all of the Media Composer project sharing and media subdirectory management that is offered for collaborative editorial. Facilis was the first to offer a true emulation of Avid filesystem over 15 years ago, and we have more experience with Avid workgroups than any 3rd party shared storage solution.
Facilis volumes are shown as Nexis workspaces, and Media Composer software enables the most critical collaborative sharing features like bin and project sharing and client-managed MXF databases. Not every storage system does this properly, which is the reason Avid warns against 3rd party storage with Media Composer. Facilis has been supporting large Avid workgroups for over 20 years, and our security and data integrity features exceed industry standards.
FastTracker creates Avid-native Proxies for offline and remote editing.
FastTracker Asset Management works as a complimentary software to Avid, allowing the editor to search, audition, and drag into the bin as a linked or imported asset. In addition, FastTracker can create 720 and 1080 Avid-native DNxHD proxies directly into the Avid Media Files folder. FastTracker maintains the link to the high res sources in it's database, for easy retrieval through the search functions.
Facilis Smart Access Rules secures your data during the post process.
Smart Access Rules is known as "ACLs for post". Because traditional ACLs (access control lists) simply don't provide the immutability necessary for critical data while allowing work to proceed on those very assets. For example, an administrator can restrict delete on certain file types, like MXF and AVB, but creating, writing and saving these file types is allowed. An administrator can limit certain files to read-only access, so they can't be changed, replaced or deleted, but they can still be created. This is nearly impossible with standard ACLs, and Facilis has the additional benefit of using OS login names, local server-based user lists and Active Directory user lists as the source for these access rules, in any combination.
In the above example, any user in the Promos user group (which may be OS names, local users and/or AD users) is unable to delete any MXF files. However, if one of these users tries to delete a MXF file from the Media Composer application, there will be no errors returned to the application. The file will not be deleted, but will also not be visible in the project until the Avid MXF databases are rebuilt.
