# Rec709 or Rec1886 Rec709

**URL:** <https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539>\
**Category:** Flame Questions\
**Tags:** color\
**Created:** [June 5, 2026, 3:39pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539 "2026-06-05T15:39:43Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 5, 2026, 3:39pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/1 "2026-06-05T15:39:43Z")

</div>

Why is it that in Flame 2026.2.2 if I have Rec709 clips it will sometimes switch them to Rec1886 Rec 709. My timelines end up having both for no reason and then I get the colour mismanagement on output even though the exports are fine? Sometimes when I reboot it will all go back to Rec709 and sometimes it won’t. Anyone else experiencing this?

---

<div class="post-metadata">

**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\
**Post date:** [June 5, 2026, 4:04pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/2 "2026-06-05T16:04:07Z")

</div>

This is a gripe of mine as well. With the OCIO 2.0 the color configuration defaults changed. My older archives throw around errors because the old rec709 color management nodes do not automatically tag themselves as rec1886/709 (or whatever it is called now).

---

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 5, 2026, 4:26pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/3 "2026-06-05T16:26:56Z")

</div>

It’s annoying to have to babysit an export knowing that the colour mismanagement error is going to pop up. This definitely should not happen

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [June 5, 2026, 4:50pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/4 "2026-06-05T16:50:18Z")

</div>

Once you don’t have any material from past jobs it doesn’t happen any more. I put a colour management node on the top layer of the timeline that tagged everything with the new tag until it wasn’t neccessary anymore.

---

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 5, 2026, 5:11pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/5 "2026-06-05T17:11:52Z")

</div>

All the material has been created in 2026.2.2 so it shouldn’t happen. I can add the colour management as a gap fx but I also shouldn’t have to.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [June 5, 2026, 7:12pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/6 "2026-06-05T19:12:05Z")

</div>

That is odd. I have a few nodes in my batch user bin that have tagging built into them and I had to update some of those. But I haven’t had any problems with anything started in 2026.whatever.

---

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 5, 2026, 7:51pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/8 "2026-06-05T19:51:36Z")

</div>

I’m well aware of what the difference is, however flame is arbitrarily choosing what to label as Rec 709 or Rec1886. All the material is Rec709 and was tagged as such upon import

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [June 5, 2026, 8:13pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/9 "2026-06-05T20:13:22Z")

</div>

Disable the preference to flag color space errors on render if it bugs ya.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [June 5, 2026, 8:39pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/10 "2026-06-05T20:39:34Z")

</div>

Where is that?

---

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 5, 2026, 9:25pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/11 "2026-06-05T21:25:32Z")

</div>

> [@randy](#):
>
> Disable the preference to flag color space errors on render

I can’t find it either

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [June 5, 2026, 9:39pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/12 "2026-06-05T21:39:59Z")

</div>

It might be 2027

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [June 6, 2026, 4:19am UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/13 "2026-06-06T04:19:52Z")

</div>

Nah, it’s been there forever. Export module, advanced options, the menu all the way to the right isn’t?

---

<div class="post-metadata">

**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\
**Post date:** [June 7, 2026, 5:38am UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/14 "2026-06-07T05:38:46Z")

</div>

ir just add a LUT on export (i hate that its called LUT still ,it just isnt…)

LUT set to tag only → rec709(or whatever) , make that your default preset and boom no more warnings and no messed up quicktime exports with wrong metadata

---

<div class="post-metadata">

**Author:** ![doug-walker](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@doug-walker](https://forum.logik.tv/u/doug-walker)\
**Post date:** [June 7, 2026, 6:58pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/15 "2026-06-07T18:58:10Z")

</div>

@mlheureux , the name “Rec.709 video” exists as an alias for the “Rec.1886 Rec.709 - Display” color space in the new default config, but it’s not possible to tag new imports with that. (The name was changed to better align with the official ACES configs.) As @ytf wrote, if you are still seeing something named “Rec.709 video”, it’s because tagged media is being brought in from a previous project that used the previous config. It should work correctly, despite the difference in naming, but it will trigger the warning on export.

The option Randy was referring to that turns off the warning is in the Export dialog box, select “Show Advanced Options”, click “Preference”, then switch “Action on Mixed Color Space” to “Ignore”.

@Sinan, please contact support if you are getting an error rather than a warning. If you are restoring an archive, it should automatically use the legacy config file which still uses the original naming. That is an option when creating new projects as well, if that is useful in some scenarios.

Doug

---

<div class="post-metadata">

**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\
**Post date:** [June 7, 2026, 6:59pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/16 "2026-06-07T18:59:44Z")

</div>

Thanks for the info @doug-walker I’ll check and report the exact issue.

Say “Hi” to Cüneyt 😁

---

<div class="post-metadata">

**Author:** ![mlheureux](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mlheureux/32/572_2.png) [@mlheureux](https://forum.logik.tv/u/mlheureux)\
**Post date:** [June 8, 2026, 2:31pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/17 "2026-06-08T14:31:35Z")

</div>

![image](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/8/804b5ec20771f1f62410a99120b2525f3dedd381.png)

---

<div class="post-metadata">

**Author:** ![knhn](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/knhn/32/5635_2.png) [@knhn](https://forum.logik.tv/u/knhn)\
**Post date:** [June 8, 2026, 3:35pm UTC](https://forum.logik.tv/t/rec709-or-rec1886-rec709/14539/18 "2026-06-08T15:35:42Z")

</div>

**Action on Mixed Colorspaces** set to **Ignore**
