Do you need dynamic ram preview? why? does it depend?

SimonGhoul wrote on 11/17/2017, 6:05 PM

I guess dynamic ram is how much ram would be used on the preview
Do I really need that? it doesn't look blurry at 0 nor anything, I can still see what I am doing and well, why turning it up? does this has something to do with having the most quality? (on preview, not the finished product)

I just find it unnecessary specially as someone who is not pretty good at noticing differences between quality and frame rate
Note:I want to remind that dynamic ram preview does not affect the finished product nor increases quality from rendering, from what I know of, it does improve preview but it makes rendering way longer (for some reason, my guess? the video plays as it renders, that counts as a preview)

Any reason for me or anyone to use dynamic ram preview?

 

 

 

 

Extra [Irrelevant, not a quote]
Some people say you shouldn't have anything open, I kind of agree, you just can't have 2 youtube videos at the same time or I dunno, just fill the RAM, and you should be careful about not going over the line and leaving 10 tabs open, I only have.... 2? this one counts! I am rendering right now, and I also have netflix open which is paused (and I bet yah it doesn't lag, youtube I guess just loses resolution or I dunno, I don't think it lags in my case). maybe it increases rendering time? or maybe it just does when you pressure your cpu? I think you just got to know your computer if you are going to use it while rendering, don't think about recording or playing games while rendering or do if your computer is that powerful (I dunno the requirements, you do, if you don't you test). My computer is not a gamer computer too, it's a laptop that runs everything without a problem, 8GB Ram, it's not too powerful, my hardware encoder and quicksync are trash that works even slower than x264 or the default vegas rendering, and I can still do that, so well, that's just my tip, you don't need the best computer you only need a fairly good computer to do stuff while rendering (just a guess though, I am not an expert)

Comments

astar wrote on 11/17/2017, 8:21 PM

Dynamic RAM preview is just that, it helps to preview complex composites, keying, or animations. You set it depending on how much ram you can dedicate to the feature. The more you dedicate the most you take away from the system disk cache and other programs. The more you dedicate the longer your preview will last after hitting shift+B, or whatever the ram preview shortcut is.

The default setting should be left alone for general use, as setting it to zero is slows renders. Some claim it helps stabilize Vegas, but I feel those people have other hardware issues that the zero setting is compensating for.

SimonGhoul wrote on 11/17/2017, 9:38 PM

Dynamic RAM preview is just that, it helps to preview complex composites, keying, or animations. You set it depending on how much ram you can dedicate to the feature. The more you dedicate the most you take away from the system disk cache and other programs. The more you dedicate the longer your preview will last after hitting shift+B, or whatever the ram preview shortcut is.

The default setting should be left alone for general use, as setting it to zero is slows renders. Some claim it helps stabilize Vegas, but I feel those people have other hardware issues that the zero setting is compensating for.

nice knowing this is more complicated than I thought :T I wish there was an expert who told people how it exactly works

Kinvermark wrote on 11/17/2017, 9:52 PM

I use it all the time to preview 4k projects with motion graphics (titles etc) and complex transitions (think Kolder style zoom-blur transition) in real time. Otherwise the footage plays back too slowly to get a sense of the pacing of the edit.

If dynamic ram preview doesn't work well for you, you can always do a "selective pre-render" which is similar, but to disk - thus slower to render but slightly more permanent.

NickHope wrote on 11/17/2017, 11:27 PM

I always used to think that the "Dynamic RAM Preview max (MB)" setting in the video preferences is the amount of RAM reserved specifically for the "Build Dynamic RAM Preview" feature:

However the Help for it is more vague, stating just "video previews" and not specifically "dynamic RAM previews":

I still believe that the main intention of this preference was/is to reserve a chunk of RAM just for the "Build Dynamic RAM Preview" feature. The problem is that it appears to do much more than that, but nobody seems to understand exactly what.

3POINT wrote on 11/18/2017, 1:16 AM

I also use it frequently, like Kinvermark, for smooth previewing complex parts of the timeline. I dedicated about 30% of available RAM (16GB) for dynamic RAM preview.

I would like to use the selective prerender option more often, but that option is completely useless like it works now. A small change in the timeline makes all already made prerenders unavailable.

Kinvermark wrote on 11/18/2017, 9:28 AM

I would like to use the selective prerender option more often, but that option is completely useless like it works now. A small change in the timeline makes all already made prerenders unavailable.

Yes it is very very twitchy. It COULD be a wonderful feature if it was smarter about not completely resetting large areas. Plus, if set up right, the pre-rendered areas can be used for super fast "smart render" on final.

SimonGhoul wrote on 11/18/2017, 12:50 PM

dynamic ram is only useful for certain effects you want to pay perfect attention to, specially to complicated ones, it's worthless when rendering.

Got it, I'll enable it when I want to fade or something.

monoparadox wrote on 11/20/2017, 7:59 AM

I use it all the time often on something as simple as a transition to make sure things look right in real time. Often, to make sure music/voice is working and syncing correctly. I usually set aside 8 -10 gigs of 24 total. I select an amount that is a multiple of 1024 (old habit), but I have never had issues with it.

-- tom

SimonGhoul wrote on 11/20/2017, 6:24 PM

I use it all the time often on something as simple as a transition to make sure things look right in real time. Often, to make sure music/voice is working and syncing correctly. I usually set aside 8 -10 gigs of 24 total. I select an amount that is a multiple of 1024 (old habit), but I have never had issues with it.

-- tom

Agree, you know animated text looks horrible if it's too fast, and transitions lags to a unbearable way also even lagging the software itself if dynamic ram is set to 0 (the lagging might be because of something else too, I dunno, I don't think so)

SimonGhoul wrote on 11/20/2017, 6:35 PM

I feel like someone should do more research on the future and make a bunch of tests in it, more information on that

And if someone knows something about coding, check the code and the logs

 

I could but I am known for having bad memory and being too lazy