AAF import from Avid - Action coming in empty

Flame Flame Questions
, ,
1

Hi all,

is anyone else experiencing errors in importing Avid AAF in 2026.2.1? I have a verified aaf that works in 2025, but on import to 2026 creates action nodes that only contain a camera (no axis, no surface, definitely no resize info).

Also noticed that AAF import takes much longer, terminal reporting many errors with .volatile file loads.

If this is a verified bug then it is of the highest urgency that it is resolved please. If it hasn’t been logged yet then I will add to Autodesk fix requests.

Best,

Gareth Parry

2

Have you tried the “Fix corrupt actions” python script?

Might work although the Actions come in empty not sure it can get back the axis etc, but def worth a try.

3

Hey Ben,

thanks Ben - I will try that. It looks like all actions I make are having the same issue, so I’m going to reset my user profile first.

Gareth

4

Are you by any chance working off of a project hosted on another machine like /hosts/other-machine…?

I ran into this exact thing last night and was getting ready to report it to support. I think it’s specific to 2026.2.1.

5

Hey - yes project hosted on a project server defined in /hosts/

6

Hi - tested on same system, same user, same project - action creation works in 2026.2 and does not work in 2026.2.1

7

We currently have a support case open for this on 2026.2.1 and no solution in sight as yet. Sharing projects via /hosts is causing more than a few headaches with some data not sharing.

Have seen the action thing but also issues with losing Dolby vision metadata, type tool missing text and copying/pasting bfx not possible.

Opening the project on the host machine and it all comes back.

8

Ugh, that sucks. I just opened a support case also.

1 Like
9

Lately, we have seen NFS client / server synchronisation issues which can be seen in a project server OR collaborative workflow between two flame workstations. I have provided offline an NFS setting to Gareth and Support will get back to your @Jason_Chambers with the recipe.

Based on these two cases, I will provide the options here and we will also update the Flame Collaboration documentation with this information.

Stay tuned!

1 Like
10

Thanks a lot! Support will provide you the solution ASAP.

3 Likes
11
12

Just came in here to see if anyone is having the same issue and looks like it’s not just me … Flame 2026.2.1 local project and Action coming in empty over here as well.
EDIT: Mac

13

Stephane has some nfs auto mount config changes that may help if you can get in touch with him

14

Please see the Import via NFS Section here and be sure to review the Important Note in that section. If that does not help your issue, please open a support case to investigate.

15

Could you open a Support call and provide the AAF file so our team could investigate the issue?

16

Hey Stéphane, will do … but it wasn’t an AAF, it was an XML and even if I manually create a new timeline with a new clip, Action is still blank when applied as timeline FX
I opened a brand new project, generated bars and same issue persists … it’s not project or AAF/XML import specific.
MAC 2026.2.1

17

Thanks a lot @Igor ! AAF and XML Conform use a similar code path for the Timeline FX creation.

Is you storage local or on a shared storage?

Please provide the XML to our Support team so they can have a look.

18

Flame storage is local but linked files are on the server

19

@Slabrie support case submitted.

1 Like