# Plugins / Tools missing from FLAME **URL:** \ **Category:** Tools and Tech\ **Tags:** plugins, tools\ **Created:** [January 18, 2026, 11:15pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992 "2026-01-18T23:15:30Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 18, 2026, 11:15pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/1 "2026-01-18T23:15:30Z")
Hey All, this is Eric from VFX Tools. I was just talking with Jeff on Logik Live about my software Headcase & Wrap It, and he suggested we could talk here about other plugins/tools that you’d like to see in Flame. The reason I made my first AE plugin (Extendo!) was because I couldn’t accept that there was no edge extension (aka pixel spread) in AE. I’m driven by solving these products. Same with Wrap It. Nuke has Project3D, and we need it in AE & Flame too! So: What’s missing from Flame that’s available in other DCCs? What are problems in your day-to-day workflow that drive you nuts that could be solved with an OFX plugin? Are there integrations with ML tools that you’d like to see in Flame? Or does the inference node pretty much cover it? ---
**Author:** ![TimC](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/timc/32/11881_2.png) [@TimC](https://forum.logik.tv/u/TimC)\ **Post date:** [January 19, 2026, 2:08am UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/2 "2026-01-19T02:08:10Z")
match grade node like Nuke. feed in a graded version and the ungraded plate and then export a LUT you can then use in a timeline, on a different take of the same shot, etc. ---
**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\ **Post date:** [January 19, 2026, 1:13pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/3 "2026-01-19T13:13:40Z")
I use a DCTL in Resolve that has a great ‘density’ tool. I bet it’s possible to do the same thing with a matchbox/ofx node and I would pay money for it: ““Density” reduces luminance, while saturation is subtractively increased to avoid greyish colors. This results in “film style colors” where colors appear deep and saturated.” > **[COLOR SHIFT 4](https://mononodes.com/color-shift-dctl/)** > > COLOR SHIFTv4.0 LOOK DEVELOPMENT TOOL INTRODUCTION I drew inspiration from FilmLight's Baselight 'Hue Shift' tool, which offers the innovative capability to shift hues towards adjacent colors. Following this initial adjustment, you can enhance the... ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 2:00pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/4 "2026-01-19T14:00:45Z")
That seems doable. Are you on Mac or Linux? ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 2:00pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/5 "2026-01-19T14:00:50Z")
I’ve converted DCTLs to Mistika in the past. It’s just another iteration of GLSL, just have to fix up syntax and swap out API calls, but turning them into a matchbox should a straight forward task. One caveat is that Mono Nodes is a commercial DCTL, so it wouldn’t be appropriate for us to do it. And a lot of people take inspiration from Baselight. ---
**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\ **Post date:** [January 19, 2026, 2:07pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/6 "2026-01-19T14:07:27Z")
Yes Jan - I wouldn’t say copy/paste the MonoNode DCTL. I just figured the math behind ‘density’ is common knowledge… just not to me 🙂 ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 2:16pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/7 "2026-01-19T14:16:00Z")
OK, following now. Density is not a singular math - well, I think it was precise in the film days with stock, but in digital color applications it has different interpretations. Usually affecting gamma or exposure in combination with a log curve. The exposure wheel in Master grade, when control is set to ‘Log’ might behave similar. Since the Mono Nodes take inspiration from Baselight’s operators, we could easily do a contrast compare of the Baselight operator and find Flame operations that are similar in response. Happy to chat further about that. And if there are no good matches, maybe write a Matchbox for it. ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 2:19pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/8 "2026-01-19T14:19:07Z")
The problem with developing specifically for Flame is that I need an expensive Flame license. $650/mo for a software I don’t use. Does Autodesk have a developers program or something? ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 2:21pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/9 "2026-01-19T14:21:27Z")
No, there is no developer program. You can run it with flex tokens on an as-need basis. 18 tokens per 24hr period ($54/day). So you want to be judicious, but cheaper than a long-term license. On occasion you can maybe borrow someone’s license for a day via remote access (i.e. remoting into someone’s system). ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 2:53pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/10 "2026-01-19T14:53:41Z")
> [@TimC](#): > > match grade node like Nuke. feed in a graded version and the ungraded plate and then export a LUT you can then use in a timeline, on a different take of the same shot, etc. > **[Colourlab AI now 22x faster - Colourlab.ai](https://colourlab.ai/?sld=estekker&gad_source=1)** > > No Credit Card Needed This seems pretty powerful. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 2:55pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/11 "2026-01-19T14:55:58Z")
They have great marketing, folks that have tried it have been mixed about it, in color circles. There have been numerous discussions in our color Discord about it. ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 5:26pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/12 "2026-01-19T17:26:52Z")
> [@TimC](#): > > match grade node like Nuke. feed in a graded version and the ungraded plate and then export a LUT you can then use in a timeline, on a different take of the same shot, etc. Hi, please try this Linux build of an OFX plugin MatchGrade node. It works in Resolve, but… we’ll see about Flame. Right now I’ve only tried 2 sRGB inputs. > **[Dropbox](https://www.dropbox.com/scl/fi/gysrpo9tomrfvzv23hs7p/MatchGrade_Linux_x86-64_GLIBC234_0119_1226pm.tar.gz?rlkey=plggea6068m800p6w1aae0y53&dl=0)** Let’s see if we have proof of life. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 6:17pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/13 "2026-01-19T18:17:25Z")
There are signs of life… I can’t seem to export the .cube LUT though. I tried a few different ways to set the path, but it doesn’t seem to write a file. Could you add a debug message with the result of the write() function and the path it was written to, so we know where to look? ![Screenshot from 2026-01-19 18-17-09](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/d/d03329e7af7083938e449828e2e5cddcb5225a9c.png) ![Screenshot from 2026-01-19 18-15-06](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/d/d2559775fbc6e299cd337815da85549aaee9968e.png) ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 7:18pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/14 "2026-01-19T19:18:55Z")
Try putting an actual path in there, like: path/test.cube. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 8:03pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/15 "2026-01-19T20:03:22Z")
That indeed fixed the file writing problem. In this relatively simple test case it does seem to work as desired. Wipe - left is the LUT applied to the original, right is the color grade that was the test case. ![Screenshot from 2026-01-19 19-55-38](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/6/66659e373333bc21827c56d645171a167bc4a199.jpeg) Applying the same LUT takes this other image to a similar treatment: ![Screenshot from 2026-01-19 19-59-15](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/3/37b169a7d9893af55665cd15478bf6d7258e607f.jpeg) ![Screenshot from 2026-01-19 19-59-27](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/1/1ed52bafdb8e673ddf8481fcc031f250c24f99ed.jpeg) I haven experimented with the other settings. I think the output name / path handling could be cleaned up. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 8:13pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/16 "2026-01-19T20:13:26Z")
More complex test case, doesn’t quite work yet. In the previous example it was simply an offset shift between the channels, a global color adjustment, which could have been a CDL. In this second test, a number of more complex color elements - a FEL, a H-S curve on the lips, a H-H curve on the shirt strap, and an overall S-S curve adjustment to remove most saturated. Not all of these changes were captured by the matched LUT. And there’s a difference between the output of the OFX, which captures 80% of the change, and the LUT which captured less: Output of the OFX (left) / color change (right) ![Screenshot from 2026-01-19 20-24-31](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/a/a8e9310388394f9014f6db3aa6b2dfa10081fa13.jpeg) Generated LUT applied (left) / color change (right) ![Screenshot from 2026-01-19 20-24-57](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/4/43331354eef28d9b4e579a028301cc9263cefc5a.jpeg) ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 8:33pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/17 "2026-01-19T20:33:03Z")
I’ll need to A/B all of this against Nuke at some point. Not sure how accurate or good that node is. The only way to figure this out is with a baseline. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [January 19, 2026, 8:52pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/18 "2026-01-19T20:52:22Z")
Completely understood. Inferring LUTs from two images is not easy and may not always resolve accurately. Which is why I added corrections to the second case that would be borderline. ---
**Author:** ![Nils](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/nils/32/12295_2.png) [@Nils](https://forum.logik.tv/u/Nils)\ **Post date:** [January 19, 2026, 9:30pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/19 "2026-01-19T21:30:19Z")
You can also just use match grade in Nuke, then export a .cube to use in Flame. Works pretty well. ---
**Author:** ![eric\_vfxtools](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eric\_vfxtools](https://forum.logik.tv/u/eric_vfxtools)\ **Post date:** [January 19, 2026, 9:43pm UTC](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992/20 "2026-01-19T21:43:52Z")
I only have Nuke non-commercial, and that node is all greyed out for me. Nils (or someone with Nuke,) you think you could run a couple image pairs through and send the results + the cube files? @**[allklier](https://forum.logik.tv/u/allklier),** do these nodes really pick up that level of detail? I thought it was a little more general than that. I should get the lips, the shirt, etc? [Next page](https://forum.logik.tv/t/plugins-tools-missing-from-flame/13992.md?page=2)