Comments

Simon Page wrote on 5/26/2005, 2:31 PM
I run with 2Gb and found V5 worked well with 500Mb but I've had to bring V6 down to 400Mb to get it going.
rextilleon wrote on 5/26/2005, 2:48 PM
Definately an issue---I dont know if they will fix it on the next release.
JJKizak wrote on 5/26/2005, 3:34 PM
So far with the setting at 16 it's been fat city. No problems, no crashes.

JJK
MyST wrote on 5/26/2005, 3:57 PM
Can you explain how complicated the project is when you're previewing it?
I ask because I have 1gig of RAM, and V6 allows me to alow up to 895megs. So, that's what I set it to.
Granted, I was only previewing back a newly captured clip with nothing added to it, but it went on for awhile without Vegas crashing.
So my question is, do you have alot of FXs, transitions, etc. in your project?
What should I add to my clip to see if I can repro your problem?

Mario
JJKizak wrote on 5/27/2005, 5:49 AM
Some 3000 x 3000 pixel stills jpg, text, cookie cutters, color correctors, color curves, brightness & contrast, light rays, transitions with the stills,
60 minute length, best sound, best render NTSC DV 720 x 480, lots of velocity changes, ripple edit on and off, quantize on and off, several sound takes Forge 8, not using media thingy, dual monitor, SP1 with all updates, no anti virus or Norton, 2 gig ram, Intel board. Captured thru ADVC 300-default settings, V6.0b. Lots of pans and zooms with the jpg's set to 1980 pixels in pan/crop.

JJK
PeterWright wrote on 5/28/2005, 7:13 PM
Glad I found this thread. Returned from holiday, installed 6.0b, had second Gig of Ram added, set render RAM to 1.6Gb, tried to render something and Vegas closed. Happened half a dozen times, just doing a Gearshift proxy render.
Changed render RAM to 400Mb and it hasn't crashed since.

RBartlett wrote on 5/29/2005, 12:26 AM
Can't say for sure, but this maybe another Gates memory managment issue. Rather, an issue caused by the way the operating system manages memory. Sony would need to work around this and we would want them to, but the origins may well be occuring outside the Sony programmers' language-compiler.

1GB, 2GB, 3GB and 4GB are painful "walls" to get through in the x86 computer world.
XP64bit might help when Vegas sits in whatever mode Sony chooses in that environment. Take a spy at the M$ WinHEC 2005 conference for some of that video workstation vision.

All this talk about dual core and PCI-express become a bit duff for me when these Giga Byte limits need overcoming on a reliable OS platform (longhorn reliable?). Then again, I'm not easily swayed by marketing specs aimed at convincing IT professionals and parents.