Project

General

Profile

Bug #8509

Broken resized images with max size != 0 x 0

Added by jetxee - over 8 years ago. Updated almost 8 years ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
General
Start date:
Due date:
% Done:

0%

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

Description

After recent pull from the git (few weeks after the previous one), I noticed that if max size is not "0x0", then the exported image is broken. See the files attached how it looks.

JPEG, PNG, TIFF are affected. PPM is not affected.

Didn't have time to bisect yet. The last FETCH_HEAD is b053b16fbe6511a38ad47c55ae86643d3b2601f8.

Build flags: CMAKE_BUILD_TYPE=Release, DBUSGLIB=OFF, DONT_USE_RAWSPEED=OFF, INSTALL_IOP_EXPERIMENTAL=OFF, INSTALL_IOP_LEGACY=OFF, USE_CAMERA_SUPPORT=ON, USE_DARKTABLE_PROFILING=ON, USE_GCONF_BACKEND=ON, USE_OPENCL=ON, USE_OPENMP=ON

History

#1 Updated by jetxee - over 8 years ago

Broken export example:

http://dl.dropbox.com/u/14110648/bugs/dt_export_maxsize_2400x2400.jpg

Exported image with max size = 0x0:

http://dl.dropbox.com/u/14110648/bugs/dt_export_maxsize_0x0.jpg

(this is also wrong, btw, I'll file a separate bug now)

#2 Updated by oliviertoulouse - over 8 years ago

jetxee, are you using opencl?

I tried various settings, and everything works for me, can you try the same picture/same parameters with last git, please?

#3 Updated by jetxee - over 8 years ago

can you try the same picture/same parameters with last git, please?

I cannot build the latest git right now, because after the merge of new keybindings dialog it depends on Gtk+ 2.22, and I am on Ubuntu LTS with Gtk 2.20. I didn't have time yet to build all the new dependencies from source.

Though, in 0.9 and in master builds just before the release I didn't experience this problem anymore.

are you using opencl?

My build uses USE_OPENCL=ON, but I don't know if it is actually used on my hardware (mobile ATI HD2400 with Open Source "radeon" driver).

#4 Updated by Simon Spannagel almost 8 years ago

Hi, you can use the command line option

darktable -d opencl

to check whether darktable really uses OpenCL in your case.

#5 Updated by Simon Spannagel almost 8 years ago

  • Target version changed from 1.0.3 to Candidate for next patch release

#6 Updated by Simon Spannagel over 7 years ago

  • Affected Version set to 0.9.3
  • Status changed from New to Closed: invalid

Hm, no answer for a year now. Since we didn't hear similar things about 1.0 OpenCL support I close this ticket as invalid.

Also available in: Atom PDF

Go to top