I encountered a strange problem developing a Nikon raw file with
digikam 3.0.0-beta2 which did not occur under digikam 2.9: Under digikam 3.0.0-beta2 (latest version from git) a pattern of a faint rectangular lattice of fine lines occurs over the entire .JPG that was produced from the .NEF file. This does not happen when using digikam 2.9, nor do I see this pattern when developing the raw file by rawtherapee or darktable. You may view the results by downloading the original NEF and the JPGs produced by digikam 2.9 and digikam 3.0.0-beta2 from the following website: raw-file: www.robert-zeller.org/transfer/DSC0607.NEF JPG digikam 2.9 : www.robert-zeller.org/DSC0607_v2-digikam_2.9.JPG JPG digikam 3.0.0-beta2: www.robert-zeller.org/DSC0607_v1-digikam_3.0_beta.JPG Since the web-page is not open for directory search you have to specify the full urls when using wget for download. Caution: the files are huge since they were taken with a NIKON D800 which has a 36 Mpix sensor. I used the same settings in digikam 2.9 and 3.0.0 when developing the raw. I am wondering what the reason may be for this unacceptable result in 3.0.0-beta2? Robert _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Sorry, I made a mistake with the urls; please refer to the corrected urls for downloading the files: I encountered a strange problem developing a Nikon raw file with digikam 3.0.0-beta2 which did not occur under digikam 2.9: Under digikam 3.0.0-beta2 (latest version from git) a pattern of a faint rectangular lattice of fine lines occurs over the entire .JPG that was produced from the .NEF file. This does not happen when using digikam 2.9, nor do I see this pattern when developing the raw file by rawtherapee or darktable. You may view the results by downloading the original NEF and the JPGs produced by digikam 2.9 and digikam 3.0.0-beta2 from the following website: raw-file: www.robert-zeller.org/transfer/DSC0607.NEF JPG digikam 2.9 : www.robert-zeller.org/transfer/DSC0607_v2-digikam_2.9.JPG JPG digikam 3.0.0-beta2: www.robert-zeller.org/transfer/DSC0607_v1-digikam_3.0_beta.JPG Since the web-page is not open for directory search you have to specify the full urls when using wget for download. Caution: the files are huge since they were taken with a NIKON D800 which has a 36 Mpix sensor. I used the same settings in digikam 2.9 and 3.0.0 when developing the raw. I am wondering what the reason may be for this unacceptable result in 3.0.0-beta2? Robert _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
It's probably a problem with last libraw 0.15.0-Alpha4 included in
digiKam 3.0.0-beta2. A new version of libraw will be include soon, but i'm not sure that your problem will be fixed. Can you report this dysfunction to bugzilla, including link to your images to download. I will CC libraw author for investiguations... Gilles Caulier 2012/10/16 Robert Zeller <[hidden email]>: > > > Sorry, I made a mistake with the urls; please refer to the corrected urls > for downloading the files: > > > > I encountered a strange problem developing a Nikon raw file with > digikam 3.0.0-beta2 which did not occur under digikam 2.9: > > Under digikam 3.0.0-beta2 (latest version from git) a pattern of a faint > rectangular lattice of fine lines occurs over the entire .JPG that was > produced from the .NEF file. This does not happen when using digikam > 2.9, nor do I see this pattern when developing the raw file by > rawtherapee or darktable. > > You may view the results by downloading the original NEF and the JPGs > produced by digikam 2.9 and digikam 3.0.0-beta2 from the following website: > > raw-file: www.robert-zeller.org/transfer/DSC0607.NEF > JPG digikam 2.9 : www.robert-zeller.org/transfer/DSC0607_v2-digikam_2.9.JPG > JPG digikam 3.0.0-beta2: > www.robert-zeller.org/transfer/DSC0607_v1-digikam_3.0_beta.JPG > > > Since the web-page is not open for directory search you have to specify > the full urls when using wget for download. > Caution: the files are huge since they were taken with a NIKON D800 > which has a 36 Mpix sensor. > > I used the same settings in digikam 2.9 and 3.0.0 when developing the raw. > I am wondering what the reason may be for this unacceptable result in > 3.0.0-beta2? > > Robert > > > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Filed bug: https://bugs.kde.org/show_bug.cgi?id=308489 at bugzilla!
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Thanks.
Post also in this file all information displayed by Help/Components Info dialog. Thanks in advance Gilles Caulier 2012/10/16 Robert Zeller <[hidden email]>: > Filed bug: https://bugs.kde.org/show_bug.cgi?id=308489 at bugzilla! > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |