3 ms·
"What is color space 1? And what are primaries?" Be thankful you have the ability to set the color space and primaries within the command. Back in the days of
by dylan604 4y ago
"What is color space 1? And what are primaries?"
Be thankful you have the ability to set the color space and primaries within the command. Back in the days of dinosaurs (mid-2000s to 2010ish) and when HD was just an infant sucking its thumb and before Apple updated the MOV container to hold these values, it was even more annoying to get colors correct. The big issue then was gamma settings. Windows used one value and Macs used another, and there were always issues getting them to look the same on either platform.
There was also the bad ol' days of when iTunes would reject your MOVs for not having these primaries and color space values in your files created by Final Cut Pro. It turns out, that within the silos of Apple, they do no communicate back and forth with each other. So the iTunes team read the white paper on the MOV file format and wrote all of their automation expecting these values to be present. Unfortunately, the team writing FCP had not updated their exporter to use these new features of the MOV. So iTunes rejected the files from not being written by an official Apple product!?!? something about left hand ands right hands can be written here. To the point, we had to have a 3rd party app developed to take the files from FCP and update them to be compliant with iTunes.
I still have scars from the shrapnel from those "early" days. If only articles like this were made at the beginning of the features rather than 15+ years after the fact and can be written after doing a google search. So hopefully future me types can find this rather than the hell of needing the feature and having to get the feature developed, and then just try it and hope for the best.
- aikinai 4y agoThis is a shot in the dark, but you seem very knowledgeable about color, video formats, and the Apple ecosystem so I thought you might have some insight into this issue I'm facing recently. I'm trying to process HLG3 video files from my Sony camera and have spent far too many hours trying to figure out how different settings affect QuickTime, ffmpeg, and Davinci Resolve, among others. The biggest thing I can't figure out right now is why Davinci Resolve renders the HLG video brighter than QuickTime. If I enable 10-bit precision and Mac display color profiles for the Davinci viewer, it does seem to tap into the HDR capabilities on my MacBook and allow for full dynamic range that looks similar to QuickTime's render. However, everything is brighter, especially highlights. Do you know of any good references to better understand how HDR works on a modern Mac?
- dylan604 4y agoI got out of this particular job type just before HDR became widespread as a consumer product. Chasing color accuracy is one of the top 3 things I hate about computing only proceeded by choosing a font, and printing. I spent time in a color correction facility where we had to calibrate Sony studio reference CRTs, LCDs (or other flat panel tech), Christie projectors, and desktop monitors. I absolutely hate Hate HATE it. The external monitors being fed by a Decklink card would have to be calibrated using a dedicated instrument for each type of screen. The desktop screens would have to be calibrated by another device. At the end of the day, the client was always advised to base color decisions on the calibrated display monitors and NOT the desktop monitors. Luckily, all of this was handled by the video engineering department, and I only know as much about it from what I asked. Thankfully, it was never my responsibility! So, I guess I'm saying good luck with that! ;-) Trying to dial in all of the different display devices to match is a journey into madness. There was a time when commercial content was only ever critically evaluated on broadcast quality monitors. As web content became larger, people were less concerned about the broadcast safe and pushed values to no longer be broadcast safe so that they looked good on iPhones. All of that to say, you're not alone in your pain. Also, are you working a PC or Mac? If you're on a PC, I have zero experience with this on that platform. Fun fact (using air quotes), there was a bug in QTPlayer so that the first file you opened would display with an incorrect gamma value. When doing critical color decisions with that player, we would open some random file first, then open up the rest of the files we were interested in. Don't know if that bug is still around or not. If you're facing brightness differences between apps, my first assumption would be gamma differences between apps.
- aikinai 4y agoOh okay, thanks for the response though! Yeah, this whole space is such a mess and I'm not even trying to do something at a professional level (which is why I'm using my Mac screen and not a reference monitor). There are a lot of blog posts and YouTube videos about matching Davinci, QuickTime, YouTube, etc. but so far I've only found answers for SDR. Native Mac screens have a true HDR mode built in you can see clearly when you play any HDR video in Photos, QuickTime, etc. The normal UI is capped to, I believe, 500 nits, and then HDR video unlocks up to 1600 nits. I can see my settings in Resolve are unlocking the higher brightness, so it should be triggering the MacOS HDR pipeline, but it's too bright, so I agree the gamma must be different somehow.
- giantrobot 4y ago> It turns out, that within the silos of Apple, they do no communicate back and forth with each other. So the iTunes team read the white paper on the MOV file format and wrote all of their automation expecting these values to be present. Unfortunately, the team writing FCP had not updated their exporter to use these new features of the MOV. I was somewhat involved in this at Apple at the time! Your description is actually a decent description of the reality on the ground. The following may however have some misremembered details so don't take it as gospel. At the time QuickTime was migrating internally the older MacOS era subsystems to newer ones under the hood. The low level frameworks were private to QuickTime, Apple didn't ship public headers for them. Both iTMS and FCP however did use the private headers to use those frameworks directly. With iTMS they had a bespoke media ingest and export pipeline. They were calling QuickTime's private frameworks but doing their own thing with the raw samples between ingest and export. IIRC they had QuickTime branch/builds of their own because their encoder fleet didn't just jump on the latest OS and QuickTime version. FCP/Compressor were also directly using QuickTime's private frameworks but as I recall shipped their own private copies of some of them. I believe this was due to those revving with the OS rather than QuickTime's package but FCP had to support older OSes. Even QuickTime's behavior wasn't entirely consistent. Videos captured on iPhones had an assumed color space (Rec.709 IIRC) but at the time didn't write the tags into the files. QuickTime had to recognize iPhone originated files and then play them as if they were tagged then tag them if it exported (pass-thru or otherwise) those files. For other untagged input files it assumed tags based on the frame size, SD sizes were assumed to be Rec.601 if they weren't tagged and HD sizes Rec.709 if they were untagged. Of course tagged files didn't need any guessing and got the tagged behavior on playback and export. It's not necessarily that the three teams didn't talk to each other, their schedules were just wildly different cadences. While the QuickTime group was writing all the frameworks being used they were concerned mostly with the low level issues. They were also supporting iLife, iTunes (the app), and QuickTime Player/plugin releases along with a good portion of the group working on iOS as well. FCP and iTMS were just internal customers writing their own stuff using the low level frameworks.
- dylan604 4y agoMaintaining backwards compatibility with FCP makes sense, but the hubris of the iTMS team was also quite funny to me as well. They could have handled this on their end knowing that the Apple ecosystem was fractured regarding QT. They could have built Transporter to be much more tolerant of files created by FCP/Compressor to not be rejected because of these differences in Atoms within the container. Instead, many 3rd party apps had to be built/used by people instead of just handling it internally. I also relate back to their air of superiority from another situation I had with them. Their original specs called for video content originating on film to use IVTC to return the frame rate back to original progressive frames for the obvious reasons. However, they clearly were not familiar with TV/Episodic content that was originally shot on film, but edited at 29.97 with broken cadences, use of 30p graphics, and other content that was true 29.97i. There was a specific F/X series that 2 different providers had their files rejected from the show because of faulty IVTC processing. My company got involved, but iTMS said to send them the unprocessed 29.97 content because they "knew" how to handle it. They didn't, and then it landed in my lap. I processed the files and submitted them where they were approved. There was a request from iTMS to find out how they were made. Very smuggly and with a righteous smile on my face, I got to quote an answer they had provided me previously back to them, "this is a proprietary process developed by our in-house engineers." We got a lot of work because of that. It was examples like this that make me roll my eyes when FAANG types are held in such high regard. They're just humans trying to figure stuff out with people available to them. They might not actually know everything just as us mere mortals, but some of us have unique experiences that allows us to tell the emperor he's not wearing any clothes when the FAANG types issue decrees from up on high that are clearly just not right.