Dynamic Ram 200 vs Zero

BruceUSA schrieb am 27.12.2018 um 17:31 Uhr

I was ask to run the test and play back MP4 file. I know there are people having Vegas crash problems and forced them to set the video preview dynamic ram to zero in order to finish rendering their project without crash. I can not say why that is the case for some people. But I have been using vegas since VP pro 8 back in 2009. I never have to change dynamic ram to anything. I always keep mine at default. Changing dynamic ram to zero is actually slow down the rendering. I rendering out this 4K test footage with dynamic ram at default. I am getting 40+ frames vs 31 frames with dynamic ram set to zero

https://vimeo.com/308430304

Intel i9 Core Ultra 285K Overclocked all P Cores @5.6, all E-Cores @5ghz               

MSI MEG Z890 ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4                                

48GB DDR5 -8200mhz Overclocked @8800mhz                  

Crucial T705 nvme .M2 2TB Gen 5  OS. 4TB  gen 4 storage                    

RTX 5080 16GB  Overclocked 3.1ghz, Memory Bandwidth increased from 960 GB/s to 1152 GB/s                                                            

Custom built hard tube watercooling.                            

MSI PSU 1250W, Windows 11 Pro

 

Kommentare

bitman schrieb am 28.12.2018 um 10:07 Uhr

@BruceUSA

The reason that you do not have issues with dynamic RAM 200 at rendering is probably because:

  1. you do not have an NVIDEA videocard
  2. are using a clean clip without FX and temporal edits.

Of my experience over the years on different PC hardware and different Vegas builds (old and new) I would have either crashes (seems to occur less with more mature SW/drivers and/or hardware), or artefacts like flickering, black frames etc.. in the rendered output with dynamic RAM set to 200. This can be easily simulated (or provoked if you like), by adding a few special effects plugins (e.g. NewblueFX) and (this is important) together with a temporal effect (like using the Vegas speeding up of the clip). I have a tread in this forum about this: https://www.vegascreativesoftware.info/us/forum/dynamic-ram-preview-max-not-zero-render-issue-vp16-and-vp15-etc--113652/#ca702427

This is not solved yet, it is still an issue in the latest build 352.

I have ticket open [Ticket#2018120517007791], no respond yet.

As a final note, I do not recall having such issues on a clean (with no effects) render with dynamic RAM set.

Zuletzt geändert von bitman am 28.12.2018, 10:21, insgesamt 3-mal geändert.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

OldSmoke schrieb am 28.12.2018 um 10:36 Uhr

The reason that you do not have issues with dynamic RAM 200 at rendering is probably because:

you do not have an NVIDEA videocard

are using a clean clip without FX and temporal edits.

Maybe that is true for Nvidia cards after Fermi. I used to have Nvidia cards, GTX560, 570 and 2x GTX580 and never had a crash with the 200 default value. And yes, these projects contained a lot of FX, Pan/Crop, Track Motion and even a bit of compositing. In fact, I came across a bug with AMD cards during SVP12 & 13 whereby a combination of Pan/Crop and Track Motion on the top track would result in flickering of the underlying track. That was resolved with later GPU drivers.

There may also be a similar bug in VP16 but unconfirmed. The current bug however does go away with a Preview Ram of 0 or CPU only rendering or setting project properties to 32bit video levels or higher.

In any case, I never had a crash with the default 200.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)