-
Notifications
You must be signed in to change notification settings - Fork 51
faq: add Q&A about dynamic range/highlight/HDR modes #269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
For the "very dull images" Q, can you please link to the section in the manual that explains about raw vs jpeg?
…On April 27, 2025 9:15:42 AM PDT, Ralf Brown ***@***.***> wrote:
Also (in separate commits if you want to cherry-pick) add a note about compression formats to the Q about unable to open, and change "Lightroom alternative" to "Lightroom replacement" as the latter is more accurate phrasing.
You can view, comment on, or merge this pull request online at:
#269
-- Commit Summary --
* add note about DRxxx/HLG/etc modes being very dark
* add note about compression formats
* alternative -> replacement
-- File Changes --
M content/about/faq.md (7)
-- Patch Links --
https://github.com/darktable-org/dtorg/pull/269.patch
https://github.com/darktable-org/dtorg/pull/269.diff
--
Reply to this email directly or view it on GitHub:
#269
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Did you have anything specific in mind? The only thing I could find about raw vs JPEG was the section linked by the existing previous question's answer (Why doesn't the raw image look like the JPEG). |
Yes, that's the one.
…On April 27, 2025 12:00:20 PM PDT, Ralf Brown ***@***.***> wrote:
ralfbrown left a comment (darktable-org/dtorg#269)
Did you have anything specific in mind? The only thing I could find about raw vs JPEG was the section linked by the existing previous question's answer (Why doesn't the raw image look like the JPEG).
--
Reply to this email directly or view it on GitHub:
#269 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
What would be the point in adding another link and having it in two successive answers, given that the manual section isn't addressing the camera's deliberate underexposure? |
Two successive answers in a row doesn't mean anything, this page is not end to end reading.
This FAQ groups well with that section. I'm not asking you to remove anything about the deliberate camera underexposure, but to add a related item.
…On April 27, 2025 10:02:08 PM PDT, Ralf Brown ***@***.***> wrote:
ralfbrown left a comment (darktable-org/dtorg#269)
What would be the point in adding another link and having it in two successive answers, given that the manual section isn't addressing the camera's deliberate underexposure?
--
Reply to this email directly or view it on GitHub:
#269 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
I specifically chose "alternative" since that's the term everyone seems to use when reporting on DT or comparing to LR. |
I also prefer alternative as replacement is exactly what we fight against new users. Darktable is not a drop-in replacement, it is very different and yes it can be an alternative. That being said I'm not an English native speaker :) |
I made the change to the question so that the answer to the question is specifically about not being a replacement, but rather an alternative. Added a more explicit statement of this at the start of the answer. |
Thinking about it, I would keep the original question, and change the beginning of the answer:
I'm actually planning to completely rewrite that entry, since I was never truly happy with it. |
@@ -92,7 +92,7 @@ In rare cases that might break other software accessing the camera though! If yo | |||
Yes, there are two libraries we heavily rely on: | |||
|
|||
* **exiv2** is used for reading metadata from image files. If something isn't shown correctly in the [image information](https://docs.darktable.org/usermanual/stable/en/module-reference/utility-modules/shared/image-information/) panel on the left side then please check with the command line tool `exiv2` and report any problems upstream on [their bug tracker](https://github.com/Exiv2/exiv2/issues) – there isn't much we can do to fix those things ourselves. | |||
* **lensfun** is used for lens correction. If the [lens correction](https://docs.darktable.org/usermanual/stable/en/module-reference/processing-modules/lens-correction/) module isn't showing your camera or lens, or a wrong one, then please report that to [those folks](https://github.com/lensfun/lensfun). | |||
* **lensfun** is used for lens correction. If the [lens correction](https://docs.darktable.org/usermanual/stable/en/module-reference/processing-modules/lens-correction/) module isn't showing your camera or lens, try running `lensfun-update-data` to get the newest lens database. If lens correction still does not show your camera/lens, or shows a wrong one, then please report that to [those folks](https://github.com/lensfun/lensfun). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not tell people to report stuff to lensfun. We should tell them how they can submit their lens if it is not supported, but often times it is exiv2 that doesn't map the lens name correctly (if the lens is supported by lensfun) and we don't want to burden them with those "bug reports".
Also (in separate commits if you want to cherry-pick) add a note about compression formats to the Q about unable to open, and change "Lightroom alternative" to "Lightroom replacement" as the latter is more accurate phrasing.