Batch Queue Manager: Save modified images the way image editor does
Gilles Caulier
caulier.gilles at gmail.com
Wed Nov 9 18:00:25 GMT 2016
Hi,
The BQM use same settings than editor when versionning options are enabled.
This must give the same result on album icon view when image are processed.
Can you run digiKam on a console and list debug statements for both
operations (editor and BQM), when you process one image in same album ?
Gilles Caulier
2016-11-08 13:41 GMT+01:00 <neinei at gmx.net>:
> Hi there,
> perhaps my issue was not that clear in my original posting. So I try it
> again with different word.
>
> When I process an image in image editor in digiKam 4.1.4 and I save it
> then I see only the modified version in album view. The original image is
> "hidden" below the modified version.
>
> When I built a batch process with the same image operations in Batch Queue
> Manager the resulting modified image is not on top of the original image in
> album view but besides of it. Therefore the result is two visible images in
> album view instead of the expected one (modified) image.
>
> How could I achieve the behavior as seen in the image editor in Batch
> Queue Manager?
>
> Thanks for a hint,
> NeiNei
>
>
>
>
> On 06.11.2016 17:58, NeiNei wrote:
>
>> Hi there,
>>
>> I built a batch process in Batch Queue Manager to apply some color
>> operations on the original jpg images. The modified pictures of tis
>> process are saved as [file]_1.jpg . In album view I see now side by side
>> two images:
>> -image_a.jpg (original)
>> -image_a_v1.jpg (modified by batch queue process)
>> Obviously, doubling the number of images bloats the album view.
>>
>> However, I expect here the same outcome as I would do the same color
>> operations in image editor. That is a stacked view where I only see the
>> current image (image_a_v1.jpg) and the original image is "hidden".
>> How could I achieve this behavior in Batch Queue Manager?
>>
>>
>>
>> Thanks for a hint in advance,
>> NeiNei
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20161109/c80c6be0/attachment.html>
More information about the Digikam-users
mailing list