![]() 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. 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. Finally, the definition must end with a semicolon ( ) and it can span several lines.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. In the definition, the arguments can appear, complete with the dollar sign preceding it. The definition itself can be any valid expression, except that channel names are not accepted since user-defined expressions are not related to any particular setup. The function name and its definition are separated by a colon ( : ). Function names and arguments are case sensitive, meaning that lowercase and uppercase make a difference.For example, $arg1 is a valid argument name, although $1 and arg3 are not. The first character of an argument must be a dollar sign ( $ ), the second character must be a letter, and subsequent characters can only contain letters or numbers.For example, sin100 is a valid function name, although 100sin is not. The first character of a function name must be a letter, and subsequent characters can only contain letters or numbers.The following rules apply for function and argument names: You start a function by its name, followed by an opening parenthesis, the arguments for the function separated by commas, and finally a closing parenthesis. A function is composed of a function name, with the list of arguments, and the expression that forms its definition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |