-
ippmpegdecoder.dll crashes PProCS3
Since installing the latest update to PProCS3 (3.2), I can’t load any mpegs without crashing the program. When it shuts down, PPro gives the message that the problem occurred in ippmegdecoder.dll.
I’ve contacted Adobe tech support – a week ago – “the problem has been escalated beyond a tech query & we’re doing our best to sort it”
In the meantime I have a $6000 project I can’t edit.
The footage cam from a Sony HD Z1P camera & was recorded direct into Adobe “OnLocation”.
I have used this same method in 2 previous projects & both were fine & are now released on DVD.
PPro won’t open these projects either.
I’ve tried uninstalling & reinstalling the whole suite (as advised by Adobe techs) & used the Adobe clean up program. This took 8 hours.
If I disable ippmpegdecoder.dll by renaming it, PPro attempts to install new codecs but gives up at about 17% & starts the program – I can then play the mpegs but eventually the system crashes when I try to do any editing.
I CAN open the mpegs in After Effects & render to an AVI but this takes about 20mins to render a 30sec segment & my footage is 3×1 hour segments.
I’ve used “sherlock” to check the codecs & re-registered anything that showed as being faulty.
Any help at this point would be appreciated – even a workaround.
Phil -
6 Replies
-
Pick up a copy of Premiere Elements 4. It edits mpeg and other consumer formats much better than CS3.
-
Adobe Premier Elements 4 exhibits the same symptoms – crashing – when handling MPEG video files, both on Windows XP and Windows Vista, with all updates from Microsoft and Adobe installed.
“ippmpegdecoder.dll” is cited as the reason whenever it crashes. So far I’ve found no solution.
-
I am having the same problem on Vista Home Premium, 64 bit, quad i7 machine.
-
Phil, I encountered the same issue yesterday. I wondered if you ever found a solution. There’s probably been several patches to CS3 since your original post, but I’m getting that exact same behaviour now.
Any advice?
Matthew P
-
Hi Matthew,
Glad to be of assistance.PROBLEM: As I understand it, Premiere verifies mpeg2 footage using the first & last few frames. If any of these are corrupt, it will screw the decoder & shut down the program.
CAUSE: I found that when I used “On Location” to capture, there was almost always a problem in this regard. This was because I was using an external HDD via USB2. Although the drive spec was fast enough, the speed of USB2 meant that On Location was chasing it’s tail to try & write the footage to the drive, which is why there were glitches at the beginning & end of each file.
SOLUTION: Apart from the obvious solution of using a faster internal HDD when shooting, I found a way to fix the footge I had already shot by bringing it into After Effects & doing a straight render to Mpeg2 Blu Ray. Don’t try to crop any frames at the beginning or end, just re-render on the above setting. Don’t woryy if you see strange green or blue checks, the re-rendering will help Premiere to ignore these corrupt frames. You can edit these out when you bring the file back into Premiere. Be patient with AE – if your files are big it will take some time to render & may not show any progress but don’t interrupt it.
Good luck & let me know how you go
Cheers
Phil -
Phil, thanks for taking the time to respond. AE does indeed indicate I have some wierd frames upfront.
I’m rendering now, but I expect your solution to be the one. I had also captured to an external USB disk.
Thanks again!
Matthew
Reply to this Discussion! Login or Sign Up