Aktion in Digikam Version 7.6.0: Eine RAW-DNG-Bilddatei (aus Adobe Lightroom) wird mit Farbraumkonvertierung in sSRG IEC61966-2.1 (sRGB Profile.icc) + Konvertierung in TIFF erstellt. Problem: Die erstellte TIFF-Datei wird von der Applikation "Nikon NX Studio Ver.1.1.2 64bit" mit der folgenden Fehlermeldung abgelehnt: "Es wurde eine Datei gefunden, die nicht unterstützt wird. Die Operation wird abgebrochen". Im Vergleich dazu wurde die Konvertierung derselben DNG-Datei von Adobe Bridge in Tiff und sRGB ohne Probleme in Nikon NX Studio verarbeitet.
Please try to write in English so that all developers understand the problem. Can you please upload a sample TIFF converted from digiKam and from Adobe Bridge? Action in digiKam version 7.6.0: A RAW DNG image file (from Adobe Lightroom) is created with color space conversion to sSRG IEC61966-2.1 (sRGB Profile.icc) + conversion to TIFF. Problem: The created TIFF file is rejected by the "Nikon NX Studio Ver.1.1.2 64bit" application with the following error message: "An unsupported file was found. The operation will be aborted". In comparison, the conversion of the same DNG file from Adobe Bridge to Tiff and sRGB was processed in Nikon NX Studio without any problems. Maik
There was a private communication here with sample images. The cause is the activated compression when creating the TIFF file. NX Studio can only read uncompressed TIFF files, it is also documented in the supported formats. If the TIFF file is exported without compression, NX Studio can read the file created by digiKam without any problems. Maik
Another note on the compression algorithm for TIFF files. NX Studio would only support LZW compression. However, digiKam uses Adobe deflate to compress TIFF files. Maik
Hi Maik, Adobe Deflate is the base of LZ77 algorithm not patented. LZW is based on LZ77 with improvements but patented (now expired). Typically LZ77 must be processed by LZW by retro-compatibility for decoding purpose (the inverse will be not of course). So the limitation in NX is a non sense, but after all it's a proprietary software which will don't care about interoperability. Gilles
There is another factor and that is Exiv2. Patrick gave me the original DNG again, it was created by Adobe. Using the ExifTool metadata writer, it creates a TIFF (without compression) that can be opened in NX Studio. If I disable ExifTool and use Exiv2, the created TIFF cannot be opened in NX Studio. The following error message can be seen when reading the metadata of the TIFF image: digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage3, entry 0x0144 is out of bounds: Offset = 0x00000000; truncating the entry digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage3, entry 0x0144: Size and data offset entries have different number of components, ignoring them. Maik
Do you mean that Exiv2 IO is more and more broken in time ? Gilles
I wouldn't say more and more. My oldest AppImage is digiKam-6.4.0, here too the TIFF created by the DNG has the metadata error. The batch processing is: DNG Image-> Color Space Conversion-> TIFF Write. Maik
Hallo Maik, Ich habe überhaupt keine Ahnung was sich da geändert haben könnte. Aktueller Stand: ein Ordner mit 33 DNGs wurde ohne Probleme in der Stapelverarbeitung von Digikam mit den Werkzeugen 1. Konvertieren in TIFF (mit Hacken bei TIFF-Dateien komprimieren) In 16 Bit oder 8 Bit konvertieren wurde alle von NX Studio angenommen und können dort verarbeitet werden. Also kann man den Fall wieder schliessen. Das wollte ich dir umbedingt mitteilen. Prima oder! Viele Grüße Patrick > Am 29.05.2022 um 3:15 PM schrieb Maik Qualmann <bugzilla_noreply@kde.org>: > > https://bugs.kde.org/show_bug.cgi?id=454537 > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > I wouldn't say more and more. > My oldest AppImage is digiKam-6.4.0, here too the TIFF created by the DNG has > the metadata error. > > The batch processing is: > DNG Image-> Color Space Conversion-> TIFF Write. > > Maik > > -- > You are receiving this mail because: > You reported the bug.