Issues with mediahub

Hello,

We’re having issues with flame importing clips in the wrong colourspace when multiple flame ops are working on the same project in different workspaces. The steps to reproduce are;

  1. User A launches flame in project A with workspace A
  2. User B launches flame in project A with workspace B
  3. User A opens MediaHub tab, sets colour management for an import e.g. Mode=View Transform, Invert=False, Display=ACEScg,View Transform=From Rules, Display=Rec.709 video. Crucially, they’ve set the colour management to a new setting, i.e. made selections in the UI to change the settings
  4. User A clicks away from the MediaHub to a different tab ← this specifically seems to be what triggers something across users.
  5. User B runs our import tools, which are essentially a wrapper around;
    `flame.mediahub.files.options.set_tagged_colour_space(colourspace)
    flame.import_clips(‘/path/to/files’, reel)`

While you would expect User B to have clips imported in their given colourspace, in fact, the clips get imported with User A’s settings. In the example given User B’s clips should be in ACEScg, but are in Rec709.

Since all subsequent imports will also be using User A’s settings, the only thing I can been able to find that clears this is for the user to manually tab to MediaHub, set the colour mode to something else, then set it back - then it will start importing in the correct settings.

I note in the Flame documentation mediahub settings do indeed state options are saved automatically and at a project-level, rather than per workspace.

For reference here is a brief outline of our systems setup:
Every artist has their own AWS EC2 instance, each running its own local Flame install.
Projects themselves live on a central project server, and that project data gets exported over NFS4 and auto-mounted on every workstation. The mount options we’re using (acdirmin=0, acdirmax=0, actimeo=0, basically) are straight out of Autodesk’s own Flame project collaboration docs for multi-workstation setup, disables NFS attribute caching so you don’t get cache desync when Flame hard-links/renames files internally.

Finally, I tested this in both Flame 2027 and 2025, which both have the same issue. However I do notice PyMediaHubFilesTabOptions does have different attributes/methods availble, which allows me to do this;
flame.mediahub.files.options.colour_mgmt_mode = "Auto Convert"
flame.mediahub.files.options.colour_mgmt_mode = "Tag Only"
which seems to be enough to replicate the ‘on and off again’ manual workaround in 2025.

Though, side note: these are not documented. @fredwarren could we get those added to the Flame 2027 docs? The missing methods/attributes are;
colour_mgmt_display
colour_mgmt_invert
colour_mgmt_mode
colour_mgmt_view
colour_mgmt_working_space
side note to the side note, this throws an Error: basic_string: construction from null is not valid unless colour management mode is set to Auto Convert, which is probably not desirable.
import_transform
tagged_colour_space

Questions;

  1. Are there any changes we can make to our systems setup to avoid this issue? Or is this expected/unavoidable behaviour because of how Mediahub works?
  2. In Flame 2025 is there any way to set colour management via python api to anything other than ‘Tag Only’?
  3. Could we get this ‘shared mediahub settings’ behaviour re-considered? It can be quite disruptive to production on multi-workspace projects because users may not notice the files have been imported incorrectly and end up sending clients shots with incorrect grades. Even though there is a workaround on Flame 2027, it is still susceptible to race conditions.

I think every person I talk to who works at a cloud based shop has this exact gripe and gets bitten by it daily. It’s worth considering a quick ingest script to get around it until it’s fixed.

To be honest, even working as a solo artist I’ve shot myself in the foot by this gun. I’ve made it a good practice to check my import settings.

I’m using python to import clips (I’m a pipeline dev) so I sort of already do have an ingest script. What else could I be doing? I’ve seen people mentioning wiretap, is that something worth looking into? Seems like quite a time investment to understand and implement

I have experienced this as well. Its just a nuisance and I just stay diligent 3x checking my settings before import. FR below.

FI-03807 Import Settings on Host

I had already started the thread and cannot rename, but in hindsight and mentioned in that improvement request, I think the Import Settings should actually live at User level. So that a users last used import settings follow them between machines.

The improvement has been renamed Project / User Import Settings options to better reflect the need.

Not clear yet what would be the best options to provide but do you see a need to persist the Import settings on a user in project basis as opposed to the current project based settings? I feel that if you work on two different type of project, user based settings might not be good enough and would show the same issue.

Thanks for your reply.

I suppose its subjective… but I think at least user would be an improvement. I personally would not find it unnatural/unexpected that the previously used import settings “follow” my user around from project to project during the day. I would find that an improvement over finding the import settings magically changed on me each time I return to the MediaHub. I thiiiiink that might be how Flame worked like pre 2022. The import settings would reset every time the app was re-opened but would persist while changing projects… as i recall… maybe… dont hold me to that. Either way, they didnt just mysteriously update when Im 100% certain I have not touched them.

Perhaps others have have more complex import settings to manage between projects and would really benefit that. To re-iterate, its not that I have wildly complex and varying import settings between projects… mostly just changing tags from ACEScg to/from rec1886, occasionally a resize import or override framerate on audio… Its just the fact that the settings are changing/updating when Im 100% certain I have not touched them.

If I understand what you are saying about project basis… yes I think that would be the true solution. Each user stores last used import settings by project, or vice versa, each project stores a set of last used import settings by user.

Thanks again for your consideration.

I am curious to hear from others who work with multiple users in the same project. The proposition above would have an impact and a small change is always a pain when you discover it while in production.