Project

General

Profile

Bug #11873

Unable to export as uncompressed 16 bit TIFF from an Adobe RGB Canon RAW image on Windows 10

Added by Rodrigo Guerreiro over 1 year ago. Updated about 1 year ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
12/21/2017
Due date:
% Done:

0%

Affected Version:
2.4.0rc2
System:
Windows
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I've tested a sRGB Canon RAW and the export runs fine. But with an Adobe RGB Canon RAW file it simply mentions that it can't export. I've tried the same RAW on the 2.2.5 Linux version and it runs with no issue.

I've attached the RAW file.

_MG_8900.CR2 (16.3 MB) Rodrigo Guerreiro, 12/21/2017 11:01 PM


Related issues

Duplicated by darktable - Bug #11967: TIF export error Duplicate 01/24/2018

Associated revisions

Revision dbccb8c2
Added by Tobias Ellinghaus about 1 year ago

Windows Fix TIFF with non-ASCII filenames

This should fix both reading and writing those files. I wished that
TIFFOpenW was mentioned in any documentation.

Fixes #11967
Fixes #11873

Revision f0ae62e7
Added by Tobias Ellinghaus about 1 year ago

Windows Fix TIFF with non-ASCII filenames

This should fix both reading and writing those files. I wished that
TIFFOpenW was mentioned in any documentation.

Fixes #11967
Fixes #11873

(cherry picked from commit dbccb8c2e69b4ba39d267b0b1fd5d910f08476c9)

History

#1 Updated by Tobias Ellinghaus over 1 year ago

  • Status changed from New to Incomplete
  • % Done changed from 0 to 20

I just tried on Windows 7 and your CR2 exported fine to uncompressed 16bit TIFF. It took quite long, but that's another bug. Do you have non-ASCII characters in your export filename or path? TIFF export doesn't support that.

#2 Updated by Rodrigo Guerreiro over 1 year ago

I had the image on a folder which the name has some accents ("Pôr-do-sol"). I've tested the same export on a folder named "test" and it worked. So probably is that non-ASCII characters issue you mentioned.

What is odd, and as I mentioned previously, I tested the same image, on the same folder (with the same name, accents and all), on the 2.2.5 darktable Ubuntu version, and it worked. I'm using the Bash on Ubuntu on Windows feature that Windows 10 has, to also run darktable. I know that isn't supported but I had zero issues with it. Does the TIFF export module on the Linux version support non-ASCII characters?

#3 Updated by Tobias Ellinghaus over 1 year ago

  • Status changed from Incomplete to Closed: invalid
  • % Done changed from 20 to 0

I am surprised that you could open that file in the first place. LibTIFF has a bug where on Windows it's not supporting those filenames. There isn't much we can do about it.

#4 Updated by Roman Lebedev over 1 year ago

  • Target version set to 2.4.0

#5 Updated by Roman Lebedev about 1 year ago

  • Target version changed from 2.4.0 to 2.6.0

#6 Updated by Roman Lebedev about 1 year ago

  • Duplicated by Bug #11967: TIF export error added

Also available in: Atom PDF