Hopefully Vegas 7 can handle unlimited (within reason) m2t files on the timeline. This would make it useable with a directory full of scene split m2t files like you end up with using HDVSplit. I expect that this will work properly with Vegas 7. Can anyone confirm this?
M2T is the file type for an MPEG-2 Transport Stream. This is the format that HDV cameras record in. It is very CPU intensive to decode and Vegas 7 improves the handling of these files.
To add to JR's comment, answer, and question...
Vegas 7 handles uber-numbers of m2t files. It was extensively tested in Beta.
GearShift still has it's values, because:
1. Slow computers still can take better advantage of proxies.
2. Output to HDCAM still requires conversion; better to convert what you need rather than entire fileset
3. While native m2t support is terrific, if you're compositing or rendering more than one time (including render to new) then you definitely don't want to be using MPEG files as your source.
The Gearshift question is: Can Vegas 7 now handle more than 80 m2t files or does it still crash and burn when you try to do this? This relates to trying to use Gearshift with HDVSplit and timecode and a bunch of timecode split m2t files rather than one single large m2t file. This would make Gearshift actually useable for me personally.
I'm aware of one beta project that used more than 3000 m2t pieces on the timeline....
I've got one open right now with 40 hours of raw footage, a 5 hour timeline, and at the moment, 1123 events. All HDV except for generated media.
This machine is a dual 270 CPU, on a Tyan mobo, with a built in 750GB RAID. 4 GB RAM...using an AJA XENA card as well, but didn't start out using that for this project, however, all new captures are being done thru the Xena.
Vegas 7 of course.