Comments

fldave wrote on 3/4/2006, 6:27 AM
Menu: Options\Preferences\Video. The Max available memory is displayed. Mine says 767MB, I would not go much over 512 to leave some room for the system. That is for editing sessions.

For final render, for V6 I always set it back to 128 or 0 (never in between), I've gotten slightly better performance. Sounds like Sony is telling people to set it to 400 recently, not sure if that is just to resolve nested veg problems or for all situations. I haven't tested different Preview RAM settings with nested vegs.
rs170a wrote on 3/4/2006, 6:31 AM
i generally set mine to the maximum allowed (it should tell you next to the box in Options - Prefs - Video) while I'm editing. I then drop it back to 256 for renders to (supposedly) avoid problems. BTW, this is with 6.0d. With 5, I left it set to the max.

Mike
wolfbass wrote on 3/4/2006, 6:31 AM
fldave:

Thanks, that did the trick.

Must go to bed!

Andy
TomG wrote on 3/4/2006, 7:50 AM
Wolfbass,
What does the "Shift B" do? I tried it and nothing happened.

fldave,
Are there multiple Preview Ram settings (one for editing and one for final render) or do you just change the one setting in Options/Preferences/Video depending on the task you are doing?

Thanks,

TomG
Chienworks wrote on 3/4/2006, 8:04 AM
Tom, Shift B generates a dynamic RAM preview. You must have a selection on the timeline and have set aside at least some RAM for this purpose. Vegas creates an in-memory rendering of that section of the timeline so that it can be played back at full frame rate no matter how complex the section is.

Preview RAM settings (theoretically)* have nothing to do with final renders. There really isn't any point as one has no effect on the other. Rendering does not make any use of RAM prerenders in the slightest.

*Well, except that there are some reports that preview RAM settings between 0 and 128MB cause rendering to be slow, but this is a bug, not a feature.
fldave wrote on 3/4/2006, 8:09 AM
No multiple settings, you have to go in and change the one value manually. It's just a habit after performing these tests:
http://www.visualretreat.com/vegas/2005_V5V6_Compare.htm
TomG wrote on 3/4/2006, 4:37 PM
Thanks guys,

I usually turn off the preview while I'm final rendering (MPEG2). I don't want Vegas to waste time with a preview while I'm rendering. I'm still not sure why a RAM preview setting would have anything to do with a final render....

TomG
Chienworks wrote on 3/4/2006, 5:19 PM
As we mentioned, it's not supposed to have anything to do with final render. It's a bug that it does affect rendering speed. And this has nothing to do with having preview enabled/disabled while rendering. That's a completely separate issue altogether.
johnmeyer wrote on 3/4/2006, 5:33 PM
I haven't kept on top of this issue in the past few weeks. Has anyone confirmed whether it is still a problem in 6.0d?
fldave wrote on 3/4/2006, 5:41 PM
John,
I updated my test page with V6d results.

http://www.visualretreat.com/vegas/2005_V5V6_Compare.htm

Edit: Yes, there are still problems with RAM settings >0 and <128MB. Haven't tested with nested vegs though. Seems like Sony is recommending 400MB setting.