Sony Vegas Movie Studio 8 Memory Issues

[Jeremy Rasnic]

I don’t know why m2t files are causing that error. How many are you putting on the timeline (the consumer version may have a limit but that sounds unlikely)? What else do you have running and what else is on the timeline?

When you say importing m2t files do you mean capturing via the capture utility that comes with Vegas? Or are they hard drive files that you are simply dragging and dropping over from the cam?

As for an easy way to edit m2t- Vegas comes with a Cineform Avi file option (they are intermediaries). You can go to Cineform and buy a more robust capture utility to capture directly to this format (more disk space when using avi). Or you could go to Vasst.com and take a look at gearshift or Ultimate S pro (US4 pro). Gearshift is included in US4 pro and it will allow you to use dv proxy files to do all your edits on and then switch back (gear shift) to HD files before rendering. Those both have 15 day free, unhindered trials. And if your files are hard drive based- AVCHD, they also make a product called AVCHD Upshift that will convert from AVCHD to M2T files which are easier to edit than AVCHD.

j razz

[Mike Schwartz]

Thanks for considering my predicament Jeremy.
I’m trying import a few hundred m2t files into my project. They are all very short clips. These files have already been captured by a different app, and are now sitting on my hard drive.

My preference is to import all of the m2t files into my project, analyze which ones I want to keep, then delete the rest. I’ll likely end up with 100+ clips (i.e., m2t files) on the timeline.

I don’t think Sony Vegas Movie Studio has any issue with the actual m2t files, as they play back just fine within SVMS. My issue is the cap of virtual memory. Even after re-formatting my drive, re-installing XP, updating to SP3, I still see this in Help>About>Computer tab:
Memory
Physical memory: 2,097.1 MB
Paging memory available: 4,194.3 MB
Virtual memory possible: 2,097.0 MB

I have tried variations on setting the page file space (let windows manage AND set explicit min/max well above 2GB). In every case, SVMS always shows the above numbers.

Can someone look in Sony Vegas Pro and see if it shows similar virtual memory limitation? I’d really appreciate it. I’m excited to move from Premier Elements to SVMS, but cannot if there is this limitation. Perhaps I’ll have better luck with Pro.

[Mike Schwartz]

I’ve done a bit more testing on the Sony Vegas clip limit I’m experiencing. The nature of the issue is this: The Media Bin has an import feature. When I import video files (from my hard drive), Sony Vegas (Pro and Movie Studio, Trial versions) starts to get flaky when Windows page file (PF) usage approaches 2GB. I think the issue is with the Sony product, because on the same computer, Permier Elements doesn’t have this issue. Furthermore, as stated in other posts below, others have the same issue (it’s still an issue 2 years later since those posts) on different hardware specs, indicating it’s likely a Sony issue.

Test 1:
Imported 90 HD video files (.m2t). At about 1.88GB PF Usage, clips stated to go “offline”, video tracks were missing in clips (but audio was present), the import file picker couldn’t produce video file properties, and finally Sony reported a memory error. This occurred in both the trial versions of Sony Vegas Pro and Movie Maker.

Test 2:
Imported about 360 low resolution quicktime (.mov) files. At about 1.75GB PF usage, all the same symptoms occured as in Test 1.

Tests were completed where:
– Windows manages the page file
– Page file was set explicitly, very large (min/max == 10GB) on a SATA-2 drive dedicated solely to the page file.

Other posts indicate Sony Vegas is buggy in that it has a clip quantity limit, and other posters have indicated the 2GB page file limit. Sadly, Sony doesn’t address any of this in their KB, nor have they repaired it.
https://forums.creativecow.net/readpost/24/821885
https://www.dvinfo.net/conf/showthread.php?t=105406

I’ve submitted details of my issue to Sony Creative, but don’t expect a return since I’m using trial versions of Vegas. The sad thing is that I’m using the trail versions to see if the Vegas product is something I should move to. I really like the Vegas UI and method of editing, but the 2GB limitation is a total non-starter, especially since I doing HD editing.