New Vegas 18 Problem with Rendering

PhilippZ wrote on 8/3/2020, 4:37 AM

Hi,

Vegas 18 have a new 8 bit full range option. This is great, because I no longer have to use this level trick (Studio RGB to Computer RGB). But I can not rendering my videos. You can see the problem here:



In ENG: The system does not have enough memory ...

I want to render UHD with NVIDEA NVENC (AVC/AAC MP4). But it doesn't work even without GPU support.

I have a Ryzen 7 1800x and a GTX 1080. I want to render a Testclip (5 seconds and 8 MB).

EDIT: If I set "dynamic RAM Preview" to 0, than I can fix that problem. I hope, Magix can fix that problem / bug soon.

Thank you!

PS: Same problem now in "old 8bit Video range". No problems with VP17

Comments

fr0sty wrote on 8/3/2020, 4:49 AM

Set your dynamic RAM preview to 0, perhaps that old bug is showing it's face again. Does that help?

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

PhilippZ wrote on 8/3/2020, 5:00 AM

Set your dynamic RAM preview to 0, perhaps that old bug is showing it's face again. Does that help?


Yes, that helps. I know this bug from VP15 and VP16, but I do not have such a problem with VP17. That doesn't make a good impression for VP18. :-(

pierre-k wrote on 8/3/2020, 5:10 AM

Set your dynamic RAM preview to 0, perhaps that old bug is showing it's face again. Does that help?

Is this also the insignificant bug that bothers a small percentage of users? I think not. This bug should have been fixed a long time ago. Nevertheless, it has been bothering us for several years.

PhilippZ wrote on 8/3/2020, 5:15 AM

Set your dynamic RAM preview to 0, perhaps that old bug is showing it's face again. Does that help?

Is this also the insignificant bug that bothers a small percentage of users? I think not. This bug should have been fixed a long time ago. Nevertheless, it has been bothering us for several years.

I have been using Vegas since VP15 and had the bug in 15 and VP16. VP17 ran / runs great and for me without errors and now VP18 starts again with an old bug. Thats not cool!

j-v wrote on 8/3/2020, 5:48 AM

Look how such a render goes with me on laptop from signature, comparison between 17 and 18

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 5:55 AM

This bug seems to mostly affect users of the old GTX series of Nvidia cards, especially those with 10xx or older cards.

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

j-v wrote on 8/3/2020, 6:04 AM

I my case indeed.
But only the render option with NVENC.
Conclusion?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 6:09 AM

NVENC is the only option that uses the GPU to render. Perhaps those old GPUs can't keep up.

Last changed by fr0sty on 8/3/2020, 6:09 AM, changed a total of 1 times.

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

RogerS wrote on 8/3/2020, 6:22 AM

Well that's not good... I hope that is addressed soon.

I'm waiting for the Voukoder developer to release a new connector as I'd rather use that anyway.

(There are "new" 10-series NVIDIA cards being sold now, like the GTX 1650, so I wouldn't disparage them as old technology).

j-v wrote on 8/3/2020, 6:23 AM

I think it is a shortcoming in the specs if it is really the case

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 6:25 AM

Well, actually, it likely isn't a hardware limitation since setting dynamic ram to 0 fixes it, probably just a bug limited to those cards that hasn't been squashed because, most folks don't have those cards. I'll make sure the team is aware of it.

RogerS wrote on 8/3/2020, 6:34 AM

I just did a render of a way more complex project (nest plus clips) with the NVIDIA 1050 at Magix AVC 1080p 23.976fps (NVENC) without issue. It averaged 70fps.

I picked a second project that has 4K source footage and rendered to Magix AVC (NVENC) 2160p 60fps (I'm in NTSC land). It averaged 3fps.

Dynamic ram preview is at 200MB. File I/O has Intel as the decoder to use. I'm on an Intel i7 processor- is that the difference between our systems? I'm trying to understand how to replicate your problem.
 

fr0sty wrote on 8/3/2020, 6:39 AM

(There are "new" 10-series NVIDIA cards being sold now, like the GTX 1650, so I wouldn't disparage them as old technology).

Technically that would be 16xx, not 10xx.

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

j-v wrote on 8/3/2020, 6:41 AM

I'm on an Intel i7 processor- is that the difference between our systems? 

Who are you asking?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 6:43 AM

I would imagine anybody experiencing this issue?

RogerS wrote on 8/3/2020, 8:00 AM

I'm on an Intel i7 processor- is that the difference between our systems? 

Who are you asking?

The people in this thread who are unable to render. Is there something different I can do with project or render settings to attempt to replicate this? I'm on a NVIDIA GTX 1050 4GB (notebook).

FWIW, the Vegas Pro page lists this for supported NVIDIA GPUs: NVIDIA® GeForce GTX or RTX 9XX series or higher with 4GB

So Vegas GTX 10 series and the newer 16 series should be supported (The 1650 has the same NVENC encoder as the 10 series if I'm reading this right, so for rendering there is no distinction).

fr0sty wrote on 8/3/2020, 8:06 AM

From my observation, it seems to be:

GTX 10xx series or earlier.

Intel CPU

=/>16GB RAM

Those seem to be the specs that get affected the most.

j-v wrote on 8/3/2020, 9:18 AM

Om my laptop from signature I'm not able to render to Magix AVC or HEVC UHD(3840x2160 50p) with NVENC only in VPro 18 with this sourcefile(s)+projectsetting

No problem same codecs to render to FHD(1920x1080 50p).
Also no problem with projectsettings FHD or render to UHD ( not NVENC)
Latest NVidia Studio drivers used nr. 27.21.14.5177

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 9:19 AM

Do you have your dynamic RAM set to 0?

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

RogerS wrote on 8/3/2020, 9:40 AM

From my observation, it seems to be:

GTX 10xx series or earlier.

Intel CPU

=/>16GB RAM

Those seem to be the specs that get affected the most.

Weird as I'm on GTX 1050, Intel i7700, 32GB ram.
(Dynamic ram=200)

I notice in j-v's media info screenshot it says dji.avc Is this drone footage? Which drone? I was testing 4.2.0 AVC footage out of Sony cameras. (I have some Phantom 3 and Mavic Pro footage somewhere).

j-v wrote on 8/3/2020, 9:51 AM

@fr0sty
0, default 200 or 1000 makes no difference.

@RogerS

 Which drone?

DJI Osmo Pocket handheld

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

RogerS wrote on 8/3/2020, 10:11 AM

Could you try once with non DJI AVC files?

j-v wrote on 8/3/2020, 10:46 AM

Yess, with 4K 25fps from my GOPro 7 AVC or HEVC, same result

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 8/3/2020, 10:47 AM

That's a different message than the low memory error described in the OP. Looks like we've got a separate issue to track down.