New Vegas 18 Problem with Rendering

Comments

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

Yess and my error message for the same render is different. The OP could clear his problem with the Dynamic Preview setting, my problem is different with the same renderoption of the same file.

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, 8:24 PM

DJI and GoPro footage is known to be challenging. Do you have any other AVC files to test? Just in the name of science (and filing a detailed bug report).

lenard-p wrote on 8/3/2020, 11:50 PM

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

I"m not technical so not pretending to understand this, but when the turing GPU's came out Nvida did an update on how software can talk to Nvenc encoder. Max B-frame look ahead and Psycho Visual Tuning became part of the Turing Nvenc chip's duties. There was no need for it to use cpu or cuda for the process. When you use OBS with Nvenc (New), the new 2 dedicated Turing Nvenc functions are offloaded to cuda (compute) on the gpu with 10 series cards, and other than reducing efficiency of GPU for compute there are no negatives. I thought this happened transparently but maybe software developers must detect and change how software acts with 10 series cards and that isn't happening.

I assumed a lot, including VP18 using Nvenc(new). could be a much less interesting bug

Grazie wrote on 8/4/2020, 12:40 AM

Late to the Party! But I'm getting successful NVENC Renders. Here I'm using the HOS RE Tool:

GPU = ON

RAM = 200

CPU = i9

Nvidia Driver a little behind but activly supporting my NVENC Renders:

 

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

Okay, jump back to my OP. :-)

I found a second problem with enable RAM Preview. If I use this function with "Shift + B" I have frame drops in my preview windows and if I want to play the RAM Rendering Clip, Vegas crashed.

Unfortunately, I must switch back to Vegas Pro 17 ...

j-v wrote on 8/4/2020, 4:05 AM

@Grazie

My problem is not with your type of render, but to render UHD files to UHD Magix AVC or HEVC( in my case 50p) with the NVENC option.

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 !!!

PhilippZ wrote on 8/5/2020, 5:21 AM



The Problem is not only for Rendering. I have playback problems too, if I set RAM preview over 0.