Build 636 - Rendering now working

Bruggeling wrote on 6/7/2022, 9:23 AM

After a week of trial and crashing I finally found a way to render my videos without crashing.

The project I am working on has a mixed bag of input : some HD some UHD. The HD came mostly from Panasonic FZ1000 cameras, who only have 8 bit color depth, so I left pixel format at 8 bit full range.

After changing that to 32 bit floating point video level, suddenly everything rendered without problems...

Although I have no idea why this works with the input from the older camera's, and also why some selections did render, and why everything rendered without colorgrading when pixel format was at 8 bit full range.

As many here are having problems with rendering, I wanted to share this info.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

Comments

jay-aero wrote on 6/7/2022, 10:29 AM

Try Uninstalling then reinstalling or Resetting VG19

I can't get build 636 to render with Voukoder.. I have 636 on a laptop .. I tried reseting VG 19 ( including cache ) finally I completely Uninstalled and reinstalled and that worked on that computer... Then I installed on my desktop and I 1st uninstalled old version then installed 636 same issue and I can't get it working.. I have to use Magix HEVC to be able to render.. very frustrating

Howard-Vigorita wrote on 6/7/2022, 2:28 PM

@Bruggeling You might be on to something with the project settings. I almost always switch to 32-bit video levels before doing final renders.

RogerS wrote on 6/7/2022, 3:51 PM

Interesting. Wonder if it's something with the ACES engine getting triggered in 32-bit full mode. Did it have the same problem in earlier builds or is this a new issue?

Bruggeling wrote on 6/8/2022, 3:11 AM

@RogerS No idea, because it was the first time I mixed HD and UHD in one project. The UHD was in fact "produced" by Vegas, because the original also had HDR and VLog, which I removed by rendering all that material to UHD without HDR and to rec. 709 from rec. 2020.

As I started the project in build 636 I couldn't go back, because there was a warning during the upgrade that it would not open in an older build.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

RogerS wrote on 6/8/2022, 6:32 AM

UHD vs HD won't trigger any issues so I guess the answer is that it is a new issue for 636 if you used the same types of media with 32-bit full before. I haven't tested 32-bit full in a while as it doesn't do anything useful for me. (I use 8-bit full or 32-bit video if I have > 8 bit media)