darktable-org / darktable-org/darktable

Lr sidecar files import: use of deprecated module crop and rotate leads to wrong display

Open
#16,200 23 comments 0 reactions 1 assignee View on GitHub

@TurboGit is already working on this.

Since Jul 18, 2026.

bug: pending difficulty: good first contribution priority: low scope: codebase
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Describe the bug

Hi,

When importing an Lr edited TIFF file as described here, it occurs that the deprecated module "crop and rotate" may be used which leads to some wrong display in the darkroom.

The following message is then displayed in the module itself:

this module is deprecated. please use the crop, orientation and/or rotate and perspective modules instead.

And when you turn off crop and rotate, you loose the following modules in the pipe...

This is an example of Lr edited TIFF file : https://www.swisstransfer.com/d/5db547a7-3e27-48f9-b6b0-992b7e579702
Corresponding XMP file : https://www.swisstransfer.com/d/6578b93a-b1e0-4f26-9f5d-0aa63661e955

Steps to reproduce
  1. import an image previously edited with Lr with its XMP sidecar file, where some cropping and/or rotation had been done
  2. switch to the darkroom to see the wrong display
  3. open the crop and rotate module to see the message
Expected behavior

dt don't use deprecated crop and rotate module

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.6

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?

None

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.