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?
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).
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
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.
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.
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.
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
Disable the preference to flag color space errors on render if it bugs ya.
Where is that?
I can’t find it either
It might be 2027
Nah, it’s been there forever. Export module, advanced options, the menu all the way to the right isn’t?
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
@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
Thanks for the info @doug-walker I’ll check and report the exact issue.
Say “Hi” to Cüneyt 
Action on Mixed Colorspaces set to Ignore