I wanted to share my own experience for those who are having the "out of memory" error.
I have about 35 minutes of HDV footage from my Sony HVR-Z1U camera that I'm wanting to render into WMV9HD @ 1080i (6MBS, CBR, 1440x1080). I'm using the Cineform codec (full retail, latest version); I never even tried using the .m2t files in Vegas.
Using Vegas 5.0d I got "out of memory" errors every single time. Farthest it ever got was 15 minutes of video rendered.
I downloaded a trial of Vegas 6 and was able to successfully do the render (all 35 minutes of it). That's when I decided it was necessary to spring for the $250 upgrade (Vegas 6 +DVDA3).
Now I've installed the new software and find that I was getting the "out of memory" error again. What did I do differently from the successful run with the trial version? I divided the footage into two regions and did a batch render from the scripts menu. Using this method, it fails after rendering no more than 3-4 minutes of video.
So I went back to doing "Render As" on the whole project. (Also created a veg file from what I wanted to be region 1). Now it does the render all the way through.
Needless to say, I am quite surprised that doing a render from the scripts/batch render would send it over the edge. Maybe some sort of scripting engine gets called and soaks up too much memory space.
Also, I have 2GB of RAM and Vegas 6 was never using more than about 950 MB of it. And the virtual memory was peaking at about 1.2 GB, so apparently it was the 2GB wall that was breaking the renders.
I would think that if there is a 2GB limit, wouldn't it make renders faster if more of this 2GB is in RAM instead of the slower hard disk?
I hope if there is an upcoming Vegas 7 that it will run on 64-bit machines and overcome the 2GB limitation. I don't have 64-bit hardware, but eventually I will.
I have about 35 minutes of HDV footage from my Sony HVR-Z1U camera that I'm wanting to render into WMV9HD @ 1080i (6MBS, CBR, 1440x1080). I'm using the Cineform codec (full retail, latest version); I never even tried using the .m2t files in Vegas.
Using Vegas 5.0d I got "out of memory" errors every single time. Farthest it ever got was 15 minutes of video rendered.
I downloaded a trial of Vegas 6 and was able to successfully do the render (all 35 minutes of it). That's when I decided it was necessary to spring for the $250 upgrade (Vegas 6 +DVDA3).
Now I've installed the new software and find that I was getting the "out of memory" error again. What did I do differently from the successful run with the trial version? I divided the footage into two regions and did a batch render from the scripts menu. Using this method, it fails after rendering no more than 3-4 minutes of video.
So I went back to doing "Render As" on the whole project. (Also created a veg file from what I wanted to be region 1). Now it does the render all the way through.
Needless to say, I am quite surprised that doing a render from the scripts/batch render would send it over the edge. Maybe some sort of scripting engine gets called and soaks up too much memory space.
Also, I have 2GB of RAM and Vegas 6 was never using more than about 950 MB of it. And the virtual memory was peaking at about 1.2 GB, so apparently it was the 2GB wall that was breaking the renders.
I would think that if there is a 2GB limit, wouldn't it make renders faster if more of this 2GB is in RAM instead of the slower hard disk?
I hope if there is an upcoming Vegas 7 that it will run on 64-bit machines and overcome the 2GB limitation. I don't have 64-bit hardware, but eventually I will.