rast works
correctly with OpenCL from AMDGPU-PRO and open source amdgpu
drivers! Much simpler. Job done.
Thanks everyone.
Forwarded Message
Subject:
Re: [darktable-dev] Loca
Ah, I didn't know that, thanks. I'll have a look at
3.2.1 and read the posts about it and then decide what to do.
On 16/08/2020 17:27, Andreas Schneider
wrote:
On Friday, 14 August 2020 20:37:29 CEST Dusenberg wrote:
Thanks for
Hi,
Am 15.08.20 um 13:21 schrieb Dusenberg:
[..] I shouldn't be seeing the problem as it only affects the/open
source/ OpenCL package running with the/open source/ amdgpu driver. Have
I got this right?
Yes. There have been problems with ROCm, darktable and visual artifacts
for years. AMDGPU-
On Friday, 14 August 2020 20:37:29 CEST Dusenberg wrote:
> Thanks for the prompt reply Andreas.
There is a workaround for the issue in 3.2.1. So you can just use ROCm without
any problems with darktable 3.2.1.
___
darktabl
@Sturm Flut: Thanks for
clarifying.
Now I know there's a solution, I can live with the slower
performance of running OpenCL disabled on a new workstation while
I work out how to make the
switch from using the open source amdgpu driver to the
On 8/15/20 7:21 AM, Dusenberg wrote:
> Thanks for your time Šarūnas and Germano.
>
> This has got me worried because my workstation has the OpenCL from the
> AMDGPU-PRO version installed (but nothing else from it) and I'm using
> the open source amdgpu driver package. My reading of the bug analyse
Thanks for your time Šarūnas and Germano.
This has got me worried because my workstation has the OpenCL from
the AMDGPU-PRO version installed (but nothing else from it) and
I'm using the open source amdgpu driver package. My reading of the
bug analyses done
On 8/14/20 2:37 PM, Dusenberg wrote:
> Thanks for the prompt reply Andreas.
> 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
> workarou
Il 14/08/20 20:37, Dusenberg ha scritto:
> Thanks for the prompt reply Andreas.
> 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
> work
Thanks for the prompt reply Andreas.
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
It's AMD opencl bug. There is a workaround in darktable 3.2.1 though -
https://github.com/darktable-org/darktable/pull/5836 check if it helps you!
czw., 13 sie 2020 o 14:53 Andreas Schneider napisał(a):
> On Thursday, 13 August 2020 14:50:02 CEST Dusenberg wrote:
> > I recently migrated to a new
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 loca
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 u
13 matches
Mail list logo
