VP14 (Build 211) Still choking on M2T files

JR42 wrote on 1/22/2017, 6:36 PM

Was hoping that this problem would be fixed in the latest update, but VP14 still has a lot of trouble importing HDV M2T files into the project. When you first open a folder that contains the M2T file, the explorer window freezes for a few minutes. Eventually it unfreezes and you can double click on the file. At that point, it chokes for a few more minutes before finally adding the file to the project bin.

Here is the mediainfo on the file:

Format                                   : MPEG-TS
Commercial name                          : HDV 1080i
File size                                : 17.7 GiB
Duration                                 : 1 h 33 min
Start time                               : UTC 2017-01-04 07:22:40
End time                                 : UTC 2017-01-04 08:56:34
Overall bit rate mode                    : Constant
Overall bit rate                         : 27.0 Mb/s
Maximum Overall bit rate                 : 33.0 Mb/s
Encoded date                             : UTC 2017-01-04 07:22:40

Video
ID                                       : 2064 (0x810)
Menu ID                                  : 100 (0x64)
Format                                   : MPEG Video
Commercial name                          : HDV 1080i
Format version                           : Version 2
Format profile                           : Main@High 1440
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Custom
Format settings, GOP                     : M=3, N=15
Format settings, picture structure       : Frame
Codec ID                                 : 2
Duration                                 : 1 h 33 min
Bit rate                                 : 25.3 Mb/s
Maximum bit rate                         : 25.0 Mb/s
Width                                    : 1 440 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 29.970 (30000/1001) FPS
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Top Field First
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.542
Stream size                              : 16.6 GiB (94%)
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709

Audio
ID                                       : 2068 (0x814)
Menu ID                                  : 100 (0x64)
Format                                   : MPEG Audio
Format version                           : Version 1
Format profile                           : Layer 2
Codec ID                                 : 3
Duration                                 : 1 h 33 min
Bit rate mode                            : Constant
Bit rate                                 : 384 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Compression mode                         : Lossy
Delay relative to video                  : -223 ms
Stream size                              : 258 MiB (1%)

Menu
ID                                       : 129 (0x81)
Menu ID                                  : 100 (0x64)
List                                     : 2064 (0x810) (MPEG Video) / 2068 (0x814) (MPEG Audio) / 2069 (0x815) () / 2065 (0x811) ()

Comments

NickHope wrote on 1/22/2017, 10:06 PM

Previous thread on this: https://www.vegascreativesoftware.info/us/forum/vp14-bug-hdv-files-and-projects-hanging-or-crashing--103590/

How were your HDV files captured?

JR42 wrote on 1/22/2017, 10:57 PM

I remember that thread, it wasn't helpful in my case. The HDV files in question are from my Firestore FS-C. (They are captured in 1.7 gb chunks, then assembled with a file joining program). The resultant m2t files work just fine in Vegas 9, 10, 11, 12, 13, but choke 14 still. I was hoping there was a workaround, other than using 13 to re-render the M2T file out.

Wolfgang S. wrote on 1/23/2017, 2:27 AM

But this means that the files may be different from original HDV files maybe, due to the assembling process?

I have tested the import of large HDV files shoot with my old FX1 and captured with earlier versions of Vegas Pro. There were also large GB-pieces, and they open without an issue. Another difference is that my files are PAL files (so 1080 50i).

JR42 wrote on 1/23/2017, 3:24 AM

Even if the joined single file from the FS-C was somehow different from a tape-captured HDV file, it still wouldn't explain why Vegas 9 through 13 could handle the file with no problems, but 14 does not.

NickHope wrote on 1/24/2017, 1:21 AM

I would try running the files through MPEG2Repair. Probably won't help, as I think I tried it unsuccessfully for the original problem with earlier builds of VP14, but you never know.

JR42 wrote on 2/14/2017, 1:03 AM

Had this problem rear its ugly head in a new way. This time, the m2t file (created in the same manner as the others that have given me problems) immediately loaded in Vegas, which surprised me. However, even though the file is 2hrs 36mins long, the same frame from the beginning is there for the full length of the video. The sound is fine.

I can play this file with VLC or Media Player and the video works as normal, but Vegas just has an image of that first frame for the whole length of the clip.

I did run that file through Mpeg2Repair, and the resulting file would play in Media Player and VLC just fine, but *after* the repair it actually crashed Vegas 13 and Vegas 14 both.

Wolfgang S. wrote on 2/14/2017, 3:03 AM

Even if the joined single file from the FS-C was somehow different from a tape-captured HDV file, it still wouldn't explain why Vegas 9 through 13 could handle the file with no problems, but 14 does not.

But that is the wrong question. Simply because the devlopment team cares about original HDV files and has ensured that also huge HDV original files can be imported without an issue. I know that for sure because I have delivered them a huge HDV projekt with long original files captured from my old FX1 directly. And this works fine now.

But the development team cannot and willnot take any responsibility for modified merged files from a third party tool, where it is not clear what happens in the structure of those files during the merging process.

So either you use original HDV files. Or you convert the merged files to another file format (for example to Cineform) if they are part in a project that you wish to continue to edit in VP14. Or you edit that in the earlier versions. I think there will not be any other solution.

NickHope wrote on 2/14/2017, 10:19 AM

I did run that file through Mpeg2Repair, and the resulting file would play in Media Player and VLC just fine, but *after* the repair it actually crashed Vegas 13 and Vegas 14 both.

Sorry about that! Hopefully you have the original copies.

What "file joining program" did you use? I'd be interested to test if it has the same effect on my various HDV programs. I have multiple versions of Vegas Pro installed.

JR42 wrote on 2/14/2017, 1:47 PM

I use Simple File Joiner. It works most of the time, but there was something about this file that just didn't want to work in Vegas. I should also note that I've used MPEG2Repair in the past and it has helped on occasion, but most of the time it doesn't.

I ended up firing up a program I forgot that I had, TMPG Mastering Works 5, and it not only read the problematic M2T file, but I was able to render out a M2T file that worked perfectly in Vegas.

JR42 wrote on 3/8/2017, 5:31 AM

Most of us, even if we're still using our XH-A1s and XL-H1's are not rolling tape, so it's essential that Vegas be able to use the files from digital recorders. I have another file joining program that essentially is a batch file with DOS commands (i.e. copy /b 001.m2t + 002.m2t + 003.m2t....etc) and I will see if the joined file works any differently from the one from Simple File Joiner.