Warning: Premiere Pro "Project Manager" does NOT include the After Effects 'dynamic linked composition' files associated with the project when "Collect File and Copy to New Location" resulting in the incomplete and loss of all dynamic linked compositions in the new project destination ( folder or disc drive ) .. I know this also includes Photoshop dynamic links and assume includes Audition audio files as well.
Ok. When I figure out the best way I will post it ..
If you miss a step .. your doomed.
Also .. seems like you have to RELINK everything to update the resource index.
Maybe there is a software think tank that can work with Adobe to solve these things.
Here's the best way: Personal Responsibility.
Put all of your project files in one file. Stop asking PPro to do it for you. It's simple. This is a no-brainer. If you create a linked comp, create it in the same file as your PPro project and files. When you send it to Encore, create the Encore project in the same folder. Works all the time, every time. When you're sure that you're finished with the project for the forseeable future, move the entire folder off your workstation into storage. Do I move a copy of each asset (video clip, image, audio, etc.) into this folder before I import it to my AE or PPro project? Yes I do. Is it overly time-consuming? Not really. I can fly on my machine. Does it beat not being able to open a project later. Oh yes. Yes it does. I'd say I did 50 projects last year this way. When I occasionally had to move a project folder back to the workstation, I had no problems. Everything worked as it did before I off-loaded it. That's because I take personal responsibility for my projects. It's imporatnat that theyt work, especially if I end up having to hand it off to a third party down the road.
BTW, my workstation is RAID 0. If you are using anything less, you need to upgrade. What I'm trying to tell you is that my system works very well. I have not always done things the right way. I have had my share of frustration. The point is that I learned. Now I'm passing that on to you. I use CS5 on an HP Z800 with a measely 12 gigs of ram and a single i7 quad core and the aforementioned RAID 0 configuration and a hacked Nvidia GTS 450. It works quite well. I'm sure I would do even better with another i7, 12 more gigs of ram and a Quadro 4000, but this is what they give me to use.
Additionally, I'm using CS5 at home on a MUCH older HP xw8200 dual dual Xeons, 12 gigs of ram and software-only MPE. Guess what? It works quite well.
Stan .. thank you.
I am on a Mac Pro 12 Core Dual 2.9 GHZ with 32 GB RAM.
I was very disappointed in the performance of my system with the CS 5 Demo. I could not believe such a high end system would choke on only 4 multichannel SD videos in such a choppy way ... as well as effect filters.
When the Activity Monitor / Disk Speed applications showed much room for I/O improvement .. I bought a Areca 1212 internal PCIe card and a 4 TB external SATA / RAID 0
Tthe reason I am trying to save the entire project on another HD is to eliminate the RAID 0 as causing the serious problems I am having with 5.5.
My original problems with 5.0 in January have been rediscovered in 5.5. I thought it was just a 3rd party AE effects plug-in ( Stabilization ) causing Linked Composition file corruption.
My work around ( recommended in the Adobe Forums and CoreMelt tech support ) was to save the file in AE and import it into PP.
This .. of course .. ruined the possibilities of "Dynamic Link" .. but worked .. and I hoped that the updated 5.5 ( with Adobe Stabilization ) would solve this.
After a firmware update and the removal of a less-than optimal HD from the RAID 0 .. there was no more RAID / Areca crash reports.
The RAID 0 seem to be operating fine .. but I still have to test the Adobe CS 5.5 Suite with just a single HD.
I will take your advice on MANUALLY saving all files.
When I get the time .. I will "Feature Request" Adobe to attempt to add additional features to their "Project Manager" to include ALL pertinent files in regard to a PP project .. something that seems would been within the evolution of the "Master Collection" Suite.
Thanks again for your comments.
I have also pretty much given up on dynamic-linking significantly layered AE comps as PPro just chokes on em. It takes as much time to render em on a PPro timeline as it does to simply render em from AE. If they need tweeking, I just bite the bullet, go back to AE and keep on keepin on.
Just wondering as a new PrPro user if this is still an ongoing issue with CS6?
Obviously good file management is critical when building a project but there is a time and place for a COMPREHENSIVE project asset collect. In the case of a current job I'm backing up the total project size is about 10TB. To restore that in entirety from LTO would take me the better part of a fortnight, a little tedious if I just need to make a few edit changes to a couple of the sequences. With this in mind I consider it good practice on large projects to also media manage the finished timelines into a separate set of self-contained folders. It's kind of annoying that the AE elements used don't get bundled up in the project. Any word on this being fixed?
I feel like this would be a simple issue to resolve. Seems fairly obvious that Premiere's Project Manager should be able to understand that those AE project files are being used in the timeline. It's not a particularly difficult fix though, after the project manage finishes all you need to do is copy the AE files over to the same directory and relink PRESTO! Still should be automatic. Any idea if this is being addressed?
there is a time and place for a COMPREHENSIVE project asset collect.
It's not about when or where, it's about what tool you use to do the work. If you want to move, copy or rename files, use a file manager, not an NLE.
Works every time.