-
how to fix *one* M2T file (or otherwise get premiere pro to import correctly)
Hi,
I am working with Premiere Pro (part of CS6) and I am having problems with only ONE M2T file (shot on a Sony Z7U). I use M2T and MTS files all the time with no problem, but a single file is giving me trouble.
The video clip is of a performace.
An M2T file up to a given point in the performance works fine.
But when I import the next M2T file into my Premire Pro project, it shows the start and end times, and the resolution in the list of clips, *but but the clip name is in italics, and for the duration it shows “pending” and the clip will not show any viewable media in the sequence.* No matter how long I wait, it doesn’t improve.
Here is what I’ve done to remedy it:
— I can run it through Media Encoder. I see the frames go by as it is transcoded, and the new file seems fine — but when I load it into Premiere pro, I get the same problem as before: the duration remains pending and it won’t show in the sequence.
— I rant it through MPEG streamclip to fix timecode breaks. Again, Streamclip shows every frame as it goes by, with no problems, and says there are no timecode breaks. But the resulting file still isn’t viewable/useable in the project.
The only odd thing about the clip is that (in encoder and streamclip) I can see that the first frame is somewhat messed up, as if different color components of the image are shifted out of alignment, kind of like a color print where one color is off register.
But otherwise, the media seems fine. So I’m assuming that some kind of end points of the file got corrupted, or the wrapper is messed up.
The most puzzling thing is that every kind of media reading software I try seems to have no trouble with the file EXCEPT premier pro.
Any suggestions?
Edwin
-
3 Replies
-
Clipwrap. Free demo. See what it can do
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Hi Shane,
Supercool. The one minute section of the clip that I ran through the trial version of Clipwrap is now viewable in my timeline. It looks like it will cost me $50 to buy the full version of Clipwrap to fix the entire clip, but I think in this case it’s probably worth it.
Do you happen to know a) what is likely wrong with the clip and what clipwrap is doing to make it work in Premiere and b) why it is that other applications (encoder most importantly) seem to just pass the clip through with whatever the problem is intact? It seems like Encoder should deal with things like this…
Thanks again,
edwin
-
The guys who write ClipWrap are geniuses. Always on top of latest tech or any issue. A new format came out that I had an issue with, they had a solution in 2 days.
I SWEAR by them.
Shane
Little Frog Post
Read my blog, Little Frog in High Def
Reply to this Discussion! Login or Sign Up