Vegas renders random frames incorrectly....

Norbert wrote on 11/27/2018, 3:16 AM

I had to make a short trailer for a performance and I used Vegas and I regret it... a h265 VBR file is the source and when I render the footage sometimes, not every time Vegas Pro 16 renders random frames where they don't belong. This was the last f**** time I used Vegas Pro for any of my projects. It's lotto, sometimes it works and you don't know why and sometimes it just doesn't and you don't know why.... -.-"

Comments

fr0sty wrote on 11/27/2018, 12:37 PM

Update your GPU drivers, that tends to help the problem when I encounter it.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Musicvid wrote on 11/27/2018, 1:09 PM

Make certain Quantize to Frames and Snapping are turned on, and Media settings Matched, before adding content to a new Project.

Norbert wrote on 11/28/2018, 4:05 AM

The driver is updated, it's random, you need luck to not have extra blinking frames......

klt wrote on 11/29/2018, 9:57 AM

Sadly GPU acceleration is broken in multiple ways. This is one of the bugs that is never going to be fixed.

I fight with it since version 14, and once i uploaded a whole project with media files to MAGIX.

If your project is simple, GPU works great and helps really a lot. If you have a dozen of videotracks, and there are also compositing children tracks, and effects, and such, GPU acceleration fails. Seems that dynamic preview set to zero decreases the chance of appearing the bug, but it certainly does not eliminate. And setting dynamic preview to zero also impacts rendering performance.

So you need to disable GPU acceleration, and prepare to an overnight CPU only render.

Norbert wrote on 12/4/2018, 1:49 PM

Sadly GPU acceleration is broken in multiple ways. This is one of the bugs that is never going to be fixed.

I fight with it since version 14, and once i uploaded a whole project with media files to MAGIX.

If your project is simple, GPU works great and helps really a lot. If you have a dozen of videotracks, and there are also compositing children tracks, and effects, and such, GPU acceleration fails. Seems that dynamic preview set to zero decreases the chance of appearing the bug, but it certainly does not eliminate. And setting dynamic preview to zero also impacts rendering performance.

So you need to disable GPU acceleration, and prepare to an overnight CPU only render.

Yeah, sadly that's what I did, I disabled GPU to render it properly but it took 4 times more to export...

The fun part is that I succeeded to crash even Premiere while using fxs and Mercury Transmit...

Now I'm experimenting with Resolve, but I need to buy a card If I want fullscreen preview on my second monitor so the conclusion is that there is no perfect video editing software.

fr0sty wrote on 12/5/2018, 5:24 PM

I just rendered out a 6 camera 2 hour long multicam with various fx applied throughout using NVENC just fine, so project complexity alone isn't the triggering factor. Probably has to do also with media used, frame rates, etc.

Last changed by fr0sty on 12/5/2018, 5:24 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

klt wrote on 12/6/2018, 12:15 AM

Hi @fr0sty, in my case nothing special was used. AVCHD footage directly from my camera, couple of PNG's as graphics and generated media solid color, and legacy-text - all those used to work fine in simple projects.

With complexity I don't mean necessarily a long project, but many video tracks.

I used a lot of them, including parent tracks with parent motion, also track motion on child tracks.

Here's how it should look (rendered with CPU only):

Here's how it looks rendered with GPU support enabled:

Watch at 0:22, where randomly some frames appeared from another event instead of the solid background, and around 0:27 where the solid background is completely "forgotten" to render, and another glitches are there, some of my lines and point are visible, but believe me, the project should not look like that. And that lasts only for 1 to 3 frames.

And these are random, if I render again, very similar glitches appear at different positions. And it looks also very similar if I render on my laptop, so the only thing those "bad renders" share is Vegas with enabled GPU.

(Desktop HW: Ryzen 5 1600 + R9 380 + 16GB RAM, Laptop: i5 5200U + integrated Intel graphics + 8GB RAM)

And they render with similar errors, if GPU is enabled.

 

 

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

I had issues with flash frames with a simple project- jpeg, solid background and video. So far I can avoid them if NVENC is not used in the rendering template, but rendering times are long.

Today I had a glitch-free render using Vegas 16 with NVENC and setting dynamic ram to 0. Try that and see if it makes a difference?

klt wrote on 12/20/2018, 3:02 AM

setting dynamic ram to 0.

It makes a difference, because there are then less glitches. But still there are.

I'm preparing the project to send to @OldSmoke to make a test render on his way much more powerful system. At the moment I think the problem will show up on his machine too, but of course as always, I may be completely wrong.

Also I'm donig my (a bit more thorough) tests at the moment. I'm going to tell my results in this thread:

https://www.vegascreativesoftware.info/us/forum/v16-permanent-problem-with-dynamic-ram-in-rendering--113885/#ca705724

Peter66 wrote on 12/20/2018, 2:12 PM

Hallo all,

 

did you ever set the number of rendering threads to 1?

Since then I never had glitches again!

Only 1 not 2! If I use 2 or more rendering threads the 'glitches’ are still present. Not often, but in nearly all rendered Projects.

Give it a try!

 

Best regards

Peter

peter-r wrote on 12/20/2018, 2:24 PM

See also

https://www.vegascreativesoftware.info/us/forum/mercalli-glitches-in-vp14-and-vp15-with-uhd-output--109577/#ca676741

 

klt wrote on 12/20/2018, 3:22 PM

did you ever set the number of rendering threads to 1?

Not at all. Thanks for another thing to try. I always used the number of rendering threads that equals to the cores (or threads) of the CPU. So on my Ryzen, I have set it to 12. I'll give it a shot, and see how it affects performance.