How to render to 3840x2160 with 50 fps correctly?

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Solved by

Jun 24, 2021 01:42

The default (PAL) AVC/HEVC rendertemplates of PD for UHD (3840x2160) have 25 fps. My footage and timeline is 3840x2160p50. I would like to render to 3840x2160p50 so I manually changed the default 3840x2160p25 rendertemplate to 3840x2160p50. After rendering, the resulting video it is indeed 3840x2160p50 (according Mediainfo) but only when playing the video it still looks like its rendered as 3840x2160p25. Moving objects become choppy. It looks as if every second frame of the 50fps is left out. It doesnt matter if I use AVC or HEVC. Only the default XAVC 3840x2160p50 rendertemplate gives a correct result.
Isn't PD not able to render UHD with 50 fps with AVC/HEVC correctly? Recware: DJI Osmo Pocket, GoproHero7Black, PanasonicFZ300/HCX909, Sony PXW-X160.
Software: Vegaspro365+Vegasaur/PowerDirector365
Hardware: i910900k,32GB,GTX2080s, 1920x1200 display
Playware: Samsung Qled QE65Q6FN, Philips 55PFL7108

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Jun 24, 2021 14:50

You've sone everything correctly so if the result looks choppy, try turning off hardware decoding from Preferences > Hardware Acceleration and also do not check the box for Fast video rendering technology on the Produce page. That will prevent PD from using your GPU for encoding and will only use the CPU.

Please post back with the results, and also with a link to the produced clip in a cloud folder if the problem remains.

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Jun 24, 2021 16:44

Quote You've sone everything correctly so if the result looks choppy, try turning off hardware decoding from Preferences > Hardware Acceleration and also do not check the box for Fast video rendering technology on the Produce page. That will prevent PD from using your GPU for encoding and will only use the CPU.

Please post back with the results, and also with a link to the produced clip in a cloud folder if the problem remains.

Indeed, unchecking the box for Fast video rendering technology on the Produce page gives a clear 50p rendering result, ofcourse with a dramatic increase of needed rendering time. I hope this issue will be solved in PD in near future. Thanks for your hint.

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Jun 24, 2021 16:56

Glad that worked. Check to see if the problem occurs with the latest nVidia Studio Driver (471.11) that was just released yesterday. Deutsch version here.

If so, you should report the issue directly to CL tech support. Include a new DxDiag report and a link to this discussion so they can see what's happened so far.

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Jun 26, 2021 00:17

Updating to latest Nvidia Studio driver makes no difference. Must be a bug in PD because rendering to XAVC 3840x2160p50 works fine. Also with enabled Nvidia GPU rendering support. Recware: DJI Osmo Pocket, GoproHero7Black, PanasonicFZ300/HCX909, Sony PXW-X160.
Software: Vegaspro365+Vegasaur/PowerDirector365
Hardware: i910900k,32GB,GTX2080s, 1920x1200 display
Playware: Samsung Qled QE65Q6FN, Philips 55PFL7108

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Jun 26, 2021 15:35

3POINT, just curious, since I believe the CL patch corrected your issue with SVRT working with your source footage, does SVRT have this frame problem too or does the frame issue only occur when hardware encoding is used with AVC or HEVC?

Jeff

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Jun 27, 2021 08:12

Quote 3POINT, just curious, since I believe the CL patch corrected your issue with SVRT working with your source footage, does SVRT have this frame problem too or does the frame issue only occur when hardware encoding is used with AVC or HEVC?

Jeff

Yes indeed, I first discovered the issue with SVRT rendering, which was solved with the CL patch.
My 2160p50 H.264 footage is recorded with 100mbps and SVRT rendering works now fast and correct. For my UHDTV I would like smaller files at lower bitrates, therefor I tried hardware encoding to 2160p50 with H.264 and H.265. Which obviously doesn't work. Disabling hardware support gives correct 2160p50 but at at very slow rendering. Recware: DJI Osmo Pocket, GoproHero7Black, PanasonicFZ300/HCX909, Sony PXW-X160.
Software: Vegaspro365+Vegasaur/PowerDirector365
Hardware: i910900k,32GB,GTX2080s, 1920x1200 display
Playware: Samsung Qled QE65Q6FN, Philips 55PFL7108

3POINT

Member Location: Germany Joined: Oct 01, 2015 03:52 Messages: 149 Offline

Jun 30, 2021 06:11

Quote
I hope this issue will be solved in PD in near future. Thanks for your hint.

That's quick. This issue seems to be solved in the latest PD365 June update.
What still is an issue, is that it's not possible to render GPU supported with H.264 in FHD resolution, "Fast video rendering technology" stays grayed out. No problem with lower or higher resoltions.

SoNic67

Senior Contributor Joined: Sep 27, 2014 14:14 Messages: 1308 Offline

Jul 01, 2021 20:41

Try rendering it at 60fps. Any modern "HDTV" should be able to play that, they are just big smartphones after all....

jmone

Senior Contributor Location: Australia Joined: Nov 26, 2010 00:05 Messages: 706 Offline

Jul 02, 2021 06:35

Quote Try rendering it at 60fps. Any modern "HDTV" should be able to play that, they are just big smartphones after all....

Very bad idea. Source is 50fps, rendering to 60fps will intoduce pulldown judder. Please stop with this nonsense. PD 64 Bit-Win10 64 Bit-32GB RAM-80TB HDD
Sony FX6 - 500Mbps 4k/50p AVC-I HLG
Canon XF400 - 150Mbps 4k/50p AVC
GoPro Hero6 Black
Pana HS700-28Mbps 1080/50p AVC (High@L4.2)
Canon HV20-HDV 25Mbps 16:9 1440x1080/25p MPEG