RAM setting still messing up composite renders.

Mindmatter wrote on 3/24/2019, 10:01 AM

Hi all,

as per suggestion on this forum I tried not setting RAM to zero while rendering. It definitely resulted in a mess, and the higher the setting, the bigger the mess.

Clip 1 - RAM at zero - no issues.

Clip 2 - RAM at 200 - wrong clip start ( mixes end of previous clip with new clip) and erratic composite behavior.

Clip 3 - RAM at 3000 - "very" erratic composite behaviour.

This has, to my knowledge, been a bug for quite some time. With V15, I even had to disable GPU in order to get fault free renders. This is not the case anymore with V16, which btw is really very stable here. But I'd really like to understand what's going on with tha RAM thing and why it's been such a consistent issue.

Comments

eikira wrote on 3/24/2019, 11:12 AM

Hard to say whats exactly is the problem. And its not like you are the only one facing that. (Beside you just ignored Switzerland, i am super offended!). Often i could fix that by setting GPU to OFF, closing Vegas, reopening Vegas, enable the GPU again, closing Vegas again and reopening again and often i then did not encountered stupid flickering and layer mixup and picture mixups. And now i have 16GB setted up in Vegas and so far not encountered this in VP16.

Kinvermark wrote on 3/24/2019, 11:18 AM

@Mindmatter

This is good material to help the dev's debug. Would be good to file a support ticket with this info.

Mindmatter wrote on 3/24/2019, 11:19 AM

(Beside you just ignored Switzerland, i am super offended!).

hehe...it's about the EU, in case you haven't come to that conclusion yet :)

bitman wrote on 3/25/2019, 1:45 AM

My heart bleeds that this is not solved yet after so many years. I have written countless comments and even new posts on this subject trying to push Magix to solve this once and forever. One way I know off to simulate is to use temporal edits and a few new blue plugins to the mix. I have written a post on at least one way to simulate this some while back:

https://www.vegascreativesoftware.info/us/forum/dynamic-ram-preview-max-not-zero-render-issue-vp16-and-vp15-etc--113652/

I am sure there are many other ways to simulate as there must be something fundamentally wrong with Dynamic RAM and rendering in certain circumstances. Think Magix. Think again, and debug it. If you can simulate it, it is solvable, that is my motto.

wilvan wrote on 3/26/2019, 1:32 AM

Still working once and a while with the SONY vegas pro 13 here . GPU OFF and about 32 GB dynamic RAM dedicated ( out of 128 GB ) . Previewing is fluent as well is rendering ( no FX , certainly no newblues since they have Always been troubles in vegas ). Doing same in trial vegas pro 16 ( 361 ) makes preview stuttering like .... and can only make preview fluent when turning ON GPU and put dynamic RAM to incredible 200 MB . Increasing dynamic RAM and crashing like .... Test with simple m2t ( 1440x1080 pal ) files .See my profile for workstation(s) specifications.

klt wrote on 3/26/2019, 2:35 AM

@Mindmatter

I remember I advised you to set it to non-zero because of performance problems. Did you also try to set the number of rendering threads to 1?

Still have the "mess" - which I called "glitch" here?

https://www.vegascreativesoftware.info/us/forum/ongoing-dynamic-ram-preview-issue--114770/#ca710271

To me it seems there's a problem about multithreaded rendering. I had glitches even with DRP=0, and those are gone if I set rendering threads to 1.

So I got the best performance with all defaults, but also glitches. Set DRP to 0 reduces glitches, but still there are, performance hit is huge. Set GPU to OFF: glitches disappear, performance hit even worse... ;)

Having GPU=ON, DRP on default 200, but rendering threads=1 gives me the best performance without glitches. If you set rendering threads to 1, have GPU=ON, DRP > 0, and still have glitches (or this mess), then my theory about the problem being in the multi-thread rendering is obviously wrong. So can you please try?

Thanks in advance.

3POINT wrote on 3/26/2019, 12:30 PM

On my system, the only way to avoid glitches and complete crashes during rendering of composite tracks is to disable GPU, despite DRP to 0 and rendering threads to 1.

This issue is the only thing I hate about Vegas. I always thought that is due my to relative old editing PC and my Nvidea GTX 650ti graphics card. But when I read here that even newer systems with newer graphics cards suffer from this issue, I'm afraid that a planned upgrade will become a big disappointment.

eikira wrote on 3/26/2019, 2:54 PM

But when I read here that even newer systems with newer graphics cards suffer from this issue, I'm afraid that a planned upgrade will become a big disappointment.

If you mean planned upgrade in terms of new hardware, yes that will probably change nothing. But i too had not encountered that glitch in VP16 so far but was very well known from 11-14 to me. Cant remember if VP15 also produced it on my machine. But with VP16 really had nothing of this and i did more stuff with VP16 now than with the other versions before.

3POINT wrote on 3/26/2019, 3:46 PM

I encounter those glitches in my last versions of VPro 16 and VMS16. Rendering of just simple projects, it's no problem, but as soon as several compositing tracks are involved, with use of trackmotion, pancrop, pipfx, cropfx. I have to disable GPU to get a trouble free rendering.

klt wrote on 3/26/2019, 3:48 PM

I got those glitches with V16 too. To me it seems at least 2 parent tracks, each of them having at least 3 children composite can trigger the bug with a high probability.

klt wrote on 3/26/2019, 3:54 PM

DRP to 0 and rendering threads to 1.

@3POINT

You got similar glitches with rendering threads limited to 1 too?

I did not, and I was quite sure it is something with multithread AND GPU. Ooops... 🙁

3POINT wrote on 3/26/2019, 4:07 PM

DRP to 0 and rendering threads to 1.

@3POINT

You got similar glitches with rendering threads limited to 1 too?

I did not, and I was quite sure it is something with multithread AND GPU. Ooops... 🙁

Yes, today tested (with VMS16) with a few composite tracks (with stills), crashes completely after a few seconds of rendering.