darktable-org / darktable-org/darktable

Nikon D1X .nef file appears like a negative

Open
#19,320 5 comments 0 reactions 1 assignee View on GitHub

@LebedevRI is already working on this.

Since Sep 11, 2025.

scope: camera support
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

I found out the problem is Nikon Capture was corrupting the .nef files. The solution is to use Exiftool to fix the raw file, but unfortunately ithat tool doesn't support the D1X. At any rate it is not a DarkTable bug.

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

When I import a .nef the image appears like a color negative. Here's a link to the file:

https://drive.google.com/file/d/1hJRP0IjZnhQ0Qs0waZ6JbwmOkErJ7dkT/view?usp=sharing

Here's link to the reddit discussion:
https://www.reddit.com/r/DarkTable/comments/1nddcnt/support_for_nikon_d1x/

I can't login to the community discussion because it won't send me a validation email. It was suggested that I use an IRC channel or Matrix. Not familiar with either, so I'm submitting here.

The file is not corrupt, happens with all the .nefs I've viewed so far, opens fine in Affinity Photo and Lightroom

Steps to reproduce

Add file to library
That's all you need to do.

Expected behavior

Display image correctly

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.2.1

What OS are you using?

Mac

What is the version of your OS?

Sequoia 15.6.1

Describe your system

MacBook Pro M1 Max

Are you using OpenCL GPU in darktable?

No

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.