Flame MIO Open Clips metadata

Hi guys,

I am writing a Flame Tool that generates comp open clips, graded open clips and generates tracks just off of a comform. It is a pipeline tool specific for the company I work at but that it can be tokenized and specified to different folder structures.

One problem that I found with MIO Open Clips is that when the metadata of the clip changes, then the Open Clip fails. This is not too much of a problem as the pipeline is set as so the metadata of a shot should always remain the same during the project, but it happens that sometimes artist get the wrong shot to copy the metadata from.

Now my question is - does anyone know what actual data is it comparing? Cause if we know the metadata used to compare, I could just write a safe check that notifies that user when clips have different metadata.

I tried to look online but couldnt find much. Can also share the code if needed.

Thanks!

hey henry

its a bit fiddly with open clip just as with pattern browsing - ive yet to learn about the open clip updates in 2026/7 but i will soon.

it checks as much metadata as it can i think - i know that if source TC, frame range, frame rate, colourspace tag, res, overscan, name, anything changes, then the pattern breaks. only way to fix was to delete the offending renders. Im trying to figure out the same kind of workflow but more of a general open clip workflwo that i can then involve with the grade pipe too.

dan

Hey Dan!!

I have been testing this pipeline on a job now - both comp and grade tracks are open clips. It is fairly smooth but yeah as you mentioned naming has to be always the same and metadata. The only thing that I need to make sure is that the renders coming from nuke/flame are all named correctly and that the same happens with the movs coming from BL.

I realised that MIO open clip scans just the last render and checks all the metadata against the previous ones using it as “hero” - so if v008 has different metadata from v007 - it won’t read v007. But if it has the same as v006 - it will read both v008 and v006 if that makes sense.

It is a very strong workflow cause you have access to all your versions in the timeline but as you mentioned it needs to be setup correctly and kind of fool proof because very easy to break

@claudngtt.09 could you collect open a call with our Support team and provide media file and Open Clip that shows the issue? Please share here the case ID so I could follow this up.

Which version of Flame are you using?

Hi @Slabrie

Could you point me where can I raise it with Support team? Sorry I am new in this forum. Also, I will need to ask permission for those media files before sharing.

We are currently using Flame 2025.2.3

Here we go: Technical support case creation procedure

You might also want to update to the latest Flame 2025.2.7 service pack to get the latest fixes.