Transfer curve/function - expression that describes the nonlinearity of values. So first what I mean with some terms in the following text: I’ll try to put down a few thoughts as precisely worded as I can because I think a lot of confusion stems from interchanged use of different concepts and terms.
#Autodesk flame 2021.2 mp4#
More often than not people deliver MP4 there which renders tags harder to deal with. Online I’m not sure if services like YouTube respect these tags. mov files at all and I think for sRGB images to look correct, you have to tag them as Rec 709 / Gamma 2.4. That said I’m not sure what to make of that really. The changes toĪfter Effects will always render 1-1-1 but internally you can manually work with its CMS.
That is a Rec 709 / Gamma 2.2 will render brighter than a Rec 709 / Gamna 2.6 image from Resolve. They will internally convert them to 1-1-1 but at the same time change the look of the picture. Premiere reads certain gamma tags but doesn’t write them correctly. Nothing will really show correctly from my experience.ĭealing with Adobe their apps are all over the place. If you take QuickTime, 1-1-1 tagged files gets washed out and 1-2-1 with gamma 2.4 gets a a super odd gamma curve. Very I few environments treat the tags / footage correctly. Sadly “the old ways” of the tags being 1-1-1 is by far the safest at the moment. In an optimal world everything would be tagged and shown correctly. Thanks! Need to have everyone using Flame be aware of this. As a workaround it works, but it isn't correct whichever way I look at it.Ĭlick to expand.This explains why a project we just received was tagged 1-2-1.
#Autodesk flame 2021.2 Patch#
Forcing wrong tagging is a workaround, a patch on incorrect handling, not correct tagging. If Apple can't pull their shit together in QT player it doesn't mean tagging is incorrect, QT player itself is handling the footage incorrectly. But it is not unknown, it is rec709, I can't see any logic behind "unknown" being correct tagging and rec709 being incorrect. Tagging 1-2-1 on the other hand means that transfer function is "unknown". Tagging 1-1-1 means that data encoded is rec709 (primaries, transfer function and matrix to Y'CbCr are according to rec709). To me, this interprets as "values of pixels in file are encoded as specified by value fields in this atom", it doesn't say those tags define the EOTF needed to view the data as-is. The common representation is the CIE XYZ tristimulus values (defined in Publication CIE No. The 'colr' extension is used to map the numerical values of pixels in the file to a common representation of color in which images can be correctly compared, combined, and displayed. This keeps the file as 1-1-1.įrom Quicktime container documentation I read: At our facility our current workaround is to simply uncheck the button when doing exports.
I'm creating this thread to make people aware that this is now a potential issue. The ColorSync Compatibility button is automatically turned ON when creating a flame export preset. This has lead to our exports from Flame being flagged as 1-2-1 again. They decided to implement their own "fix". As Autodesk released Flame 2021.2.1 (patch notes here: ) This worked well when going ProRes 444 to a Flame, doing online / finishing work and then doing master exports to ProRes 444. My solution for this have been to work in Rec 709 (scene) as it flags my quicktimes as 1-1-1. As you all are probably aware, there's been quite a lot of discussions the past year regarding NCLC flagging of Quicktime files, and Apple ColorSync, etc.
0 kommentar(er)
