-
CS4 Quicktime import failure
I am working with HD material created on FCP and Avid systems. The clips are Quicktime DNxHD and ProRes. When I started the project, everything was working well, but suddenly the clips are not importing. I get an “ImportProcessServer has stopped working” warning, and another warning “Dimensions too large”, which I understand is a typical message when there are codec issues.
I had previously installed the DNxHD codecs; I have tried to install the ProRes codecs, but system says they are already installed (I presume they are bundled with the latest versions of Quicktime now).
Yesterday I did a complete clean install, thinking that there was a software corruption issue, but the problem still persists!
There is no additional software installed at this point other than what is absolutely needed – no codec packs, etc.
These clips all play in QT player. Shouldn’t anything that plays in QT player import into PPro?
The system is a dual quad core Xeon (Intel X5400XT), 64-bit Vista,
8 GB RAM, ATI Radeon 3870, PPro CS4.1, SAS 8-drive RAID (5), Matrox Axio (4.1 RC drivers).By the way, as far as I can determine, this is not a Matrox issue (problem persists with native Adobe sequence settings).
I have found other people having similar issues on the forums, but no solutions.
-
4 Replies
-
Not sure what else to add. By clean install, do you mean OS install, or uninstall and reinstall.
Without formatting and reinstalling the OS, this is how I do a clean install, otherwise the issue will often remain.
Uninstall all Adobe software, including flash, Acrobat, etc.
Delete all Adobe folders afterwards. First you will have to go to Control panel > Folder options > View and show hidden files and folders.
Delete from C:Users{yourname}/AppData/Roaming/Adobe
C:Users/{yourname}/AppData/Local/Adobe
C:Program Files/Adobe
C:Program Files/Common Files/Adobe
C:Program Files (x86)/Adobe
C:Program Files (x86)/Common Files/Adobe
C:ProgramData/Adobe
Another PITA option would be getting a copy of QT Pro and exporting to something else.
Vince Becquiot
Kaptis Studios
San Francisco – Bay Area -
Thanks, Vince,
It turned out to be a corrupted Quicktime DNxHD clip. The wierd thing is that the clip worked for a while, then decided to go south. Other QT clips with the same codec continue to work fine.
Yeah, before I discovered the clip was the problem, I did a complete clean install of the C: drive. Took me four hours. Doh. System’s neat as a pin now, though.
-
I guess my point is that with Vegas, and from what I hear from FCP, you don’t have to do all this crazy stuff.
Very rough for a 24/7 business to have to stop and lose a day doing this kind of stuff.
I have never been an Apple person but we are strongly considering the switch as reliability is #1 for us.
Cheers and thanks for the tips.
Todd
Todd Roush
Dreamscape Digital Media
Canon XH-A1’s – Dell Studio XPS i7, 920, 2.66 gig,6 gigs RAM (soon to be 12) 650 gig SATA, 1TB eSATA external, 3TB USB(storage). 512gig ATI video card, 28″ HannsG Monitor, 24″ Dell Monitor. -
Yeah, Premiere is going through a rough patch right now. Frankly, this is just sloppy code writing – the import and export DLLs should be adequately trapped to prevent crashing at the very least.
I was helping a friend with a Premiere edit the other day on CS2, and it was like coming back to an old friend. Imagine being able to burn a DVD in the actual editing application!
One of my two systems is still on CS3, and I’m keeping it that way for the time being.
There is no question in my mind, though, that Adobe will ultimately fix these issues. I’m not at the point yet where I’m ready to jump ship – too many years invested in Adobe at this point.
Reply to this Discussion! Login or Sign Up