RAW editing
Locked
12
12
 
|
On Lørdag den 21. januar 2012, Remco Viëtor wrote:
> Also, don't forget that Digikam's RAW import tool is exactly that, RAW > import. This means that a lot of the processing that is done on the > developed image is NOT in the RAW import tool (sharpening, saturation, > local contrast etc.). From what I've seen, darktable and others don't have > this sharp separation between RAW development and editing. So, what you > think of as RAW development in darktable is RAW development + editing in > DK... This is exactly what I appreciate about the digikam way. But it have som drawbacks, first it requires that you can actually figure out how to get a nice image, and then you have to (re)do that all the time. This is where, for me, being able to save some recipes would come in handy, and obviously some default recipes would help many users getting started. -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by S. Burmeister
On Lørdag den 21. januar 2012, Sven Burmeister wrote:
> Am Samstag, 21. Januar 2012, 10:14:32 schrieb gerlos: > > Il giorno 20/gen/2012, alle ore 18.50, Anders Lund ha scritto: > > > On Fredag den 20. januar 2012, Dr. Martin Senftleben wrote: > > > My most missed feature is to be able to apply a set of operations to > > > other images, or to the same one again, reimporting the raw file. > > > (*hint *hint). > > > > Something like "Lift/Stamp metadata and Adjustments" commands in Apple > > Aperture, I guess... > > > > It would be nice to have them, indeed. > > It would be nice indeed to have the possibility of saving tool-chains from > the editor and apply them to other pictures or at least batch queue > manager tool- chains. > > The latter has been long requested. > > https://bugs.kde.org/show_bug.cgi?id=251126 I voted for that :) > But I think digikam simply does not want to be a raw utility and leaves > this to other apps specialising in that area. AFAIK it's not even possible > to have the demosaicing tool in bqm and apply the default settings, > because they ignore the luminosity curve and all post-processing > parameters. Well, in my (current) workflow digikam *is* a raw utility. And I really think it is great to be able to convert directly into the editor. I agree very much that raw conversion should be part of the bqm, that would be a great improvement. -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Anders Lund
2012/1/21 Anders Lund <[hidden email]>:
> On Lørdag den 21. januar 2012, Sven Burmeister wrote: >> Am Samstag, 21. Januar 2012, 11:10:54 schrieb Anders Lund: >> > That is absolutely right. But I don't see darktable doing a better job >> > than digikam, albeit a different one. So far, I see darktable images >> > being a bit more saturated/vivid than the preview, while digikam goes a >> > bit the other way. (I use a canon EOS 30D) >> > >> > The problem must relate to knowing how the camera jpeg is created, maybe >> > that knowledge is part of what you pay for using a commercial tool? >> >> http://www.darktable.org/usermanual/ch03s04s13.html.php has defaults that >> work a lot better than the digikam defaults which do not apply any base >> curve. > > Yes, and maybe darktable applies a few more corrections? > >> >> Another example, set digikam to reconstruct the highlights and then do the >> same in darktable. Digikam produces a dark image while darktable does not. > > I guess darktable have a curve to compensate - at least that is what I do > using digikam. I had to figure that out, of course, and create some presets. > > Maybe we can agree that digikam is missing some pr camera defaults to apply, > and compensation for highlight rebuilding. > > It is interresting to identify how digikam could/should be improved, as I > prefer digikams UI to darktable. digiKam use libraw in background, through libkdcraw. libraw as introduced curve management, but we don't have supported this feature yet in libkdcraw. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Remco Viëtor
2012/1/21 Remco Viëtor <[hidden email]>:
> On Saturday 21 January 2012 11:29:06 Martin wrote: >> Am 21.01.2012 11:10, schrieb Anders Lund: >> > On Lørdag den 21. januar 2012, gerlos wrote: >> [...] >> >> > That is absolutely right. But I don't see darktable doing a better job >> > than digikam, albeit a different one. So far, I see darktable images >> > being a bit more saturated/vivid than the preview, while digikam goes a >> > bit the other way. (I use a canon EOS 30D) >> >> For me the main difference here is that darktable does a constant job. >> If I have a series of pictures the results are predictable (more than >> with digikams raw processing). Esp. if you enables some of the automatic >> tools the results are sometimes very good but sometimes next to useless. >> And then it is very hard to get a pleasing result with digikam's >> available settings. > > What settings do you use for the raw import (from 'settings', then 'Raw > decoding tab')? I tell it to always use the last option: 'Always open the Raw > Import tool...'). This, like other tools, keeps the settings from the previous > use. > > And, click the 'Update' button after a change to apply the changes. Don't use > the 'Use default' button, as it applies the defaults defined in the settings > dialog, and imports straight away. > > And I agree that raw decoding seems slow in Digikam, compared to e.g. > darktable; otoh, once you have a good preview, importing it is virtually > instantanuous. compile libkdcraw and libraw with OpenMP support. Install libgomp devel package, and look if demosaicing parallelization is supported in digiKam Help/Components Info dialog. As libkdcraw print a lots of debug message in the console, disabling debug in libkdcraw and enabling all speed-up optimization, will change your life with Raw import performance... Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Remco Viëtor
Am 21.01.2012 13:06, schrieb Remco Viëtor:
> On Saturday 21 January 2012 11:29:06 Martin wrote: >> Am 21.01.2012 11:10, schrieb Anders Lund: >>> On Lørdag den 21. januar 2012, gerlos wrote: >> [...] >> >>> That is absolutely right. But I don't see darktable doing a better job >>> than digikam, albeit a different one. So far, I see darktable images >>> being a bit more saturated/vivid than the preview, while digikam goes a >>> bit the other way. (I use a canon EOS 30D) >> >> For me the main difference here is that darktable does a constant job. >> If I have a series of pictures the results are predictable (more than >> with digikams raw processing). Esp. if you enables some of the automatic >> tools the results are sometimes very good but sometimes next to useless. >> And then it is very hard to get a pleasing result with digikam's >> available settings. > > What settings do you use for the raw import (from 'settings', then 'Raw > decoding tab')? I tell it to always use the last option: 'Always open the Raw > Import tool...'). This, like other tools, keeps the settings from the previous > use. I have this enabled. This does not help if I want to change the white balance after some days. In general I do some basic setup for my raw files and in a second run I do the fine tuning. > > And, click the 'Update' button after a change to apply the changes. Don't use > the 'Use default' button, as it applies the defaults defined in the settings > dialog, and imports straight away. > > And I agree that raw decoding seems slow in Digikam, compared to e.g. > darktable; otoh, once you have a good preview, importing it is virtually > instantanuous. To me digikams raw importer is really fast. darktable seems not to be faster here (Fedora 16). > > Also, don't forget that Digikam's RAW import tool is exactly that, RAW import. > This means that a lot of the processing that is done on the developed image is > NOT in the RAW import tool (sharpening, saturation, local contrast etc.). From > what I've seen, darktable and others don't have this sharp separation between > RAW development and editing. So, what you think of as RAW development in > darktable is RAW development + editing in DK... Yes, darktable is not only pure raw development. But if I sit down and work on my photos it matches my work flow. And as I said several times: If I need a different version of my raw file I can simply export the same photo once again into a different format and work on it, without the need to do the same stuff I did weeks ago once again. Martin _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Gilles Caulier-4
On Lørdag den 21. januar 2012, Gilles Caulier wrote:
> digiKam use libraw in background, through libkdcraw. > > libraw as introduced curve management, but we don't have supported > this feature yet in libkdcraw. I like the "yet", in the light of this discussion :) -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Dr. Martin Senftleben
I really haven´t the time to read the whole tread but maybe I have a
few useful thoughts
First of all if downloaded my camś pictures to the computer, than I use the jpegs out of cam in gwenview to compare and select which photoś I want to use. I set dk in settings to rebuild highlights on opening raw file I open the Raw file in editor I apply local contrast on the raw file I see if autocorrection does do any good sometimes a little curve adjustment after that color balance if needed (most of the time not) do a little bit saturation done Itś easy, it works great, never need any other software (except gimp once in a while) Good luck, have a nice day Rinus Op 20-01-12 07:02, Dr. Martin Senftleben schreef: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After the long discussion about jpg lossiness, I have tried some editing on the raw files, but I do not seem to be the person for that ;-) Ijust can't find the settings which are best to work on, or most helpful to improve an image. Is there some place where a workflow description can be found on improving an image based on the RAW data? I believe that would help me a lot. Regards Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8ZA5IACgkQUmmuY48ByEiMvQCfcG3X5JMp3lCk/x8PAJKJWJ5G 55QAn1s96Lu7QHVZQ13NBqDxCSzyDwPI =pODy -----END PGP SIGNATURE-----_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |