Comments

Musicvid wrote on 5/16/2019, 6:25 AM

It would be nice to know your version of Vegas so someone with the same version could check.

If you are making such large RAM prerenders, file prerenders or render to new track may be more useful for you.. I would think that much RAM would be put to better use as swap space, as buffers can grow like crazy over an editing session.

Kinvermark wrote on 5/16/2019, 10:49 AM

+1. Huge RAM previews are not really a good way of working in Vegas. Not completely reliable / accurate and dissappear like bubbles the moment you touch them.

andrew-barbato wrote on 5/16/2019, 3:53 PM

It would be nice to know your version of Vegas so someone with the same version could check.

If you are making such large RAM prerenders, file prerenders or render to new track may be more useful for you.. I would think that much RAM would be put to better use as swap space, as buffers can grow like crazy over an editing session.

Version 16, latest update

fr0sty wrote on 5/20/2019, 2:42 AM

I have 64GB, I can rarely get RAM preview to work at all... then there's the performance issues of setting too much RAM in RAM preview and it slowing things down elsewhere. Then the stability issues...

mintyslippers wrote on 5/20/2019, 3:45 AM

IF your having performance issues then dynamic preview isn't the answer. Your better off using the proxy files and its so easy to use them now.

There is another thread here where we talk about dynamic ram and how the value impacts performance and stability. Some can only get a stable system with it off but for those that can work with it we found that any value over 1GB will actually lead to lower performance, certainly during a render.

For most users 16GB is perfect for Vegas and you wont actually use more than that. For me I have around 3-4 copies of vegas open as I like to move footage from one to another (way quicker workflow than using media bins) so I have 32GB but NEVER has my ram usage gone above 14GB. 128GB is going to be a real waste unless your working on some monster complex projects. and I really mean absolute monsters.

AVsupport wrote on 5/20/2019, 7:15 AM

not worth the $ in my book...

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest drivers

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Kinvermark wrote on 5/20/2019, 10:58 AM

Your your should be you're. :) Just FYI.