I've upgraded my editing computer from 32 gig of ram to 256 gig. In the Vegas 18 Pro preferences menu it's still only recognizing 32 gig of ram. How can I have Vegas recognize the 256 gig? Thanks in advance for your help.
Marc
Vegas already recognize all your RAM. This setting is the amount that is allocated to dynamic preview. If you find 32G not to be enough for Dynamic RAM preview, you can increase the limit in the internal. There are other problems that appear if you allocate too much here, use with caution.
Holding Shift, click on Options menu. The menu Internal will appear, last row, select it.
For some reason, I am no longer able to use the search box to locate the particular parameter so I hade to scroll manually. The parameter is called RAM Preview Limit (MB), just below the one I selected in blue here, it is about 3/4 of the way down, after a long list of TRUE/FALSE flags.
Change the value to what you want. As an example, I set it to 64G. Restart Vegas.
Now if you go to Video tab in preferences, you can see your updated value (Not quite 64G, the UEFI reserve some part of the total RAM)
Thank you very much for your help. It worked just fine.
Best, Marc
@Marc-Gold
Do you really think you need so much when you use in the program a big region to use with Shift+B to look real time that region and not in preview?
Most of the time such settings gives a lot of problems with rendering if you forgot that setting to undo before rendering.
Thank you for your advice. I'm checking it out right now to see how vegas performs. I'll let you know. Just need to know how to properly optimize both for preview so that I can see my editing in real time, and also for rendering so the render moves as quickly as possible. Any suggestions for those settings? Much appreciation for your help.
Marc
Any suggestions for those settings? Much appreciation for your help.
Like I already said, for realtime previewing do what you want to do, but after that at rendertime set it back to the default 200 or 0 MB.
What j-v said. You can switch amounts without restarting so it's quick to put it to zero before a render.
@Marc-Gold
Do you really think you need so much when you use in the program a big region to use with Shift+B to look real time that region and not in preview?
Most of the time such settings gives a lot of problems with rendering if you forgot that setting to undo before rendering.
Dynamic RAM preview is not only used with Shift-B. See answer from Derek here: https://www.vegascreativesoftware.info/us/forum/vegas-refuses-to-use-more-than-3gb-of-ram--127930/
Any suggestions for those settings? Much appreciation for your help.
Like I already said, for realtime previewing do what you want to do, but after that at rendertime set it back to the default 200 or 0 MB.
I have set my Dynamic RAM preview to 8G and I don't need to change anything for renders.
With NVIDIA there is a chance of out of memory error or glitches when using NVENC encoding and dynamic ram preview greater than 200. I've had it happen and helped numerous other people with the same issue.
With NVIDIA there is a chance of out of memory error or glitches when using NVENC encoding and dynamic ram preview greater than 200. I've had it happen and helped numerous other people with the same issue.
True, I know. But I have tweaked my setup to get it working.
Here is another example that Dynamic RAM is not only used with Shift-B.
I have modified the RAM to 32G
When I playback my timeline, the memory fills-up slowly until it reaches the max set previously. The value used is higher than 32G because Vegas uses ram itself, not only the preview.
This is my cached rendered timeline. It will remain there as long as I don't edit some part of it. Subsequent playback are smooth.
If I resize the preview window, the cache is flushed.
The only way I was able to get my system stable was to follow a suggestion from one of Scrapyard Film tutorials some time ago where he suggested to disable OpenCL interop. This is located in the Internal menu
My system is stable even since I did this change.
Thanks very much for your advice. I searched the internal menu and didn't see Open CL interop listed. I was going to disable it as you suggested. Any idea where it might be found?
Search for "opencl/", you should find it. It works on my side.
Thanks for the clarification. I did find it and changed it to 'FALSE'