When we do this manually corruptions sneaks back in at least when we just open the project on another flame, same with all these copy paste and move segment up/down things.
the save as file , remove tlfx and re-apply from file
seems to be the first own to actually stick and I cant break it again
The code snippet from @mybikeislost can be used recursively on multiple timelines simultaneously.
It’s faster than a greasy weasel.
There is another Known Issue related to this but I can’t find it in the 2025 Docs:
FLME-60206 PreProcessing resolution is wrong when conforming media and sequence have different resolution than project
I feel like they know about this issue but it only affects us five people that keep making new Logik posts about it 
my guesses
→ way more people are getting avid AAFs than we think so they dont have this issue
→ big shops are still on pre python3 versions like flame2021 wher apparently this was not a issue
→ most people dont know that they need to scale the scale values based on proxy res. so for then the actions are useless anyhow
→ there are way less flame users than we think.
→ people dont know that resolve 1 click conforms all these xmls, so they blame adobe for having bad xmls…
i dont know which one it is 
maybe a combination of all 
this should effect everyone
@finn - perhaps it takes people, or more than one peoples, all day to conform, so they don’t have time to check this forum?
Autodesk 0:1 Community
make flame opensource now