-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RAW: .NEF
files have wrong resolution information
#2447
Comments
Thanks for reporting this and adding examples! We use a generic Exif extractor for RAW files, which often include a thumbnail. Probably 160x120 is the resolution of this JPEG thumbnail, while the full RAW file may not conform to the Exif usage in JPEG. |
The output of
The information returned by exiftool should then be preferred as it appears to be correct. There is no need to use Darktable or any other external app to extract metadata. It would also be very slow. Converters are generally not intended for this purpose.
|
@lastzero thanks for the explanation.
|
As written above, For clarification, |
@lastzero no problem, there is absolutely no reason for you to work on this today, or to work on this at all. It is your software after all 🙂 Anyhow if you find time: is it exiftool (by phil harvey) that is used by PhotoPrism, or does PhotoPrism use a Go package or some other exif tool, that is what I don't understand currently. |
We use both plus additional sources for gathering metadata like XMP and Google Photos JSON. Data is extracted in a deterministic order, first using the internal library, then exiftool, and so on. This generally works well except in rare cases where the initial information is incorrect such as apparently in this case. This is great to know, so thanks for your report! Should I learn more about what is causing this, I'll let you know. |
I was not able to find anything that should cause Darktable to reduce the image size. The
|
I found the following remarks in the Exiftool forum at https://exiftool.org/forum/index.php?topic=7705.0:
To me it reads like ImageWidth and ImageHeight are NOT metadata, but the actual resolution based on the binary image data. That would explain why our exif header parser doesn't find them. |
Nice thanks! Currently on vacation in I presume your home country, so I will test this whenever I find some free WiFi. |
NEF
raw file shows incorrect resolution.NEF
files have wrong resolution information
@lastzero I tested this and it seems to work fine now! I had to remove any (from NEF) generated sidecar files and had to use the "Complete Rescan" check-mark in order for the sidecar files to be generated again. There is also no need anymore to switch to |
I noticed that some of my NEF files (Nikon Raw) where being converted into super small sidecar images 160x120. Then I noticed that in the files section the RAW file itself was reporting 160x120 as a resolution as well. Switching to
RawTherapee
solved (see #2446) the sidecar resolution size, but the reported RAW resolution is still 160x120 (I assumeRawTherapee
andDarktable
are not used to read metadata?).Result:
Resolution shows as 160x120 while it should show as 4608x3072
Expectation:
Resolution of RAW file should show as 4608x3072
Reproduce:
I've attached a sample image (in a .zip file, otherwise GitHub does not allow me to upload it). I hereby give permission to use this image and include it in the sample library if needed.
DSC_7534.NEF.zip
The text was updated successfully, but these errors were encountered: