Good find, Alan, that’s not how the program should work.
Not ideal, but have you tried running it through a 2D Transform instead of a Resize / Reformat?
Nope…that doesn’t really work for live timelines.
wow - is this fixed now in 2023? thanks for doing these - saving the flame burning
No it is not.
Is it hard to fix maybe a cosmetic thing
It is MUCH MUCH more than just a cosmetic issue. It has major repercussions everywhere in the software.
I’ve also noticed where the resolution i set in flame can’t be replicated on export. So if i’m making jpgs the resolution will be different than open exrs. This has burned me a few times.
@fredwarren Is it possible to share what the issue is?
@blakieman Someone here mentioned the technical reason behind it…something about how the format itself needs to have the height and/or width be divisible by either 2, 4 or something along those lines. Basically even numbers if I recall.
yep! i remember! very annoying though just the same.
@kyleobley Without going into too much details because it could be a long discussion…
We did a re-architecture soon after Flame 20th Anniversary and one of the main component of it was the introduction of the new Batch pipeline engine. For those who remember you used to have the choice between the Legacy pipeline and “Flame Reactor” when you would create a project.
In this re-architecture we decided (and had to) to round the aspect ratio when it was close enough to “common” aspect ratio such as 1.333 and 1.778 and this is the cause of the issue mentioned by Alan; his 1.785 ratio is within the range we have set to round to 1.778.
Can we change that? Yes. Is it a cosmetic change? No because it affects Project Conversion, Conform, Archive Restore, Batch, etc. Pretty much every part of the software would be affected by that change and it is hard for us to predict what other problems would arise from that rounding being removed.
Is this limitation to accommodate the older image storage formats that have all these even number, divisible by 4 legacy limitations? Will any of these issues be resolved the newer graphics api stuff?
Is this limitation to accommodate the older image storage formats that have all these even number, divisible by 4 legacy limitations?
Will any of these issues be resolved the newer graphics api stuff?
My best guess would be no but I honestly don’t know.
Thank you for the explanation, I think a lot of us appreciate this type of transparency and it goes a long way in helping us understand why something that may seem trivial is indeed not.
This issue has been fixed in 2023.2 Update