Skip to content
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

Orientation module not working after crop #14788

Open
ActarusLeGrand opened this issue Jun 27, 2023 · 13 comments
Open

Orientation module not working after crop #14788

ActarusLeGrand opened this issue Jun 27, 2023 · 13 comments
Labels
no-issue-activity reproduce: confirmed a way to make the bug re-appear 99% of times has been found scope: DAM managing files, collections, archiving, metadata, etc. scope: image processing correcting pixels

Comments

@ActarusLeGrand
Copy link

ActarusLeGrand commented Jun 27, 2023

Describe the bug

4.4.0

After doing a crop on a picture.
The flip horizontally work great.
The flip vertically,, rotate clockwise, rotate counterclockwise, is not keeping the crop in place.

Steps to reproduce

Do a crop on a picture.

The flip vertically,, rotate clockwise, rotate counterclockwise, is not keeping the crop in place.

Expected behavior

Rotate will keeping the crop in place.

Logfile | Screenshot | Screencast

No response

Commit

No response
image_2023-06-27_084530083

2023-06-27_7-45-09
2023-06-27_7-45-29
2023-06-27_7-45-37

2023-06-27_7-46-19
2023-06-27_7-45-50

Where did you install darktable from?

darktable.org

darktable version

4.4.0

What OS are you using?

Windows

What is the version of your OS?

10

Describe your system?

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@ActarusLeGrand ActarusLeGrand changed the title Orientation module Orientation module not working after crop Jun 27, 2023
@jenshannoschwalm
Copy link
Collaborator

You had opened a very similar issue a month ago, it's not concidered to be "nice" to do :-)

All devs read these issues and

  1. if somone thinks it's a genuine bug someone will fix it (often pretty soon)
  2. If it's a feature request find someone being interested to implement as important
  3. if you think it's relevant you might think about joining the project ...

@ActarusLeGrand
Copy link
Author

It's a completly different issue. 1 month ago I never used that module. I start using that module after 4.4.0.
It took me 1h of my time to make that post.

@jenshannoschwalm
Copy link
Collaborator

Excuse me i closed if you think it's a different issue. For me it's pretty much the same...

@ActarusLeGrand
Copy link
Author

I forgive you.

@jenshannoschwalm
Copy link
Collaborator

Just to explain, both issues are related to the way we handle orientation.

@ActarusLeGrand
Copy link
Author

Just to explain, both issues are related to the way we handle orientation.

That sound right.

@jenshannoschwalm jenshannoschwalm added reproduce: confirmed a way to make the bug re-appear 99% of times has been found scope: image processing correcting pixels scope: DAM managing files, collections, archiving, metadata, etc. labels Aug 23, 2023
@github-actions
Copy link

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

@guigri
Copy link

guigri commented Jan 2, 2024

I scan a lot of slides and then edit them in darktable. The scanned slides all have a black border, so cropping is necessary.
Some slides need to be rotated as they were taken on edge. I would like to crop them as long as they have not yet been rotated - it works much better in this order on the monitor. So first crop them while the images fit perfectly on the monitor and then rotate them 90 degrees to their correct orientation. Unfortunately, this is not possible in this order because of this bug.

I'm actually trying to say that this bug is not just a cosmetic flaw. Maybe I can motivate someone to take care of it. If I could, I would vote for it to be fixed. :-) Regardless of this - please don't get me wrong - it's a bit of a pity that with a tool with such professional standards, not even cutting and rotating work properly together. :-)

@ptilopteri
Copy link

why don't you make styles for cropping based on image orientation?

@Niklas-Zeidler
Copy link

same problem as guigri, I perceive this also as a bug btw.. My workaround for now: have one style for the slides / negatives I'm scanning (e.g. HP5+ ) which does NOT include orientation or crop and have another two styles which include the orientation and the applicable crops for both landscape and portrait orientation. That way I can apply the crop style first and afterwards process all scans the same way. Hope that helps @guigri

Copy link

github-actions bot commented Apr 4, 2024

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

@ralfbrown
Copy link
Collaborator

The underlying issue is that the crop module's parameters are merely what percentage to remove from each side of the image it is given, followed by forcing the crop back to the specified aspect ratio if not "freehand". But it has no knowledge of rotation applied by the orientation module...

You can work around this by making a custom module order which puts orientation after crop.

Copy link

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity reproduce: confirmed a way to make the bug re-appear 99% of times has been found scope: DAM managing files, collections, archiving, metadata, etc. scope: image processing correcting pixels
Projects
None yet
Development

No branches or pull requests

6 participants