Media Info doesn't report much out of the ordinary, but it also won't load in Ppro either.

Sorensen Squeeze will accept/reencode it and once reencoded (mpg), Vegas will take it but I have no idea what the original problem is.

This may or may not be related, but back when I used HDV, I would get occasional random errors embedded in the captured clips if I had virus protection turned on while I captured video. It took forever for me to figure that one out. I believe my computer was checking the captured media for viruses as it was capturing. The errors ranged from minor but annoying glitches to completely unuseable clips that would hang or crash Vegas. Turning off virus protection during the capture completely eliminated this. This was with the P4 I used to use back then, and of course current PCs are a lot more powerful, but virus protection has also gotten more invasive and clunky, especially Norton and Security Essentials. You might want to try recapturing with no virus protection.

remuxed with tsRemuxer (different from tsmuxer) an result worked fine.

original crashed here too.

http://www.videohelp.com/tools/TsRemux

This piece of freeware has saved MANY weird HDV captures for me back when I got a lot of HDV from clients. It fixes and logs all errors, I got to the point where I just ran all HDV captures through it just to make sure it there was nothing weird.

http://home.roadrunner.com/~mwilczyn/mpeg2repair/

1. Opens and plays fine in VLC media player.

2. Opens and plays fine in Vegas 7.

3. Opens and plays fine in Vegas 8.

4. Opens and plays fine in Vegas 10.

All these are installed on Windows XP Pro 32-bit SP3.

So, once again, later versions of Vegas are more buggy, less forgiving, and generally less reliable.

I also have Vegas 11 installed on my Windows 7 partition, but I almost never boot to that and haven't had any reason to use any later version of Vegas for the past year.

So, if you have access to any earlier versions of Vegas, you can certain use that.

I had an extra moment, so I booted up to Windows 7 64-bit and ran Vegas 10, 64-bit.

1. Vegas 10, 64-bit crashed, even though Vegas 10, 32-bit under Windows XP Pro 32-bit SP3 worked fine.

2. I then tried Vegas 11, 32-bit under Windows 7 64-bit, and it worked!!

3. Finally, I tried Vegas 11, 64-bit under Windows 7 64-bit, and it crashed.

Conclusion: the problem is in the 64-bit implementation of Vegas. It looks like a bug to me, and the problem extends backwards to at least one previous revision.

SCS, are you listening? Does anyone want to file a bug report??

I tried the file in Vegas Pro 9-64 bit, 10-64 bit, 11-64 bit and 12-64 bit on my System 1 running Windows 7 64 bit.

Vegas 9-64 bit worked fine. All others failed.

The bug appears to me to have been introduced in the Vegas Pro 10 code.

I trust that someone is filing a formal bug report on this.

Edit: I ran the source file through VideoReDo Quick Stream Fix and all versions of Vegas Pro were able to accept the resultant file. The repaired file was 6 frames shorter at the end than the original. Earlier versions of VideoReDo may not look for the .M2T extension but will accept the file if one enters *.* in the search box.

Hello everyone,

Thanks for testing the source and giving suggestions of small useful repair apps.

MPEG2Repair and TsRemux repair the file.
MPEG2Repair log:

MPEG2Repair: D:\20140125 Sugih - Lia Hyatt\Vid Z5\01_0021_2014-01-25_170147.M2T


Sequence Frame 987(5-P) / Time 0:00:39 :
VideoError: Missing 4410 slice macroblocks at MBA=1710(0,304)
Additional error(s) detected. Increase VerboseLogLevel in INI file for details.
FileInfo: Last video errors span 41 bytes at file offset 129010632

Sequence Frame 988(0-X) / Time 0:00:39 :
FileInfo: Last video errors span 7 bytes at file offset 129010669
VideoWarning: Unexpected MPEG2 start code 00000100 skipped
Info: End of MPEG2 sequence

Sequence Summary:

File Size Processed: 123.03 MB, Play Time: 00h:00m:39s
1440 x 1080, 25.00 fps, 25.00 Mbps (25.01 Mbps Average).
Average Video Quality: 122.01 KB/Frame, 0.64 Bits/Pixel.
MPEG Audio.
1 of 988 video frames found with errors.
0 of 0 audio frames found with errors.
47 corrupted video bytes in file.
0.000000 seconds of video timestamp gaps.
0.000000 seconds of audio timestamp gaps.

End of Log


Question of TsRemux: which output preferred? m2ts or ts? look similar when put to timeline.
How do you make batch process for whole files for this tool?
I hope this can also fix other bad error I had too before... (all of them are rescued too)

John Dennis, cutting 6 frames with VideoReDo seems too much, usually freezed-image on every end of recorded hdv media are just 2 or 3 frames...

---
Whether this has been reported or not, just sent ticket via my support, to tell developers about this 64bit issues we found together with link to this thread. Hopefully this info can be useful for further Vegas Pro development.

"Conclusion: the problem is in the 64-bit implementation of Vegas. It looks like a bug to me, and the problem extends backwards to at least one previous revision."
But it doesn't load in Ppro either. Same bug in two different nle's? Nah... I don't think so. There is a problem with that clip and some nle's/versions are simply better than others at overlooking the issue(s)

MPEG2Repair does a good job of repairing the file so that it opens in later versions of Vegas Pro. Because of the error, you still might have to look for what appears to be error frames that were possibly part of the original problem.

Here

Frame 987 didn't even show in VideoReDo, it stopped at 984.

??? on batch manager.

Rob Franks, try put this clip into PPro:
https://www.dropbox.com/s/k9k87u9dl7h6l4w/00_0001_2014-01-25_063256.M2T
It is normal first recorded clip of that day. I guess it should be no problem.

Yes John, the last frame is a little 'bad'. Other from bad, freeze 2 or 3 frames too.
It is usual for every tapeless HDV record compared to tape workflow (Record using HDVSplit program but without automatic splitting. Scene Splitting is done later after whole tape is recorded.)
So inside Vegas, all last frames must be cut, one by one...

At least now all media has been safe and ready to be edited.


Sorry for confusion of batch process...: When I look for MPEG2Repair or TsRemux, I noticed somewhere about how to make batch process for whole files using this tool, but instantly forgot where i read that and can't find the article again...

Hi, as you know before, I have reported this problem via 'My Support' as well.
Just had reply how to deal with this problem:

Go to C:\Program Files\Sony\Vegas Pro 12.0\FileIO Plug-Ins\compoundplug

In that folder, you will find a compoundplug.dll file. Copy and paste this file to another directory on your hard drive to back it up. After you back up the file, rename that file to something like compoundplugOld.dll

I had tried it and I can finally import without issue. You will see dialog box error, but just ignore it, render to intermediate format. When render finished, you can rename compoundplug back. I'd rather touch this dll when I need it.

Hope this helps for other users too. This issue has been forwarded to development team too.
Better a bit late then never answered. Thanks Travis G. from Customer Service for replying :)