@Phil-MJr. rendering (final output) with Nvidea HW acceleration should always be with Preference ==> Video ==> Dynanic RAM preview put to 0

This is (and has) been an issue (rendering artifacts, blanking, flickering, etc) for every Vegas release I know off (and any of my PC builds over the years with different NVIDEA high end videocards). It is aggrevated by the type of contend and use of plugins. Just put it to 0 when rendering, rendering takes just a little bit longer, but not by much.

@bitman If @Phil-MJr. is using HW encoding then the following info. may be of use. Long story short don't use RC mode set to vbr if your render output file is a relatively high data rate. Long story below ...

The following table identifies some of the issues = "Fail". It also highlights the best quality settings highlighted in green, with the variations that I tested.

These quality comparison tests using ffmpeg were done on my Desktop.

---------------------------------------------------------------------------------------------------------------

 Testing the limits at which the following settings fail to produce a useable file, tested on laptop ...
 --------------------------------------------------------------------------------------------------------------------------------------
 

@Phil-MJr. Hi Philip, “Rendered output is often unusable” i’m assuming that you’re using Nvidia hardware rendering, if not then ignore the following ... what data rate are you rendering out the UHD to and which Preset and RC Mode are you using.

Thank you for your help.  I have tried numerous quality settings and bit rates.  Today I rendered at 50 mbps average 135 mbps max. VBR. It is as you say that it will freeze up during rendering. If I set dynamic RAM to 0, then it completes the rendering, but at a slower pace. When it locked up, I sent a detailed crash report.

@Phil-MJr. rendering (final output) with Nvidea HW acceleration should always be with Preference ==> Video ==> Dynanic RAM preview put to 0

This is (and has) been an issue (rendering artifacts, blanking, flickering, etc) for every Vegas release I know off (and any of my PC builds over the years with different NVIDEA high end videocards). It is aggrevated by the type of contend and use of plugins. Just put it to 0 when rendering, rendering takes just a little bit longer, but not by much.

Thanks bitman, this helped.  I rendered a 1:42 segment at 50 avg. /135 max. Mbps VBR 29.97 fps with the NVidia (EVGA) card in 19:41.  I then rendered with Intel QSV in 26:49.  The NVidia rendering (with dyn RAM set to 0) was an improvement, but not near where it should be.  

I rendered with NVIDIA in 1080p 50/135 (dyn RAM 32000) in 5:31.  If I could turn on the dynamic RAM in UHD, it would make a tremendous difference in rendering speed.

Source files were 100 Mbps UHD HEVC and 15 Mps AVC (1080p) files, plus audio tracks. Extensive video plug-in effects in the project. 

I created a simple test project with 3 UHD clips on one video track totaling 1:44, with no plug-in effects. It rendered UHD in 2:22 with the NVIDIA hardware (0 dynamic RAM).  If I tried rendering with dynamic RAM (32000) it locked up midway. Rendering with Intel QSV took 8:11.

Interesting discussion as I'm having the exact same trouble on my laptop Razer Blade with built in Nvidia GP. Project crashes at playback and rendering process crashes as well. Usually I never get as far as to render as a project that cannot be made cannot be rendered. Anyway, since I'm not really getting any help in my own thread I might get some help here. Lets say its worth checking my Vegas Pro 17E settings. Lets start with the play back feature. Any settings that you might recommend I try?

@TDK Well I do believe that the other users in your previous thread did try to help you. Anyway, a good place to start is adding your computer specs to your signature, this saves re-entering it in different threads .  Example, select my user icon and look there if your unfamiliar with this.

A short general troubleshooting list, not in any particular order, some of the following may or may not be applicable to your problems.

Use proxy files for easier playback if it’s a 4K project and your computer has marginal specs. See this link.

Confirm your computer meets the minimum system specs required ...

Supply mediainfo screenshot(s) of file(s) thats giving trouble. Supply render template(s) screenshot(s) also.

Supply a downloadable version of (for example via dropbox) the project or file that other users can confirm if it's the cause of the problem

Use the latest Nvidia Studio drivers

Set Dynamic Ram Preview to zero

Uncheck all items in Preferences/File I/O options ... Options/Preferences/File I/O

Disable Intel iGpu in bios

Disable QSV ... in Options/Preferences/General/Enable QSV Encoding & Decoding ... 21st. item down in VP17 list.

Disable GPU HW Acceleration in Preferences

Nick Hopes link for crashing and stability.

Reset VP to default settings

If your project is saved in VP17, try copying and pasting it to VP16, see if the project will then playback/render better.

Hi,

I know my reply here will not be terribly helpful to you, but I promised myself that I will mention this each time when I see a driver related problem here on the forum. :)

In my experience, the only solution that would allow me to use the nVidia card that my laptop has - 1050Ti , was to stick to driver 399.24. Nothing newer would work, much to my disappointment. NOTHING up until 419 when I stopped trying and I forced Windows to never update (which in itself was another huge endeavor).

It was terribly frustrating to me to have a dedicated GPU and not be able to use it.

Anyway, it is working, but I will probably never update to another driver. After all, I don't think I really need it.

But definitely, Vegas should deal somehow a little bit better with GPU enabled.

I hope the development team works to improve Vegas Pro 17 performance with the NVidia Studio drivers. The RTX-2070 card I have does not take advantage of its high performance through-put capabilities without errors in Ultra HD projects (using Win 10 Pro i7-6700K 64 Gbytes RAM system). The more complex the project, the more likely it will not be able to either preview or render past the first several seconds of the project, without video blanking. Rendered output is often unusable. Thanks to tips on this forum, I found I need to switch off the File I/O option (Enable hardware decoding for supported formats) of the NVIDIA NVDEC decoder and switch on the Intel QSV decoder, which does work correctly with Vegas Pro, although slower. I don't notice these problems in 1080p. I have continuously upgraded to the latest NVidia driver, with no improvement. The program has some very powerful features and is well thought out.

Does Vegas Pro 17 recognize 64 Gbytes RAM? For dynamic RAM preview (it says 32768 MB max available and that is the max it allows).

Thanks.

Hi,

I know my reply here will not be terribly helpful to you, but I promised myself that I will mention this each time when I see a driver related problem here on the forum. :)

In my experience, the only solution that would allow me to use the nVidia card that my laptop has - 1050Ti , was to stick to driver 399.24. Nothing newer would work, much to my disappointment. NOTHING up until 419 when I stopped trying and I forced Windows to never update (which in itself was another huge endeavor).

It was terribly frustrating to me to have a dedicated GPU and not be able to use it.

Anyway, it is working, but I will probably never update to another driver. After all, I don't think I really need it.

But definitely, Vegas should deal somehow a little bit better with GPU enabled.

Thanks!

@adimatis

But definitely, Vegas should deal somehow a little bit better with GPU enabled.

Lucky this works great at my laptop from signature, so to me nothing wrong with the options and the latest Studio driver 441,66 for the Nvidia 1050.
I tested this again with Windows 10 and the Intell GPU completely updated since yesterday, my results for 30 sec FHD 50p MTS file (AVC codec)
1. rendered with the default Magix AVC 50p (Mainconcept) 110 sec. for 75 MB
2. rendered with the default Magix AVC 50p QSV (Intel) 76 sec for 73 MB
3. rendered with the default Magix AVC 50p Nvenc(Nvidia) 30 sec for 75 MB

All files play the same and fine.