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

Revisiting noise and contrast issues in exports

Community Beginner ,
Feb 03, 2023 Feb 03, 2023

Copy link to clipboard

Copied

I know this has been discussed at length... I have a project open, everything looks good in the timeline, then the export is full of noise, the contrast is off, and the exposure is bumped way up. The solution is the Gamma shift LUT from Adobe, etc., etc.

 

But I feel like there's something else at play that is causing this on certain machines. Case in point: I have two, nearly identical XPS laptops - one provided by work and the other is my personal device. The work laptop, an XPS 15 (9520), W10, NVIDIA GTX 1650 Ti running Premiere Pro 23.1.0, creates the export error. The personal laptop, an XPS 17 (9710), W11, NVIDIA RTX 3050 running the same version, does NOT create the error, even when working on the same project file. I find myself exporting projects into the cloud and opening them on my personal device just for exports, then sending the file back to myself. 

 

In the last two years, I've worked on and exported roughly 1,000 videos for web (I'm a full-time producer) and this issue just popped up about 4-5 weeks ago.

 

All project settings, inport and export, are identical, and NVIDIA drivers are up to date on both machines. I'm at a loss.

 

Oh, and I've tried using the Gamma Correction LUT's with no success...

 

The first (left) photo is footage from a ZCam E2 S6; the second (right) is from a Sony FS5 mkII.

Error1.pngexpand imageError2.pngexpand image

TOPICS
Error or problem , Export , Hardware or GPU , Performance

Views

175

Translate

Translate

Report

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
Community Expert ,
Feb 03, 2023 Feb 03, 2023

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

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 ,
Feb 03, 2023 Feb 03, 2023

Copy link to clipboard

Copied

As you're on a PC, not Mac, that's not the "gamma LUT" thing that is used because Macs use the improper gamma for displaying Rec.709 video media.

 

So we're looking more at color management settings on your computer. Do you have the Display color management preferences option set on one or both?

 

Next,on the work laptop computer, reimport the file into Premiere on that computer. Is the reimported file displayed the same as you see on the sequence in Premiere?

 

And use the scopes ... check your black and white points. Is the file actually brighter or simpy displayed brighter?

 

What are the Nvidia settings on the two computer for video levels ... the Nvidia control panel, Video Color, Advanced option?

 

Neil

Votes

Translate

Translate

Report

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
Community Beginner ,
Feb 05, 2023 Feb 05, 2023

Copy link to clipboard

Copied

LATEST

Neil,

 Thank you for the thoughful troubleshooting. Your suggestions echoed my steps before posting. All three color boxes are unchecked on both machines (Log Color, Display Color Management, and EDR). I also wondered if the NVIDIA driver could be causing the issue, and verified that both machines are running NVIDIA Studio Driver v528.24. As far as I can tell, all of the NVIDIA settings are identical on both machines (my version of NCP no longer has the advanced menu, unfortunately).

 

I'm going to run some scope tests tomorrow, but seeing that I can get a clean export on one machine (that looks good in playback on the other), I'm pretty confident that there's something happening in the export on one machine that's causing the error.  Might be time to simply reformat & reimage the device and start from scratch...

 

Votes

Translate

Translate

Report

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