A few days ago, Netflix posted somewhat embarrassing “educational” video “The Benefits of Color Management”

https://www.youtube.com/watch?app=desktop&v=vdmFjFoE2YA&fbclid=IwAR0g2eg1Z3B8LiBfgdWi24M-A3Nlp67bZYy2zyQY7uwSgyj644sLZaog2HU&ab_channel=NewDigitalBacklotBrandAccount

In this video Netflix says they “define Color Management”, literally! (sarcasm)

I think there is already a lot of confusion in this space as it stands. And, for a large, well-resourced organisation, to come out and make blatantly incorrect “educational” presentation is an insult to the injury.

For those that are confused: in this video they present “Colour Managed” and “Non-colour Managed” workflows. So far so good. But the next minute they go to explain that the “Colour Managed” workflows are inherently “Scene-Referred” while the “Non-colour Managed” workflows are somehow “Display-Referred” and should be avoided. The presentation goes downhill from there.

I guess it may come as a surprise to Netflix that ALL of their films have, in fact, been produced using Display-Referred workflows – the exact opposite to what they present in their “educational” video. Display-Referred workflows are the basis of pretty much every single production these days.

If well-resourced companies, like Netflix, pump out this sort of misinformation and confusion, what we, as cinematographers, colour scientists and colourists can do to about this general lack of understanding?

Shame their channel is followed by 3.89K subscribers, it attracted 2,517 views so far, and comments are “conveniently” disabled.

I’m taking the first step: I’m calling it out.

Any other suggestions?

Ø  Pawel has already flagged this in other threads online and we are viewing the feedback. 

Thanks, Michael. Good to hear. I wasn’t sure if my (and others’) feedback on Facebook was followed through.

I think it is extremely important that everyone is on the same page and we communicate with consistent language and terms that mean the same to everyone.

Let me know if I can help with anything.

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel

Hi Charles,

Thank you for taking time to provide explanations. I think it is great that Netflix is advocating ACES. But this is not where the incorrectness lies.

Ø  A colour managed workflow (like the one that Netflix is using) is inherently scene referred.

No. The fact that they are using ACES workflow or any other Colour-Managed Workflow doesn’t make it Scene-Referred. The critical distinction that they missed here is the camera IDT (from sensor-specific colour space to AWG, RedWideGamutRGB or SGammut3, etc…) that eventually brings us into ACES with a fixed transform is not Scene-Referred. This IDT is not Scene-Referred and therefore nothing downstream is (with one exception, addressed below). This is because it doesn’t Reference the Scene. It references a different Scene that camera maker “canned” in their lab as their “Colour Science” for particular camera model. In order to be corrected for the actual Scene illumination, it requires Chromatic Adaptation and/or some other transforms downstream. And this process is inherently Display-Referred (or Output-Referred in general) because you are working in Display Colour space in order to do so.

Almost all workflows in Cinematography/Video are Display Referred and this doesn’t mean that they are or aren’t Colour-Managed, as incorrectly stated by Netflix.

Ø  I see where the confusion might be for you... Because for a lot of people colour management also means that you can convert from one colour space to another. And this is right in essence... For example, you grade in P3 and use a LUT convert to BT1886 (rec709). This in essence is colour managed. But, it's obviously not scene referred colour managed. Which ultimately give you better results and this is what Netflix is trying to explain. 

No, this is not where the incorrectness is. Netflix stated that Colour-Managed workflow is Scene-Referred and that Non-Colour-Managed workflow is Display-Referred. This is incorrect.

The ACES workflow that Netflix presented is Display-Referred workflow and it is Colour-Managed because it does assure consistent colours even if source material is coming from variety of cameras. There is nothing wrong with this workflow and this is how most movies are made.

In distinction to that workflow, Scene-Referred workflows assure Scene colorimetry to look the same across different Scenes and lighting conditions. Whether you shot a scene using tungsten lighting, LED, or natural sunlight, or next to a purple wall, the colours will be consistent across those shots in terms of colour reproduction. The reason they will be consistent is not because they went through Chromatic Adaptation process using your Display in a Display-Referred workflow, but because they didn’t need to. Camera Scene-Referred IDT already assure those colours to be consistent across different Scene illumination.                                                                                                                                                                                                                       

Scene-Referred workflows are much more common in still photography. Capture One, Photoshop, RawTherapee – all allow Scene-Referred workflows. They do so by allowing custom, Scene-Referred camera IDT that was created at the Scene, to be used instead of the “canned” camera IDT provided by the camera maker that was captured in a different Scene and forcing you to use Chromatic Adaptation or other means to make the look across the scenes with different lighting consistent. ACES workflow doesn’t address this colour consistency across Scenes with varied lighting conditions.

Most cinema cameras do not allow for Scene-Referred workflows. This is because their IDT is fixed and cannot be made Scene-Referred (specific to scene illumination). The workflow requires Chromatic Adaptation (setting your CCT and/or Tint), colour balance or other transforms in Display (or Output) space, hence they are all Display-Referred workflows.

There is one “exception”. Davinci Resolve does provide a “semi” Display-Referred workflow for cameras that do not support Scene-Referred IDT.

It allows you to create a Scene-Referred transform downstream of the IDT. This is not the same as using Scene-Referred IDT (and can result in unwanted colour “twists” and out of gamut values) but, at least, if used to bring different Scene illuminations into common look, for all intents and purposes, it would count as Scene-Referred workflow.

I quite like the explanation given by Bram Desmet on Facebook thread:

“ …I've seen from some people promoting concepts of 'scene referred' color grading and mastering. The moment you are making a decision based on how things look on a display you are participating in display referred decision making imo and while that may seem obvious to you or I it is a point I've had people argue with me. "No, this is scene referred grading." Me: cool, so you aren't looking at a display when making your decisions? "Yes, we are." Me: so you are referencing a display, but not working display referred...weird…”

Look, I’m glad that Netflix is advocating ACES workflow. It is good workflow. But, let’s call it what it is: ACES workflow. Why use some other term that means something completely different?

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel

Hi Charles,

Thanks for your thoughts. See my comments below:

Ø  Thus the fact that your are not « locking things in » when using ACES (and could technically regrade at any point if archiving is done correctly) means that the workflow is retaining scene referred data. 

I think it is extremely important to use accurate and correct terms in professional environments.

I’m all for ACES (or any other common colour space). ACES workflow works very well in both: Scene-Referred and Display-Referred workflows. But, again, ACES workflow doesn’t actually assure consistent look despite variations in scene illumination. That’s what either Scene or Display-Referred colour workflows do. Scene-Referred workflow is inherently upstream of ACES. Display-Referred workflow is usually done within ACES. Hence, I prefer using Output-Referred term.

But, for all intents and purposes, Netflix was trying to explain that their managed colour workflow (which is in reality Display-Referred, but they called it incorrectly Scene-Referred) does not rely on having properly calibrated monitors for the process to produce consistent results. That’s incorrect. I can give you black-and-white monitor and a colour blind operator and good luck getting the colours consistent or correct through that process. Why? Because it is inherently Display-Referred. It is a “stab in the dark”, an approximation at matching the colours by looking at the monitor display. It is not consistent process and it doesn’t actually assure accurate or consistent colours. It depends on accuracy of Displays, people looking at those Displays and how far the actual scene illumination was from the reference illumination of the camera IDT.

Scene-Referred workflow is different. It assures colour consistency and accuracy by not having to reply upon calibrated Display or human interpretation of what they see on those displays. You can use it with black and white display throughout the entire pipeline (not that you should). It ensures the most consistent colour reproduction irrespective of scene variations in illumination. It assures accurate colours whether you used LED, tungsten, HID or natural lighting. It assures consistency and accuracy the moment footage is handed over by cameraman to the DIT. It assures colour accuracy and gamut irrespective of Display limitations. The only role of the colourist is to apply creative colour grade.

Therefore there is substantial difference and consequence between those two distinct workflows.

Ø  But, as a engineer working in VFX, scene referred simply means that we can retain the correct data for a bunch manipulation and math to operate in a natural way.

We need consistent terms, not just among colourists, but across entire production team.

Just because Scene-Referred workflow can get results that, in most cases, are almost as good as Scene-Referred, doesn’t make it Scene-Referred. Far from it.

Unlike Display-Referred workflows, Scene-Referred workflows do not rely upon display technology to be accurate. In fact you can have black-and-white monitor or no monitor at all to assure colour consistency and accuracy. Scene-Referred workflows would almost always deliver more consistent results. There are exceptions, of course. You would not use Scene-Referred workflows for night-time scenic shots, or under sodium lights, or some other extreme lighting conditions. These are best handled through Display-Referred workflows to look “good and natural”.

The reason Scene-Referred workflow will almost always deliver more consistent results is because it doesn’t depend on calibrated monitors, individual variations in perception of colours and multiple transforms that often cause colour “twists”, colour discontinuities or out-of-gamut clipping.

Ø  But, if we are talking math and physics the data is the back end is scene referred (in that sense) and thus retains all the pure data from the scene you shot (without the grade of course).

Not exactly. Two wrongs make it right. Having “canned” (non-Scene-Referred) camera IDT transform and then another transform to “undo” the colour mapping to apply chromatic adaptation and/or correction back to the actual Scene is not always lossless, consistent or accurate. These processes are not equivalent. But, that’s not to say one is “colour-managed” and one is “non-colour-managed” as incorrectly stated by Netflix. They are both colour managed, just managed very differently.  

Ø  . But, I feel this « debate » is purely semantics.

I disagree. I disagree because it creates a lot of confusion.

It creates confusion as to who is responsible to deliver colour corrected images: the cinematographer or the colourist?

It creates confusion as to whether or not one needs colour calibrated displays to ensure colour consistency throughout production pipelines.

It creates confusion as to the camera’s capability or lack therof. To my knowledge, my company’s camera, the 9x7, is the only cinema camera currently available that offers proper Display-Referred workflow (in addition to “traditional” Display-Referred workflows). Does it mean it is the only camera that Netflix is going to accept on their productions? Who knows? But somehow I do not think this is what Netflix meant. Again, more confusion.

As cinematographers and professionals we need to use correct terms to describe concepts, processes and specifications. It is not about “semantics”. It is the basis of effective communication in any profession: medical, engineering, legal or scientific. Why not cinematography?

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel

Hi Mike,

Thanks for the corrections! Glad someone is awake. J Yes, my mistake.

Ø  if so, are you saying that you provide a scene-referred IDT to your customers ? Free ? charge ? Is that an industry first for cine cams ?

When using the 9x7, Scene-Referred IDT can be created on set by the cinematographer. It is a choice and you can easily throw away multi-illuminant reference IDT that is supplied with the camera in favour of that Scene-Referred IDT. We also supply workflow software (for Linux and Windows) that supports whatever workflow you chose. And, if you change your mind in post, you can easily switch back to Display-Referred workflow on clip-by-clip basis. It is a flexible choice and yes, it is free. J

There are “lower-end” stills/video cameras that that, with a little bit of “gymnastics” allow for Scene-Referred workflow, but none of the “big names” that I’m aware of. One prominent still picture camera that supports Scene-Referred workflows is Phase One + Capture One workflow software. In terms of actually supporting Scene-Referred workflow on set, yes, I believe the 9x7 is the first one.

Ø  Can you share examples (using footage shot w/ your cam) how a true scene-referred workflow and pipeline can provide better and more consistent results than a display-referred workflow in scenes that were shot under different lightning conditions ?

Here are two examples of vastly different illuminations (I have included spectral data of each illuminant in “light” folder).

Please note that, whilst CCT was set in the metadata to the actual values measured with spectrometer, it is actually irrelevant as long as it is set to the same value when Scene-Referred IDT is created and viewed. The actual CCT value is irrelevant because it is taken care of by the IDT, not chromatic adaptation.

1.   Tungsten

https://drive.google.com/drive/folders/1BxnjhFS8l5V6M5tV0wk3-2UlfQLOMqf5?usp=sharing

2.   Daylight

https://drive.google.com/drive/folders/1B7rCcRx4ZcOEh-PgQzl_fERBKunTyd4W?usp=sharing

These colour profiles were custom created for Scene-specific illumination on set. And, they can be easily created using uncalibrated monitor, even black-and-white monitor, because they are completely independent of any ODT.

I am intending to make a better illustration by showing how Display-Referred workflow with “canned” IDT can produce less accurate colours in certain situations due to colour “twists” or out-of-gamut values. It is coming. We are not as well-resourced as Netflix J

Some excellent points, Brett.

You are absolutely right. If cinematographer’s intent is to create distinctive look through his/her lens choices or creative filters, Scene-Referred workflow is not going to be suitable.

However, if cinematographer’s intent is to create consistent colours irrespective of scene illumination, irrespective of different lens looks, or irrespective of different cameras, then Scene-Referred workflow will most likely be a better choice. Baltars will look indistinguishable from Zeiss (as far as colour is concerned). LED will look indistinguishable from daylight or HMI.

As you rightly pointed out, it’s not the case of “one fits all” or telling filmmakers that one is better than the other. It is the case of identifying and therefore naming those processes correctly, so that everyone is on the same page. And this is also to help make informed decisions as to which workflow better suits the filmmaker’s intent.

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel

Hi Phil,

Thanks for the post, but you seem to confuse what IPP2 Creative Cube is and what it does. It has nothing to do with Scene-Referred workflow.

An ability to apply custom look in camera’s display pipeline is not the same as Scene-Referred workflow. Far from it.

The 9x7 also offers a Creative Transform, similar to the Creative LUT implemented by RED. But, this is completely different, serves different purpose and it is a “trivial” compared to complexities of Display-Referred workflow as a function of the camera.

Creative Cube is an Output Transform, not an Input Transform. It works downstream of RWG/Log3G10 Input Transform, which is always not-Scene-Referred. The reason it is not Scene-Referred is because it doesn’t depend on the actual Scene. It is “canned” and “baked-in”. You can’t change it depending on the Scene.

By RED’s admission, the Creative Cube is an Output LUT, which will limit both, the Dynamic Range and colour space. This is explained by RED very clearly:

The Creative LUT with IPP2 workflow doesn’t assure consistent colorimetry across different scene illuminations and it cannot be reasonably obtained without referencing a display (with its limitations and imperfections). If you created Creative LUT on particular monitor (and unable to observe out of gamut mapping that is outside that monitor’s gamut), clearly this is not going to be Scene-Referred. Creative LUT is just that, a creative LUT.

However, as I mentioned earlier, it is possible to have a “poor man’s” Display-Referred workflow with any camera using “Color Match” function in Davinci Resolve. Compared to a “proper” Display-Referred workflow, it uses the non-Scene-Referred, “backed-in” IDT and then applies a corrective transform downstream from that. The benefit of “Color Match” function over IPP2 Creative LUT is that it doesn’t depend on the actual viewing device to apply the transform. You can do it on a black and white or uncalibrated monitor and still achieve consistent results. The limitation, however, remains the same: it can create unwanted colour “twists”, reduced dynamic range, colour discontinuity and out-of-gamut values, which “proper” Scene-Referred IDT doesn’t suffer from. In short “Two wrongs, don’t make it right”. The “baked-in” IDT that brings camera specific gamut into RWG must be corrected and that correction will be inevitably lossy depending on how much the actual Scene illumination differs from the one that is “baked-in” in the non-Scene-Referred IDT provided by the camera maker.

Scene-Referred workflow, which uses proper Scene-Referred IDT will almost always produce higher dynamic range, wider gamut and more accurate colours than any Display-Referred workflow that is based on non-Scene-Referred IDT and downstream correction.

And this is why Scene-Referred workflows are such a big deal and correct understanding of forces at play is important.

The comments below are off-topic but, I felt, needed to be addressed.

Ø  I like RWG due to the cameras actually being able to capture insane saturation way out there that we can utilize, which has small benefits in regards to HDR grading when it comes to colors we as humans can see.  

This is not supported by my measurements or experience.

Starting from RED Dragon, which had terrible (almost unusable) reproduction of blue colours, which were reproduced as “dirty” magenta-grey. This was never fixed by RED and my understanding is that the problem was compound of poor CFA/sensor design, badly matched OLPF and inaccurate IDT.

This was largely corrected in Monstro, but still not in the same “league” as some of the best cinema cameras offer.

RED Monstro also suffers from colour “twists”, discontinuities and clipped gamut using “canned” Display-Referred IDT and IPP2 workflow. In particular, the magenta line is heavily twisted around red spectra and saturated greens are significantly clipped compared to, say, ARRI or Sony Venice, just to name a couple of cameras with really good fixed IDTs. An additional LUT downstream of RED’s IPP2 IDT is likely to cause further and significant colour shifts and gamut issues and would be counter-productive to the overall process of colour consistency and accuracy. Essentially: exactly what RED is warning about in their article about Creative LUT IPP2 usage.

Below is an illustration how Monstro reproduces monochromatic colours using RED-supplied IDT under IPP2. You can see very “dirty” magenta line with red colours reproduced as magenta. This is problematic and not easy to correct without affecting other colours. Secondly, you can see significant gamut clipping. The camera is not capable to reproduce even REC 709 saturated cyans or greens.

For comparison, below is the same test with Sony Venice:

You can see almost perfect “magenta line”. You can also see very impressive reproduction of pretty much the entire range of monochromatic colours without “twists” or significant clipping. Kudos to Sony.

Also, remember that RED RWG does not encapsulate all visible colours, unlike CIE XYZ (used in 9x7 IDT), which is wide enough to not only encapsulate all visible colours, but also as a standard working colour space without a need for additional transforms. In particular RWG doesn’t reproduce saturated cyans and greens, which will be clipped, even if the camera sensor could actually reproduce them. This seems to explain why RED Monstro is unable to reproduce those colours: not even the Output colour space (RWG) can accommodate them without clipping.

In summary, RED cameras are not capable of reproducing deep saturated colours using RWG IPP2 because even the output colour space has limited range it can possibly reproduce.

Hope it helps.

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel

Hi Phil,

My point about IPP2 Creative Cube were that its function doesn’t lend itself to Scene-Referred workflows and it doesn’t achieve any of Scene-Referred workflow advantages. It is applied downstream of non-Scene-Referred and “backed-in” IDT. It is a “red herring” to the discussion we are having.

Ø  Also I believe Graeme explained and demonstrated the impact of correctly adjusting the ISO so the data isn't getting clipped to eliminate the distortion, which is occurring due to RED's gamut mapping attempting to show a pushed high gamut color.  Your spectrum was exposed well, but you pushed it to ISO 1600 which pushes it to the edge of the Rec.709 Output Transform.  Even with that said, it's really nice to craft your own transforms or even drag things through ACES.

Yes, Graeme did demonstrate that changing ISO and colour temperature to default 5600K eliminate colour “twists” and gamut clipping – an advice, which I consciously ignored. J

The reason I ignored it is because the purpose of the test was to see how colour inaccuracies and gamut clipping occur under chromatic adaptation (or colour correction in general), which is a necessity when working in Display-Referred workflows. Sony Venice, ARRI LF and RED Monstro were tested under exactly the same setup and settings. Only RED Monstro showed extensive colour “twists” and gamut clipping (both extremely difficult to correct). The purpose of the test was to learn from it, not to change test parameters in order to suit the narrative.

What I learned from the test was that:

1.   Monochromatic light test is a very-well conceived test because, in theory, all the colours should be invariant to colour adaptation. Thus, it allows to observe the limitations in colour reproduction of each camera.

2.   Colour adaptation (a necessity in Display-Referred workflows) can cause significant reduction of colour gamut, metamerism, and colour inconsistencies

3.   When using “default” CCT (which I presume is the one under which the IDT was created) the results were always better and got progressively worse as deviating from it. This was the case with all cameras under test. But, the degree to which it got worse varied.

4.   RED Monstro exhibited extensive colour shifts (“twists”) and gamut clipping during chromatic adaptation, which indicates limitations in either sensor or IDT or both

5.   Sony Venice showed outstanding accuracy and invariance under chromatic adaptation. It also showed the largest gamut.

6.   Scene-Referred IDT doesn’t suffer from any of the above problems because it doesn’t require chromatic adaptation or colour correction downstream.

The feedback that I got from RED were:

1.   “Change the test parameters to avoid the problem” (i.e. change CCT)

2.   “This is caused by excessive UV” (as in case of RED Dragon and Helium sensors)

3.   “These colours do not exist in real-life scenarios”

4.   Silence the critics

This is not to bag RED. It is what it is. I used and owned most of their cameras since RED One and they have a lot of compelling features that other cameras do not have.

This is to point out that many of those issues, like colour twists and gamut clipping can be quite severe under chromatic adaptation and that they can be avoided altogether or minimised by using Scene-Referred IDT instead of “baked-in” IDT created under ideal lighting source.

And, most importantly, it is to point out the differences between Scene-Referred and Display-Referred workflows.

Hi Charles,

Many thanks for your feedback and it is great to hear from vice from different perspective.

Indeed, Netflix’s push for ACES workflow is good and makes things streamlined and consistent. I’m personally all for it.

Ø  The main masters you'd deliver to Netflix would be display referred and there you are spot on. But, Netflix also pushes to get what they call a NAM (non graded archival master) and also get a GAM (graded archival masters). The NAM is technically 100% scene referred (from the original scene and the VFX) but the GAM is not... It's like a linear version of your grade. So it retains a lot of info but not all.

I like NAM and GAM terminology because they are descriptive and clear. In my mind there are two ways to arrive at NAM:

1.   Scene Referred

This is done either through straight Scene-Referred camera IDT as I described earlier or (the “poor man’s version”) by using “backed-in camera IDT and corrective Scene-referred transform downstream (for example through the “Color Match” function in Resolve). Both would be technically “Scene-Referred” except the second workflow may be limiting the gamut and/or introducing unwanted colour “twists” depending on how much the “backed-in” IDT reference lighting differs from the actual scene lighting. As I demonstrated with RED Monstro, it can be a lot.

2.   Output Referred

This is most common workflow where colour correction (before grade or look are applied) happens by referencing display. However, I personally call it “Output-Referred” because it usually happens in space that is much wider than the actual display, but the transform to P3 or BT1886 or REC 2020 (ODT), etc. is always fixed. So, it may not have to be display-specific, but it is always created based on evaluation of the output.

All of the above are obviously colour-managed, just managed very differently.

What is characteristic about Scene-Referred workflows (and what really defines them) is that it requires capture of spectral data at the scene. There are different ways and techniques to do so, but this is one critical ingredient that is needed to go from camera-specific colour space to working colour space (NAM). It also puts the burden of colour correction on the cinematographer rather than the colourist. The look is ultimately applied downstream by the colourist. Scene-Referred workflow also doesn’t require chromatic adaptation (setting colour temperature).

Hope it makes sense.

Maybe it is a good time to bring this discussion into IMAGO Technical Committee (ITC), which I’m a full member of, and get a broader consensus for consistent terminology.

I look forward to input from anyone. How do we make those distinctions clearer?

Kind Regards,

Pawel Achtel ACS B.Eng.(Hons) M.Sc.

“Sharp to the Edge”

ACHTEL PTY LIMITED, ABN 52 134 895 417

Website: www.achtel.com

Mobile: 040 747 2747 (overseas: +61 4 0747 2747)

Mail: PO BOX 557, Rockdale, NSW 2216, Australia

Email: Pawel.Achtel@...

Facebook: facebook.com/PawelAchtel

Twitter: twitter.com/PawelAchtel

Skype: Pawel.Achtel