Storage
Cocreate reads what the workstation has already mounted. There is no connector to configure, no library to move, and no second copy of your media kept anywhere else.
- A001_CFEXPRESSexfat
- NEXIS_SHOW_01smbfs
- NEARLINE_04nfs
- POST_SAN_Aacfs
- BACKUP_02apfs
Matched on UUID and serial, not on path.
What it reads
Cards and local disks
CFExpress, SD and USB readers, Thunderbolt and USB drives, and the disk inside the machine.
Network shares
SMB, NFS and AFP. An Avid NEXIS or EditShare space arrives as SMB, and Cocreate reads it as one.
SAN volumes
A fibre-channel or Xsan volume is mounted by the workstation, so it behaves like storage sitting inside it.
Cloud, once it is mounted
If your cloud storage presents itself as a volume, Cocreate treats it as one. No separate connector, and no second copy of your library.
Matched by identity, not by path
A path is not a reliable name for a drive. Cocreate records what the volume actually is, so work already done stays valid when the mount moves.
Volume UUID and serial first
Where the operating system exposes one, the volume's own identifier is what a job is pinned to. A share falls back to its share ID and relative target.
Remounts do not strand a job
Before resuming, Cocreate re-checks the identity of both source and destination. If it is the same storage the job continues; if it is not, it stops and says so rather than writing to the wrong disk.
Mounts and unmounts are seen live
Drives appearing and disappearing are picked up while you work, and you can eject from inside the app.
Nothing migrates
Read in place
Media is analyzed where it already lives. There is no import step that duplicates your library somewhere Cocreate controls.
Originals are never rewritten
The only files Cocreate writes are the copies, transcodes and reports you asked for.
Shared storage stays usable
Reads are governed per volume, so background analysis backs off rather than saturating a share other people are working on.