Project

General

Profile

Bug #8304

Artifacts on all exports with opencl

Added by Ulrich Pegelow over 9 years ago. Updated over 9 years ago.

Status:
Fixed
Priority:
High
Assignee:
-
Category:
General
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

This relates to current git version of darktable from 12-17-2010 and started to appear with post-0.7.

All exports (jpg, tiff, ...) have some surrealistic artifacts like the one attached. In contrast darktable version 0.7.1 is working fine for me.

Switching opencl off during compile solves the export issue but leads of course to a much lower performance.

Running darktable with '-d opencl' does not give any indication of errors. A sample output is attached.

My system: openSUSE 11.3; kernel 2.6.37; Nvidia GeForce 8600GTS; Nvidia Driver 260.19.

History

#1 Updated by Ulrich Pegelow over 9 years ago

Some more observations found during playing around. The problem seems to be
related to the pixel size of the image (width x height). If I limit the size to
about 1000 or below the output is OK; at 2000 or above the problem occurs.

BTW: The on-board memory of my graphics card is 256MB.

#2 Updated by Johannes Hanika over 9 years ago

256 MB? that won't do at all.. :(

okay, we need:

- checks if an opencl device supports image2d objects

- checks if a device supports textures of appropriate size (i think 8k^2 should be minimum, but of course memory limits it)

- and while we're at it, also check a user option if opencl should be used.

#3 Updated by Johannes Hanika over 9 years ago

  • Status changed from New to Fixed

- image2d support is checked, dt now refuses to start on these drivers

- non-std image support is checked, generates a warning and continues (-d opencl)

- the option is --disable-opencl (pass to dt at runtime)

Also available in: Atom PDF

Go to top