Vegas 16 yet another GPU rendering problem

pl.blessu wrote on 1/22/2019, 1:40 AM

Dear Community,

I'm facing a serious problem with Vegas 16. When I'm trying to render a video I'm unable to finish it. Mostly I get an stranger error, when at some point, the render crashes and a few frames are repeated over and over again until render hits 100%. Weirdly, the file is most of the time completed fine, but video itself is buggy (as on render preview - at some point few frames are starting to looping). 1 of 10 times instead of an error I mentioned above my render just stops without throwing any error.

Here's my spec:

- Latest Windows 10 Home

- Vegas 16 (Build 361)

- AMD Ryzen 5 2600

- 32GB RAM

- GTX 1060 3GB

I've tried to investigate further this issue:

- No problem at all on Vegas 13 and no problem at all with gpu disabled (but render time is about 5 times longer, so I need to have GPU working properly)

- Occurs on different render codecs and on different source media codecs

- Tried different versions of GPU drivers, the latest one and older ones, no luck with this.

- Tried set Dynamic RAM Preview to 0, tried to disable So4, those also didn't help

- I've noticed that about let's say a minute before crash occurs my GPU is running out of memory, and Vegas starts to using "shared memory" (RAM?). So it looks like my 3GB GPU memory is not enough... But on my old PC with GTX 460 (1GB), Windows 7 and Vegas 16 everything worked fine just couple days ago.

I desperately need to get it fixed :( Could You help me with it?

Comments

Grazie wrote on 1/22/2019, 1:51 AM

@pl.blessu 

1) What is the MediaInfo for the Media?

2) What are your Project Settings?

pl.blessu wrote on 1/22/2019, 2:06 AM

Dear Grazie,

Current project:

Media info - https://mediaarea.net/MediaBin/YzBL32Gk

Project settings - set automatically by Vegas when import those files to timeline.

To be honest - I doubt it about media oraz project setting, I've tried many different project settings,many different render setting and many different source media, all of them working fine on Vegas 13 or worked fine on my old PC, and on all of them problems occurs now.

Grazie wrote on 1/22/2019, 2:17 AM

@pl.blessu

1) You’ve got Variable Bitrate Media. Search this Forum regarding Variable Bitrate and VP.

 

2) Still need to see your Project Settings. Need to get an idea of how much Math your rig is needing to do.

3) Other demands being made on your rig will be what kind of FXs your employing.

Last changed by Grazie on 1/22/2019, 2:18 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

pl.blessu wrote on 1/22/2019, 2:38 AM

Dear Grazie,

1) I didn't find anything that could be related to my problem regarding VB and VP. Could you share some light on this?

2)

3) I'm using Color Correction, a bit of Sharpen, Video Stabilization and LUTs.

Grazie wrote on 1/22/2019, 2:52 AM

@pl.blessu

1) Try this thread for ideas: https://www.vegascreativesoftware.info/us/forum/help-please-rendering-problem-video-goes-blocky-halfway-through--114493/#ca708122

2) Hmmm... “Adjust Source Media....” ?

3) Woah, that’s a mass of FXing! Also not much space to allow for system and also render?

I’d be sorely tempted to start over and work up to a Render.

I think you’ve got too much going on all at the same time for a render. I don’t stabilise and colour correct and sharpen at the same time. Add the Variable and asking that Media to be adjust to theRender. Others may take another view.

Last changed by Grazie on 1/22/2019, 2:53 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

pl.blessu wrote on 1/22/2019, 3:06 AM

1) Disable resample didn't help

2) Unchecked it, tried to render, problem still remains

3) 4 FX's added to media is a lot? That's just the basic effects added to media. I worked the same way on much, much slower PC with less space, with much much longer projects (2 hours + ) and everything were going flawlessly.

Grazie wrote on 1/22/2019, 3:15 AM

@pl.blessu

1) Is that all you got from that thread?

2) Could be that you’re so hard-up against a Render wall that this is another straw on the Camels back.

3) It’s not just about the amount, it’s the Type of FX. All those are, save CC, are intensive.

Do try to render a piece of non-variable bitrate Media without any FXing. Let’s try and work-up from a baseline.

pl.blessu wrote on 1/22/2019, 3:44 AM

Well, I found something.

Apparently Vegas 16 has a massive memory leak when LUT FX is added. Memory usage goes up until there's nothing left and render crash.

When I disable LUT FX, everything goes well, GPU memory usage is stable at around ~800Mb, no matter of settings, another FXs or anything related to media.

Looks like a bug that MAGIX should fix.

Grazie wrote on 1/22/2019, 3:50 AM

@pl.blessu Excellent! Breathe out..... and ....relax.... 😎

pl.blessu wrote on 1/22/2019, 3:55 AM

Dear Grazie,

To be honest LUTs are pretty important to me, it helps a lot with colors tweaking. It looks like I need to work without LUTs for some time until Magix fix it.

Nevertheless, thanks for Your involvement Grazie 🙏

Grazie wrote on 1/22/2019, 4:27 AM

@pl.blessu Have you added this thread to a Techical Support/Request ticket? Wouldn’t do any harm?

Last changed by Grazie on 1/22/2019, 4:30 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

pl.blessu wrote on 1/22/2019, 5:36 AM

Request ticket is send.

VEGASDerek wrote on 1/22/2019, 10:39 AM

We have looked at this and have reproduced the problem here. We will attempt to get a solution for this in a future update. Thank you for the detailed information.

pl.blessu wrote on 4/9/2019, 4:38 PM

@VEGASDerek

How's the fix development? Is there some chance that this problem would be solved in near future, maybe next update?