

Guess it will still take quite some time until someone fixes that for good…

If UFraw was forced to implement this workaround already few years ago, so I The billions of existing files out there.Īm Samstag, 30. Would be great, but 1) that won't happen and 2) GIMP still needs to recognize Well, if we could convince camera manufacturers to fix their file formats that Or is this something that needs to be fixed by the camera manufacturers? Is this something that needs to be fixed in GIMP?

Mitch has been working on the magic part last week already, so it's currently Just from curiosity, who is the "someone" who should fix loading of raw Personally prefer to keep the behaviour broken to make someone fix it for This issue is easily handled by other RAW loading plug-ins by My suggestion: implement the workaround as soon as possible, and then identify the person that should implement a proper fix into GIMP and try to convince her/him to do the job. If UFraw was forced to implement this workaround already few years ago, so I guess it will still take quite some time until someone fixes that for good… meanwhile you will be flooded by comments from unhappy users because this new DT plugin code already made it into PPAs that lots of people use. Personally prefer to keep the behaviour broken to make someone fix it for real. Sure, you can work around that, but it's not a proper fix, is it? So I tiff extension and running the normal GIMP This issue is easily handled by other RAW loading plug-ins by intercepting Here is an example from the PhotoFlow plug-in, which was originally derived from UFraw: tiff extension and running the normal GIMP loading procedure in such cases. This issue is easily handled by other RAW loading plug-ins by intercepting the input files with. Maybe you can provide a sample file to bugzilla so someoneĬan have a look at properly supporting them in GIMP. Some older TIF files with many Photoshop layers. I do remember having trouble opening some TIF files in GIMP before, I think The lower left hand corner of the open dialog. Until that is fixed you have to manually select the TIFF loader in Right now the code wrongly assumes that your TIFF is a NEF and sends it toĭarktable. However can't be reliably distinguished from TIFFs. (Canon was clever enough to have a unique magic for their files), other formats For CR2 that's not a big problem, there is a way to recognize them The problem is that most raw formats are TIFF files with someĮxtra data. This happens with some TIF filesīut not with all TIF files. launching darktable and upon exitingĮxporting the file to GIMP as 32-bit EXR. TIF files in GIMP, it uses the plug-in in the same fashion as if I was The plug-in works great in importing NEF to GIMP, but now when I open some
