Dynamic RAM preview MAX not zero = render issue VP16 (and VP15 etc..)

bitman wrote on 11/9/2018, 2:03 PM

I am having issues with rendering if dynamic RAM preview max is set to anything other than 0. This is not new, I am plagued with it on all my hardware builds, different motherboards with different chipset, different CPU, memory and videocards from titan x to 1080ti and now also 2080ti. The source material ranges from HD to 4K on RX10iii and other HD cameras. These issues can be graphical glitches, flickering or even crashes at times. It all goes away like magic if I put it to zero. Editing on the timeline does not seem give me to much issues with it being set at 200. I know, you loose a bit of render speed if putting it to 0 (but not much). Just recently I found out what can trigger this and almost is guaranteed to reproduce it.

So here is the recipe for glitches, flickering:

Put dynamic RAM to 200 (default)
Take a clip and put in on the time line (e.g. 4k 25P from RX10iii , or HD 50P Leica DLUX-6)
increase the speed (ctrl + grab the end edge of the clip and move to the left)
(optionally: disable resampling on the event), you do not want ghosting after new speed
add newblue plugin "auto contrast"
add newblue plugin "tilt shift"
Render using NVENC (e.g. HEVC internet HD 25P NVENC, default template), or 50P etc..

NOTE it does not have to be those 2 plugins, I had it with others as well, probably any newblue plugin will do as long as there are at least 2 (more chance to cause the glitches)

Result: flickering, glitches, I recall from the past it could crash as well

Same recipe but now with Dynamic RAM to 0, render result is fine now.

So who is to blame?

Vegas which cannot handle rendering temporal (speeded up ) edits with dynamic ram active and some plugins?

Newblue who does not respect the memory (Dynamic RAM) reserved by Vegas?

Vegas that does not succeed in really blocking memory from other applications?

Or Nvidea that cannot handle VEGAS dynamic RAM active when rendering. The video cards I had were all rather large memory cards (Titan, Titan X with 12 GB, 1080ti and 2080ti with 11 GB) ...

Magix please look into dynamic RAM, it still stinks after all these years for rendering with nvidea GPU (I suppose under certain conditions and/or plugins - see recipe).

Comments

Former user wrote on 11/9/2018, 8:55 PM

So here is the recipe for glitches, flickering:

Put dynamic RAM to 200 (default)

Take a clip and put in on the time line (e.g. 4k 25P from RX10iii , or HD 50P Leica DLUX-6)

increase the speed (ctrl + grab the end edge of the clip and move to the left)

(optionally: disable resampling on the event), you do not want ghosting after new speed

add newblue plugin "auto contrast"

add newblue plugin "tilt shift"

Render using NVENC (e.g. HEVC internet HD 25P NVENC, default template), or 50P etc..

NOTE it does not have to be those 2 plugins, I had it with others as well, probably any newblue plugin will do as long as there are at least 2 (more chance to cause the glitches)

Result: flickering, glitches, I recall from the past it could crash as well

Excellent! Fully reproducible artefacts with VP15 & GTX1070

NickHope wrote on 11/9/2018, 9:36 PM

To both of you: But only with NewBlue effects, right?

Former user wrote on 11/9/2018, 10:58 PM

I've seen it with mocha pro 5.6 in combination with speed ramping. There were other filters in use, but disabling mocha pro stopped the type of glitching seen above. I did not know about the dynamic ram 0 fix

bitman wrote on 11/10/2018, 3:19 AM

@Former user exactly the type of glitches!

@NickHope I mostly use NewBlue, have not used others on top of speed ramps yet I think.

matthias-krutz wrote on 11/11/2018, 11:25 AM

Right now it happened to me again. I use AMD graphic, no FX, and the whole project is only 2 minutes long. 2 attempts to render fail, then RAM -> 0 and it rendered successfully. I suspect that it would have been enough to just clear the RAM and restore it to its original value.

Robert Johnston wrote on 11/11/2018, 2:38 PM

It took 3 NewBlueFX to cause glitches on my system. You've probably seen the option to disable GPU processing for the NewBlueFX (when you click on the Info button on the control itself). When I disable GPU processing, there are no glitches, even with 7 NB effects on the event. When I enable GPU processing, I see the glitches when RAM > 0. As I have the trial version of the GPU-enabled NB effects, there is a watermark when GPU is enabled. While watching the rendering in the preview, I could see during the glitches the watermark disappear. I figured the effect couldn't use GPU at the moment so it switched to disabled GPU (no watermark). There are odd results when there is a switch, including images being upside down.

I had to triple check that all NB effects had GPU enabled or disabled. Sometimes I would add a NB effect, and that would change the status of the other NB effects already on the event.

Andrew-Lenczycki wrote on 9/8/2019, 12:15 PM

I've been a user of Vegas since Version 6. Recently upgraded from 16 to 17 (but haven't done any real editing in over a year). Forgot about the 200MB Ram deal (I know I've seen this before when I previously had rending issues). Set the Ram to 0 and the file rendered fine. Thanks for the reminder!

james-ollick wrote on 9/8/2019, 12:57 PM

You've probably seen the option to disable GPU processing for the NewBlueFX (when you click on the Info button on the control itself).

Where is the info button? I cannot seen to find it. Is it in TP7 ot VP17? Can you post a screenshot?

Thanks.

AVsupport wrote on 9/9/2019, 5:20 PM

I've seen this also on VP17/ GPU renders where there's ColorFast2 and Filmconvert being used. Dynamic RAM=0 fixed my issues (ram leak during render, overrun)