darktable-org / darktable-org/darktable

JPEG as starting point for raw files

Open
#19,102 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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 out of camera jpeg is usually really close to what I want but the raw takes quite a lot of effort to get there.

Describe the solution you'd like

To get the jpeg as starting point for the raw file, like rawtherapee has with auto-matched-curve.
This should probably be a separate mode than sigmoid, filmic and those things as starting point

Alternatives

I've personally often edited the jpegs as alternatives but that's not ideal.

Additional context

the kind of photography I do is mostly outdoor events and activities.

I encounter this is for every single picture I will edit.

This has also resulted in me shooting jpeg+raw but with this feature I wouldn't need the jpegs which would mean that I need less SD cards

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

The issue names no source files or tests. Start by reviewing how darktable currently provides sigmoid and filmic starting modes, then compare the requested behavior with RawTherapee's auto-matched-curve. Done should mean a raw file can use the camera JPEG as its starting point without requiring the JPEG to be retained.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.