The settings aren't supposed to affect rendering at all, which I think (hope) is one of the things they fixed.

This is an update I think deserves its own thread to raise awareness...

. . . .

Hopefully this brings and end to all the issues that dynamic RAM preview previously caused.

👏👏👏👏

@fr0sty - Stunning performance. I can easily monitor the usage under TM and my GPU. So fast and so reliable. Shift+B is going back onto my Contour Shuttle Pro2.

The settings aren't supposed to affect rendering at all, which I think (hope) is one of the things they fixed.

Hoping for the same. Ive had to toy with dynamic ram quite a few times to get my renders to finish in Vegas 18. Purchased my upgrade 👍. Time will tell

Previously always set to 0... and now I kept it 5% by default and no trouble on editing and direct rendering. no surprise glitches so far.

I see no difference in performance... Have 64GB quality RAM here and fast one 3600MHz, still nothing to brag about it at all, or be excited for. i am not impressed, actually i am very disappointed.

Throwing more RAM at something doesn't by default make it faster, if you have bottlenecks elsewhere. This update doesn't mean better performance unless what you were trying to do was RAM-bound and not held back by something else, but it does mean that the many bugs that plagued dynamic RAM preview for decades should be dealt with now, and the interface is less confusing.

I haven't had to disable it for renders so am satisfied. Finally!

Having a greater amount by default is helpful for actually using it with 4K and greater than few seconds' length.

I see no difference in performance... Have 64GB quality RAM here and fast one 3600MHz, still nothing to brag about it at all, or be excited for. i am not impressed, actually i am very disappointed.

@eikira - And yet my experience is diametrically opposite to yours. Mind you, my MONSTA! (PC) has the latest s/w and h/w Build; optimised for Video and Audio Editing; setup by an Internationally renowned company that prides itself on doing just that. I’m stoked! And KUDOS to Team-Vegas for putting so much work into SHIFT+B.

I’m going to carry on testing combinations of RAM and Renders. Oh yeah, just got myself a higher-end, DELL 27”. This is a good period for me 😀.

I find the Shift+B method to use the RAM preview isn't needed anymore in VP19 because the Shift+M prerendering is noticeably improved. But I still have around 15 % of my RAM allocated to the RAM preview for a nice playback buffering.

Is this at last recognition of a problem that has existed since VP17?
If so then VP18 and VP17 users deserve a patch as way of saying "thank you for sticking with us in spite of the frustrations".
So far 19 looks good - time will tell.

I don’t know about “needed” (?) but I find SHIFT+B faster than PreRender, waiting for a multitude of files being rendered. However, PreRendering is not limited to RAM Building, if that’s what you want 😉. Ultimately I’ll decide to use either SHIFT+B or SHIFT+M depending on where I’m at in my Narrative. So, another tool in box.

For the stuff I used so far prerendering is as fast as building the RAM preview.

Is this at last recognition of a problem that has existed since VP17?
If so then VP18 and VP17 users deserve a patch as way of saying "thank you for sticking with us in spite of the frustrations".
So far 19 looks good - time will tell.

The issue is far older than that. It would be nice to retroactively patch it, but there might be technical issues that would take the team away from the goal of improving VEGAS' current versions for too long, or prevent patching this into older versions entirely.

Is this at last recognition of a problem that has existed since VP17?
If so then VP18 and VP17 users deserve a patch as way of saying "thank you for sticking with us in spite of the frustrations".
So far 19 looks good - time will tell.

I had this issue going back to 15/16. Are they really going to update Vegas going back that far? I see the annual upgrade as a continuous update and improvement process and under this model you have to keep paying for updates and bug fixes each year or live with workarounds.

I'm looking forward to the day when the prerender will be automatically without using shift + b. Like in the premiere.

Me too! Dynamic should be dynamic : )

I had this issue going back to 15/16. Are they really going to update Vegas going back that far?

No they are not, but they should'nt have too. An issue dragging on for 4 versions is not good. I wasnt aware of it until 17.

I had this issue going back to 15/16. Are they really going to update Vegas going back that far?

 

No they are not, but they should'nt have too. An issue dragging on for 4 versions is not good. I wasnt aware of it until 17.

Agreed, apparently it was a pain in the ass to get fixed. They are a small team that is trying to simultaneously update old code (some of it as old as VEGAS is) while building new features on top of the foundation they are also fortifying to be able to handle the weight of those features. This was probably the oldest major bug still left in VEGAS.

All these long dated issues are gonna gradually be fixed or improved over time. Not what we wanna here of course, but so it goes..... This dedicated development team is making it happen. They are now on the right path!

..... This dedicated development team is making it happen. They are now on the right path!

@Steve_Rhoden - Yes!

The settings aren't supposed to affect rendering at all, which I think (hope) is one of the things they fixed.

Well time did tell..

I just had to adjust dynamic ram "ie set to 0" for my current project to finish rendering. It was stopping at 17% before hand. No difference from vegas 18. The dynamic ram issue is still present in v19. 😡 There is no correlation either; sometimes a render freezes with dynamic ram set to 0 and setting it to a higher # yields a render to completion; however setting to 0 still seems the have the most reliable results. Disappointing...

The settings aren't supposed to affect rendering at all, which I think (hope) is one of the things they fixed.

 

Well time did tell..

I just had to adjust dynamic ram "ie set to 0" for my current project to finish rendering. It was stopping at 17% before hand. No difference from vegas 18. The dynamic ram issue is still present in v19. 😡 There is no correlation either; sometimes a render freezes with dynamic ram set to 0 and setting it to a higher # yields a render to completion; however setting to 0 still seems the have the most reliable results. Disappointing...

 

Sounds to me like it may be something else, if it doesn't fix the issue every time.