just FYI those are not readable by 2025 flame .
I would like to have a 2025 service update that enables reading these , that would be a nice and probably quick fix?!.. i mean i can just change the header version in the openclip and then 2025 can read them.
Also anyone knows what this actually means? What colour spaces, what distinc metadata? what does this mean?
Openclip V7;
“Format now has distinct metadata and resolved colour spaces”
@finnjaeger - Remember that between Flame 2025 and Flame 2026 there was a structural change when SynColor was supplanted by OCIO. Although I’m making assumptions, I would hazard a guess that OCIO metadata was a necessary improvement to Openclip. You were on the development cycle.
sure thats my assumption that it uses the ocio colorspace names now, which is good as “rec. 709 Video” was annoying to parse…
@finnjaeger - so backward compatibility might be a significant engineering challenge since OCIO is not available in older versions.
Header changes for openclips that don’t contain such metadata is trivial text editing type stuff - which you’ve already done.
Similarly, there are reasons why LOGIK-PROJEKT changed between Flame 2025 and 2026 - structural change (userdb, projectdb, OCIO) is complex and bleating or whining about it infrequently results in good outcomes.
We build structures that can roll into the future, not structures that address historical issues with our 20/20 vision, right?
I am afraid that your only option is to write automation using Python around the Open Clips generated with 2026 release for the legacy version since content created is not readable in legacy version. This goes for project, archive, setups, etc.