Creative workflows

Shared Avid Media Composer bins and media with Suite

Use Suite for shared Avid projects and media, with Mimiq bin coordination and a practical two-editor collaboration test.

Give editors shared media and a coordinated bin workflow

Suite can provide the shared filesystem for an Avid Media Composer project and its media, while the application's collaboration setup governs how editors work together. The benefit is a common working library available across supported client environments, with bin ownership handled deliberately rather than through repeated copies of the whole project.

Our Media Composer guide documents Mimiq by Hedge for shared Avid projects on Suite. Mimiq presents Suite to Media Composer as an Avid NEXIS drive, enabling bin locking and bin refresh behavior. The same guide directs users to the applicable Avid requirements and recommends putting the Search Data Folder on a local volume or Local Default.

Suite file access and Mimiq's application collaboration role are distinct. Do not assume that mounting a drive alone configures every bin-locking requirement.

Organize ownership around the edit

For a proposed two-editor pilot, create a clear division of work: one editor owns interview selects while another develops the assembly. Agree on how bins move between owners and how changes become visible. Keep source media in a stable shared location so the editorial conversation can concern the material and decisions rather than identifying which copied package is current.

Record the project name, active bins, current owners, expected media locations and workstation configuration. This record is a team convention, not a Suite administration API or an automatic lock-management feature.

An assistant editor can prepare the next batch of media without asking every editor to prepare a complete local copy of the broader library first. The application still determines which data it reads, and an import or analysis task may read substantially more than interactive selection does.

Test the collaboration behavior, not just playback

Use a representative project and confirm the required software setup on both workstations. Then test a bin being held by one editor, the other editor seeing the expected ownership state, a saved change being released and the second editor refreshing to see that revision. Include media added during the session, not only media present before the pilot began.

Keep a short result log: what editor A changed, what editor B saw, when the handoff became usable and any manual step required. If a bin does not behave as expected, separate the application and Mimiq configuration from whether the Suite files themselves are accessible. That distinction makes support and rollout decisions more precise.

Keep reusable media separate from local working data

Shared source media, project decisions and deliverables serve the team. Local search data and other application working files serve a workstation. Following the application-specific placement guidance helps avoid unnecessary shared traffic while retaining the common media workspace.

Start with direct streaming and assess the real editorial task. Optional pre-caching can be used for selected work; it is not a requirement to copy the entire project library before opening the first useful bin.

Start with Suite Managed and use the pilot to establish a repeatable editorial handoff. S3 Native inquiries are the route for supported storage your organization owns, from 20 TB active. Signup continues on Suite Studios' main site.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.