What problem are you trying to solve? In general I would keep it on default settings.
For more specific advice please share a screenshot of your file io as well as your CPU and GPU model and MediaInfo for any media you are having trouble with.
You didn't share your CPU, GPU or Mediainfo- advice in VEGAS is much more valuable if it's specific to the situation. There is no one best for all.
I'd suggest keeping everything on defaults. Try the benchmarks in my signature and see how it compares against simliar hardware. If worse, change one setting at a time and see if it makes a difference.
For dynamic ram preview 5% is what I'd recommend. I actually use ram previews (shift b) so set it to 10%. The only reason to reduce it to 0 is if you have render glitches as it kills performance.
Times went down 2 minutes with render threads at 16
And I had a setting an associate put in my nvidia Control panel I had to wipe my laptop and reinstall everything when I installed a 32gb ram in the laptop
That with testing was able to render a old edit in Vegas 19 same settings in program..in 26 minutes. I opened that same project in Vegas 21 build 208 and it says and 1hour and 13 min
There are too many variables here for me to give useful advice. Keep VEGAS on the default settings as you don't have a reason to change them yet.
Which benchmark did you try- VP 20 sample project? 7 minutes isn't good.
I recommend using a free app like HWINFO64 to see if you are thermally throttling during the render. https://www.hwinfo.com/download/
Before doing more tests turn off the PC and let it cool down (go for a walk, have dinner). Then try rendering the sample project to MagixAVC with NVENC with HWINFO64 open. Watch your CPU core and GPU temperatures and see if it says throttling for any of them.
If that's fine (temperatures aren't too high), the next question is what driver versions you are using. VEGAS help/ driver update can guide you to newer ones for your GPUs.
As for a 3 minute render taking an hour, that's probably due to some Fx you are using. AI enabled ones including denoise take a very long time to process and that is unavoidable.
I thought you were supposed to modify for better performance. I guess not..
Yes the vp20 benchmark
Temps don't raise past 70c
Im using the newest nvidia driver available
In the update window in Vegas
I updated 3 days ago
I appreciate your time
I will retrieve the media info tomorrow and post
I know it's a avc1 file from a gh5 shot in 4k
Vlog -l
The nvidia control panel is the only system change and program change that I have done in 3 years of using the program and this is the first time my renders skyrocketed
OK understandable I am using one instance of neat video ver.3 and one instance of magic bullet looks on on every project...needed for dark lowlight shots...once again thank you.
Try the same render without the Fx to see if they go much faster. I also use NeatVideo (version 5) and does make good use of the GPU. Magic Bullet looks, I don't know.
I have two NVIDIA GPUs (RTX2080 and mobile GTX 1050) and haven't touched NVIDIA Control Panel.
To make VEGAS work slightly faster I undervolted my laptop (stopped when it blue screened) and increased CPU GHz on my desktop until I couldn't cool it enough. I also mildly increased the GPU clock speeds.
For media, AVC should decode fine with Radeon Graphics assuming that driver is also not ancient. HEVC depends on which kind of HEVC it is. That's just decoding though, the bottleneck may be processing the Fx.
The default setting for VEGAS should select NVIDIA for preferences/ video and AMD for hardware decoding in file io. There's no reason to change it in general.
For a render crash that's not good. Did a crash report screen come up? What did it say in "show problem details"?
OK I'll reset and test today yes setting amd in pref and i/O instant crash...ill reset vegas and nvidia control and try to render. Last time I did that the render time went up to 10 hours
Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.2 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 1 min 2 s Bit rate mode : Variable Bit rate : 143 Mb/s Maximum bit rate : 158 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.287 Stream size : 1.03 GiB (99%) Encoded date : UTC 2023-10-03 13:59:29 Tagged date : UTC 2023-10-03 13:59:29 Color range : Full Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : avcC
Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 1 min 2 s Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 11.4 MiB (1%) Encoded date : UTC 2023-10-03 13:59:29 Tagged date : UTC 2023-10-03 13:59:29
Other ID : 3 Type : Time code Format : QuickTime TC Duration : 1 min 2 s Bit rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Time code of first frame : 12:30:09;16 Time code, striped : Yes Encoded date : UTC 2023-10-03 13:59:29 Tagged date : UTC 2023-10-03 13:59:29
Hmm, that AVC file (8-bit 4K60 AVC) should be easy for VEGAS to deal with.
If AMD decoding isn't doing well you could change file io hardware decoding to NVDEC or off and see if that helps any.
5:33 still isn't great for the benchmark but isn't terrible either. I'm not sure why your system isn't performing better here.
Undervolting, increasing clock speed, etc. may help 5% so I wouldn't worry about it at this time. The undervolting is mainly useful to me as it reduces heat which means my laptop can run at a higher clock speed for longer before it starts to throttle. If you don't see a decrease in clock speeds during the render or warnings of throttling in HWINFO, that isn't a problem for you.
What are your settings for this test? Encoding or decoding would be on the selected GPU.
For example, for the VP 20 benchmark the 3D calculation part is so resource intensive there will be a bit of decoding and encoding every few seconds but then the GPU has to wait to finish the rest before any more decoding or encoding activity can occur.