I've seen several people state they set the Dynamic RAM Preview to zero (0). However, when did this in Vegas Pro 20, and then tried to use the Dynamic RAM Preview, it popped up a message saying that the DRP was set to 0 and I needed to increase it to use this function.

Going on a similar subject, regarding the RAM Preview, I have heard (mostly on YouTube videos), that if you set the RAM Preview usage to 0%, VEGAS Pro will manage PC RAM for RAM Preview itself (dynamically, I assume).

Shift +B won't work, but the caching that happens when you play over an edit point, it lags so do it again and again, and eventually it's smooth still works with Ram Preview at zero. Not sure it works less well or identically but that aspect of caching is not disabled setting DRP to zero.

The problem with setting DRP to zero is playback is affected, in a test I did where I artificially created a situation where Vegas could only barely hold on to 60fps playback with DRP set to 10%, it played back at 45fps with DRP set to zero. Rendering speed is also affected, but not by too much that it's an issue, if you needed to set DRP 0 for black flashes. Reduction in playback speed by 25% is an issue though (In the limited testing I did)

@Former user +1

I use always default RAM settings and never use Shift+B (but Shift+M instead and only when needed). No problems with preview, render or other issues caused by too high or too low RAM settings.

Dynamic RAM preview behaviour was changed/overhauled from V19 onwards. In this case the best setting as others have said above is the default 5% setting (unless you have a specific and good reason to change it. Changing it because you believe it gives Vegas more RAM to run normally is not a good reason.) for versions V18 and before then setting dynamic RAM to 0 can help with stability especially if you do not need to preview selected regions of the timeline.

Thanks for the clarification. I'm going back to ALL default settings except for the Legacy HVEC (File I/O) which I uncheck. As far as lag goes for using Shift-B, I normally hit Alt-Shift-B first to delete any previous prerender and then it renders much faster. I was freezing both in edit and render (way too often) and after setting the Dynamic RAM lower (10%) those issues have gone away.

Hi, I am using Vegas Pro 19 build 643. My problem is that when Dynamic Ram Preview is set to 0% rendering a 10 minute .veg file (with lots of transitions and around 24 tracks) takes one hour fifteen minutes and runs at about 3.5 frames a second, but the rendering completes every time. CPU usage is around 30% and GPU and 12-15%. If I move the Dynamic Ram to 30% rendering will run at about 10 frames a second, CPU usage is about 70-80% and GPU increases to about 15-18% but rendering will always freeze at some point before half the video is rendered. Increasing the Ram percentage increases the number of frames rendered per second proportionately, but rendering always freezes at some point using any value of RAM above 0% . Is there any settings I need to change, or idea on how to render quicker, because my system should render quicker than this I would have thought.

'Enable Legacy HEVC decoding' has been ticked and unticked but makes no difference to rendering freezing above 0% Ram.

System: Ryzen 3700x, RTX 3060, 32 GB ram 1TB SSD 4TB HD Windows 11 - 21H2

@paul-priestley Hi, which render template are you using, in some templates there's two options, one with (NVENC) at the end & one without, ?

Also can you share the MediaInfo of your files, there's an App called MediaInfo, download it, it's free & a fast download with no added adverts or any of that rubbish. https://mediaarea.net/en/MediaInfo

After downloading, right click on the media file in your Windows folder, open MediaInfo, choose Text from the options at the top, Copy & paste the information in a new comment on here 👍

Like this -

Hi,

Thanks for the response, I'm using Magix AVC/ACC MP4 using Nvidia NVENC. I have attached the info you wanted.

Cheers

@paul-priestley
Can you give us a screenshot of your Help/Check for Driver Updates?

I found the rendering to be most stable at the default 5%. I made this comment in another post, but editing/rendering became more stable after I did a Control-Shift reset at startup.

Hi j-v,

I updated the Graphics driver a couple of days ago.

Hi Mark-Linenbroker,

I'll try the 5% recommendation and also try the Control-Shift reset. Thanks

I'd also suggest doing a restart of your PC to clear your GPU memory... I think a lot of the rendering issues comes down to the GPU running out of memory (I only have 8GB) which makes me wonder is there isn't a GPU memory leak in the software, since a reboot almost guarantees I won't have a rendering freeze. However, it could be some other Windows App I'm using that isn't reallocating.

Hi Everyone,

I have rebooted my machine, set the dynamic ram to 5% and done a control shift reset to clear the cache. It now renders three times quicker than it did with dynamic cache set to 0% but it still freezes or stops working during the render. Tried it twice and crashes at different points.

Hi Everyone,

I have rebooted my machine, set the dynamic ram to 5% and done a control shift reset to clear the cache. It now renders three times quicker than it did with dynamic cache set to 0% but it still freezes or stops working during the render. Tried it twice and crashes at different points.

There must be a problem with your system somewhere as I have just finished a 13min 4K (Sony XAVC ) which due to neat Video noise reduction took 8 hours to render. I used a batch render + Shutdown script to auto close down the PC. The render template was Voukoder VBR 2 pass, bitrate 60/120. The project included a title, a few fade transitions, noise reduction on quite a few clips, a few levels filter to brighten up the mainly inside shots. DRAM was 5%.

I was freezing both in edit and render ...

There is the possibility that one or more of your media events is corrupt or has some sort of issue causing the problem. If there is a particular point on the timeline where the freeze problem occurs, perhaps check the integrity of all the media events at or around that point.

I've experienced this anomaly of corruption in my media that was causing the rendering to freeze.

I'd suggest rendering this edit with only your CPU (don't include the NVENC option). It will render more slowly without the help of the GPU, but it might not freeze.

Next edit, include the GPU and see if you have more success.

You may also try deleting any transition effects and see if you can render with the GPU.

I suspect the developers launched a new NVENC/HVEC(?) encoder after the Vegas 19 v550 update. Because that's when it became less stable, and the freezes started happening. Hopefully, they can get the bugs worked out in future updates.

Interesting, I'll give that a try tomorrow. Cheers

Wow, i just discovered this topic, and my problem is very similar!

Currently i have 2 projects with a problem:

Project #1

New year's concert with two HD cam, two 4k cam. I tried to render with stock template 1080/25 NVENC.
At first, rendering crashed at 95%, i was not happy at all :( After restart and try again, it crashed at 50%,
next time again at totally different part of the timeline. Seems random. This issue only exist when i use dynamic ram preview other than 0%! If i change it to zero, rendering will finish with the same template. Every time!
Set back to 10% and render crash again. With 0% total time needed is around 20-30% more.

What bug is that?? When it's flawless, it's mean that all my source files, effects, transitions, etc are good, right?
So please don't ask for mediainfo :)

Project #2

A short, 5 minute dancing clip with 4k files from ZV-E10 cam.
Some CC, levels change, few transitions, nothing more.
Everytime i start playback timeline it's fine, stable 30fps, but after i made a few edits,
or only jump in the timeline here and there, fps goes down to unusable 3-5 fps and nothing help.
Nothing, except Vegas restart. Then that part which was 5 fps one minute before, plays at 30fps now.
For a few minutes again...
This issue only exist when dynamic ram preview is more than 4% (i have 32GB total)
With 1-2-3 or 4% i can edit hours, without fps dropping.

Again: What bug is that??
I think it's a serious memory handling problem (leak?), which Magix should fix for us.

Of course i use latest nvidia studio drivers and my pc is perfectly fine in every other app.

To me it looks no bug.
My first question to you is: Do you know the reason for using more Dynamic RAM Preview than 0 or the default amount?

To me it looks no bug.
My first question to you is: Do you know the reason for using more Dynamic RAM Preview than 0 or the default amount?

I don't think setting the dynamic RAM to zero is relevant to the latest versions of Vegas Pro.

More Dynamic RAM allows you to render longer portions of the video for better playback when editing. However the higher you set it, the more application memory it takes away from Vegas and other apps. In my experience, I found if I set it too high, the instability issues become more prevalent. I go with the default 5%.

j-v:
yes, i often use SHIFT-B (don't like to use other method!) and this won't work with 0 RAM Preview.
Also, rendering is smoother, faster, so i like to use a few % of my ram.
Why don't you call this a bug? Then what?

Mark: interesting, that by me 5% dont work either, only 4% or below for editing and 0% for rendering.