[Digikam-users] Re: digiKam and Kipi-plugins 1.8.0 released...

[Gilles Caulier]

Between 1.7.0 and 1.8.0, which lbkdcraw and libraw version you use ?
Go to help/component info for details

Gilles

2011/1/26 Stedtlund <falolaf at gmail.com>:
> Hi,
>
> Tested with a new config for a different user. Still same problem.
>
> /Anders
>
> 2011/1/26 Gilles Caulier <caulier.gilles at gmail.com>:
>> Check if problem is not in digiKam rc config file. rename it to .old
>> and try again (you need to reconfigure digiKam of course)
>>
>> Gilles Caulier
>>
>> 2011/1/26 Stedtlund <falolaf at gmail.com>:
>>> Hi,
>>>
>>> Reinstalled kipi-plugins 1.7.0, still problems. Then resinstalled
>>> digiKam 1.7.0, all back to normal again.
>>>
>>> /Anders
>>>
>>> 2011/1/26 Stedtlund <falolaf at gmail.com>:
>>>> Hi,
>>>>
>>>> I just dicovered the same behaviour here. digiKam 1.8.0 and kipi-plugins 1.8.0.
>>>>
>>>> Just tested with a crw-file. It's not just the EV correction, e.g.
>>>> brightness is broken  the same way.
>>>>
>>>> /Anders
>>>>
>>>> 2011/1/26 Remco Viëtor <remco.vietor at wanadoo.fr>:
>>>>> on Tuesday 25 January 2011, Gilles Caulier wrote:
>>>>>> Dear all digiKam fans and users!
>>>>>>
>>>>>> The digiKam development team is happy to release 1.8.0.
>>>>>>
>>>>>> For more details, see announcement on digikam.org:
>>>>>>
>>>>>> http://www.digikam.org/drupal/node/567
>>>>>> http://www.digikam.org/drupal/node/568
>>>>>>
>>>>> ...
>>>>>
>>>>> Thank you :)
>>>>> Metadata get read again in raw development, and I like having my Sony
>>>>> makernotes visible :)
>>>>>
>>>>> However, I hit another snag when developing RAW files (Sony ARW in my case):
>>>>> it usedd to be that if I added an EV correction, and then decided it was too
>>>>> much, the new (lower) correction was applied to the original RAW output (i.e.
>>>>> an image update after having lowered an EV correction was less luminous);
>>>>> with the 1.8.0 version, the second lower correction is applied to the already
>>>>> corrected image => severe over correction and no way to get back, except
>>>>> through an update in the RAW tab
>>>>> (say I start with a correction of +.3, then decide +.2 would have been better:
>>>>> in <=1.7.0 I ended up with a correction of +.2,
>>>>> in 1.8.0 I end up with a correction of +.5...)
>>>>>
>>>>> Any suggestion about where the bug is (Kipi, Digikam, elsewhere)?
>>>>>
>>>>> Regards
>>>>>
>>>>> Remco
>>>>> _______________________________________________
>>>>> Digikam-users mailing list
>>>>> Digikam-users at kde.org
>>>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>>>
>>>>
>>> _______________________________________________
>>> Digikam-users mailing list
>>> Digikam-users at kde.org
>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>