-
How much memory is enough?
I’m having a really annoying issue with vegas.
Typically when cutting I never switch applications in windows. However, occasionally it’s necessary (like if I edit and embedded veg).
Seems to be half the time when it switches back to the parent project vegas takes a massive dump and crashes.
I’m guessing this is a memory related issue. I only have 4 gigs of ram. And my parent project is 2 hours worth of standard def veggies.
I cannot verify this though cause when I switch to task manager to see my memory usage I believe it’s paging my vegas.
Is there some way to setup the app so it remains in memory? And or how much memory should I have for projects like I’m doing?
I’m learning the ropes of online publishing. Mostly as an excuse to play with more cameras.
Here’s several of my latest ventures,
https://www.keystoaz.com
https://www.fitlish.com
https://www.corvettemedic.com -
3 Replies
-
You probably need to describe your computer, OS, etc. before anyone can comment on the memory question.
One thing does come to mind if you are using many pictures, clips, etc. on the time line. At one time, an older computer of mine would take a long time to recover if I went from Vegas to another application and returned. I learned that it was bogged down reopening all the media in the project. After I told it to keep the files open, the long delays disappeared.
-
There are several schools of thought.
One, of course, is the default: my PC is maxxed out on RAM, so I’ll just live with it until it’s time to upgrade. These days, of course, you can have a slightly different scenario — my OS is maxxed out on RAM… if you have Windows 32-bit and 4GB. Which may actually mean only about 3GB really available to play with — you get a small memory upgrade just going to 64-bit Windows.
There’s the common rule-of-thumb you’ll hear around here, 2GB per processor core. This works fairly well for Vegas, it’s overkill for some apps and insufficient for others. Photo work, for example, can be very, very memory intensive at times, but less processor intensive than video.
For HD in Vegas 9/10/11 on 64-bit Windows and a six core CPU, I have never run into a practical limit with 8GB of RAM. No paging, no other low memory issues. But some of that’s workflow… if I were using a different mix of apps all at once (say, Vegas and After Effects up at the same time), maybe I’d benefit from more RAM. I did upgrade to 16GB last summer, but that was for photo work (merging 25-50 18Mpixel photos to a panorama in RAW or 48-bit color… does eat memory).
For SD work, I was pretty happy with 1GB memory, though of course, that was like Vegas 6 or 7, so that’s less easy to compare to today’s Vegas.
You guys are right on about the Vegas “wake up” effect. When you de-focus Vegas and it’s otherwise not doing something, it releases locks on the assets you’re using. That’s intentional. If it didn’t do that, you wouldn’t be able to, say, jump to Photoshop to adjust a still or Forge to edit audio. When you re-focus Vegas, it’s going to grab those back, checking for changes in the process. In a big project with lots of assets, yeah, that’s going to take time. You’ll speed your project up (in general, but here specifically) moving some of those assets to separate hard drives.
-Dave
-
Do you have a scratch disk?
Monte Krause
Dallas, TX
Reply to this Discussion! Login or Sign Up