I've been cutting on V11 over the years -- 3-4 projects a year. Now using V13 and I hope someone can clarify a few things for me.
1 There is a pref choice for up to 9 past projects for the app to remember, but in the file dropdown there is no "Open Previous file" as there was in V11. is that possible that it's just gone or did they remove it?
2. How do i get the file names to appear on the clips?
3. It seems that Vegas is only using 200 mgs for Dynamic Ram Preview. What is that?
4. I have 16 gigs of RAM, how can i use it to make sure Vegas is working at it's best and fastest? it seems as crash prone as V11 at least.
5. Are the color adjustment tools showing split screens now? I tried to use Sony Color Correct and that's what it did on the clip, and then the split just stayed.
Thanks for the help,
Dell Windows 10
Intel6700 quad CPU
16 Gigs RAM
3 Gig GPU
3. Preferences > Video tabIt seems that Vegas is only using 200 mgs for Dynamic Ram Preview. What is that?
4. This is a tougher discussion. It depends on your GPU and your CPU; what you want to make faster: Previewing?; Rendering? BTW 16gbs is pretty standard almost to low on rigs nowadays. Being crash prone is another conversation.
5. Yeah, try the Dropdown again and Select All. It's a bit odd. Maybe open and close Vegas a couple of times and reboot PC to get system and Vegas bedded-in
Hope that helps?
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge
[Rob Lindsay]"3. It seems that Vegas is only using 200 mgs for Dynamic Ram Preview. What is that?"
If you selet a region of time on the timeline, and press shift-B (or in the main menu select Tools / Build Dynamic RAM preview), that portion of the timeline is selectively prerendered into RAM. Say, there are couple of composite tracks with numerous effects, which require huge computational performance for smooth playback. You can prerender such a section or region. Dynamic RAM preview is the amount of memory buffer to store such prerenders. You can increase this value, but if you don't use this feature, there will be no benefit, but the opposite, because you dedicate RAM to a purpose which you don't use, and loose that RAM otherwise available for other useful things.
I noticed that if this value is set to zero, that deeply impacts rendering performance. So this buffer is probably used during normal renders as well.
I would keep it at the default setting, unless there's a clear sign, that you need more buffer (for longer prerenders), increase the value to have more buffer, or decrease if you need more free RAM (but don't go down to zero).
You can experiment how much buffer you need for your renders to work normally.