Skip to main content
Participating Frequently
November 2, 2022
Question

Colors are wrong when I use CUDA GPU Acceleration, but not when I use the Mercury Software Engine.

  • November 2, 2022
  • 3 replies
  • 6029 views

Please see title above. I'm desperate for a solution to this problem.

 

My colors are wrong when I use CUDA GPU Acceleration, but not when I use the Mercury Software Engine.

 

Here's what I see in the program monitor when I'm using the Mercury Software Engine. These colors are correct, and accurately reflect what I see in-camera. These colors also accurately reflect what I see when viewing the original video clip outside of Premiere:

 

...and here's what I see in the program monitor when I'm using CUDA GPU Acceleration:

 

As you can see, my black levels are completely incorrect, making it impossible for me to color grade with CUDA GPU Acceleration turned on.

 

Mercury Software Engine simply isn't a reasonable solution for me, so I'd appreciate any assistance I can get with this issue.

 

Specifications of machine and all other details below:

 

  • Computer

    • OS: Windows 11 Pro

    • CPU: Intel i9-10850k

    • GPU: GTX 3060 Ti

 

  • Software

    • Premiere CC 23.0

      • This problem also used to occur with Premiere CC 22.0 (all version updates).

    • Graphics Driver: NVIDIA Studio Driver 522.30

      • I have also tried using the most recent version of the NVIDIA Game Ready Driver (526.47) and several earlier versions.

 

  • Footage

    • The sample shot above was captured with the Canon R6 using the IPB Light Codec in 4K at 23.976 FPS.

    • I can confirm the footage format is not the problem, as I experience this even with the proxy files I generate.

 

Please help me resolve this before I lose my sanity!

This topic has been closed for replies.

3 replies

tim.hansberry
Participating Frequently
March 26, 2024

Did you ever get to the bottom of this issue?

Participating Frequently
March 26, 2024

No, I have no solution to this problem. I recently upgraded my editing machine, and the problem has since disappeared.

 

The lack of any type of official response from Adobe or their support staff on a major software issue which so many people have experienced is disgraceful. They must be too busy finding a way to justify further subscription price increases.

R Neil Haugen
Legend
March 26, 2024

You changed your computer, the problem disappeared, so therefore ... it's an Adobe problem.

 

There's a problem to me with the logic there. As the issue is caused by some setting in that machine. Not something "Adobe" does.

Everyone's mileage always varies ...
dermot_faloon
Inspiring
September 4, 2023

Did you solve this? or is there another thread I should follow - This is crazy that its like this after all this time.

tim.hansberry
Participating Frequently
March 26, 2024

I was wondering if anybody has solved this.  It's definitely an Adobe issue.  Not sure if it's only Adobe in tandem with a Nividia GPU, but since a driver update about 2 years ago I have been experiencing this quite a bit.  I have been working with software only for a long time now but would love to get to the bottom of this.

Neil, if you are reading this, your information is very insightful but this isn't a color pipeline issue at all.  I have a fully callorbrated system and the color is fine in other programs such as AVID and Resolve.  Unfortunately the client requires I work in Adobe Premiere.

Has anybody figured this out or has tried Premiere Pro 2024 yet.  I really don't want to install that version of the application on my workstation at the moment due to it being unvarified as a stable version of the software yet.

Participating Frequently
March 26, 2024

No, I was never able to solve the issue either and I tried everything that I could think of...
But luckily for me when I upgraded my graphics card from 2070s to 4080 the issue went away!

Before the gpu upgrade I had also upgraded my every other pc componenct expect the gpu and the issue was still there. The issue only went away after the gpu upgrade to 4080. Also before the gpu upgrade I tried doing a fresh windows 10 install as well as fresh windows 11 install, neither woked for me.

So I think the issue is definetly connected between NVDIA and Adobe! 

Sorry dude, I feel your trouble! The only solution that worked for me was upgrading the gpu lol.
Good luck at resolving the issue! (or just use resolve :D)

R Neil Haugen
Legend
November 2, 2022

Have you set either your camera, your monitor's settings or the Nvidia control panel settings to assume all Rec.709 is full range rather than limited? Which is wrong, but so confusing a lot of people do.

 

And the IPB Light is the file compression setting, not the codec. Are you using a C-log form? That would be useful data.

 

As ... all Rec.709 video is set by standards to be encoded to 'limited' range code values, unless it's the full RGB 4:4:4:4 12 bit stuff. Which is not a common camera setup. So the vast majority of cameras record their Rec.709 as YUV (technically Y/Cb-Cr) files.

 

But there are a few cameras that allow users to set 'full' range on shooting Rec.709 even though they only produce YUV media. Which is simply wrong. It doesn't give you one iota more dynamic range, as that only controls how the data is encoded to the file, not the range of date recorded.

 

In a properly setup system, YUV Rec.709 media is displayed at 0-255 even though encoded 16-235. And RGB media is also displayed at 0-255 even though encoded as 0-255. So it works perfectly as long as the standards are followed all the way through from camera to monitor.

 

Next ... Premiere is set to follow the standards rather tightly. NO camera has an accurate screen, not even the Red, Arri, & Sony rigs above $70,000. On-set, they'll have an expensive and hignly calibrated monitor to check image values, not the camera screen. So do not rely on your camera's screen image as "correct" for anything.

 

Which is why most users and ALL Mac users should set the preferences option for Display Color Management to 'on'. And well ... both calibrate and profile your monitors, but it seems rare enough anyone calibrates the monitor these days.

 

Neil

Everyone's mileage always varies ...
Participating Frequently
November 2, 2022

Hi Neil,

 

Thank you for your response.

 

I appreciate all of your comments regarding the project settings and the footage itself, but this is definitely not the cause of my problem.

 

I took the exact same project file and footage, loaded it on my laptop using CUDA GPU Acceleration, and even connected that laptop to the same computer monitor. When I do this, the issue completely disappears.

 

This leads me to believe the problem is computer-specific, but I have no idea what could be causing it.

 

I did try your suggestion of using the NVIDIA Control Panel to adjust the color range from 16-235 to 0-255, with no effect.

 

In other words, I'm at a loss here!

Participating Frequently
March 9, 2023

I've tried absolutely everything you can imagine. Wasted days of my life trying to fix this problem. Adjusted every single setting, including black level settings. No solution, and nobody at Adobe seems to care.


Yeah I can see that this is very frustrating since for example lumetri color works much more slower than with the GPU acceleration turned on.