Peter Harde writes:
> The modules are grouped. Selecting the group symbolized by the "power switch"
> icon (most left) , the modules applied are shown in the order of the
> pixelpipe (bottom - first, top - last). The order can be modified by
> CTRL-SHIFT-dragging a module to a new position.
Ch
Peter Harde writes:
Hi Peter,
> did you compare the order of the modules you applied in the pixelpipe when the
> issue appeared and when it did not?
I did not compare the order of the modules. I might need some advice how
to do it. I never used to changing the order.
Anyway, I tried the follow
Hello!
Let me start with my thanks to Peter, Juha and István!
The crop and rotate module caused the problem. I deactivated all other
modules than retouch except the crop and rotate module. The problem is
still present then.
Starting with a duplicate of the original picture without modules I was
Hello,
I used the retouch module on a large picture (10165 x 4018). It did not
work as expected. At normal size pictures (16 Mpix) it worked as
expected. Using a shape at the large picture did not use the selected
area to be copied - it copied/healed from an area different than
the selection.
Sho
Germano Massullo writes:
> Il 23/04/2018 18:28, Maurizio Paglia ha scritto:
>> Well, downgraded lensfun from 0.3.2 to 0.3.1 and now all works!
> You probably should tell darktable maintainer to rebuild darktable
> against new lensfun version
I guess I had the same problem - asked for help here
Hello,
just upgraded darktable and recognized a problem with my setup: lens
correction module does not show the camera as well as it reports to
choose camera and lens manually.
Trying to choose the camera and lens does not show anything, just an
empty chooser, no camera or lens to choose.
Dar
Pascal Obry writes:
> About this... I have been able to build amdgpu-pro with 4.9 but it does
> not work!
I have the same problem, I want to use OpenCL but the opensource driver
(GalliumCompute) does not support image handling. It would be good if
the driver would be able to do so.
As this is
Roman Lebedev writes:
>> I there anything I can check to help tracking down the problem?
> I would recommend reporting this upstream, either to your distros
> bugzilla, or AMD?...
Thanks, I will do so.
Frank
___
darktable
