Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Hardware Encoding Export Corruption

Explorer ,
Jul 03, 2020 Jul 03, 2020

Hardware: GIGABYTE AERO 17 XB

Operating System: Microsoft Windows 10 Professional (x64) Build 18363.900 (1909/November 2019 Update)

Intel Core i7-10875H

Intel UHD Graphics/Driver: 26.20.100.7642

NVIDIA GeForce RTX 2070 Super/Driver 26.21.14.4253 (GeForce 442.53)

32 GB RAM

1x 512GB SAMSUNG MZVLB512HBJQ-00000 NVMe

1x 1TB ADATA SX8200PNP NVMe

 

Premier Pro Version 14.3

 

Footage: QuickTime.mov from Fuji GFX

 

The Problem: Everything works fine so far in Premiere except for both Source Monitor and Render Preview/Program Monitor display glitchiness during playback, and more importantly, exporting with hardware encoding enabled will only yield some sort of interlaced corrupted file. I have tested with all drivers updated and reverted back several times to no end. It appears to speed through the render process quite quickly, utilizing both Intel and Nvidia GPU's, but ultimately will not produce a correctly rendered video. No mattter what export settings I configure, the result is the same with hardware encoding enabled. See pic. Please Help.

 

TOPICS
Error or problem , Export , Hardware or GPU , Performance
734
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 03, 2020 Jul 03, 2020

Forgot to add footage info.

Type: MPEG Movie
File Size: 12.28 GB
Image Size: 1920 x 1080
Frame Rate: 59.94
Source Audio Format: 48000 Hz - 24-bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00;08;32;32
Pixel Aspect Ratio: 1.0
Alpha: None
Video Codec Type: HEVC 10 bit 4:2:0 (Full Range)

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 03, 2020 Jul 03, 2020

Did you select the option to do a "clean install" and use the Studio driver?

 

Neil

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 03, 2020 Jul 03, 2020

Hey Neil, Thanks for the reply.. I did do a clean install, however, i usally perfer to use DDU for absolutely clean install of Nvidia drivers and i did not this time.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 03, 2020 Jul 03, 2020

... and yes, i am only using the studio drivers.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 03, 2020 Jul 03, 2020

Huh ... I've heard of a few that had to go back to 442.19, but most have been able to work as long as they were at 445.x or earlier.

 

Neil

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 03, 2020 Jul 03, 2020
LATEST

i am thinking it may be a problem with the Quicktime h265 codec from the FUJI GFX. I tested some footage off my sony FX7 and had no problems, completely different codec though. Will keep checking.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines