Vegas Pro 16 rendering glitches

Deuce wrote on 11/30/2018, 2:16 PM

I just upgraded to VP 16 (build 307) from 11. I always had issues with rendering in VP and was looking forward to finally not having those issues any more.

The project is nothing overly complicated - 5 minutes HD with some processing on the clips and a couple of audio tracks. When I went to render the project it froze at 92%. Here we go again. So after some Googling I turned off GPU processing figuring that had to be the issue and it rendered. When I went to watch it there were glitches all over the place and odd frames randomly showing up all through it. So some more Googling brought up the suggestion to set Dynamic RAM Preview to 0MB. Voila! It rendered glitch-free.

So my questions are:

1. Why are there so many issues with using GPU acceleration? I have a 2GB GeForce GTX 950. I know they recommend a 4GB card but it still shouldn't cause rendering issues, should it?

2. Why would Dynamic RAM set to 200MB create such a complete mess of my render?? I have 16GB with no other programs running.

I can't believe after all these years I'm still having these type of issues. VP has even locked up on me a couple of times while editing. I'd hate to see if I was doing something complicated or, heaven forbid, a 4k project.

 

Windows 10, Quad core i7 920

 

 

Comments

j-v wrote on 11/30/2018, 3:00 PM

1. Which driverversion is installed for your GTX 950?
Which rendertemplate are you using for your render?

2, What type of sourcefile you use?
Which projecttype?

Give the information you find here under C.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 581.29 and Intel UHD Graphics 630 with driver 26.20.100.7985
Vegas software: VP 10 to 23 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

klt wrote on 12/1/2018, 2:28 AM

Welcome to the club :)

https://www.vegascreativesoftware.info/us/forum/vegas-renders-random-frames-incorrectly--113883/

Most of the time GPU acceleration is great. For me it becomes unreliable on complex projects, say 14 videotracks, including multiple compositing parent having more children...

Yes, sometimes set dynamic ram preivew to 0 helps, sometimes it just decreases the chance for the problem to appear. However, this set highly impacts rendering performance.

To me this thing looks like some incorrect buffer handling.

I have started a ticket about this few days ago - not the first time, and I'm afraid not the last time.

 

Last changed by klt on 12/1/2018, 2:31 AM, changed a total of 1 times.

Camera: JVC GY-HM600

Desktop: AMD Ryzen 5 1600, 16GB RAM (dual channel 2400 MHz) - Videocard: Radeon R9 380 2GB

Laptop: i5 5200u, 8GB RAM (1600MHz single channel) Videocard: integrated HD5500

Jessariah67 wrote on 12/1/2018, 6:31 AM

This answer is not intentionally vague - it just is by nature.

I had similar problems occasionally in previous versions of Vegas. Trying looking at the preview window, identify the clip/image that Vegas is in the middle of when it freezes on the render. Remove that clip/image from the time line and try to render the project again. Whenever this has happened to me, it has always turned out to be Vegas "not liking" the source media it is trying to render. If you find that it renders 100% without the clip/image, then convert the media in a third party software and see if that takes care of the problem.

I've also had times when I'd get blinks while rendering a PSD and had to convert it to a PNG, or vice-versa. There was also a version of Vegas (I think it was either 10 or 13) that, on my system, showed MP4s created in Screencast-o-matic as solid green, and I would have to convert them in a freeware program (I use Movavi now) from MP4 to MP4 - and then they would playback fine.

Sometimes, Vegas just "doesn't like" things as they are natively.

Deuce wrote on 12/1/2018, 8:22 AM

To answer j-v:

GTX 950 - latest drivers

Render template - Sony AVC Internet 1920x1080 30p

Source files - mostly AVCHD (.mts) with a few .avi files from After Effects and some .mp4 clips

Project type - 1920x1080 29.97

Deuce wrote on 12/1/2018, 9:32 AM

I did a couple of tests:

GPU processing turned on, dynamic RAM 0MB - rendered glitch-free

GPU on, dynamic RAM 200MB - froze halfway through

So it appears my issue is related to dynamic RAM but why??

j-v wrote on 12/1/2018, 9:35 AM

GTX 950 - latest drivers

That means 416.94 ?

Render template - Sony AVC Internet 1920x1080 30p

That is a very old codec and you will not see any advance compared to the same render in ancient Vegas versions.

Did you already tried the Magix AVC with NVENC option?
That one renders for me always fine since the first builds of Vegas Pro 15 and 16.
Maybe you have also the same codec with QSV option(from the Intel GPU), with me in lower bitrates that one give sometimes frames with a little blurry, but not the NVENC option of that codec.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 581.29 and Intel UHD Graphics 630 with driver 26.20.100.7985
Vegas software: VP 10 to 23 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Deuce wrote on 12/4/2018, 9:29 AM

I tried the Magix AVC with NVENC.

GPU processing on, Dynamic RAM set to 200MB - froze part way through

GPU processing on, Dynamic RAM 0MB - rendered quickly and without any glitches

So there is definitely an issue/bug regarding Dynamic RAM.

RogerS wrote on 12/19/2018, 7:19 PM

I have had issues with glitches where I run photos (and a black border to hide the different aspect rations) over regular HD mp4 video clips. I'd get flash frames where there were none in the underlying project. I could solve this by not using NVENC for rendering, but it takes a long time CPU only.

I just ran three tests on the same problem project.

Vegas 15, NVENC
Vegas 16, NVENC
Vegas 16 NVENC dynamic ram = 0

I let the computer (Dell XPS 15, NVIDIA 1050) cool down between runs

Vegas 15, NVENC 4:48
Vegas 16, NVENC 5:14
Vegas 16 NVENC dynamic ram = 0 7:27

Both the Vegas 15 and 16 with NVENC had glitches in different places.
Vegas 16 with dynamic ram 0 was the slowest but appears glitch free. I'll continue to test this but it seems like an acceptable workaround.

Norbert wrote on 2/19/2019, 2:46 AM

I have had issues with glitches where I run photos (and a black border to hide the different aspect rations) over regular HD mp4 video clips. I'd get flash frames where there were none in the underlying project. I could solve this by not using NVENC for rendering, but it takes a long time CPU only.

I just ran three tests on the same problem project.

Vegas 15, NVENC
Vegas 16, NVENC
Vegas 16 NVENC dynamic ram = 0

I let the computer (Dell XPS 15, NVIDIA 1050) cool down between runs

Vegas 15, NVENC 4:48
Vegas 16, NVENC 5:14
Vegas 16 NVENC dynamic ram = 0 7:27

Both the Vegas 15 and 16 with NVENC had glitches in different places.
Vegas 16 with dynamic ram 0 was the slowest but appears glitch free. I'll continue to test this but it seems like an acceptable workaround.

Have you found any solution to render using GPU+RAM without glitches?

Peter_P wrote on 2/19/2019, 4:09 AM

Did you try to set the Maximum number of render thread to 1 ?

Norbert wrote on 2/19/2019, 8:05 AM

Maximum number of render thread to 1 didn't help, I tried dynamic ram 0 and didn't help either. It's a RAM management issue the codec has.

Norbert wrote on 2/19/2019, 8:21 AM

It starts filling the RAM during rendering and when it's full the GPU crashes.