Premiere CS5.5 appears to be causing a glitch/stutter at the same spot consistently. I've trashed the renders and re-rendered, I've un-nested the sequence and re-rendered + recompressed, I've exported to MPEG2 via Pr and via dynamic link using Media Encoder and I still can't overcome this error. I've checked the source footage and the glitch is not present there (source foorage was a tape capture). All source files are transcoded to DV 29;97 NTSC 4:3 QT files.
The glitch itself is similar to a playback stutter but only at one specific point and always at that point. This glitch is also present on the SD DVD created in Encore. That's how I first noticed the error.
The timeline itself is almost 2 hours; I can export a shorter section around the glitch and that encodes without errors but I don't understand why encoding the entire timeline causes this reoccurring glitch/error.
I'm running production CS 5.5.1 (updated to current version), on a Win7 SP1 64-bit box, 16GB ram. Mercury Playback Engine is disabled since my card doesn't support it.
Any suggestion or help would be greatly appreciated. I've spent the last two night troubleshooting this issue and would love to get back to producing something instead of troubleshooting.
What format of footage are you using?
Is what you are seeing the same as what's being discussed here...?
(see the screenshots near the bottom of that page)
Thanks for the quick reply. The format is DV25 29:97 NTSC 4:3 in a Quicktime file. I read through the post and I don't think the pictures are similar to what I'm experiencing. I would say my glitch is closer to what's being described by the OP in this post:
There are a couple of significant problems with QuiRcktime:
That is all, at least AFAIK, but IMO that is enough of a show-stopper.
Can you offer insight into Harm's comment. Should I avoid QT in favor of AVI for future projects since I'm on a Windows machine?
Quicktime is not a requirement to run PrPro on windows. But if you want full suite-wide feature support and optimal performance, it is highly recommended that you install quicktime on windows. That's not my opinion, it's an official Adobe statement:
"QuickTime 7.6.6 software required for QuickTime features"
I've had no problems with mov files on windows as long as I have the latest qt installed. A lot of people hate QT, although I'm not sure if they've actually had any problems with it or if its just part of mac vs pc animosity.... kinda like snowboarding vs skiing or Yankeees vs Sox. Different people prefer one or the other for different reasons and I've been unable to PROVE that one is always superior or inferior to the other. (I'm pretty sure the Yankees are evil though)
But if you're working mainly in SD and exclusively on windows, then I would definately recommend using DV AVI as your format of choice. But I would still say you should have QT installed, eespecially if you're running the production suite on there.
I wanted to update this issue. I was able to successfully overcome the glitch last night. Using Media Encoder I exported the Pr sequence to an uncompressed AVI then compressed that to MPEG2 using Media Encoder again. Efficent? Not in the least. However now I'm back on track. I guess the lesson for anyone who stumbles upon this post is if your video exports out glitchy, kick out an intermediate file (AVI, Animation QT, etc) then compress that file to your final format. Thank to jstrawn and Harm for their assistance.
Europe, Middle East and Africa