What a pain, I use local laplacian a lot. The github threads say the AMDGPU-PRO drivers don't have this problem, so I'm wondering if I should replace the open source amdgpu driver with the PRO version as a workaround for the time being. Do you know if this is a realistic option for a non-dev user?
On 13/08/2020 13:53, Andreas Schneider
wrote:
On Thursday, 13 August 2020 14:50:02 CEST Dusenberg wrote:
I recently migrated to a new Linux workstation with OpenCL capability, and Darktable 3.0.2 from the OpenSUSE 15.1 distro repository. The Local Contrast Module (LC) is broken and produces ugly, extreme 'shading' and artifacts in local laplacian mode that makes it unusable. The problem manifests on viewing images previously developed on my old laptop with LC enabled (same DT version but no OpenCL) as well as developing on the workstation. Everything else in DT (and other apps) that I use in my workflow is working as normal on the workstation. OpenCL compiled and loaded with no errors. There are no runtime error messages, normal or with debug. Disabling OpenCL fixes the Local Contrast module and it works as expected. I've tried rebuilding locallaplacian.cl.bin, which again compiled and loaded without error, but the problem remains.Appears to a be bug in OpenCL code. Any ideas/help?
___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
