# ColorSync Compatible

**URL:** <https://forum.logik.tv/t/colorsync-compatible/4505>\
**Category:** Flame Questions\
**Created:** [November 23, 2021, 6:31pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505 "2021-11-23T18:31:55Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![onlycarlyouknow](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/onlycarlyouknow/32/2535_2.png) [@onlycarlyouknow](https://forum.logik.tv/u/onlycarlyouknow)\
**Post date:** [November 23, 2021, 6:31pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/1 "2021-11-23T18:31:55Z")

</div>

So does anyone know, is the new magic ColorSync Compatible button in Export just tagging it 1-2-1 instead of 1-1-1?

Is it doing anything else in the background or is it 100% just fixing the tag?

---

<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:** [November 23, 2021, 7:31pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/2 "2021-11-23T19:31:11Z")

</div>

Original topic “What the heck is going on?”

> [@Gamma issues with .mov / colorspace metadata in Quicktimes / NCLC tags](https://forum.logik.tv/t/gamma-issues-with-mov-colorspace-metadata-in-quicktimes-nclc-tags/1352):
>
> I’ve received a colour correct from a un-named but well known companythat I have loaded just the same as any other job, and exported as well. The client says my final is brighter, and sends a screen grab of side by sides, one the stringout provided by the colour company, and the other my final spot. Indeed, mine is brighter. It’s become a Major issue. Anyone have any ideas? For the record, I can round trip endlessly without any change, so it’s not a problem with my exports

Follow up topic “How to ‘fix’ it.” (its not really fixed, it just breaks other things. Its an unfixable dilemma, really.)

> [@Scripts to change QT NCLC tag within Flame](https://forum.logik.tv/t/scripts-to-change-qt-nclc-tag-within-flame/1868):
>
> With all the discussion lately over Quicktimes and NCLC tags lately I wanted to be able to change the color tags within Flame as a stopgap measure until ADSK gives us the ability to do so. I hope some of you find it helpful. [Media Hub & NCLC v0.3 script update](https://www.kyleobley.com/flame_share/nclc_mediahub_tag_v0.3.zip) There are two scripts: nclc.py (Acts as the middleman to send things to AMCDX) nclc\_mediahub\_tag.py (Media Hub Hook) How To Install: Download AMCDX Video Patcher for [Mac](https://github.com/da8eat/VideoEditorInstaller/raw/master/v0.6.0/AMCDXVideoPatcher.dmg) or Linux Modify nclc.py to point to the correct locatio…

---

<div class="post-metadata">

**Author:** ![La\_Flame](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/la_flame/32/200_2.png) [@La\_Flame](https://forum.logik.tv/u/La_Flame)\
**Post date:** [November 23, 2021, 7:37pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/3 "2021-11-23T19:37:08Z")

</div>

Hi Carl,

The ColorSync Button is only changing the tagging in the file’s metadata. It does not alter anything concerning the actual media.

Thanks

Grant

---

<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:** [November 23, 2021, 7:45pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/4 "2021-11-23T19:45:50Z")

</div>

I’m confident I did not use the word “heck.”

---

<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:** [November 23, 2021, 7:46pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/5 "2021-11-23T19:46:26Z")

</div>

Confirmed.

---

<div class="post-metadata">

**Author:** ![onlycarlyouknow](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/onlycarlyouknow/32/2535_2.png) [@onlycarlyouknow](https://forum.logik.tv/u/onlycarlyouknow)\
**Post date:** [November 23, 2021, 8:36pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/6 "2021-11-23T20:36:38Z")

</div>

Aha, my answer was down that second rabbit hole. Was looking for some way to make a quicktime exported from AE match the quicktime exported from flame with the colorsync button pushed so that I didn’t have to import/export a ton of tiff sequences for them.

The answer is @finnjaeger ‘s very nicely formatted ffmpeg command and/or accompanying script.

Thanks all!

---

<div class="post-metadata">

**Author:** ![onlycarlyouknow](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/onlycarlyouknow/32/2535_2.png) [@onlycarlyouknow](https://forum.logik.tv/u/onlycarlyouknow)\
**Post date:** [November 23, 2021, 9:57pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/7 "2021-11-23T21:57:03Z")

</div>

Actually one other question Grant if you know, is the ColorSync Compatible button basically doing the same thing that @finnjaeger is doing and setting the nclc tagging to 1-2-1 and then using the ‘gama’ tag quicktime is supposed to be ignoring to set the gamma to 2.4 or are they doing something else sneaky?

---

<div class="post-metadata">

**Author:** ![onlycarlyouknow](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/onlycarlyouknow/32/2535_2.png) [@onlycarlyouknow](https://forum.logik.tv/u/onlycarlyouknow)\
**Post date:** [November 23, 2021, 10:00pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/8 "2021-11-23T22:00:01Z")

</div>

Also also, in case anyone feels like doing this in AMCDX instead:

 ![Screen Shot 2021-11-23 at 1.45.31 PM](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/0/0f7bc080216b63ebd3355f279148703e6e172710.jpeg)

---

<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:** [November 23, 2021, 10:17pm UTC](https://forum.logik.tv/t/colorsync-compatible/4505/9 "2021-11-23T22:17:19Z")

</div>

its doing that you cna see it in amcdx.

it has a bit more logic in it though, like when you select srgb as your outpput lut it does 1-13-1 I think (sRGB) .

Afaik the button only switches between 1-1-1 and 1-2-1 doe anything 709

---

<div class="post-metadata">

**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\
**Post date:** [November 24, 2021, 11:15am UTC](https://forum.logik.tv/t/colorsync-compatible/4505/10 "2021-11-24T11:15:13Z")

</div>

If this fixes the gamma issues we have all struggled with, would it not make sense for it to be on as default, rather than off?

---

<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:** [November 25, 2021, 6:55am UTC](https://forum.logik.tv/t/colorsync-compatible/4505/11 "2021-11-25T06:55:22Z")

</div>

Well whether or not it “fixes” the issue is up for debate and depends on who you talk to. There’s an argument for both sides. Frankly, it’d be great if we didn’t have to deal with this and if everyone could agree on what is correct…and by everyone I mean colorists and software developers (Filmlight, Autodesk, YouTube, Instagram, Apple, etc, etc, etc).
