You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I cannot add my own pigment-based checker card to darktable.
Describe the solution you'd like
Half solution:
Move the .cht definitions out of colorchecker.h to textfiles (as a csv, json or .cht file) so everyone could add own color calibration cards by adding new files to the folder.
Full solution:
Add GUI color checker card editor. It could be usefull for the darktable-chart too.
PLUS:
Add button to run darktable-chart from main darktable app. (Usefull for flatpack version).
Alternatives
Now i need to edit the src/common/colorchecker.h file manually and recompile darktable. It is not possible due to #17854 issue.
The text was updated successfully, but these errors were encountered:
Dear @Donatzsky this is not the same case.
I'm a painter and I'm using high quality pigments with known LAB values.
I have access to the official x-rite color card and calibration tools. This is not about cheap chinese replacements. I just want to calibrate to different pigments that are not present on the common used color cards.
Is your feature request related to a problem? Please describe.
I cannot add my own pigment-based checker card to darktable.
Describe the solution you'd like
Half solution:
Move the .cht definitions out of colorchecker.h to textfiles (as a csv, json or .cht file) so everyone could add own color calibration cards by adding new files to the folder.
Full solution:
Add GUI color checker card editor. It could be usefull for the darktable-chart too.
PLUS:
Add button to run darktable-chart from main darktable app. (Usefull for flatpack version).
Alternatives
Now i need to edit the src/common/colorchecker.h file manually and recompile darktable. It is not possible due to #17854 issue.
The text was updated successfully, but these errors were encountered: