[Digikam-devel] [Bug 130525] Saving large (>5M) jpg's result in corrupt file
kdebugs at nacnud.force9.co.uk
Wed Jul 12 14:38:01 BST 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From kdebugs nacnud force9 co uk 2006-07-12 15:38 -------
If I start with a 2.3 MB JPEG source, resize to 50% and re-save to a 385KB JPEG, the resulting JPEG is intact.
If I start with a 8.8 MB RAW file, and save to PNG, I get a 27 MB file with no tags at all (EXIF, Makernote or ITPC), but it's fine other than Exiv2 not liking it (digikam: Cannot load metadata using Exiv2 (/home/dhill/Images/2006/2006-07-10/z.png: The file contains data of an unknown image type))
If I start with a 8.8 MB RAW file, and save to JPEG with no changes, I get a 781 KB JPEG that's intact.
If I start with a -different- 8.8 MB RAW file, and save to JPEG with no changes, I get a corrupt JPEG. If I resize to 50% I get a corrupt JPEG.
The correlation between corrupt and not corrupt appears to be the 'density' of colour data in an image. The image that produces good JPEGs when saved is just a bowl of food. The image that produces bad JPEGs when saved is a big yellow truck.
Resources to help test:
More information about the Digikam-devel