-
ImporterProcessServer instability in PPro CS4
I’ve been editing projects lately on CS4 with many of the clips using 3rd party codecs: Quicktime ProRes and DNxHD. I have had instances where the clips imported fine initially, but then at some point (probably after a crash) would crash ImporterProcessServer when the project was reopened.
It’s a real pain trying to isolate the offending clip, because once IPS (ImporterProcessServer) crashes, NONE of the picons will load. You basically have to take all clips offline and relink them until IPS crashes. Then you confirm by attempting to import the suspect clip into a new project. Typically a bad clip will crash IPS there as well.
In an attempt to remedy the problem, I have done a complete clean install (reformat) of my C: drive – but I still am having the same problem, so I don’t think it is a software configuration issue.
The wierd thing is the corrupt clips will play in Quicktime player and import fine into After Effects. But not Premiere (CS4. They DO import into PPro CS3!). I end up transcoding in AE and relinking to use the clip.
Needless to say, this is very frustrating and time consuming. Between this issue and the dismal implementation of AME in CS4, I long for the good old CS3 days. Let’s all say it together so Adobe can hear: BRING BACK EXPORT MOVIE (adio, still) in the parent application! And please address the shortcomings in IPS. I can’t work this way.
By the way, the CS4 system is dual quad Xeons, Intel X5400XT MOBO, 64-bit Vista, 8 GB RAM, Radeon X3870, Axio LE, 8-bay 8TB SAS array. My sotware is fully updated.