I regularly move projects across systems, but I have
never tried to copy the Media Cache Files or Preview Files.
I always plan to allow time for the 2nd system to re-generate
the cache. It makes for a smaller project transfer, and avoids
any confused / corrupted / duplicated / unrecognized files, etc.
Thanks for the reply.
It takes about 5% of the time to copy the files across even a busy network than it does time to recreate them. For rush projects (which is where we generally need additional editors involved) this time is critical.
Any one have suggestions on how to avoid this re-conforming, since the files already exist?
You have to be certain that the drive letter and folder paths
for both your project and your Media Cache files are identical on
both systems. Premiere looks to absolute, not relative file paths
when it is linking media on opening a project.
As a test, I have copied a project from one system to
another and included the Media Cache files.
For the purposes of this test I deleted all of the existing
Media Cache files on system one, opened the project
and re-generated them on system one before transferring
the project and Media Cache files to system two.
All of the drive letters and path names for the project and
the Media Cache files are identical on both systems.
(I never use "Save Media Cache files next to originals...",
they are always stored on a second RAID0 separate from
the project and Media RAID0).
On opening the project on system two, all media was properly
linked, and no re-conforming of Media Cache files occurred.
This is the first time I have used this method
of migrating a project between systems.
I will regularly have several current projects in different stages
of completion, and all projects are set to generate Media Cache
and Preview Files to a common location on my second RAID0.
Given the cryptic names of the .cfa and .pek files, it is nearly
impossible to determine which files go with what project.
Another reason I simply allow time for Media Cache files
to re-generate on the second system.
Thanks again for the reply.
I've taken to renaming all the source files first with the project & source card prepending the file name, so all files are unique and matching the various cache files becomes trivial - especially when I store them with the source media.
Now, since they are stored with the source media why would it need to recreate the files again?
Source File = PRJCT_C10_MVI_0001.mov
Cache Files = PRJCT_C10_MVI_0001.pek
When copied PP insists on creating the following file IN THE SAME folder
PRJCT_C10_MVI_0001_1.pek instead if using PRJCT_C10_MVI_0001.pek.
The paths apear to be the same on both machines...... so...... I'm stumped.
...IN THE SAME folder
Premiere looks to absolute, not relative file paths.
If on system one the path to the project's media is:
and, on system two the path to the project's media is:
...the Media Cache files will not be linked due to the
differing drive letter ("D" vs. "E").
If the absolute path to the media (and cache files) is not identical,
and your project's settings are to "Save Media Cache files next to originals...",
Premiere will re-generate new cache files "next to originals", and will
append the file names since they already exist.
The paths apear to be the same on both machines..
Make certain that they are the same.
Another reason to take the time for Media Cache files
to re-generate on the second system is that once they
are there (in a common folder separate from original media),
you have no need to move them back and forth again if you
move the project between systems.
I just want to bump up this issue for ExactImage and say I hear you, brother. I understand what Joe Bloe is saying, but this is not the way it should be. Just as Premiere can infer relative folder paths for media files, it should be able to check for media cache files (.pek, .cfa, .qtindex) in relative locations as well. This is an encumberance that needs to be fixed!