[Digikam-devel] [digikam] [Bug 318726] Some BQM tools in a workflow don't restore (all) parameters properly

[Jan Wolter]

https://bugs.kde.org/show_bug.cgi?id=318726

--- Comment #4 from Jan Wolter <jan.wolter at upb.de> ---
I tested the remaining BQ-Tools and found the following errors, problems, or
suggestions for improvements:

LOCAL-CONTRAST:
Add local contrast tool to the workflow and assign values to the "Power" and
"Blur" parameters of the four stages. Then save the workflow, close digikam and
restart it afterwards. When you load the saved workflow, all "Power" and "Blur"
parameters are set to 0, unless they are saved in the queue.xml in the correct
way.

UNSHARP-MASK:
Use the unsharp mask tool in a workflow and assign to the "Radius" parameter a
value with a decimal place unequal 0 (e.g. 2,8). Then start processing the
workflow and look up the Xmp.digiKam.ImageHistory tag in the meta data of the
processed image. There you see an entry like this: <param name="radius"
value="2"/>, where decimal position is cropped. Using the unsharp mask tool in
the image editor, this error is only noticeable.

RESIZE:
Add resize tool to workflow, use custom length and choose a length with slider.
Save the workflow, close digikam and restart it. When you reload the workflow,
the slider displays in any case length "10" unless you have chosen another
value before.
Furthermore, the resize tool in BQ is less powerful than the resize tool in the
image editor. In BQ it is not possible to resize images to another aspect ratio
then the actual image's aspect ratio.

I tested Martins Problem from Comment #2 as well and can say that workflows
using the crop and resize tool are saved correctly to the queue.xml

I'm quite sure that the three errors in local contrast, unsharp mask and resize
tool in addition to the errors in the curves adjust, b&w, and lens
auto-correction tools (reported by the comment #3) are the last errors
concerning BQ tools. I tested really a lot, by defining different workflows,
comparing the saved queue.xml as well as the XMP image history in the processed
image. I would be really happy, when the last six problems get fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.