You are also several builds behind to for 18. Try updating to 482.

Put dynamic ram preview back to the default, it only limits the ram Vegas can use for renders.

Set back to default, now I'm only getting a max of 1.8gb of RAM being used for renders

@gabem
Amount of RAM used in Vegas Software depends on

- Projectsettings
- Used sourcefiles
- Used Effects
- Vieuwing or Rendering
- and so on
But non of this you tell or show us, so how can we give suggestions what to do?

Understood, so depending on what my project is, Vegas chooses how much RAM to use?

Have you updated to Build 482 as RogerS suggested?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-4-build-482--127859/

Understood, so depending on what my project is, Vegas chooses how much RAM to use?

That's my understanding (and is standard for most software these days). I think Vegas can access up to half system ram. I often see ~2GB used for rendering shorter projects. Ram's fast so information can be streamed in and out of it as needed.

Maybe one of the developers can tell exactly how dynamic RAM and RAM is supposed to work since in this forum there's a lot of different assumptions about this . In the sony versions ( 13 ) with GPU=OFF , when I put dynamic RAM to 5 GB , vegas starts gradually using it till the value set in dynamic RAM whilst previewing and whilst rendering . When I put dynamic RAM to 25 GB , vegas starts gradually using it till the value set in dynamic RAM whilst previewing and whilst rendering . ( I do have 256 GB RAM in the workstations , so 25 GB of RAM is a peanut . After Effects , for example , automatically detects the installed RAM amount upon installation and I do allow it to use 128 GB of RAM and it happily does ) .

Maybe that has all changed in the meanwhile since the focus on graphic cards , no idea with the latest versions of magix and why this works best without dynamic RAM

I don't think the feature has yet been updated to work with the newer decoders and GPU timeline acceleration, so it can cause serious errors and graphical glitches in post-Sony versions of VP. Numbers greater than 0 can result in out of memory errors with NVIDIA encoding and that's regardless of the amount of GPU or system ram available. There also seem to be hardware-specific issues as some people have problems and some don't, based on reviewing many reports of errors on this forum.

I'm hoping fixing or removing this is part of an overhaul to the Vegas graphics engine.

Never heard of a machine with 256 GB! Hello to you in the future.

... the value set in dynamic RAM whilst previewing and whilst rendering . ...

I observed the same behavior. Dynamic RAM is not used only with the Shift-B, it is used while previewing. If the preview is not fluid on the first playback, subsequent playback are perfect.

Illusion is correct as far as what that Dynamic RAM settings are intended for. A side effect is that during rendering the Dynamic RAM stuff is also used since the preview of the frames is part of the rendering process (but the preview during rendering can be turned off). Having the preference setting too high most certainly can lead to problems in the encoding process. We have been investigating better handling of the Dynamic RAM feature, better management during the rendering process, and some automation of the process as well.

@VEGASDerek thanks for confirming

We have been investigating better handling of the Dynamic RAM feature, better management during the rendering process, and some automation of the process as well.

@VEGASDerek
Thank you, for now, for your participation!
For me, as a non-native English speaker, this sentence only says that something has been investigated, but not yet that work is underway to improve it.
Can you please be a bit clearer so that I can understand it too?
As it is one of the most discussed topics here in the forum and is also afflicted with a lot of uncertainties about which value is favourable for which machining process - and above all which value is completely unfavourable (because this can then lead to a crash).
I (and I think many others) would like a much clearer answer.

@walter-i.

+1

Jøran

@RogerS : nothing at all about future , the HP Z840 is already an older model 😂. I do have 2 of those and these can now be bought refurbished at a MUCH lower price I did pay when they were released ( each has 2 x 10 core Xeon's , good for 40 threads ) . Those systems are also certified by Adobe and Avid . ( See also my profile and signature ) .

In this post, by @NormanPCN if I understood it correctly, he believes that DRP also assists in the loop region playback.

”So does dynamic ram offer any benefits other than when doing a Shift+B?

“Vegas caches frames during playback and uses unused preview RAM for this. So it you loop, you get the equivalent of a Shift+B. The size of the loop region where this works is of course dependent on the preview RAM size. Also, scrubbing back and forth Vegas can uses these cached frames.”

Now that I remember it, I think it was Marco that suggested to set DRP to zero in the Benchmarking project when testing the Avg. FPS value for the Region 1 loop section. Thus to help prevent artificially high readings.

@JN-

Thank you for the link to this wonderful thread!
It shows so beautifully how a problem has been dragging on for so long.

But it also shows very clearly that Vegas/Magix has a corps in the cellar, that should finally be dealt with thoroughly.

Above all, there should finally be a clear statement from Vegas about what and how this attitude is causing.
I can't understand why they are so silent about this.

@walter-i. My best guess is what RogerS said ...

“I don't think the feature has yet been updated to work with the newer decoders and GPU timeline acceleration, so it can cause serious errors and graphical glitches in post-Sony versions of VP. Numbers greater than 0 can result in out of memory errors with NVIDIA encoding and that's regardless of the amount of GPU or system ram available. There also seem to be hardware-specific issues as some people have problems and some don't, based on reviewing many reports of errors on this forum.

I'm hoping fixing or removing this is part of an overhaul to the Vegas graphics engine.”

But Derek did clarify intentions, aspirations ... “better handling of the Dynamic RAM feature, better management during the rendering process, and some automation of the process as well.”

This might for example, just guessing, give a user operable slider for setting DRP, with hard limit(s) based on Ram availability, and overall machine system capability. I’m sure internally it would require some extra stuff.

At the end of the day, currently, it’s still a very useful feature. It allows some fine tuning, usually by setting to zero. I think this is to mostly overcome using a lower specced machine on the likes of more demanding projects than (4k media) the PC can comfortably handle.

@JN-, @RogerS
My full agreement and also my experience - but as I said, it would be nice to get an agreement / correction from Vegas - perhaps @VEGASDerek, so we're not always in the dark on this.