-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrected dimensions while exporting #16692
Corrected dimensions while exporting #16692
Conversation
I know that this has been discussed years ago in #3757 but as we have things fixed in finalscale and the interpolator i thinks it's fine to re-evaluate. |
0b0b916
to
a4f7e9e
Compare
Updated comments about old issues, don't ceil but round. Tested all of that old issues and current ones, seems good to me now. |
I'm not sure for all cases, but there is still issues and it is hard to evaluate if more cases are better covered with this PR. For example, take the integration test image Edit it in darkroom and do a square crop taking the whole height ( Now back to crop and resize the crop area to have an even size, for example Back again to crop and resize the crop area to have an odd size, for example Also, do a crop size I found out that even/odd if not really a parameter but more the actual crop size. As I said I'm not sure how to get this right in all cases, a very hard issue to fix to me as the pixelpipe is handled. |
Will investigate further next week |
Depending on pipe.processed_width&height and the given width&height from the export dialog the dimensions for the pixelpipe run could be too small due to flooring. Instead we do rounding here for the processed width&height and afterwards recalculate the scale to a) be sure there are no pixels missing b) avoid out-of-bounds problems.
a4f7e9e
to
4554c4f
Compare
Closing this, pending work will be based on #16748 |
Depending on pipe.processed_width&height and the given width&height from the export dialog the dimensions for the pixelpipe run could be too small due to flooring.
Instead we do rounding here for the processed width&height and afterwards recalculate the scale to
a) be sure there are no pixels missing
b) avoid out-of-bounds problems.
One report about such rounding errors is in #16689
To reproduce you can take any raw with a size of at least 8288x5520 pixels and crop the size to exactly that in rawprepare while watching the dimensions in the "Image information" section.
darktable -d pipe -d imageio
will report the dimension as herekeeping at least one dimension for what we want.
This is a tricky part of the pipeline and we had a number of issues related to export dimensions so please test in depth - i did so and couldn't spot anything wrong - watching out for
So hopefully
Fixes #16689
Fixes #16638
Also seems good for #16133
without introducing a regression.
If good the release note would simply be "Fixed exported image dimensions"