| Summary: | Improve RAW development without to need constant updating | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | DrSlony <bugs> |
| Component: | Plugin-RawImport-Native | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | bugs, caulier.gilles, online, tpr |
| Priority: | NOR | ||
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
DrSlony
2010-01-10 00:08:38 UTC
This is how libraw run in background. All demosaicing need to be recomputed on RAW image (here a reduced version to speedup). i recommend to use libkdcraw from trunk, and to compile it with openmp to parallelize demosaicing operations. Gilles Caulier I mean't that the user has to keep moving the mouse back to the "update" button after every tweak. It could simply update the image after the cursor let's go of the slider. As for the need to re-demosaic after every tweak, this is IMHO a bad design. It makes working with raw files in showFoto cumbersome to the point of making one look for other software. Regarding white balance in particular, it is best to perform it before demosaicing to avoid color artifacts, yet this might be something you would want to do after demosaicing while working on the preview to speed it up. The color artifacts are not something one would care about while working on the preview - speed is what matters here. However, once the user presses "Import", then quality matters, so then it should perform white balance and all other relevant tweaks before demosaicing at the expense of time. I'm abandoning this report as I use digiKam for managing my photos but not for raw development. I let's open this report. We need to see if something can be done here... Gilles Caulier |