If anyone has ideas or interest about Ftrack integration with Flame they are listening.
You can add the request / vote here
FTRACK INTEGRATION
As a quick update, they are directly asking what key features and must haves any flame integration would have.
Personally we work on episodic shot based projects where we are exporting plates as well as comping and reviewing in Flame / Nuke
whaaat? Been bugging them for years at all the trade shows and always been given the standard "yeah sure but no one uses flame and we have to use our resources where it matters(Maya+Nuke)
" So this is nice if it happens at some point
Here’s an FTRACK update…
It seems that the team at ftrack are still looking into this Flame integration but would like to get some support from studios so that the request can be significantly bumped up the list. If there are for example 5 studios willing to share some of the development cost then it can be achieved quite quickly. I know that there has already been some talks / interest in this so just putting this out there on behalf of ftrack.
If you are interested then it would be great to send FTRACK a brief email with your support and ideas.
I find it pretty amazing that after like 10 years they still don’t have Flame integration. F-Track is almost exclusively used in commercial environments, where Flame dominates as a software. If they just have Flame integration it would be a serious alternative to ShotGrid for us.
7 years (until I left at the end of 2020) of fiddling with ftrack at the mill and it was never integrated. IMHO, it’s a white elephant.
I agree. It would be great to give the Flame community an option to switch or have an alternative to ShotGrid.
@johnt - if it was implemented so there was less fiddling to integrate then it might be more attractive… but understand your experience
My experience of working with ftrack was that they didn’t listen much. There was a fella from ftrack who was supposed to be helping us integrate. I remember overhearing him talking to a colleague giving it the Larry Large saying how he’d worked on features and we didn’t know anything. My argument was that we weren’t making features and we needed things to work faster than features.
i’ve been using Ftrack with flame for over 5 years. It doesn’t come that way out of the box, MPC advertising (now MILL) built custom integration on top. I publish straight out of flame with MILL presets for all post production tasks and all kinds of plates for my team, local or remote. Having worked at small to medium sized shops most of my career i dont have any other asset management systems (shot grid) to compare it to but many of our artists like it and want every job to run through it. It doesn’t really make sense for every job (finishing style jobs, versioning, quick turn around) and we dont use every single feature in it but we continue to build more automation and integration tools into it. We have our own pipeline team so i dont know what the prevailing attitude towards flame is there. I agree it would be a big boon to flame to have integration out of the box but i imagine autodesk is somewhat of a competitor?
Hey everyone, hope you’re all doing well!
Due to a need in our pipeline — and after years of not finding a solution to integrate ftrack with Flame — I decided to spend some free time between projects to build something myself using Vibe Coding. It’s a simple tool that lets you create shots in ftrack directly from Flame’s timeline. It still has a few bugs I plan to fix, but I hope it can be useful for the community. I don’t have much programming experience, but I managed to put it on GitHub. I also tried to make a demo video, but the screen capture quality isn’t great — sorry about that! So far I’ve only tested it on my workstation: Rocky Linux 9.5 with Flame 2025.2.2. I plan to install it on other machines here at the studio with different Flame versions to see how it behaves.
Features:
- Create shots from Flame sequences (single or batch)
- Auto-creates conform task with user assignment
- Built-in time tracker for tasks in progress
- Publish versions with comments for review
GitHub: GitHub - wiltonflame/flame-ftrack-integration
Demo video: https://www.youtube.com/watch?v=wG8z91TjOZ8
Feedback and suggestions are welcome!
Cheers
Looks great.
There was an update on FTRACK for publishing single shots here:
https://github.com/ftrackhq/integrations/releases/tag/framework-flame%2Fv24.11.0
Looks like you have been hard at work with other aspects of integration.. will check it out.
Thanks for sharing! I took a look at the official ftrack framework and it’s interesting, but it’s a bit complex with pre-compiled files that are hard to modify or update. It’s also quite dated (November 2024) — still on Python 3.9 and PySide2. It could definitely complement my tool, but the thumbnail and shot review functionality already works well in my integration.
One thing I’m still investigating: when I create shots and upload version videos to the conform task, it creates all tasks as “Ready to Start” — but then after the video upload, ftrack automatically changes only the compositing tasks to “In Progress”.
I initially thought this might be some automation set up by another department, but when I recorded the demo video using a trial account, it had the exact same behavior. When I create shots with just thumbnails (no version videos), the compositing tasks stay in their correct status.
Still digging into this one, but everything else is working great!