Flame Feedback requests implemented in Flame 2027

Hello Everyone,

Here’s the list of requests submitted at flamefeedback.autodesk.com that have been implemented in Flame 2027.

FI-00131 Tokens: Ability to add custom token entries in the Tokens drop down

FI-00399 Open Clip: Expose more Metadata.

FI-00439 Tokens: Limit “” to a fixed number of characters.

FI-00805 Media Export: Include colour space tagging in openEXR metadata

FI-01250 Workflow: Preserve Metadata from all channels

FI-01377 Animation: Ability to export channel data out of a node

FI-01392 Batch: Ability to keep Markers from a clip node always visible in the Timebar.

FI-01394 Batch: Ability to add Markers

FI-01575 Batch Render / Write File: if the node is expanded, then the result should be expanded.

FI-02077 Markers: Make name and comments accessible in Batch FX

FI-02231 Markers View: Ability to add and manage markers from the Effects tab.

FI-02528 Paint in Timeline Markers to leave notes

FI-02683 Batch: Add a means to view a checklist of tasks in Batch

FI-02301 Python API: Ability to Import XML, AAF and EDL files

FI-02819 Markers: Persist the scrollbar position in the Markers view

FI-02826 Rendering: Burn for macOS

FI-02943 Action: Add PNG file support for Textures

FI-03137 Markers: Make the Markers view available in Batch.

FI-03230 Media Export: Embed token into EXR metadata

FI-03232 Batch: Set a default compression for Write File nodes of Batch Setups created in Shot Publish

FI-03298 Batch: Have the Write File node inherit the Source Timecode of a clip.

FI-03361 Tokens: Add a Workspace token in places where the project and user tokens are available.

FI-03415 Grab Reference: Add support for and tokens

FI-03575 Lens Distortion: Support for the 3DE ‘3DE4 Radial - Stabilizer, Degree 6’ distortion model

FI-03581 Batch: Allow more than 3 digits in the Iterate As’ Current Iteration field

FI-03589 Selective ML: Planar track without Scaling

FI-03592 Project: Create project backups in a more efficient way than archiving

FI-03611 Python API: Have “Update Source” accessible via Python

FI-03612 Python API: Get Current Version of Clip

FI-03613 Python API: Tape Name from PyClip

FI-03629 Shot Publish: Use the Write File node’s Version Mode preference in Shot Publish

In addition, these requests were partially implemented:

FI-02779 OTIO - Open Timeline IO - Support

  • OTIO Import has been implemented, but not export.

FI-03587 Export: Add the Writing Application metadata to the final exported video of Flame

  • Metadata keys can be manually added and custom tokens can be used to help adding this key, but it is not out-of-the-box.

FI-03628 Project Management: Support right-click to “copy” text from buttons in the Manage Project window.

  • This workflow has been implemented in the text fields, but not in non-editable fields.

The custom token stuff is huge. Merci!

Oh
You should make a bit more of a big deal about flame_backup.

@fredwarren @Slabrie And for those of us considering upgrading to 2027 from 2025, especially on Mac, is there any recommended method? Do we need to completely uninstall the current version?

I’m sure you are aware of negative comments/feedback in regards to 2026 on here so we chose to not upgrade. Have these been rectified, especially the massive slowing down of systems that are utilising project server?

Probably not helpful for you on macOS, but rocky 9.5 flame 2026 to rocky 9.7 flame 2027 takes 27 minutes on the long end.
Once virtualized and templatized it’s less than 60 seconds to launch.
It’s less than sixty seconds to roll back to 2025 or 2026, but you wouldn’t want to.
YMMV

Hi Adam,

Over the past two years, I had installed updates on top of earlier updates (i.e. 2025.2.6 on top of 2025.2.4) without clean uninstalls. Before adding 2027 to the pile, I wanted to clear this up and decided to remove all unwanted versions. I ran the uninstaller selectively on my system and this broke something in the way the 2026+ versions interact with previous S+W based versions. All my projects disappeared with the message that my databases were corrupt and I needed to rebuild. Which also didn’t work.

Beau sorted me out with an article on clean uninstalls (https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Clean-uninstall-of-Autodesk-programs-on-a-Mac.html) that preserved all the good stuff I wanted to keep and none of the bad stuff. I now have one version each of 2025, 2026 and 2027 and everything is humming along nicely again.

Happy to report no data actually lost. Just time.

Josh

There is no issue installing Flame 2027 on a configuration with 2025.x and 2026.x.

Many issues reported on the forum related to configuration issues have been fixed with a Support ticket.