Premiere Pro CC 2019 still not working with apple P3 Displays (MacBook Pro 2016)

A number of Mac users have reported that after setting their OS monitor option to sRGB (and perhaps Rec.709 ... don't know if that's listed as part of the option) that they've returned to "normal" working. So apparently there is an OS option that helps.

Neil

No Video no audio, just massive errors!

That sounds very different and unrelated to the subject of this thread. How about filing a new thread stating your specific troubles? That way we can try to troubleshoot with you.

Neil

Don't worry about understanding my opinions. I like everyone having different ones ... it means they're thinking independently. My opinion from the above, is it would be good if PrPro gave the user the option to turn off the Bt1886 display transform so some users would be happier.

I do suggest we all worry about understanding the technical details.

I don't know how familiar you are with colorists, and the tremendous effort they spend to get accurate representation of the image on their 'confidence' screen. I've never met a colorist who considered a computer off-the-rack and any 'normal' computer monitor a system even capable of being calibrated to the needed standards. There's a reason for this. (No guarantee anything out of that system will come close to passing the mechanical QC test for b-cast acceptance ... period.)

You note QuickTime is the main video player from Apple. Some things flow directly from this.

First, the Apple OS is not setup to respect both transform aspects of modern Rec709 out of the box. Second, the monitors used on most newer Macs use one of several versions of the P3 wide-gamut color space. Which is way different than the video-sRGB standard for b-cast work. Realistically, to get a P3 monitor showing video sRGB correctly takes one heck of a lot of calibration and a transform LUT. But wait ... there's more: each different size Mac P3 monitor will need a different calibration transform to be accurate.

Now, we get to QuickTime player ... which is a notoriously color-stuupid app. It doesn't properly apply the flags/tags of any media coming into that player. If that is the standard you want say Adobe's PrPro to apply, well ... it will be wrong on the vast majority of systems and users out there.

Next, to the relationship with FCPx ... which is built in-house to run on an OS that doesn't respect the full Rec709 "modern" version but is juiced to run great with FCPx ... and naturally, with other apps like QuickTime that don't apply full transforms. Yea, that and QuickTime are both designed with the same shortcoming, naturally ... they play together well.

It seems to come as a shock to many Apple users, but that company's rigs are what, a bit less than 10% of the total computer/device user base? And yet many Apple users assume that what would work best on their rigs (without bothering to go through any tech consideration or calibration/setup) should be the main operational consideration for any other app out there.

That's not particularly a rational consideration ... to plan to build around a minute portion of the user-base and make everyone else work around a poorly designed setup that is based on wrong assumptions at the start.

As I noted in an earlier post, I do advocate giving users the switch to turn off the Bt1886 display transform part of the Rec 709 professional standard. I normally tend to hold with giving wider choices ... something of course, Apple itself never does.

To me, anyone assuming that only Apple users will ever view their media is well ... not wanting a wide adoption of their content. But that's my opinion and they're welcome to theirs.

Technically, turning off the display transform renders media rather less-than-pro quality. As it clearly chooses to violate the full pro standard that's the only one we've got.

So feel free to request the off-switch for Bt1886 display transform. I'll vote right along with you for that to be added. And of course, I know any media produced on such a setup machine will look poorly on my setup ... and many others out there properly calibrated for the full Rec709 standard.

But please ... understand the technical side of what you ask for. Not opinions, the math/physics of the issue.

Neil

You don't understand what the reality of video files and computers apps and players is.

I've a long post in the thread on color management near the end that explains the system from computer, OS, video card, monitor,  to apps and the files that create or read/play.

Your example shows exactly what happens when using apps that pay attention to the file header tags ... and using apps that don't.

All the ones that don't show properly in your example are noted for NOT paying attention to the tags for color space in the files they display.

PrPro has no control over those apps, period. Neither does any other app.

Now ... if as I mentioned in that other thread, IF you carefully go through your OS, video card, and monitor settings, you can essentially create a system where even non-color aware apps look sorta close. You still can't make them identical because the apps are not designed to conform to any standard.

Neil

What's the point of that? if it converts the rec709 display we see in Premiere to the display, but it's still completely different to the export then how has this addition helped anyone

Also confirming that I am experiencing this issue. On an iMac Pro with the latest Premiere. Display color management is ON however exports to quicktime/vimeo do not come close to matching the gamma/saturation seen in premiere. The display has been calibrated with a Spyder5 Pro, and short of getting a second screen I'm not sure what to do here.