Vegas M2T audio peak issue... a fix!

jcloninger wrote on 2/1/2009, 6:36 PM
In prior versions I had the problem of peaks flatlining or missing on some clips and the audio would or would not be audible in these regions. I've seen this issue in several forums... well, On version 8.0c, I never really saw this issue until yesterday! I tried and tried all kinds of things (I won't list them all here, but trust me... almost everything from trying to export audio from other programs and incorporate to "fix it all" programs, etc.)

Sony needs to look into this program I'm about to tell you so they could create a feature like this in their next version. Anyways, here it is:

http://www.videoredo.com/en/Download.htm

Download the trial (I'm gonna buy it just to have for when I need it... it costs $50) Register for the trial key!!!

Open Video.

On files of type, choose "All files".

Select your faulty m2t file.

Go to tools and select "Quick Stream Fix"

Choose your output file name, and CHANGE THE EXTENTION TO M2T.

Open that file in Vegas. ALL IS FIXED!

It took 11 minutes to do a 1 hour 5 minute clip (it would go faster if the program would use all 4 cores, but it won't) and it said it found 5 Video resync frames removed.... whatever that means.

Its a corny looking program, but it works! That's all I care about!

Comments

owlsroost wrote on 2/3/2009, 11:32 AM
it said it found 5 Video resync frames removed.... whatever that means.

These are caused by data errors in the original file - it removes the corrupt data frames (so you'll now have jumps in the file where the errors were) and re-constructs the timestamp data so everything is error-free.

It took 11 minutes to do a 1 hour 5 minute clip (it would go faster if the program would use all 4 cores, but it won't) and it said it found 5 Video resync frames removed.... whatever that means.

It's more limited by disk performance than CPU speed.

Tony
jcloninger wrote on 2/3/2009, 3:45 PM
These are caused by data errors in the original file - it removes the corrupt data frames (so you'll now have jumps in the file where the errors were) and re-constructs the timestamp data so everything is error-free.

Cool. Kind of what I figured, but didn't know for sure.

It's more limited by disk performance than CPU speed.

I probably should have had it write to another hard drive.