The second meeting of the CLF Spec / Code Review Virtual Working Group will take place on
Wednesday, February 6th, 2019 9am - 10:30am PST (Los Angeles time)
The meeting will be lead by working group Chairman JD Vandenberg.
We will again use GoToMeeting to allow you to connect using your computer, tablet or smartphone, or call-in using any phone.
Instructions for GoToMeeting are below and also on the VWG Document Workspace which also provides relevant background documents for this group.
Please continue to discuss specific topics on the appropriate discussion threads here on ACESCentral. We look forward to your participation!
The ACES Team
Instructions for using GoToMeeting to join an ACES VWG Meeting
All Virtual Working Group Meetings will use GoToMeeting for their meeting calls. Check
ACESCentral for the specific time and date of each VWG’s next meeting.
You may join via computer/smartphone which will allow you to see any presentations or
documents that are shared or use a telephone which will be an audio only experience.
Please note that meetings are recorded and open to the public. By participating you are
agreeing to the ACESCentral Virtual Working Group Participation Guidelines
Audio Only
You can also dial in using your phone.
Dial the closest number to your location and then follow the prompts to enter the access code.
United States: +1 (669) 224-3319
Access Code: 241-798-885
As always, the agenda, call-in information, and any supplemental documents are available on the workspace site. There you will also find a brief summary of meeting #1 decisions with direct links to the relevant conversation threads here on ACESCentral where the discussions were continued after the meeting.
Thank you to all who participated in the second CLF meeting.
Some outcomes:
After much discussion, the option for different number encodings (integer,float) should remain in the specification. [Discussion]
The biggest impediment to implementation/adoption of CLF seems to be the complexity in parsing something that can potentially have a huge number of process nodes in arbitrary order and having to run that efficiently on hardware. It requires savvy GPU acceleration and there is hardware in use where that is not easy to do.
Re: Process Nodes and complexity vs. convenience: Need to determine the basic alphabet of what’s required to manipulate all anticipated LUTs without adding too much complexity so as to be burdensome to implementors. [Discussion]
There could be value to adding a basic log operator in the form of a log with linear form to support the many camera log formats that have a breakpoint between a log and linear segment. [Discussion]
Please continue to discuss these items, but please do so in the relevant discussion threads linked above (or start a new one specific to your question/comment).
The next meeting is planned for Friday, March 8th @9am. Details will be sent out in a new thread for that meeting shortly.
