# DCI-P3 to rec709

**URL:** <https://forum.logik.tv/t/dci-p3-to-rec709/8897>\
**Category:** Flame Questions\
**Tags:** color-space, colorscience, rec-709, color, color-management\
**Created:** [August 1, 2023, 8:44pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897 "2023-08-01T20:44:05Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 1, 2023, 8:44pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/1 "2023-08-01T20:44:05Z")

</div>

Looking for help from my color science nerds out there. I am working with a feature graded in DCI-P3. I will be doing some additional trailer grading on top of the feature grade. My final deliverables will all be rec709. When using input transform from DCI-P3 to rec709 on the timeline, I get a pretty big color shift (more saturation, darker). However, when I use an input transform that goes from rec709 to rec709 (yes, that’s correct), the image looks identical—no color shift whatsoever. I’m going to go with it for now, but I am pretty confused. I know they have different gammas (2.6 for DCI-P3 and 2.4 for rec709) so I’m not exactly sure why what I did works…anyone know? Should I just keep my mouth shut and not jinx it?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [August 1, 2023, 8:50pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/2 "2023-08-01T20:50:17Z")

</div>

Never done this before but I know that gamma is different and colour primaries are different. I am fairly certain that the white point is D65

> **DCI-P3** has a 25% larger **color gamut** than **sRGB**. **DCI-P3** uses Illuminant **D65** for the **white point**.

You could do a test where you use an intermediary like ACES

Remove gamma 2.6 (make it linear) apply 2.4 gamma

Convert DCI-P3 primaries to ACES then ACES to rec 709

🤔

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 1, 2023, 8:57pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/3 "2023-08-01T20:57:56Z")

</div>

I guess the question is…do I need to? If an input transform of rec to rec “works”?

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [August 1, 2023, 9:35pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/4 "2023-08-01T21:35:55Z")

</div>

Just as an experiment.  
Call it a sanity check because rec to rec makes no sense. I guess that was why you put the question out there. Sorry I have no experience of this particular transform

---

<div class="post-metadata">

**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\
**Post date:** [August 1, 2023, 10:37pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/5 "2023-08-01T22:37:00Z")

</div>

Shouldn’t it look different, though? I think the goal of the conversion is to make it look as close to the same as possible on a calibrated rec709 monitor as it does on a calibrated P3 monitor. Doing so should change what the picture looks like on your artist monitor.

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 1, 2023, 10:47pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/6 "2023-08-01T22:47:19Z")

</div>

Ideally in my current case, they would not look different, as the director is quite attached to the P3 grade and wants the rec deliverables to look the same. My monitor supports both P3 and rec709 but I’m not using an viewing transforms on the media, only input transforms.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [August 1, 2023, 10:55pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/7 "2023-08-01T22:55:51Z")

</div>

Depends how you are doing your colour management.

In theory any footage tagged as P3 will convert to your monitor settings and look correct but turn off your viewing LUTs by selecting bypass and see what is really going on.

With the viewing LUT, yes you would expect them to look the same (ideally) but this can also fool you so I go for bypass as well.

Like I said this isn’t a transform I have done but I dance extensively around LogC, ACES and rec.709

and I always go for a sanity check by using bypass so that I can see the pixels changing and then pull my viewing LUT back up and see them looking identical.

---

<div class="post-metadata">

**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\
**Post date:** [August 1, 2023, 11:03pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/8 "2023-08-01T23:03:53Z")

</div>

Sorry, I meant that in order to have deliverables that look the same on rec709 and p3 external monitors, you will have to generate deliverables that look different out in the OS, as rec709 and p3 primaries and gamma are different. Flame’s color management might try to hide this from you, but I can’t say for sure because I hand-manage everything.

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 1, 2023, 11:09pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/9 "2023-08-01T23:09:03Z")

</div>

I’m bypassing everything which is what I meant when I said I’m not using any viewing transforms, only the input transform, so you can see my confusion with there being no discernable difference.

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 1, 2023, 11:10pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/10 "2023-08-01T23:10:26Z")

</div>

> [@PlaceYourBetts](#):
>
> …Never done this before but I know that gamma is different and colour primaries are different. I am fairly certain that the white point is D65DCI-P3 has a 25% larger color gamut than sRGB . DCI-P3 uses Illuminant D65 for the white point .You could do a test where you use an intermediary like ACESRemove gamma 2.6 (make it linear) apply 2.4 gammaConvert DCI-P3 primaries to ACES then ACES to rec 709

Would you mind walking me through how you’d accomplish this using color management on the timeline so I can test this out?

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [August 1, 2023, 11:22pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/11 "2023-08-01T23:22:48Z")

</div>

![colourTransform](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/b/b8405d3fe7cb1489139d32f38eb865b5366e2dca.png)

Ooops. big mistake. I forgot to change my Tagged Colour Space from P3 to rec 709 (bottom left) ⚠

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 2, 2023, 1:37am UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/12 "2023-08-02T01:37:27Z")

</div>

This results in the obvious gamma shift but nothing beyond that. Still perplexed on the rec to rec but I will use this. Thanks!

---

<div class="post-metadata">

**Author:** ![kyleobley](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@kyleobley](https://forum.logik.tv/u/kyleobley)\
**Post date:** [August 2, 2023, 5:25am UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/13 "2023-08-02T05:25:49Z")

</div>

Perhaps I’m missing something here but to me it sounds like you should be using a **view transform** from source to rec709 as opposed to an input transform as essentially you’re wanting apply said viewing LUT so you don’t see any shift which should be fine as you’re creating your final deliverable so you can bake-in the viewing LUT.

---

<div class="post-metadata">

**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\
**Post date:** [August 2, 2023, 5:30pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/14 "2023-08-02T17:30:28Z")

</div>

A view transform from DCI-P3 (D65 white) to rec709 video also results in no color shift from the DCI-P3 plates so yes, this is what I have been using. I guess I was more curious about some of the unexpected behavior I was experiencing.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [August 2, 2023, 7:32pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/15 "2023-08-02T19:32:52Z")

</div>

I mean there is a small colour shift. Not a huge one. You might not see it if your viewing LUTs are doing their job.

 ![IMG_2675](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/7/7f491c9c3c4f2fcd7cf8dcb451a5e8d19433fab4.jpeg)

That is why I like using the more manual Colour Transform (custom). You can flick certain bits, like the primaries, on or off, to see the shift.

The view transform is much easier and more automatic but on the right hand side of the buttons you can see the transforms it is using.

It is using a different intermediary, XYZ colour and the results when compared to my custom Colour Transform, are similar but not identical.

If I was going to commit to one or the other I would probably trust the Autodesk View Transform a little more. Especially since I was just making up the ACES one.

Best of luck

---

<div class="post-metadata">

**Author:** ![ChrisKasten](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/chriskasten/32/150_2.png) [@ChrisKasten](https://forum.logik.tv/u/ChrisKasten)\
**Post date:** [August 3, 2023, 5:43pm UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/16 "2023-08-03T17:43:40Z")

</div>

> [@krystenr](#):
>
> I guess the question is…do I need to? If an input transform of rec to rec “works”?

If you use rec to rec: There should be no difference, because this input transform does not change anything. Only if Input CS and Working CS are different, a transform is applied.

In my opinion you will always see a difference when you convert DCI-P3 to rec709. Less gamut and a different gamma.  
If you now put a DCI-P3 calibrated monitor next to a rec709 monitor and show the matching footage in the respective color space, then it should “look very similar” but not identical, because one monitor can “only” display rec709 colors and nothing more.

---

<div class="post-metadata">

**Author:** ![omarank](https://avatars.discourse-cdn.com/v4/letter/o/d07c76/32.png) [@omarank](https://forum.logik.tv/u/omarank)\
**Post date:** [April 14, 2024, 8:42am UTC](https://forum.logik.tv/t/dci-p3-to-rec709/8897/17 "2024-04-14T08:42:35Z")

</div>

> [@krystenr](#):
>
> … However, when I use an input transform that goes from rec709 to rec709 (yes, that’s correct), the image looks identical—no color shift whatsoever. I’m going to go with it for now, but I am pretty confused. I know they have different gammas (2.6 for DCI-P3 and 2.4 for rec709) so I’m not exactly sure why what I did works…anyone know? Should I just keep my mouth shut and not jinx it?Thanks in advance!

This is an interesting topic. Let me share my opinion:

This conversion should be seen as a three step process (although mathematically these steps do not come one after the other in the listed order):

1. Just a conversion from \<_DCI-P3, Gamma 2.6, DCI white point_\> space to \<_Rec709, Gamma 2.4, D65 white point_\> space won’t cause any change in colors, except for the out of gamut colors (which Rec709 display can’t do, but are part of the DCI-P3 space).

2. If after conversion, the content will be evaluated in a dim room with 5 to 10nits ambient light level (and ambient light color temperature of 6500K), it is suggested that a chromatic adaptation transform be also applied with the above conversion.

3. In a Rec709 viewing environment (with 5 to 10nits ambient light level with color temp of 6500K), the target peak luminance would be 100nits (instead of 48nits, under which the DCI-P3 content would be graded). Here, a viewing conditions adjustment transform should be applied as well with the above conversion. For instance, CIECAM02 based viewing conditions adjustment can be applied.

The idea behind 2. and 3. is to make the content look perceptually very similar when it is evaluated in a different viewing environment with a different calibration target.

It should be noted that 2. and 3. do not apply, if the Rec709 converted content is to be evaluated in a projection setup in a completely dark room.

Well, this is how we provide Calibration 3DLUTs to our clients, so as to directly calibrate their display (in a Rec709 viewing environment), for presentation of DCI-P3 graded material (or DCI XYZ material, that was graded on a projector in a dark room). Such 3DLUTs include the combined color processing of 1., 2. and 3., and do the required color correction as well for the display.
