Jim Ho
Forum Replies Created
-
Problem disappeared.
Didn’t use it for a while for larger projects. Now, 1Gb projects are okay again. Memory usage is rock stable.
Don’t know what happened.
As I said, it’s a not a hardware problem.
-
No Nigel,
I have Studio 10 32b-bit.
-
NIgel,
I do minimal PP. Just trim, sharpen, brighten and color correct (Studio Colorspace to Computer colorspace).
My system spec – i7 2600 8 GB. Windows 7 64-bit, GEForce GT40 dedicated 1gb total 4GB shared 3GB.
-
Did it again!
Got a small project (500 MB media files) to render. Tinkered with it. Error message (not Low Memory warning).
Tried again and again after waking the machine from sleep. Finally, success. It rendered the full project!
Monitored Task Manager for the computer statistics. Can’t see any hint of a system issue. CPU usage about 80%. System memory usage BELOW normal.
-
Hi Jack,
I started off using AVCHD from Pany GH1. The size was very efficient, but it took much longer to extract 30p from its 60i container.
Yes, there was a limit to the size of the project, but rendering was not buggy. Funny thing was that I was using a 4GB machine.
With the new 8GB machine, Vegas worked ok with Nikon D5100 MJPG files. Then, a few weeks ago, the problems started. Can’t figure out why a multimedia 200MB project can run out of memory?
-
Interesting.
My projects at this time are small. My media files are @1GB and my output wmv is 500MB (<4 minutes). Makes no sense to upgrade to $500 Vegas Pro.
I don’t mind breaking the project into two. But, why does rendering abort when I use media files of only 500MB or less.
Last nite, I ran one of the old projects from a time when Vegas wasn’t acting up. 956 MB media files to produce 459MB. Runs fine. Task manager shows 600MB usage that peaks at +700MB.
Then, I render a recent project. 976MB to produce 500MB. No major differences from the first project.
Crashes immediately. Task Manager shows memory usage started at +700MB.
Of course, I checked to make sure that the computer was idle before I began rendering (Processes 57, CPU 0%, Memory 14%).
-
Dear Stephen,
Windows is only the messenger. The issue is how Vegas uses memory. Why is memory use not linear and consistent?
Windows closes down Vegas when the program exceeds its allotted memory. Why does the program use so much memory?
The standard line is to upgrade your OS. software and RAM. But, this is the brute force approach. You don’t know what is going on. You just hope that more of everything fixes the problem.
Apparently, it doesn’t fix the problem for everyone.
-
Yes!
None of which deals with stability. I have had aborted renderings from as low as 250MB project.
-
Dear Stephen,
I specifically said that it should be possible to work around a low memory ceiling. The real problem is that the amount of memory specifically used by Vegas 10 can surge suddenly (and without apparent cause).
My prelimary conclusion is based on hours of tesing and observation. Nigel doesn’t use Vegas 10. I presume you don’t either. So, thanks for your contribution.
-
Definitely a Vegas bug.
Spent many hours testing and observing. Not a hardware issue. I7-2600 and 8GB should be enough for my modest needs. Not the OS – Windows 7 64-bit.
Vegas 10 (32-bit)crashes when it exceeds +800MB. It should be possible to plan your rendering around this limit.
The real problem is that Vegas uses memory erratically. Sometimes, memory use by Vegas surges. Even small projects abort when this happens. For example, a project may be churning along at 600MB when usage suddenly spikes to +800MB.
Cannot recommend this software until Sony has stabilized Vegas. Cannot be trusted for critical use (for money or for grades).
Has anyone else had this problem? Does the pro or Version 11 have this problem?