Another question about RAW processing

[gerlos]

Hello everyone!
Till now I shot a really small number of photos in RAW (I was mostly happy with my jpg images), so please understand that I have a very little experience with RAW...

OK, let's go to my question: I've shot quite a number of astronomical images with a friend, using his Canon 50D, different lenses and some of my telescopes. He said "RAW is better", I agreed, and now I have a lot of images needing editing, and mostly need to fine tune white balance (technically, we need to look for a G2 star in the shot and use it to set our white point).

I think digikam is very convenient when I need to organize and edit a lot of shots and I'd prefer to use it to work on them instead of using something else, like ufraw, but I found that I can't tweak RAW conversion parameters on a per-image basis, but only globally, from the main configuration window.

It seemed very strange to me, so I ask you: is there a way to change that parameters individually for each image?

Since we used different ISO speeds, obviously we'd like to change the noise reduction parameter for each image, and also to change chromatic aberration correction for each lens used. Any suggestion?

Thanks in advance
gerlos


--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2009/5/27 gerlos <[hidden email]>:
> Hello everyone!
> Till now I shot a really small number of photos in RAW (I was mostly happy with my jpg images), so please understand that I have a very little experience with RAW...
>
> OK, let's go to my question: I've shot quite a number of astronomical images with a friend, using his Canon 50D, different lenses and some of my telescopes. He said "RAW is better", I agreed, and now I have a lot of images needing editing, and mostly need to fine tune white balance (technically, we need to look for a G2 star in the shot and use it to set our white point).
>
> I think digikam is very convenient when I need to organize and edit a lot of shots and I'd prefer to use it to work on them instead of using something else, like ufraw, but I found that I can't tweak RAW conversion parameters on a per-image basis, but only globally, from the main configuration window.
>
> It seemed very strange to me, so I ask you: is there a way to change that parameters individually for each image?

Of course.

There are 2 way : Let's digiKam apply same demosaicing parameters +
auto post processing adjustments. This is the default option,
dedicated for beginneer.

For advanced users, just go to Editor Settings page, and set on " Use
RAW Import tool..." option. Now open RAW file in editor and enjoy.

http://www.flickr.com/photos/digikam/3562292552/sizes/o/in/pool-817639@N22/

Note : Work only with 0.9.5 or 0.10.x

>
> Since we used different ISO speeds, obviously we'd like to change the noise reduction parameter for each image, and also to change chromatic aberration correction for each lens used. Any suggestion?

Use Raw Import tool...

Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[gerlos]

On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
: > 2009/5/27 gerlos <[hidden email]>:

> > Hello everyone!
> > Till now I shot a really small number of photos in RAW (I was mostly happy with my jpg images), so please understand that I have a very little experience with RAW...
> >
> > OK, let's go to my question: I've shot quite a number of astronomical images with a friend, using his Canon 50D, different lenses and some of my telescopes. He said "RAW is better", I agreed, and now I have a lot of images needing editing, and mostly need to fine tune white balance (technically, we need to look for a G2 star in the shot and use it to set our white point).
> >
> > I think digikam is very convenient when I need to organize and edit a lot of shots and I'd prefer to use it to work on them instead of using something else, like ufraw, but I found that I can't tweak RAW conversion parameters on a per-image basis, but only globally, from the main configuration window.
> >
> > It seemed very strange to me, so I ask you: is there a way to change that parameters individually for each image?
>
> Of course.
>
> There are 2 way : Let's digiKam apply same demosaicing parameters +
> auto post processing adjustments. This is the default option,
> dedicated for beginneer.
>
> For advanced users, just go to Editor Settings page, and set on " Use
> RAW Import tool..." option. Now open RAW file in editor and enjoy.
>
> http://www.flickr.com/photos/digikam/3562292552/sizes/o/in/pool-817639@N22/

Great! I knew I was missing something! And, mostly, thank you for this really fast answer!
I'm thinking even more that what's matters is not only the software, but also the people "around" that software! :-)

Anyway, I skimmed the config dialog a couple of times looking for something similar, without noticing it... I guess I need to look better next time! It was written in the top line of the RAW settings page!

Sorry for the dumb question... :-)

thanks
gerlos

--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[gerlos]

On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
> For advanced users, just go to Editor Settings page, and set on " Use
> RAW Import tool..." option. Now open RAW file in editor and enjoy.

OK, I found the RAW import tool great!
I started working on some more "terrestrial" ;-) and easier images, like flowers near home, everything is good, but there's something that I didn't like and since I know all of you love constructive criticism ;-) I will tell you...

Just after I opened the RAW image in the editor, I wanted to tune its white balance. I expected to find a color picker tool like in the "other" white balance tool, but it wasn't there. OK, not a great problem, since I can use it after I imported the RAW image, but I really liked if it was there, so I can do it in just one step.

A second point: I'd liked to take the camera white balance as a starting point, and then tweak it. But I've seen that when I choose "camera" as method, the temperature and green sliders are locked, and I cannot change them. I'm sure there is a good reason for this behaviour, but, another time, I'd expected that I could change them and as I did it the method automatically changed to "manual". Same thing for the other methods different from "manual".
The important thing it's missing imho is that I can't see the values of temperature and green from the camera, so when I want to change them manually I have to start from scratch.

Another thing I didn't like is that when I've changed something in the "post processing" tab, and go back to the "raw decoding" tab and change something and click "update", I find that my changes in the "post processing" tab are lost, and I have to tweak them again. I'd preferred very much if they still were there as I leave them.

Why during RAW import is the zoom drop down menu in the toolbar locked? When I was trying to correct the chromatic aberration I wanted to zoom in to 100% and the only way to do it was click many times on the "zoom in" icon on the toolbar. The same when you want to zoom out back to fit window. The only commands I can use are "zoom in" and "zoom out", any other zoom option in the menu is disabled.

Last thing (no more RAW import tool, just see this thing and reported it): when I choose the "Gray" theme of Digikam, it's almost impossible to use the curve tool, since the color of the curve is the same of the histogram, and you can't see the curve.

hope you won't hate me :-)

regards
gerlos


--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2009/5/28 gerlos <[hidden email]>:

> On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
> : > 2009/5/27 gerlos <[hidden email]>:
>> > Hello everyone!
>> > Till now I shot a really small number of photos in RAW (I was mostly happy with my jpg images), so please understand that I have a very little experience with RAW...
>> >
>> > OK, let's go to my question: I've shot quite a number of astronomical images with a friend, using his Canon 50D, different lenses and some of my telescopes. He said "RAW is better", I agreed, and now I have a lot of images needing editing, and mostly need to fine tune white balance (technically, we need to look for a G2 star in the shot and use it to set our white point).
>> >
>> > I think digikam is very convenient when I need to organize and edit a lot of shots and I'd prefer to use it to work on them instead of using something else, like ufraw, but I found that I can't tweak RAW conversion parameters on a per-image basis, but only globally, from the main configuration window.
>> >
>> > It seemed very strange to me, so I ask you: is there a way to change that parameters individually for each image?
>>
>> Of course.
>>
>> There are 2 way : Let's digiKam apply same demosaicing parameters +
>> auto post processing adjustments. This is the default option,
>> dedicated for beginneer.
>>
>> For advanced users, just go to Editor Settings page, and set on " Use
>> RAW Import tool..." option. Now open RAW file in editor and enjoy.
>>
>> http://www.flickr.com/photos/digikam/3562292552/sizes/o/in/pool-817639@N22/
>
> Great! I knew I was missing something! And, mostly, thank you for this really fast answer!
> I'm thinking even more that what's matters is not only the software, but also the people "around" that software! :-)
>
> Anyway, I skimmed the config dialog a couple of times looking for something similar, without noticing it... I guess I need to look better next time! It was written in the top line of the RAW settings page!
>
> Sorry for the dumb question... :-)

In next digiKam version, when you start digiKam at the first time, it
ask you if you want to use RAW Import tool in your workflow :

http://farm4.static.flickr.com/3391/3490737082_c48be289c3_o.png

Gilles

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2009/5/28 gerlos <[hidden email]>:
> On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
>> For advanced users, just go to Editor Settings page, and set on " Use
>> RAW Import tool..." option. Now open RAW file in editor and enjoy.
>
> OK, I found the RAW import tool great!
> I started working on some more "terrestrial" ;-) and easier images, like flowers near home, everything is good, but there's something that I didn't like and since I know all of you love constructive criticism ;-) I will tell you...

No problem (:=))). When time permit, i try to respond to users...

>
> Just after I opened the RAW image in the editor, I wanted to tune its white balance. I expected to find a color picker tool like in the "other" white balance tool, but it wasn't there. OK, not a great problem, since I can use it after I imported the RAW image, but I really liked if it was there, so I can do it in just one step.

For this one code already exist in libraw, but libkdcraw interface
from kdegraphics need to be adjusted. still in my TODO list.

Also, preview widget used by RAW Import tool is not yet factorized
with all preview code from digiKam core (used by other editor tools).
It's planed to do it and to add picker color tool here.

>
> A second point: I'd liked to take the camera white balance as a starting point, and then tweak it. But I've seen that when I choose "camera" as method, the temperature and green sliders are locked, and I cannot change them. I'm sure there is a good reason for this behaviour, but, another time, I'd expected that I could change them and as I did it the method automatically changed to "manual". Same thing for the other methods different from "manual".

All other Demosaicing WB options than Manual are computed
automatically by libraw. you cannot adjust green factor...

> The important thing it's missing imho is that I can't see the values of temperature and green from the camera, so when I want to change them manually I have to start from scratch.

I'm not sure if libraw provide this meta-information as feedback. I
need to check it too in the future...

>
> Another thing I didn't like is that when I've changed something in the "post processing" tab, and go back to the "raw decoding" tab and change something and click "update", I find that my changes in the "post processing" tab are lost, and I have to tweak them again. I'd preferred very much if they still were there as I leave them.

Raw import to divised to 2 part :

1/ demosaicing using libraw algorithms.
2/ post processing using digiKam core algorithms

Both are 2/ do not depand of 1/ : you can adjust postprocessing
without to run demosaicing. digiKam store demosaiced image in memory.
Post processing is generally faster than demosicing. This is why it's
can be computed in live (with a delay of 500ms).

But of course if you change something in demosaicing settings all need
to be done again: 1/ and 2/. As demosaicing is really slow, an
"update" button is present in GUI.

Note : to compute faster demosaicing, you need to install libgomp and
recompile libkdcraw. demosaicied computation will be parallelized, but
you need at least double core CPU (:=)))

>
> Why during RAW import is the zoom drop down menu in the toolbar locked?  When I was trying to correct the chromatic aberration I wanted to zoom in to 100% and the only way to do it was click many times on the "zoom in" icon on the toolbar. The same when you want to zoom out back to fit window. The only commands I can use are "zoom in" and "zoom out", any other zoom option in the menu is disabled.

Hum, it's fixed in current implementation. Try to use mouse wheel instead.

>
> Last thing (no more RAW import tool, just see this thing and reported it): when I choose the "Gray" theme of Digikam, it's almost impossible to use the curve tool, since the color of the curve is the same of the histogram, and you can't see the curve.

Already reported in bugzilla. Still in my TODO list

>
> hope you won't hate me :-)

no (:=))

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[gerlos]

On giovedì 28 maggio 2009 10:41:15, Gilles Caulier wrote:
: > 2009/5/28 gerlos <[hidden email]>:
> > On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
> > Just after I opened the RAW image in the editor, I wanted to tune its white balance. I expected to find a color picker tool like in the "other" white balance tool, but it wasn't there. OK, not a great problem, since I can use it after I imported the RAW image, but I really liked if it was there, so I can do it in just one step.
>
> For this one code already exist in libraw, but libkdcraw interface
> from kdegraphics need to be adjusted. still in my TODO list.

Nice!

>
> Also, preview widget used by RAW Import tool is not yet factorized
> with all preview code from digiKam core (used by other editor tools).
> It's planed to do it and to add picker color tool here.

Even nicer! ;-)

> > A second point: I'd liked to take the camera white balance as a starting point, and then tweak it. But I've seen that when I choose "camera" as method, the temperature and green sliders are locked, and I cannot change them. I'm sure there is a good reason for this behaviour, but, another time, I'd expected that I could change them and as I did it the method automatically changed to "manual". Same thing for the other methods different from "manual".
>
> All other Demosaicing WB options than Manual are computed
> automatically by libraw. you cannot adjust green factor...
>
> > The important thing it's missing imho is that I can't see the values of temperature and green from the camera, so when I want to change them manually I have to start from scratch.
>
> I'm not sure if libraw provide this meta-information as feedback. I
> need to check it too in the future...

I understand.
I suppose that if we knew these things from libraw, one could expose in the interface the computed WB options, and let the user tweak them, isn't it? The manual change in the sliders could trigger a change of WB setting method, from automatic to manual. Hope it will be possible some day...

>
> >
> > Another thing I didn't like is that when I've changed something in the "post processing" tab, and go back to the "raw decoding" tab and change something and click "update", I find that my changes in the "post processing" tab are lost, and I have to tweak them again. I'd preferred very much if they still were there as I leave them.
>
> Raw import to divised to 2 part :
>
> 1/ demosaicing using libraw algorithms.
> 2/ post processing using digiKam core algorithms
>
> Both are 2/ do not depand of 1/ : you can adjust postprocessing
> without to run demosaicing. digiKam store demosaiced image in memory.
> Post processing is generally faster than demosicing. This is why it's
> can be computed in live (with a delay of 500ms).

Fast enough for me!

>
> But of course if you change something in demosaicing settings all need
> to be done again: 1/ and 2/. As demosaicing is really slow, an
> "update" button is present in GUI.

I see... using more the interface, I've seen that only the changes in the post-processing curve are lost. The setting of the sliders don't change. Another time, it was my fault... I always overlook these sliders and go fast to the curve tool!

> Note : to compute faster demosaicing, you need to install libgomp and
> recompile libkdcraw. demosaicied computation will be parallelized, but
> you need at least double core CPU (:=)))

Unfortunately, no dual core near here! :-( I'm still on a single core Pentium 4 @ 2.6 GHz, asking myself if I could do the same things on ms windows without changing the hardware... ;-)

> > Why during RAW import is the zoom drop down menu in the toolbar locked?  When I was trying to correct the chromatic aberration I wanted to zoom in to 100% and the only way to do it was click many times on the "zoom in" icon on the toolbar. The same when you want to zoom out back to fit window. The only commands I can use are "zoom in" and "zoom out", any other zoom option in the menu is disabled.
>
> Hum, it's fixed in current implementation. Try to use mouse wheel instead.

Wow, you people are faster than complains! ;-)
I tried with the mouse wheel here and there, but where should I use it? Nothing happens. Anyway, I think I could wait for digikam 0.11... and I couldn't I will compile it from svn!

> > Last thing (no more RAW import tool, just see this thing and reported it): when I choose the "Gray" theme of Digikam, it's almost impossible to use the curve tool, since the color of the curve is the same of the histogram, and you can't see the curve.
>
> Already reported in bugzilla. Still in my TODO list

I was sure someone else said it before!

regards
gerlos


--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2009/5/29 gerlos <[hidden email]>:

> On giovedì 28 maggio 2009 10:41:15, Gilles Caulier wrote:
> : > 2009/5/28 gerlos <[hidden email]>:
>> > On mercoledì 27 maggio 2009 21:04:29, Gilles Caulier wrote:
>> > Just after I opened the RAW image in the editor, I wanted to tune its white balance. I expected to find a color picker tool like in the "other" white balance tool, but it wasn't there. OK, not a great problem, since I can use it after I imported the RAW image, but I really liked if it was there, so I can do it in just one step.
>>
>> For this one code already exist in libraw, but libkdcraw interface
>> from kdegraphics need to be adjusted. still in my TODO list.
>
> Nice!
>
>>
>> Also, preview widget used by RAW Import tool is not yet factorized
>> with all preview code from digiKam core (used by other editor tools).
>> It's planed to do it and to add picker color tool here.
>
> Even nicer! ;-)
>
>> > A second point: I'd liked to take the camera white balance as a starting point, and then tweak it. But I've seen that when I choose "camera" as method, the temperature and green sliders are locked, and I cannot change them. I'm sure there is a good reason for this behaviour, but, another time, I'd expected that I could change them and as I did it the method automatically changed to "manual". Same thing for the other methods different from "manual".
>>
>> All other Demosaicing WB options than Manual are computed
>> automatically by libraw. you cannot adjust green factor...
>>
>> > The important thing it's missing imho is that I can't see the values of temperature and green from the camera, so when I want to change them manually I have to start from scratch.
>>
>> I'm not sure if libraw provide this meta-information as feedback. I
>> need to check it too in the future...
>
> I understand.
> I suppose that if we knew these things from libraw, one could expose in the interface the computed WB options, and let the user tweak them, isn't it? The manual change in the sliders could trigger a change of WB setting method, from automatic to manual. Hope it will be possible some day...
>
>>
>> >
>> > Another thing I didn't like is that when I've changed something in the "post processing" tab, and go back to the "raw decoding" tab and change something and click "update", I find that my changes in the "post processing" tab are lost, and I have to tweak them again. I'd preferred very much if they still were there as I leave them.
>>
>> Raw import to divised to 2 part :
>>
>> 1/ demosaicing using libraw algorithms.
>> 2/ post processing using digiKam core algorithms
>>
>> Both are 2/ do not depand of 1/ : you can adjust postprocessing
>> without to run demosaicing. digiKam store demosaiced image in memory.
>> Post processing is generally faster than demosicing. This is why it's
>> can be computed in live (with a delay of 500ms).
>
> Fast enough for me!
>
>>
>> But of course if you change something in demosaicing settings all need
>> to be done again: 1/ and 2/. As demosaicing is really slow, an
>> "update" button is present in GUI.
>
> I see... using more the interface, I've seen that only the changes in the post-processing curve are lost. The setting of the sliders don't change. Another time, it was my fault... I always overlook these sliders and go fast to the curve tool!
>
>> Note : to compute faster demosaicing, you need to install libgomp and
>> recompile libkdcraw. demosaicied computation will be parallelized, but
>> you need at least double core CPU (:=)))
>
> Unfortunately, no dual core near here! :-( I'm still on a single core Pentium 4 @ 2.6 GHz, asking myself if I could do the same things on ms windows without changing the hardware... ;-)
>
>> > Why during RAW import is the zoom drop down menu in the toolbar locked?  When I was trying to correct the chromatic aberration I wanted to zoom in to 100% and the only way to do it was click many times on the "zoom in" icon on the toolbar. The same when you want to zoom out back to fit window. The only commands I can use are "zoom in" and "zoom out", any other zoom option in the menu is disabled.
>>
>> Hum, it's fixed in current implementation. Try to use mouse wheel instead.
>
> Wow, you people are faster than complains! ;-)
> I tried with the mouse wheel here and there, but where should I use it? Nothing happens.

move the mouse over the preview and turn wheel. It must zoom.

To pan, there is a railway on the right bottom corner of preview (as
gimp). Press button and move red rectangle where you want to pan
preview, as in this screenshot :

http://farm3.static.flickr.com/2464/3573255820_4c6b8f5ac3_o.png

Look also settings view on the right : we use an expander box to host
settings group (as Aperture or RawTherapy). It more easy to see more
than group at the same time and more easy to use than the standard
QTollBox from Qt4 (Usability issue)


Anyway, I think I could wait for digikam 0.11... and I couldn't I will
compile it from svn!

It will be 1.0.0 (:=)))

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[gerlos]

On venerdì 29 maggio 2009 06:18:13, Gilles Caulier wrote:
: > 2009/5/29 gerlos <[hidden email]>:

> > On giovedì 28 maggio 2009 10:41:15, Gilles Caulier wrote:
> > : > 2009/5/28 gerlos <[hidden email]>:
> >> > Why during RAW import is the zoom drop down menu in the toolbar locked?  When I was trying to correct the chromatic aberration I wanted to zoom in to 100% and the only way to do it was click many times on the "zoom in" icon on the toolbar. The same when you want to zoom out back to fit window. The only commands I can use are "zoom in" and "zoom out", any other zoom option in the menu is disabled.
> >>
> >> Hum, it's fixed in current implementation. Try to use mouse wheel instead.
> >
> > Wow, you people are faster than complains! ;-)
> > I tried with the mouse wheel here and there, but where should I use it? Nothing happens.
>
> move the mouse over the preview and turn wheel. It must zoom.

No, it doesn't (just with the wheel). But I thought that it needed some modifier key, and discovered that it works if I turn the wheel when pressing the CTRL key, like in gwenview (but there, when you press Ctrl while the pointer is on the preview, the pointer icon changes to a magnifier lens, a nice hint).
So another time, thanks for your hint!

>
> To pan, there is a railway on the right bottom corner of preview (as
> gimp).

Knew it, and love it, it's very useful. It's nice that good features are somehow "standardized" between similar software in gnu/linux!

> Look also settings view on the right : we use an expander box to host
> settings group (as Aperture or RawTherapy). It more easy to see more
> than group at the same time and more easy to use than the standard
> QTollBox from Qt4 (Usability issue)

Nice work!

But playing with the sidebar and with the railway, I've seen that when I change the width of the sidebar, the railway icon disappears from the right bottom corner, and I can't use it to pan any more. To restore it I've seen that I have to change the zoom clicking on the icons on the toolbar, for example.

> Anyway, I think I could wait for digikam 0.11... and I couldn't I will
> compile it from svn!
>
> It will be 1.0.0 (:=)))

It's just a number, but it means a lot of things! Great!
You're almost convincing me to get the latest source code!

regards
gerlos

--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Am Donnerstag 28 Mai 2009 10:41:15 schrieb Gilles Caulier:

> Raw import to divised to 2 part :
>
> 1/ demosaicing using libraw algorithms.
> 2/ post processing using digiKam core algorithms
>
> Both are 2/ do not depand of 1/ : you can adjust postprocessing
> without to run demosaicing. digiKam store demosaiced image in memory.
> Post processing is generally faster than demosicing. This is why it's
> can be computed in live (with a delay of 500ms).
>
> But of course if you change something in demosaicing settings all need
> to be done again: 1/ and 2/. As demosaicing is really slow, an
> "update" button is present in GUI.
>
> Note : to compute faster demosaicing, you need to install libgomp and
> recompile libkdcraw. demosaicied computation will be parallelized, but
> you need at least double core CPU (:=)))

So if it benefits from parallelization, why not using the GPU to accelerate
the process? I assume it then would be a lot faster. Are there any plans to
implement this in the medium term?
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andreas Weigl]

Hi

Am Thursday 28 May 2009 schrieb gerlos:
> Anyway, I skimmed the config dialog a couple of times looking for something
> similar, without noticing it... I guess I need to look better next time! It
> was written in the top line of the RAW settings page!
>
> Sorry for the dumb question... :-)

There are no dumb questions, only dumb answers ...

I had to search for some time to find out how to use the raw import tool.
To be honest, I find it strange that you can only use the raw import tool if
you change the behaviour of the image editor.

Why not have it in the import tab, so I could say in my editor options to not
use the import tool but when I want to just go to the "Import" menu and open
it via the raw import tool.

Andreas

--
My Public GPG Key: http://www.silicoids-world.de/gpg.asc
Join Xing: http://www.xing.com/go/invite/7217885.c75a68

"I still believe in God, but God no longer believes in me"
    [Andrew Eldritch, singer of the Sisters of Mercy]

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2009/5/30 Tobias Schula <[hidden email]>:

> Am Donnerstag 28 Mai 2009 10:41:15 schrieb Gilles Caulier:
>
>> Raw import to divised to 2 part :
>>
>> 1/ demosaicing using libraw algorithms.
>> 2/ post processing using digiKam core algorithms
>>
>> Both are 2/ do not depand of 1/ : you can adjust postprocessing
>> without to run demosaicing. digiKam store demosaiced image in memory.
>> Post processing is generally faster than demosicing. This is why it's
>> can be computed in live (with a delay of 500ms).
>>
>> But of course if you change something in demosaicing settings all need
>> to be done again: 1/ and 2/. As demosaicing is really slow, an
>> "update" button is present in GUI.
>>
>> Note : to compute faster demosaicing, you need to install libgomp and
>> recompile libkdcraw. demosaicied computation will be parallelized, but
>> you need at least double core CPU (:=)))
>
> So if it benefits from parallelization, why not using the GPU to accelerate
> the process? I assume it then would be a lot faster. Are there any plans to
> implement this in the medium term?

This can be done only in LibRaw. Please report your wish to www.libraw.org

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users