# ACES workflow **URL:** \ **Category:** Flame Questions\ **Created:** [September 20, 2021, 2:02pm UTC](https://forum.logik.tv/t/aces-workflow/3843 "2021-09-20T14:02:12Z")\ **Posts on this page:** 7\ **Page:** 3
**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 15, 2022, 6:10pm UTC](https://forum.logik.tv/t/aces-workflow/3843/41 "2022-06-15T18:10:18Z")
Ah. If that was a nine minute aces video then I’d probably would have stated the following. If you are the last person to “touch the color science of a shot”, then auto convert away. The perspective of that video is one from a compositors perspective, not from a colorists perspective. So if you need to bring everything together, then auto convert could be your friend for that. ---
**Author:** ![RufusBlackwell](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/rufusblackwell/32/422_2.png) [@RufusBlackwell](https://forum.logik.tv/u/RufusBlackwell)\ **Post date:** [June 16, 2022, 5:01am UTC](https://forum.logik.tv/t/aces-workflow/3843/42 "2022-06-16T05:01:36Z")
Hi. I grade a lot of jobs in Flame and use all the colour spaces extensively. Personally I don’t use the auto convert option, so much so that I had actually forgotten it existed. I simply tag everything correctly on import then take the clips to the colourspace I want using colour management nodes. That way you can easily check before and after and make sure things are converting as they should. I did got through a period where I auto converted everything to ACES CG on import, but that was quite a problematic workflow. In the end it’s better just to bring things in in the colourspace they already exist in, then deal with it in Flame. ---
**Author:** ![Jonhollis](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/jonhollis/32/11832_2.png) [@Jonhollis](https://forum.logik.tv/u/Jonhollis)\ **Post date:** [June 16, 2022, 8:11am UTC](https://forum.logik.tv/t/aces-workflow/3843/43 "2022-06-16T08:11:16Z")
a few things to note. half the nodes don’t work properly. including keying and tracking. so beware. ive had to outsource all the tracking and doing the keying in fusion. most of the nodes the controls just aren’t set up for this sort of workflow. simple things like transparency. its very difficult. ---
**Author:** ![RufusBlackwell](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/rufusblackwell/32/422_2.png) [@RufusBlackwell](https://forum.logik.tv/u/RufusBlackwell)\ **Post date:** [June 16, 2022, 8:46am UTC](https://forum.logik.tv/t/aces-workflow/3843/44 "2022-06-16T08:46:54Z")
Yeah that’s why I would bring it in in it’s existing colourspace. So for example if it was a log source and I was working in ACES CG, I would bring it in log, key it in log, convert to rec709 to track it and convert to ACES to comp (I actually usually comp in REC709, only in ACES if it needs to be ACES). So a simple setup like this: ![Screenshot 2022-06-16 at 15.40.25](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/e/e2beff5f95dc0ca857ee200c55d0d1eb7a743983.jpeg) ACES is great for stuff that needs to be ACES, but there’s still a bunch of stuff that has to be done in other colourspaces. However once you are used to bouncing between colourspaces you are flying. ---
**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:** [June 16, 2022, 10:27am UTC](https://forum.logik.tv/t/aces-workflow/3843/45 "2022-06-16T10:27:49Z")
Yes, you can’t just convert to ACES and think that’s it, you need to be prepared to shift colourspace for different nodes. Fun, fun, fun! ---
**Author:** ![Fernandovfx](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fernandovfx/32/4331_2.png) [@Fernandovfx](https://forum.logik.tv/u/Fernandovfx)\ **Post date:** [January 25, 2026, 11:19am UTC](https://forum.logik.tv/t/aces-workflow/3843/46 "2026-01-25T11:19:02Z")
> [@finnjaeger](#): > > …original camera gamut for all files written , work in 32bit completely (if you convert the gamut to aces working space, which you should, just dont write out a file) and then write out 16bit linear/aalexaWidegamut again …Its a bit weird of a thing but yea, for me its either acesCG or linesr wirh camera native gamut for writing out and then all filenames have to have the colorspace written into them. I receive the file as ACES2065-1, but I end up importing it as ACES2065-1 because I have to return it to the colorist as ACES2065-1. I don’t know if this is the best way to work in Flame, and to avoid the risk of the file not having metadata, I don’t use “from file rules” for importing; I choose to import as ACES2065-1. ---
**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:** [January 25, 2026, 3:23pm UTC](https://forum.logik.tv/t/aces-workflow/3843/47 "2026-01-25T15:23:56Z")
Input Transform in Batch. Set Input to ACES2065-1 and Output to ACEScg or ACESCct. When you’re done, Invert the Input Transform. Boom. [Previous page](https://forum.logik.tv/t/aces-workflow/3843.md?page=2)