darktable-org / darktable-org/darktable

Leverage duplication for files created by "neural restore"

Open
#21,393 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity not planned
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is your feature request related to a problem? Please describe.

The new files created by the neural restore module appear as separate entities in the film roll despite being logically the duplicates of the original file. Comparing the results between them becomes clunky and has you search the collection. Their import time to the collection also changes which disrupts the workflow where you have your collection sorted by "import time". The new files aren't grouped together with the original despite logically belonging to the same group. Navigating multiple similar looking files (indistinguishable by the thumbnail) created by the module becomes clunky, it's difficult to tell which file belongs to which original and it takes a lot of time to see what tags/culling/etc has been applied to the original.

Describe the solution you'd like

Have the new files appear as duplicates to the original file.

Alternatives

Additional context

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.

Research direction

Start by locating the neural restore module and tracing how it creates and imports new files into the film roll. Check the existing duplicate and grouping behavior before deciding where the integration belongs. Done means restored files appear as duplicates of their originals, remain grouped with them, and preserve the expected collection workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-vision, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.