Easy, don't do any of these as the default settings are now the optimal ones for most users.

YouTubers are rewarded for views, not being right.

im not doing any of them ;) but i did when i didnt know any better, but im tired of all the false info out there, so i wanna make it right.

I see, that's a good thing you are doing.

Could you share what you're writing about with dynamic ram preview? Maybe we can offer some feedback about its evolution.

Here's my attempt at these.

For OpenCl the only reason to disable it was if there are resource conflicts. I thought VEGAS was moving away from this even doing anything as it's antiquated. So this is advice likely for older versions of VEGAS that aren't really relevant anymore.

For admin it has the downside of not being able to directly import media from Windows Explorer by drag and drop for some reason. In general there aren't any real upsides to it, all VEGAS needs are write permissions for various system folders which a user account should give anyway. If there are permissions issues there are workarounds like creating a temporary user account to get it installed in but admin doesn't help with this or anything else from what I'm aware.

For priority this is something best handled by Windows as you may again lead to resource conflicts or even system instability in the pursuit of speed. If you want VEGAS prioritized, keep it in the foreground and close resource-intensive apps if you have limited computing power or ram.

Not sure about multistream render- what era is this from?
Now for lowering rendering threads, there may be a benefit if there are rendering issues causing a render to stall. If the user just wants faster renders use the modern GPU-enabled templates like NVENC, VCE and QSV through MagixHEVC or MagixAVC. These are much faster than the 10 year old opencl "legacy GPU encoding" one through SonyAVC.

For people with render glitches, on pre-19 versions turning dynamic ram preview off (0MB) may help, as there were bugs where it was conflicting with GPU encodes. Same with turning off GPU preview acceleration in preferences/ video. Both should be obsolete advice at this point. Build 300 seems to have also fixed longstanding render glitches with NVENC where images before or after videos can smear together in a glitched way. QSV still has it to some extent (and doesn't look sharp in my opinion- I'd avoid it and do it through Voukoder if you really want QSV encoding).

To figure out what works and what doesn't it's helpful to do controlled tests. My signature has two test projects, one that works with VP 16+ and one with 20+ that anyone can use to see how their systems compare to similar ones. They can also compare settings themselves by doing one run with dynamic ram preview at 0, one at 5%, etc. or with any other setting combination they choose. Both projects are relatively complex timelines that are GPU intensive in different ways vs the media being difficult to decode, so keep that in mind.

In support of @RogerS 's first comment, I ask why it would be thought that any company like Vegas would release products with sub-optimal settings by default when better default settings were readily and sensibly available. Of course, there may be instances when a default setting is better changed in special circumstances unique to a particular user's situation

When looking at YT videos, seek out YT channels that have a long history with reviewing Vegas Pro (or any other product for that matter )and are not based on "magic" fixes for perceived problems.

I see, that's a good thing you are doing.

Could you share what you're writing about with dynamic ram preview? Maybe we can offer some feedback about its evolution.

Here's my attempt at these.

For OpenCl the only reason to disable it was if there are resource conflicts. I thought VEGAS was moving away from this even doing anything as it's antiquated. So this is advice likely for older versions of VEGAS that aren't really relevant anymore.

For admin it has the downside of not being able to directly import media from Windows Explorer by drag and drop for some reason. In general there aren't any real upsides to it, all VEGAS needs are write permissions for various system folders which a user account should give anyway. If there are permissions issues there are workarounds like creating a temporary user account to get it installed in but admin doesn't help with this or anything else from what I'm aware.

For priority this is something best handled by Windows as you may again lead to resource conflicts or even system instability in the pursuit of speed. If you want VEGAS prioritized, keep it in the foreground and close resource-intensive apps if you have limited computing power or ram.

Not sure about multistream render- what era is this from?
Now for lowering rendering threads, there may be a benefit if there are rendering issues causing a render to stall. If the user just wants faster renders use the modern GPU-enabled templates like NVENC, VCE and QSV through MagixHEVC or MagixAVC. These are much faster than the 10 year old opencl "legacy GPU encoding" one through SonyAVC.

For people with render glitches, on pre-19 versions turning dynamic ram preview off (0MB) may help, as there were bugs where it was conflicting with GPU encodes. Same with turning off GPU preview acceleration in preferences/ video. Both should be obsolete advice at this point. Build 300 seems to have also fixed longstanding render glitches with NVENC where images before or after videos can smear together in a glitched way. QSV still has it to some extent (and doesn't look sharp in my opinion- I'd avoid it and do it through Voukoder if you really want QSV encoding).

To figure out what works and what doesn't it's helpful to do controlled tests. My signature has two test projects, one that works with VP 16+ and one with 20+ that anyone can use to see how their systems compare to similar ones. They can also compare settings themselves by doing one run with dynamic ram preview at 0, one at 5%, etc. or with any other setting combination they choose. Both projects are relatively complex timelines that are GPU intensive in different ways vs the media being difficult to decode, so keep that in mind.

Sure you can see my current "script" i made for my coming video, this is my first ever writinbg down what im gonna say, so any pointers would be appriciated :)

Maybe i should add something like, "i can only say that this is for vp20 and onwards, or something like that?

anyway here is the script :

"""

Hello my friends

So...what is dynamic ram and what does it do, and doesnt do in vegas pro.

i will show you, firstly ill show you were you change it.
You go to options, then pref, video, and here at the top you can change how much you wanna allocate.

so what Dynamic RAM do, is letting you render a part of your timeline to memory, you just highlight a section like this

(show excample in vegas)

you then hit shift+b and you can see how its reading the highlighted section.
How much its gonna read is depended on what amount of ram you have allocated in the video settings.

(show example,turning ram amount up and down)

Lets try and set it low and see what happends, shift + b again and watch the cursor.
Im just gonna highlight the whole project so its easier to see how much it can read to memory.

(show timeline with low settings)

You CAN get it to save more of the timeline for the same amount of ram allocated,
just have to change the preview quality up here

(move cursor to button)

Lets set it at the worst preview quality and see.

(change preview)

Set it to draft and quarter, and the overall review windows will run smoother,
but it wont look very good, and that depends on what type of project you are rendering,
if you dont care about the video quality, just leave it at this setting, most of the time
you wont need to store any memory with it, when its set to the lowest.

If you want to preview the best quality and have a particular section of your timeline that is lagging or very choppy,
you just highlight that section and do the shift + b.
 
This will most of the time, help with the playback being more smooth.

(show example with best/full preview - shift - b)

As you can see, the preview video runs alot smoother, and will most of the time hold the framerate you have set in project properties
But it wont stay that way, if you store another part in memory, the first part you did will be gone from memory.

And thats it, dynamic ram does nothing else.

It dosent allocate more ram for vegas to use, in fact, its just gonna use more of your system ram to be able to store it,
it doesnt help with rendering time

And there you have it folks, thats how dynamic ram works in vegas pro, i hope you find this video helpful.
Please let me know in the comments if it helped you in any way.

I will see you in my next how to video.

byiiii :)"""

Im probably not gonna say this word for word excatly, but you get the idea

I think you have the main function of dynamic ram preview totally right.

I would suggest taking one of the projects in my signature as they are complex with moving graphics and elements. Each one has a section for playback tests- it's labeled in the VP 16 one (in the middle) and also in VP 20 (first to second marker). Try setting dynamic ram preview to the default and playing that section on a loop. Watch the framerate at best/full. Now try the same with it at 0. You should notice a huge drop in performance.

So in addition to being used to make ram previews it is also a preview buffer.

So if 5% is better than 0%, 50% must be better than 5%? You can test that too and you will see it hits a point of diminishing returns (there's a reason the default is 5%). If you're not making many ram previews keep it on that. I do make them so I have it at 10%.

The reason to turn it to 0 was as a workaround for the errors, mainly render errors I described. Losing this preview buffer normally hurts performance and results in longer render times.

For me the best use of ram previews is for transitions that don't play back at full speed.

@Shogun__Gaming try selective prerender preview(shift+m) instead of dynamic RAM preview. Is almost as fast as dyn RAM preview, doesn't need RAM settings, has no length limitation and is not temporary. I never use dyn RAM preview.

@Shogun__Gaming try selective prerender preview(shift+m) instead of dynamic RAM preview. Is almost as fast as dyn RAM preview, doesn't need RAM settings, has no length limitation and is not temporary. I never use dyn RAM preview.

appriciate the tip, but im not asking how to use dynamic ram, im making a video about how it works ;)

It is a decent idea to recommend selective prerender for people who need a preview longer than the memory they have reserved for dynamic ram preview, or who want it to not get overwritten while editing.

It is a decent idea to recommend selective prerender for people who need a preview longer than the memory they have reserved for dynamic ram preview, or who want it to not get overwritten while editing.

im still very much a rookie about many things in VP, so im trying to make these video`s as simple as possible, im thinking about making shorter vid, focusing on just one thing in each video, so lets not get to many things in at once :) but keep the advice coming, i could use it for later vids

Make a series- even YouTube shorts? People seem to watch those.

heh...nah shorts are to...well short :) i hate shorts myself, i only have a few on my channel as a test, i never watch other shorts, im a "long video" kinda viewer :)

Take baby steps, make lots of good mistakes, plan on arriving late, carry a mirror, and know that your observations apply only to you, but still share.

But thanks to @RogerS i didnt know about the difference in setting dynamic to 0 vs 10%, here is a quick render test i did of the first 6 seconds in the fanmade ad...big difference in render time

So thats something i need to add in my script, so technically dynamic ram CAN slowdown or make it faster, depends on the context :) but thats an important piece of info that needs to be in it

Updated script, i added the part down at the botton with the kursiv and lines under it

""Hello my friends

So...what is dynamic ram and what does it do, and doesnt do in vegas pro.

i will show you, firstly ill show you were you change it.
You go to options, then pref, video, and here at the top you can change how much you wanna allocate.

so what Dynamic RAM do, is letting you render a part of your timeline to memory, you just highlight a section like this

(show excample in vegas)

you then hit shift+b and you can see how its reading the highlighted section.
How much its gonna read is depended on what amount of ram you have allocated in the video settings.

(show example,turning ram amount up and down)

Lets try and set it low and see what happends, shift + b again and watch the cursor.
Im just gonna highlight the whole project so its easier to see how much it can read to memory.

(show timeline with low settings)

You CAN get it to save more of the timeline for the same amount of ram allocated,
just have to change the preview quality up here

(move cursor to button)

Lets set it at the worst preview quality and see.

(change preview)

Set it to draft and quarter, and the overall review windows will run smoother,
but it wont look very good, and that depends on what type of project you are rendering,
if you dont care about the video quality, just leave it at this setting, most of the time
you wont need to store any memory with it, when its set to the lowest.

If you want to preview the best quality and have a particular section of your timeline that is lagging or very choppy,
you just highlight that section and do the shift + b.
 
This will most of the time, help with the playback being more smooth.

(show example with best/full preview - shift - b)

As you can see, the preview video runs alot smoother, and will most of the time hold the framerate you have set in project properties
But it wont stay that way, if you store another part in memory, the first part you did will be gone from memory.

But there is one important note about dynamic ram, dont ever set it to 0%, if you do, you will slow down your rendertime alot, so just set to something like 5 or 10%

And thats it, dynamic ram does nothing else.

It dosent allocate more ram for vegas to use, in fact, its just gonna use more of your system ram to be able to store it,
it doesnt help with rendering time

And there you have it folks, thats how dynamic ram works in vegas pro, i hope you find this video helpful.
Please let me know in the comments if it helped you in any way.

I will see you in my next how to video.

byiiii :)""

Another thing i need some input about, the naming of my new playlist.

My current idea are something like "Vegas Pro 21 Explained" or something along those lines, it needs to be short at to the point, my plan is like i said before, i will make it into a type of "season" with episodes about one thing in vegas pro per video

Take baby steps, make lots of good mistakes, plan on arriving late, carry a mirror, and know that your observations apply only to you, but still share.

 

oh i am taking lots of babysteps :) what ived been doing alot this past week, is testing ALOT of different render methods, trying to find that rendertime/size/quality sweet spot for my youtube gaming vids.

If you go to my channel (link in signature) you can see most of the test ived done in my vegas pro playlist :)

@RogerS here is the multi stream thing i saw one youtuber talk about

video is out finally :)