Ru Cook
Member
Hi all, i've noticed something slightly odd with this feature.
Ive got a project thats at about 150gb....if I select the project & use 'Copy Project to new library' & point to an external drive, everything works just fine. The mac wirrs away for a bit, & copys across only the clips that are in the project & creates a new library thats 60gb in size. So far so good.
If I try this process on the *same* drive that the library currently exists on, it does this *instantly*....like....in zero seconds, so it can't really be copying 60gb ! I've double checked that i'm not using 'Move to new Library' by accident. The strange thing is, the old 160gb library is still intact (as it should be)
Anyone else notice this? I'm just not sure I trust what FCPX is doing behind the scenes, in case it is still referencing a file at another location.
Ive got a project thats at about 150gb....if I select the project & use 'Copy Project to new library' & point to an external drive, everything works just fine. The mac wirrs away for a bit, & copys across only the clips that are in the project & creates a new library thats 60gb in size. So far so good.
If I try this process on the *same* drive that the library currently exists on, it does this *instantly*....like....in zero seconds, so it can't really be copying 60gb ! I've double checked that i'm not using 'Move to new Library' by accident. The strange thing is, the old 160gb library is still intact (as it should be)
Anyone else notice this? I'm just not sure I trust what FCPX is doing behind the scenes, in case it is still referencing a file at another location.