Copying Content Between Projects
The content of a project can be copied to another project using the Projects tab in the MediaHub.
If the Media Cache location of the project from which content is being copied is on the same file system as the current project, and the media cache formats are the same for both projects, hard links are created when copying content, avoiding unnecessary media duplication. If the media cache formats are different, copying content generates new cached media.
Use the following command to validate if a cached content is a new file or a hard link. Hard links show two or more links. New files show one link.
stat <file name of a hard link>
File: 0x000000000000000a.mov
Size: 1895424 Blocks: 3704 IO Block: 4096 regular file
Device: fd01h/64769d Inode: 3952935555 Links: 2
Access: (0644/-rw-r--r--) Uid: ( 2242/testing_o1) Gid: ( 1002/ open)
Access: 2024-11-05 09:04:08.174859135 -0500
Modify: 2024-11-05 09:04:08.174859135 -0500
Change: 2024-11-05 09:10:01.842770941 -0500
Birth: 2024-11-05 09:04:08.174859135 -0500
stat <file name of a new file>
File: 0x000000000000000a.dpx
Size: 8323072 Blocks: 16256 IO Block: 4096 regular file
Device: fd01h/64769d Inode: 4298782920 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 2242/testing_o1) Gid: ( 1002/ open)
Access: 2024-11-05 09:20:31.520110791 -0500
Modify: 2024-11-05 09:20:31.520110791 -0500
Change: 2024-11-05 09:20:31.520110791 -0500
Birth: 2024-11-05 09:20:31.520110791 -0500
Note: The link count can be seen in the second column of the ls -l command output, right next to permissions.