This content has been marked as final. Show 9 replies
Using Magic Bullet Looks?
Sometimes you can have a bad filter or a bad spot on the timeline. It can also be a time change that can effect something. See if you can figure out where it is bombing and check that area for effects on your footage that might need a tweak.
Source: FFDShow Mpeg2, 30fps, 640x480
Premiere Pro CS4 4.0.1 EN
Sequence: 640x480 @ 30 FPS, 48 kHz audio
Length is approximately 13 minutes.
No 3rd party plug-ins.
Windows XP SP2 EN
AMD FX-53 2.4 GHz
2 GB RAM
Nvidia 7800 GT
WD Raptor 73 GB. 12 GB free. NTFS
It was encoding prior to 4.0.2 @ 4.0.1. Well, with caveats. Lagarith would have red artifacts in a few frames. Divx and xvid encodes using AME had heavy artifacts in almost every frame. But at least it would finish encoding.
No magic bullet looks; at least, I don't think so. I'm not sure what those are.
I don't think it's a bad spot on the timeline because the stop point doesn't ever seem to be in the same spot. Sometimes 10% into the encode, sometimes 50%, sometimes, 95%.
Encoding a small subset of the sequence, does seem to work. I suppose I could just encode the whole sequence in pieces and string them together with a different app if I really have to.
Other than that, it's looking like a reinstall?
Yes, sorry. The original original was MJPEG @ 30 fps, 640x480.
Others have reported problems with the MJPEG codec. What MJPEG codec do you have installed on your system? IIRC, MainConcept seems to be the best choice.
Hi Jeff. Actually my PPro source files are in mpeg2 (or 1, i forget which now). I was just clarifying for Eddie.
Right now, I've decided to cut up my sequence into blocks of 6000 frames. It seems to encode fine like that. Very bizarre. So far, anyway. I've only done 1 so far.