FLME-60206- PreProcessing resolution is wrong when conforming media and sequence have different resolution than project
I dont think anyone still works with footage the same resolution as the timeline… i NEVER have.
This is not a problem with where the XMLs where made, its just a plain and simple bug in Flame.
We have reported this from multiple posthouses now as freelancers and now yet again, this has been a bug for a very very long while and my biggest issue with flame.
Is there any way to have people vote on a fix to show ADSK how important that fix really is? I think this is super important for anyone doing conforms in flame which, you know is sort of the feature of flame.
All the “fixes” are working sometimes but not always, generally we have to trash the tlfx action and manually match ALL repos using resize nodes.
Could just be “fixed” by ignoring the rotation info from the incomming XML and using resize instead of a action.
Action for this is a horrible choice anyhow as its absolute and not relative, if you take a HD timeline and copy clips with action on it to a UHD timeline, everything will be WHACKO .
Resize is a much better choice as it works the same way as premiere and resolve scale clips on the timeline so we can match whatever the editors did.
i put in a feature request for this option here , I am happy if its just the rotation thats lost, that would still be better than corrupt actions everywhere…
its 1-2 full DAYS per project as we are getting sometimes HUNDRETS of sequences to go through…
its infuriating to see that in resolve everything comes across without ANY intervention, i can conform 200 timelines and dont have to touch a single repo or timewarp… … and in flame its like this will take days
I think FLME-60206 is a bug report and I don’t think that you can see that until it gets fixed and added to release notes. I have a few bug numbers and although I can see them in my support history, they are not widely available …
right now - they corrupt. so right now action for me on timeline from a conform is impossible to use.
But yes you coulf solve this with a second axis that you set during conform that scales the values , just like what @KuleshovEffect did with his oremiere fixer script, he changes the values of the incomming data to scale the action.
resize just matches what resolve does much better logically and moving stuff across timelines and resolutions works well because its relative to timeline res, so you dont end up with black edges everywhere
Resize is great though it doesn’t do rotation. 2d transform needs a resize in order to work. Action is the best compromise though I agree with comments about it being unstable.
I think that a script that can add an extra acid offset is the easiest solution. It’s something I do myself. It’s usually constant.
Nicer not to have to think about it and have to paste on each shot though.
It’s a bit beyond my BASIC programming skills though.
Ive re-read your original post several times, I fear we might be talking about different thing and I should start a separate ticket…
The studio I work at only recently updated to 2023.3.2. So on 2021, an XML would come in fine generally, i wouldnt have to start an Action from scratch… I could usually just pop in an axis above the surface that scaled to the proxy size the editors used and everything would line up. Not every time, but mostly.
Now on 2023.3.2… a XML comes in w a timeline Action and the picture is squashed, but there isnt an unequal scale value on the axis nor in the Preprocessing. The only way Ive seen to fix it, is just to start a fresh Action timelineFX.
We have been fighting this for a while now, too. Sometimes if I dupe the segment and get crazy removing and copying the Action back, it will wake up and correct the size of the Action surface. But not always. Argh!
maybe once bigger studios finally make the jump from 2021 to a newer version they will all start complaing to ADSK. one can hope smaller shops like us always upgrade fast
Most of the time I can get the action to fix itself by introducing one of the ‘Source’ green timeline effects. It seems like this forces flame to re-evaluate the resolution of the incoming clip and then things appear correct.
I made a small python script that adds a source color management and then deletes it. Hotkey this and you can quickly make things better.
This is my workaround and has no official endorsement. I’d still prefer it to not be an issue.
