Can Vegas handle .m2t files?

Chienworks wrote on 4/11/2008, 12:51 PM

I use 1080p and 1080i .m2t files with Vegas often. No problems at all.

blink3times wrote on 4/11/2008, 1:13 PM

I used to get lots of crashing on the original version 8, but I'm finding 8b to be much more solid. What version are you using?

MH_Stevens wrote on 4/11/2008, 2:27 PM

"Can vegas handle m2t files?"

Is the pope a Catholic? Mpeg 2 transport stream is the native format of the Sony HDV cameras. Yes, Vegas handles transport streams effortlessly. Of course, you PC might not unless it is at least of moderate power.

johnmeyer wrote on 4/11/2008, 2:40 PM

Use either the latest version of Vegas 8 (8.0b), or use Vegas 7.0d. Earlier versions do not handle m2t, and versions other than the two I listed can, under some circumstances, have problems with m2t.

Videojohn wrote on 4/12/2008, 12:25 AM

OK thanks.
But are the .m2t files from 720p (JVC) equals to the .m2t files from 1080i (SONY)?

Thus the best way to edit HDV (.m2t) files with Vegas is simply to import the original footage directly to Vegas (without using a third party like cineform for example) and edit. That's all?

I have a 3,0 Ghz processor and 2 GB RAM and maybe it is something else but I have quite a lot of problem with those files!

Videojohn wrote on 4/12/2008, 4:58 AM

Anyone can help on this issue?
Thanks

Chienworks wrote on 4/12/2008, 5:16 AM

"But are the .m2t files from 720p (JVC) equals to the .m2t files from 1080i (SONY)?"

I'm not sure what you are asking. One format is 720p and the other is 1080i. No, they're not equal. Yes, they are both .m2t files, but the 1080i frame contains 2.25 times as many pixels as the 720p frame. This means that Vegas and your computer have 2.25 times as much work to do when using 1080 files. The frame rate might drop and the renders could take longer. Other than that Vegas can handle both formats equally well, just slower for 1080. Is that the problem you are seeing?

With Vegas 6 and 7 converting to cineform was recommended. With Vegas 8 enough improvements were made that this generally isn't necessary anymore.

Videojohn wrote on 4/12/2008, 8:09 AM

Thanks. It answers to my question.
Thus I will use Vegas only to import HDV (because I have been having very strange problems of audio streams being shorter than vidoe streams - in terms of time indicated but ot in terms of clip envelop!!?!) - when importing with connect HD 2.1).

Even without any effects added, the fnel project will have to be rndered in .avi isn't it?

Chienworks wrote on 4/12/2008, 10:55 AM

Yes, it will have to be rendered to avi ... only if you need an avi output file. If you need an MPEG output file then it will have to be rendered to MPEG. Whats your final output requirement?

Laurence wrote on 4/12/2008, 11:16 AM

I have learned a lesson lately about m2t clips crashing in Vegas: that is that the crashes are due to errors the were introduced during the capture process. I have had flawless captures over the last week by turning off my virus protection and anything else that might be running in the background during capture. What a difference. The captures since I started turning off background processes have not crashed once.

I use HDVSplit. but with the Vegas capture as well, turning off background processes should give you m2t clips that won't cause the crashes you have been experiencing.

Videojohn wrote on 4/12/2008, 1:00 PM

The problem thatI discovered now is that when I try to import the .m2t files from the hard disk to Vegas Media Pull. Vegas constantly crash giving a message like "memory error".

A way not to crash is by importing the files one by one in the media pool. But I have more than a hundred files per tape!!! (by the way is it possible to import a one big 1hour .m2t file, with Vegas capture window - it does not give the option to do that and creates a file at each cut in the tape)

I have Kasper sky antivirus installed on the computer, do you think it's an issue? But my problem is not with the capture of the file from the tape but with the importing of the .m2t files into the Vegas media pool.

ANy suggestion?
Thanks

Videojohn wrote on 4/12/2008, 4:18 PM

It is not the anti virus because I disabled it.

But What happens is very strange.
I don't succeed to import at once several .m2t files from the disk into Vegas Media Poo. When I try that, Vegas crashes.

At first I thought that it was because some files were corrupted, because I was seing green clip in the pool. Thus I trie to import all otther clips except the one I thought was corrupt. But each time I isolated the pretended corrupted files, others were appearing and making Vegas crashing!

tHus I trie to import the pretended corrupt file alone and it worked!!
My conclusion is then that the .m2t files are not corrupted but that Vegas does not succeed to import them into the pool

Whe this happens the error message says something like "reading memory error"

Does it means that Vegas does not succeed to import many .m2t files at the same time?
What should I do to fix the problem?

[Just for info my hardware spec are: Pentium 4, processor 3.0 Ghz; RAM 2 GB, mother borad Asus delux pc800]

Former user wrote on 4/12/2008, 4:20 PM

I've never had a problem with .m2t - just straight into Vegas and start cutting.

Heck, I've just dragged VOB files off of DVDs and edited (it takes a while, but it works).

Jim H wrote on 4/12/2008, 10:40 PM

sounds like you are running out of memory. The only time I have crashing problems with Vegas and HD files is when my projects grow large...like 30 minutes or more. But my crashes come during rendering not loading onto the timeline.

And your idea of capturing via one LARGE m2t file is probably not a good one. I think you're better off with smaller files as far as memory management goes.... but I have no proof of that, just a strong hunch.

Terry Esslinger wrote on 4/12/2008, 11:17 PM

I captured a one hour HDV 1080i tape via Vegas7d. It was one long clip (a stage play) and the camera was never stopped. But it captured in 4 separate files, some short and some long. I had scene detection turned off, which shouldn't have made any difference since it was one long scene anyway. There was a short missing segment at each capture break. Should I somehow break the capture up intop smaller segments? And how? It is possible that dropouts occurred at the capture break points. Would this cause this kind of problem at capture?
Hope this fits into this thread, if not I apologize.

Videojohn wrote on 4/13/2008, 3:38 AM

Hi Jim, when you say a memory problem, what do you mean?
I guess it's not the RAM memory because I've got 2GB and when I import thoses files into Vegas I only have Vegas opened.

What king of reources do Vegas need to import these .m2t files in the media pool? Can it be linked to the lack of space in disk C?

Videojohn wrote on 4/13/2008, 8:32 AM

I made other test and again, Vegas crashes when I want to import the .m2t files from the disk to to media pool.

The error message says that the computer is running low in memory and that I should close all other applications. But I have no other applications open in the background!!!!

And I have 2GB RAM! So what is the problem? Anyone has a suggestion?

Videojohn wrote on 4/13/2008, 9:11 AM

Definitly Vegas does not succeed to import in the media pool, the .m2t files
Here is a copy of the details of the error message that it produces (can it be a problem with the MPEG plugins?)

HERE IS THE ERROR MESSAGE:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0xE7080053 IP:0x760045
In Module 'vegas80.exe' at Address 0x400000 + 0x360045
Thread: GUI ID=0x9F8 Stack=0x12A000-0x140000
Registers:
EAX=e707fc3f CS=001b EIP=00760045 EFLGS=00010286
EBX=0012a5c0 SS=0023 ESP=0012a5a4 EBP=8004e02e
ECX=fffebee8 DS=0023 ESI=61ec0388 FS=003b
EDX=014079f0 ES=0023 EDI=231c47c5 GS=0000
Bytes at CS:EIP:
00760045: 8B 80 14 04 00 00 85 C0 ........
0076004D: 0F 84 FA 00 00 00 F6 00 ........
Stack Dump:
0012A5A4: 432B2B00 431E0000 + D2B00
0012A5A8: 474E5543 47380000 + 165543
0012A5AC: 61EC0A40 61530000 + 990A40
0012A5B0: 0012A5C0 00040000 + EA5C0
0012A5B4: 0012A5C8 00040000 + EA5C8
0012A5B8: 8004E02E
0012A5BC: 0012A57C 00040000 + EA57C
0012A5C0: 06C0F0F1 06B10000 + FF0F1
0012A5C4: 0012A604 00040000 + EA604
0012A5C8: 61EC0A40 61530000 + 990A40
0012A5CC: 61EC0388 61530000 + 990388
0012A5D0: 00120000 00040000 + E0000
0012A5D4: 0012A5E4 00040000 + EA5E4
0012A5D8: 231C47C5 23000000 + 1C47C5 (mcmpgvdec.dll)
0012A5DC: 61EC0A40 61530000 + 990A40
0012A5E0: 00120000 00040000 + E0000
> 0012A5E8: 231C34B2 23000000 + 1C34B2 (mcmpgvdec.dll)
> 0012A5F0: 231D4C58 23000000 + 1D4C58 (mcmpgvdec.dll)
> 0012A5F4: 231C4DD0 23000000 + 1C4DD0 (mcmpgvdec.dll)
> 0012A61C: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A620: 231C735C 23000000 + 1C735C (mcmpgvdec.dll)
> 0012A628: 231C3450 23000000 + 1C3450 (mcmpgvdec.dll)
> 0012A648: 231C350A 23000000 + 1C350A (mcmpgvdec.dll)
> 0012A650: 0FB004F1 0FAF0000 + 104F1 (mcmpgdmux.dll)
0012A654: 6B3B2E48 68130000 + 3282E48
0012A658: 6B4A3E48 68130000 + 3373E48
0012A65C: 0012A75C 00040000 + EA75C
0012A660: 61EC09B0 61530000 + 9909B0
> 0012A67C: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A680: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
> 0012A688: 231C3528 23000000 + 1C3528 (mcmpgvdec.dll)
> 0012A6A8: 23024BB9 23000000 + 24BB9 (mcmpgvdec.dll)
> 0012A6D0: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0012A6D8: 2302D629 23000000 + 2D629 (mcmpgvdec.dll)
> 0012A708: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0012A740: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A744: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0012A74C: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0012A758: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0012A788: 23029B99 23000000 + 29B99 (mcmpgvdec.dll)
> 0012A7B8: 23027D9C 23000000 + 27D9C (mcmpgvdec.dll)
> 0012A7D8: 2302612B 23000000 + 2612B (mcmpgvdec.dll)
> 0012A7F8: 2322735F 23200000 + 2735F (mcmpegin.dll)
> 0012A828: 2322C39C 23200000 + 2C39C (mcmpegin.dll)
> 0012A888: 33BBAF6B 33BB0000 + AF6B (mcplug.dll)
> 0012A8A8: 7C913E62 7C900000 + 13E62 (ntdll.dll)
> 0012A8BC: 003A004C 00360000 + 4004C (sfwbdmux.dll)
> 0012A8C0: 0041005C 00400000 + 1005C (vegas80.exe)
> 0012A8C4: 00740063 00400000 + 340063 (vegas80.exe)
> 0012A8C8: 006F0069 00400000 + 2F0069 (vegas80.exe)
> 0012A8CC: 0041006E 00400000 + 1006E (vegas80.exe)

Laura K wrote on 4/13/2008, 10:10 AM

Ya until you have to render to m2t.
Good luck.

Videojohn wrote on 4/13/2008, 11:39 AM

Good luck thank you.
But does anyone has any suggestion?

John_Cline wrote on 4/13/2008, 12:33 PM

Some .M2T files can cause problems for Vegas, one thing to try is a freeware program called "mpeg2repair." It's fixed a fair number of problematic .M2T files for me.

http://download.videohelp.com/download/mpeg2repair1015.zip

Videojohn wrote on 4/13/2008, 1:19 PM

OK Thank you I will try this.
But Why the .m2t files should be corrupted?

I really need a solution. Because I tried to import the footage via connect HD 2.0 and waht happens is that the audio stream is shorter than the video stream!!!!!!!! (thus the audio is out of synch -and not just a little as much as 1 sec.)

PLEASE HELP!!!!!!!!!!!!!!!!!!
I really don't know what to try now!

Videojohn wrote on 4/13/2008, 3:25 PM

I reinstalled Vegas 6.0c and succeeded to import the .m2t files.
It seems to be Vegas 8 that has problem. Can it be a bug?

Chienworks wrote on 4/13/2008, 4:36 PM

If the only problem is the audio track being shorter then this is easy to fix. Ungroup the audio and Ctrl-stretch it to match the video. Select both and regroup.