Vegas can't handle lots of m2t clips at once!

Comments

johnmeyer wrote on 4/19/2006, 4:04 PM
I never did get an answer on what version of Vegas is being used. I know from something I read several months back that Sony has improved the handling of "native" HDV files (m2t) since Vegas 6 was first introduced. If you are not already using 6.0d, I'd definitely suggest that you upgrade.
riredale wrote on 4/19/2006, 4:09 PM
John, 6d.

So I guess my best bet is to capture to disk using HDVSplit. Then I GearShift render into widescreenDV and Cineform. At that point I can just throw the original m2t clips away.
Laurence wrote on 4/19/2006, 6:57 PM
I have been using Vegas 6d since it came out.
Laurence wrote on 4/20/2006, 4:18 PM
Just an update:

I have two current open projects. One is a local art piece with about six hours of footage and one is the short and sweet wedding of my best friend. I just converted all the footage on the longer piece to Cineform AVIs, but when I got to the shorter piece, I noticed it was only about 45 clips and it will work just fine (being less than 90) with the Gearshift/HDVSplit short m2t clips approach so I left it alone. Now at least I know what parameters I'm dealing with. I know not to put more than around 80 m2t clips on a Vegas timeline at once.
Wolfgang S. wrote on 4/23/2006, 7:33 AM
Unfortunately, the whole story is not new at all. Anly some month after the launch of Vega 6, this problem was reported in our German spoken Vegas forum. The limit was identified somewhere between 60 to 80 m2t files - then the page file climbs up dramatically, until Vegas crashes. Where the limit is,depends on your machine and your RAM.

With Vegas 6d it has become a little bit better - but even here the NLE crashes at 100 or 150 m2t files.

Well, we have reported that to the Medision team 10 month ago. But it became clear that the recommendation is to work with the intermediate codec (Cineform is fine, but also the Canopus HQ works fine with Vegas). When you do so, you avoid the issue with the page file - and these codecs allow better preview capabilities.

In addition, it is not true that you will loose significant quality when you use the Intermediate instead of the native m2t file. I have tested that in some detail. The opposit is true. If you have to render m2t files more then one time, the quality drop is higher, compard with the workflow where you render m2t -> intermediate -> final product.

Originally, I have published the results here:
http://videotreffpunkt.com/tutorials/Intermediates/Intermediates%20Part%201.html

I think that Vegas7 will be better here. But in the meantime one possible way is to use Gearshift (or other tools) to render to the intermediates - and cut the intermediates.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems