14.0.1 max bit depth BUG

Matthias,

The vast majority of users aren't having this problem. Which actually makes it more important that you post a detailed description of your issue over on their UserVoice system.

THAT system goes directly to the engineers, and every post is read by at least one engineer. I got to talk with one of the engineers who reads those at Adobe MAX last November, and his biggest complaint was not getting enough posts with enough detail for him to get a good handle on what's going on. "X is broken, fix it!" ... doesn't tell him squat if none of his systems can replicate some sort of problem.

So ... include details of your system, the media involved and whence it came, what storage it lives on, what effects are involved in the sequence, and the steps that you take when this occurs.

That gives them enough data to correlate posts and sort out some of the factors that may be critical in causing this, and ... if needed ... gives them users to contact for additional data or testing a fix/workaround.

Neil

I'm having the excact same issue. Also only on ProRes Files. Any other format like .MXF or .MP4 do not show this problem.

This is just one of many issues i have with the new 2020 Update!

Hi Mike, 

Sorry to hear about this. Is it possible for you to share a download link for the sample ProRes media to test the issue at our end? 

Thanks,

Sumeet

With your rig, and that codec ... I'd leave it off. From all the discussions I've had with the engineers, Robbie & Pat ... and all the testing we've done ... I can't find any issues. Which isn't to say that there might not be an issue if X times Y is applied to Q over there ... sigh. There's always caveats.

Do be careful not to use any 8-bit effects, so always make sure any color/tonal effect you apply has a 32 bit "lego block" in the listing in the Effects panel.

Max Bit depth does the same thing basically in both Sequence and Export work.

Max Render Quality btw is another ... hmmm ... option. What that does is "up" the math density if there's resizing going on. So ... if you're resizing, and you see jaggies on a diagonal, then definitely use Max Render Q. But ... if you're not resizing, or even if so, and you're not getting jaggies on diagonals ... then MRQ isn't needed either.

Neil

Not getting any difference here, Win10, Nvidia 1060.

Let's see if some others can post their results ... see if this is something on your rig or across some subset of users. Either way, good to know.

For a bit of information ... Max bit depth is a semi-optional setting. IF you have a full GPU like yours ... so something other than "Software Only" is available in the Project Settings dialog for Mercury Acceleration ... and IF like me, everything is getting Lumetri color effect applied ... then the Max Depth option doesn't do anything. All calculations will be at max bit depth anyways.

Premiere's processing chain takes the bit depth of the individual clip on import/ingest ... calculates the clip as effects are used on a sequence ... and then takes the export dialog settings for format/codec chosen and computes the import data into the export data. If all effects that have bit-depth are at 32 bit, Premiere will stay in 32 bit float for the entire processing chain.

So 10/12 bit media coming in, processed as above ... and exported to format/codecs with standards for 10/12 bit media ... will go directly into the bit-depth of the format/codec chosen for output.

Where you need that Max Bit Depth option is:

1. If you do not have a full discrete and recognized GPU. How do you know? If you can set anything other than Software Only in that Project Settings dialog for Mercury Acceleration.
2. If you do not use any color correction on a clip, and are not doing any major re-sizing either. Either color correction or major resizing will set Premiere to sending computations through the GPU ... at the higher bit depth.

What Max Bit Depth normally does ... is when you don't have a full GPU ... it tells the CPU to process the encoding using the higher-bit-depth 32 bit float math all the way through the process. Which is why ... if you have a GPU and it will be used, it's not necessary to have Max Bit Depth selected.

Here's a link to a tutorial I did for MixingLight.com's subscription website ... and this one is free, outside the paywall. I spent hours of time on phone and screen-share and in person with then-color engineer Francis Crossman (who's now Co-Product Manager for Premiere Pro) and many emails forth and back between Francis and colorists Robbie Carman and Patrick Inhofer of MixingLight to both get this ready as a presentation in the Flanders/MixingLight booth at NAB last April and for this tutorial.

How Do You Finish at the Highest Possible Quality?

Neil