This content has been marked as final. Show 9 replies
As an update, I tested the MPEG2VCR trimmed files in Vegas 7.0e, they import and play perfectly. The trimmed files also play perfectly in media players like VLC and PowerDVD. The problem only happens when importing these files into PPro CS3!!!
Patrick avoid posting the same thing in multiple forums.
You will not like the answer, rather than trim your footage just import all the original footage and trim in Premiere.
Use Premiere 2.0 even though you do not want to.
As another experiment, I tried trimming an M2T file in Womble MPEG Video Wizard DVD (their replacement for MPEG2VCR) and the trimmed clip again plays back pixellated in PPro CS3 but ok in other programs.
Rather than just throw in the towel and go back to 2.0, I'd really like to know the root cause of why this is happening, and why the files work ok in 2.0 but not in CS3. My understanding is that a TS file (transport stream) and MPG file (program stream) are identical except that the TS (M2T) file adds a few additional error correction bits for carriage of the signal over less reliable carriers, like broadcast. There must be something with those bits that are changed by trimming in MPEG2VCR, even though it is supposed to be a GOP-accurate editor, which other players can correct for but not CS3.
I cannot answer your question, however I would personally drop the entire intermediate step and import straight into Premiere.
Do not forget Premiere Pro is not well suited for MPEG in general, stick to Premiere Elements or Vegas.
>Do not forget Premiere Pro is not well suited for MPEG in general, stick to Premiere Elements
So - let me get this straight - Premiere Elements can handle MPEG files for a measly $150 or so, yet the much more expensive Premiere Pro cannot? Do I need *both* applications, and would this cause conflicts?
Neil and Patrick,
I have very few problems editing MPEG on Premiere Pro's timeline, with or without the MPEGPro plug-in.
CS3 seems to be very fussy about GOP structure. If you examine a clip that works with one that doesn't using GSPot's graphical display of GOP structure, you'll see nice, consistent GOP lengths for the clips that work, and irregular, choppy, inconsistent GOP lengths for those that don't.
And if it turns out that a muxed Program Stream works, but still has the irregular GOP structure, then I don't know what is going on.
EDIT: Womble may not re-encode the video, but trimming is most likely changing the GOP structure to the point where PPro CS3 doesn't like it.
I have to agree with Howard. Why trim the clips before bringing them into an editor whose very purpose is to trim the clips?
If the original files work, use them. If you need more hard drive space (as many editors do), buy another hard drive.
I trim in MPEG2VCR to save HDD space and delete unneeded HDV footage before bringing in into CS3. I know it's easy to 'trim' on the timeline in CS3, but by design CS3 does not modify/trim the original file, which is what I wanted to do before bringing it into CS3.
I will check out that program to analyze GOP structure.
And if you save the clips as MPG program stream in MPEG2VCR, CS3 takes them and plays them just fine. Can anyone confirm, there is no image quality loss whatsoever by this transcoding to MPG from M2T, correct? Bitrate, resolution, colorspace, all remain unchanged, and from my understanding, what changes is you lose some of the extra error correction bits that are embedded in the M2T files.
>I trim in MPEG2VCR to save HDD space
The second part of my earlier post would be the correct handling there.