https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #20 from Gilles Caulier <caulier gilles gmail com> 2009-10-14 00:46:01 --- Do you use Exiv2 0.18.2 ? I have implemented PNG support to Exiv2. I recommend to use this version Look in Help/Components Info for details... Gilles Caulier -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #21 from Gerald Cox <gbcox bzb us> 2009-10-14 05:09:33 --- Yes, I use Exiv2 0.18.2 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #22 from Gerald Cox <gbcox bzb us> 2009-10-14 20:42:52 --- I received my response back from Flickr support today, which is basically what we have already discovered: After using the geolocation function and prior to uploading to Flickr, does the file on your computer still show the EXIF? Because the originals posted in your Flickr photostream, geopng and geojpg, do not have any EXIF metadata embedded within them and our upload servers do not do any processing to the originals. It is probably best to ask the developer of the image editing software about the lack of EXIF after using the geotagging function. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #23 from Gerald Cox <gbcox bzb us> 2009-10-15 03:16:31 --- Created an attachment (id=37587) --> (http://bugs.kde.org/attachment.cgi?id=37587) output from exiv2 -pa geopng.png -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #24 from Gerald Cox <gbcox bzb us> 2009-10-15 03:18:32 --- OK, I found and installed the exiv2 program. The output is too long put put in the comments so I have attached the output in a file. Here is the command I ran: exiv2 -pa geopng.png > exiv2pa_geopng.png I also receive this message which Johannes referred to above which about and unknown entry in the file. This shows each time I run the command: Warning: Directory Image, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. If you look at the attachment, you will see the geo information is in the file. What I do not understand is why it shows when using the exiv2 command rather than the exiftool command? As I mentioned earlier, Flickr replied and they do not see EXIF information either. I hope this helps discover the issue. Thanks again! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #25 from Gerald Cox <gbcox bzb us> 2009-10-15 21:19:57 --- OK, I think I have figured out exactly what is going on. When I convert a JPG to a PNG file, the conversion causes corruption of the EXIF data buy adding the "Exif.Image.0x0001". This corrupted tag is causing Flickr and EXIFTOOL not to function properly. EXIV2 shows the correct part of the EXIF data and issues a warning regarding "Exif.Image.0x0001". I found I can use EXIV2 to remove the corrupted tag by issuing the following command: exiv2 -M "del Exif.Image.0x0001" image_file_name wildcards also appear to work, so I can delete the corrupted tag for all png files in the directory by entering: exiv2 -M "del Exif.Image.0x0001" *.png You should be able to recreate by taking a jpg file, and using the convert function (Select the file, then use Batch, Convert). If you enter exiv2 -pa file_name - you will see the warning: Warning: Directory Image, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. after you do the convert from jpg to png. Then try: exiftool -a -u -g1 file_name You will not see the complete EXIF information. Then delete the invalid tag: exiv2 -M "del Exif.Image.0x0001" image_file_name and when you run the exiftool command again, everything should be OK. So the badness is being introduced by whatever does the convert from JPG to PNG. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #26 from Gilles Caulier <caulier gilles gmail com> 2009-10-15 21:47:08 --- No. it's not a problem to file format conversion, but metadata transfert. This is a problem with Exiv2 library. Please report to Exiv2 bugzilla... Gilles Caulier -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #27 from Gerald Cox <gbcox bzb us> 2009-10-16 03:41:49 --- I opened bug 650 under Exiv2: http://dev.exiv2.org/issues/show/650 I also discovered this evening that even though I can apparently remove the invalid tag, something is still wrong with the file which causes the tag information to not be viewable by Flickr. I consider this a serious issue since unless people are checking their files with Flickr, they may be unknowingly introducing corruption - and if they haven't backed up their source (and they may not since they consider PNG their archive), they will be stuck with a corrupted file. If they do have original backups they will have to redo all their tags. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #28 from Andreas Huggel <ahuggel gmx net> 2009-10-17 11:14:56 --- Let's continue the discussion here rather than heading over to the Exiv2 bug tracker. For now I don't understand what needs to be fixed. 1. Where do the invalid tags come from? From an Exiv2 perspective these tags are not immediately a problem: Exiv2 will add such tags if instructed to do so, and that's not a bug. It is only an issue if Exiv2 adds them without the user's instructions. Gilles, have you checked if these are added by the application? If they aren't, how do I get Exiv2 to add these tags by itself - a reproducer would be helpful? Can you point me to the relevant code that onverts from JPG to PNG? 2. Why does Flickr not see the GPS tags in the image without the invalid tag? After removing the invalid tags, exiftool also considers the metadata valid. I'm at a loss as to what prevents Flickr from seeing the GPS tags. Gerald, with two open-source programs having no problems with the metadata, maybe you can convince the good people at Flickr to take a closer look at the image and advise what they think is wrong with it. Andreas -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #29 from Gilles Caulier <caulier gilles gmail com> 2009-10-17 11:35:33 --- Andreas, Converting JPG to PNG use libjpeg to open image data and libpng to write image data. In all case, metadata are not transfered by this way. All is deegate by libkexiv2 and Exiv2. I'm sure that no tags like this is added by digiKam and code. Why we will do it ? Relevant code: PNG save image : http://lxr.kde.org/source/extragear/graphics/digikam/libs/dimg/loaders/pngloader.cpp#555 Metadata transfert : DMetadata = libkexiv2 customization for digiKam http://lxr.kde.org/source/extragear/graphics/digikam/libs/dimg/loaders/dimgloader.cpp#194 That all (:=))) Each Exif, Iptc, Xmp block are transfered as well from JPG to PNG. As you know PNG image structure do not depand of metadata. Each metadata block are hosted in a dedicated png chunk. It's clean and better than TIFF... Gilles -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #30 from Gerald Cox <gbcox bzb us> 2009-10-17 16:50:44 --- Thanks again for everyone helping with this. I have an open case with Flickr on this issue. I have done some additional testing. Here is the copy of the note I sent them. I will let you all know what they say. Here is the note: ================== OK, I found a tag of: "Exif.Image.0x0001" which was causing some issues with some programs. When I used the exiv2 tool, it issued a warning for this tag. When I used the exiftool utility, it wouldn't display the exif info, so I deleted the tag and both programs were able to read. I then downloaded the file basepng.png from Flickr. I added the geotag information. I then used a conversion utility to create a jpg version of this file. I then uploaded both of these files to Flickr. The link for the PNG version is: http://www.flickr.com/photos/9550073@N03/4017660506/meta The link for the JPG version is: http://www.flickr.com/photos/9550073@N03/4016899647/meta I also attached two files: The exiv2jpg shows the tag information for the jpg version The exiv2png shows the tag information for the png version As you can see the tag information is identical, and remember the jpg file was created from the png version with no additional processing. And both of the files above were created from the basepng.png file which was downloaded from Flickr. For some reason, Flickr is still not showing the PNG file after it has been tagged with the geo information. However, the tag information shows up fine in the basepng file which is here: http://www.flickr.com/photos/9550073@N03/4001381895/meta What is happening? ================== -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #31 from Gerald Cox <gbcox bzb us> 2009-10-17 16:55:21 --- Created an attachment (id=37637) --> (http://bugs.kde.org/attachment.cgi?id=37637) Output from exiv2 -pt corrected_geo.jpg -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #32 from Gerald Cox <gbcox bzb us> 2009-10-17 16:56:04 --- Created an attachment (id=37638) --> (http://bugs.kde.org/attachment.cgi?id=37638) Output from exiv2 -pt corrected_geo.png -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #33 from Gerald Cox <gbcox bzb us> 2009-10-17 17:29:11 --- An additional note of clarification I didn't put in the note to Flickr which I am sending now. You will notice that the tag information is showing correctly (including the geo information for the corrected_geo.jpg file - it is not showing for the corrected_geo.png file. This gets a bit confusing, so I try to explain as follows: 1. I downloaded the basepng.png file from Flickr ===> http://www.flickr.com/photos/9550073@N03/4001381895/meta 2. I removed the bad tag by: exiv2 -M "del Exif.Image.0x0001" basepng.png (yes, the file which is showing tag information on Flickr has the invalid tag which the exiftool program does not like - but apparently Flickr doesn't care) 3. I copied basepng.png to corrected_geo.png 4. I added the location information to corrected_geo.png (note, adding the geo information does not add the bad tag. That appears to be introduced when using the convert function. I validated using exiftool and exiv2 that the tag information was correct and included the location information.) 5. I created corrected_geo.jpg by converting the corrected_geo.png file (with the location information added in step 4) to a jpg file. 6. The corrected_geo.jpg now has an invalid tag. I remove by issuing: exiv2 -M "del Exif.Image.0x0001" corrected_geo.jpg 7. I verify that the tag information can be seen using exiv2 and exiftool for both files 8. I upload corrected_geo.png to Flickr http://www.flickr.com/photos/9550073@N03/4017660506/meta ====> The tag information is NOT showing <===== 9. I upload corrected_geo.jpg to Flickr http://www.flickr.com/photos/9550073@N03/4016899647/meta ====> The tag information IS showing (including the location information) <==== To recap: 1. basepng.png on Flickr shows tag information correctly 2. corrected_geo.png created from basepng.png with location information added does not show tag information on Flickr 3. corrected_geo.jpg created from corrected_geo.png SHOWS tag information correctly -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #34 from Gerald Cox <gbcox bzb us> 2009-10-23 23:24:29 --- Here is the latest communication from Flickr. There developers are going to research, but they asked me to pass this information along. If you look, you will notice there is a difference between the tags in the PNG file and the JPG file which was created from the PNG file. My comments back to Flickr are at the beginning of the note: ========== Cris, Thanks for the reply and again for your looking into this. I would expect to see some differences between the jpg and png files since they are different formats. However, what I am curious about is why the EXIF information shows up in the png file here: http://www.flickr.com/photos/9550073@N03/4001381895/meta - which is the basepng.png file in the photo stream and not in the png file which has the geo information? Also, its weird that the jpg version shows "unknown tag" information, and displays alot of the info on Flickr whereas the png version appears to show the info fine using exiftool below (with no unknown tags) but basically shows nothing on Flickr. I'll run this information below by the developers and see what they say. In the meantime, I think we'll all be interested in what Flickr says. Thanks again! On Fri, Oct 23, 2009 at 13:28, Flickr Support <[hidden email]> wrote: - Hide quoted text - > Hello, > > Actually, we do see a difference in metadata between these > two images. This is the EXIF from the originals on Flickr, > so I'm not at all sure what the software company is > referring to. You may want to run this data past them. > > As I mentioned earlier, our developers are going to take a > look at this case to see if we're displaying the metadata > that we normally display. Bear in mind that we do not alter > the originals posted to Flickr and that if the metadat that > we expect to find in the file is not there, then we won't be > adding it to the More Properties page. > > Thanks, > Cris > > > ==== metatdata examples (2) ==== > > 1. This photo does not have metadata on Flickr: > http://www.flickr.com/photos/9550073@N03/4017660506/meta > > > ---- ExifTool ---- > ExifTool Version Number : 7.89 > ---- System ---- > File Name : > 4017660506_81fce130de_o.png > File Size : 10 MB > File Modification Date/Time : 2009:10:23 09:22:35-07:00 > ---- File ---- > File Type : PNG > MIME Type : image/png > Exif Byte Order : Little-endian (Intel, II) > ---- PNG ---- > Image Width : 3264 > Image Height : 2448 > Bit Depth : 8 > Color Type : RGB > Compression : Deflate/Inflate > Filter : Adaptive > Interlace : Noninterlaced > Pixels Per Unit X : 7086 > Pixels Per Unit Y : 7086 > Pixel Units : Meters > ---- IFD0 ---- > Make : Canon > Camera Model Name : Canon PowerShot S80 > Orientation : Horizontal (normal) > Y Resolution : 180 > Resolution Unit : inches > Modify Date : 2007:08:11 07:59:01 > Y Cb Cr Positioning : Centered > ---- ExifIFD ---- > Exposure Time : 1/1000 > F Number : 4.0 > Exif Version : 0220 > Date/Time Original : 2007:08:11 07:59:01 > Create Date : 2007:08:11 07:59:01 > Components Configuration : Y, Cb, Cr, - > Compressed Bits Per Pixel : 3 > Shutter Speed Value : 1/1002 > Aperture Value : 4.0 > Exposure Compensation : 0 > Max Aperture Value : 2.8 > Metering Mode : Multi-segment > Flash : Off, Red-eye reduction > Focal Length : 5.8 mm > User Comment : > Flashpix Version : 0100 > Color Space : sRGB > Exif Image Width : 3264 > Exif Image Height : 2448 > Focal Plane X Resolution : 11412.58741 > Focal Plane Y Resolution : 11439.25234 > Focal Plane Resolution Unit : inches > Sensing Method : One-chip color area > File Source : Digital Camera > Custom Rendered : Normal > Exposure Mode : Auto > White Balance : Auto > Digital Zoom Ratio : 1 > Scene Capture Type : Landscape > ---- Canon ---- > Macro Mode : Normal > Self Timer : Off > Quality : Fine > Canon Flash Mode : Off > Continuous Drive : Single > Focus Mode : Single > Record Mode : JPEG > Canon Image Size : Large > Easy Mode : Landscape > Digital Zoom : None > Contrast : Normal > Saturation : Normal > Sharpness : 0 > Camera ISO : Auto > Metering Mode : Evaluative > Focus Range : Auto > AF Point : Auto AF point selection > Canon Exposure Mode : Easy > Lens Type : Unknown (-1) > Long Focal : 20.7 mm > Short Focal : 5.8 mm > Focal Units : 1000/mm > Max Aperture : 2.8 > Min Aperture : 8 > Flash Bits : (none) > Focus Continuous : Single > AE Setting : Normal AE > Zoom Source Width : 3264 > Zoom Target Width : 3264 > Spot Metering Mode : Center > Photo Effect : Off > Manual Flash Output : n/a > Focal Type : Zoom > Focal Length : 5.8 mm > Focal Plane X Size : 7.44 mm > Focal Plane Y Size : 5.59 mm > Auto ISO : 100 > Base ISO : 50 > Measured EV : 10.31 > Target Aperture : 4 > Target Exposure Time : 1/1002 > Exposure Compensation : 0 > White Balance : Auto > Slow Shutter : Off > Shot Number In Continuous Burst : 0 > Optical Zoom Code : 0 > Flash Guide Number : 0 > Flash Exposure Compensation : 0 > Auto Exposure Bracketing : Off > AEB Bracket Value : 0 > Control Mode : Camera Local Control > Focus Distance Upper : 65.53 > Focus Distance Lower : 0 > F Number : 4 > Exposure Time : 1/1002 > Bulb Duration : 0 > Camera Type : Compact > Auto Rotate : None > ND Filter : Off > Self Timer 2 : 0 > Flash Output : 0 > Canon Image Type : IMG:PowerShot S80 JPEG > Canon Firmware Version : Firmware Version 1.00 > File Number : 100-0544 > Owner Name : > Canon Model ID : PowerShot S80 > Num AF Points : 9 > Valid AF Points : 9 > Canon Image Width : 3264 > Canon Image Height : 2448 > AF Image Width : 3264 > AF Image Height : 204 > AF Area Width : 588 > AF Area Height : 37 > AF Area X Positions : -588 0 588 -588 0 588 > -588 0 588 > AF Area Y Positions : -38 -38 -38 0 0 0 38 38 > 38 > AF Points In Focus : 4,7 > Primary AF Point : 4 > Thumbnail Image Valid Area : 0 0 0 0 > Date Stamp Mode : Off > My Color Mode : Off > Firmware Revision : 1.00 rev 6.00 > ---- InteropIFD ---- > Interoperability Index : R98 - DCF basic file > (sRGB) > Interoperability Version : 0100 > Related Image Width : 3264 > Related Image Height : 2448 > ---- GPS ---- > GPS Version ID : 2.0.0.0 > GPS Latitude Ref : North > GPS Latitude : 37 deg 48' 38.88" > GPS Longitude Ref : West > GPS Longitude : 119 deg 29' 8.19" > GPS Altitude Ref : Above Sea Level > GPS Altitude : 2569 m > GPS Map Datum : WGS-84 > ---- IFD1 ---- > Compression : JPEG (old-style) > X Resolution : 180 > Y Resolution : 180 > Resolution Unit : inches > Thumbnail Offset : 2506 > Thumbnail Length : 3857 > ---- Composite ---- > Aperture : 4.0 > Drive Mode : Single-frame shooting > GPS Altitude : 2569 m Above Sea Level > GPS Latitude : 37 deg 48' 38.88" N > GPS Longitude : 119 deg 29' 8.19" W > GPS Position : 37 deg 48' 38.88" N, 119 > deg 29' 8.19" W > ISO : 50 > Image Size : 3264x2448 > Lens : 5.8 - 20.7 mm > Lens ID : Unknown 5-20mm > Scale Factor To 35 mm Equivalent: 4.6 > Shooting Mode : Landscape > Shutter Speed : 1/1000 > Thumbnail Image : (Binary data 3857 bytes, > use -b option to extract) > Circle Of Confusion : 0.006 mm > Field Of View : 67.4 deg > Focal Length : 5.8 mm (35 mm equivalent: > 27.0 mm) > Hyperfocal Distance : 1.30 m > Lens : 5.8 - 20.7 mm (35 mm > equivalent: 27.0 - 96.2 mm) > Light Value : 15.0 > > > > === > 2. This photo does have metadata on Flickr: > http://www.flickr.com/photos/9550073@N03/4016899647/meta > > ---- ExifTool ---- > ExifTool Version Number : 7.89 > ---- System ---- > File Name : > 4016899647_c93c8e10fd_o.jpg > File Size : 4.1 MB > File Modification Date/Time : 2009:10:23 09:34:34-07:00 > ---- File ---- > File Type : JPEG > MIME Type : image/jpeg > Exif Byte Order : Little-endian (Intel, II) > Image Width : 3264 > Image Height : 2448 > Encoding Process : Baseline DCT, Huffman > coding > Bits Per Sample : 8 > Color Components : 3 > Y Cb Cr Sub Sampling : YCbCr4:2:2 (2 1) > ---- JFIF ---- > JFIF Version : 1.01 > Resolution Unit : inches > X Resolution : 180 > Y Resolution : 180 > ---- IFD0 ---- > Make : Canon > Model : Canon PowerShot S80 > Orientation of image : 1 > Resolution unit : inch > File date and time : 2007:08:11 07:59:01 > Y and C positioning : centered > -- Exif IFD -- : > Exposure time : 1/1000 s > F number : 4.0 > Exif version : 0220 > Date and time of original data generation : 2007:08:11 > 07:59:01 > Date and time of digital data generation : 2007:08:11 > 07:59:01 > Meaning of each component : reserved > Image compression mode : 3.0 > Shutter speed : 10.0 APEX = 1/1002 s > Aperture : 4.0 APEX = F4.0 > Exposure bias : 0.0 > Maximum lens aperture : 3.0 APEX = F2.8 > Metering mode : Pattern > Flash : reserved > Lens focal length : 5.8 mm > -- Canon IFD -- : > Unknown tag (1) : {92,2,0,3,0,0,0,4,65535,1,...} > Unknown tag (2) : {2,5800,293,220} > Unknown tag (3) : {0,0,0,0} > Unknown tag (4) : {68,0,128,330,128,319,0,0,0,0,...} > Unknown tag (0) : {1,0,0,160,0,0} > Image Type : IMG:PowerShot S80 JPEG > Firmware Version : Firmware Version 1.00 > Image Number : 1000544 > Owner Name : > Unknown tag (13) : {0,1,0,985,13,13,-6,0,0,0,...} > Unknown tag (16) : 24510464 > Unknown tag (0) : {0,0,0,0,0,0,0,0,0} > Unknown tag (18) : > {9,9,3264,2448,3264,204,588,37,64948,0,...} > Unknown tag (19) : {0,0,0,0} > Unknown tag (24) : > Unknown tag (25) : 1 > Unknown tag (28) : 0 > Unknown tag (29) : {32,1,0,2,2,2,2,0,0,0,...} > Unknown tag (30) : 16778752 > -- End of Canon IFD -- : > User comments : 264 bytes > Supported Flashpix version : 0100 > Color Space : sRGB > Valid image width in pixel : 3264 > Valid image height in pixel : 2448 > -- Interoperability IFD -- : > Interoperability Index : R98 > Interoperability Version : 0100 > Related Image Width : 3264 > Related Image Height : 2448 > -- End of Interoperability IFD, EXIF IFD continues : > Focal plane x resolution : 11412.6 (1632000/143) ppi (pixel > per inch) > Focal plane y resolution : 11439.3 (1224000/107) ppi (pixel > per inch) > Focal plane resolution unit : inch > Sensing method : One-chip color area sensor > File source : DSC > Custom image processing : Normal process > Exposure method : Auto exposure > White balance : Auto white balance > Digital zoom ratio : 1.0 > Scene capture type : Landscape > -- Main IFD continues -- : > -- GPS IFD -- : > GPS tag version : 0,0,0,2 > North or South Latitude : N > Latitude : 37°48'38.88" > East or West Longitude : W > Longitude : 119°29'8.19" > Altitude reference : Sea level > Altitude : 2569.0m > Geodetic survey data used : WGS-84 > -- Thumbnail IFD -- : > Compression scheme : JPEG > X resolution : 180.0 ppi (pixel per inch) > Y resolution : 180.0 ppi (pixel per inch) > Resolution unit : inch > Offset to JPEG SOI : 2486 > Bytes of JPEG data : 3857 > > > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #35 from Andreas Huggel <ahuggel gmx net> 2010-02-01 13:43:06 --- Any news from Flickr? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #36 from Andreas Huggel <ahuggel gmx net> 2010-04-03 08:04:04 --- I'm rejecting the related exiv2 bug (http://dev.exiv2.org/issues/show/650). Nothing can be done without specific information about what is wrong. Andreas -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WAITINGFORINFO -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #37 from Gilles Caulier <[hidden email]> --- New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Gerald B. Cox
https://bugs.kde.org/show_bug.cgi?id=210226
--- Comment #38 from [hidden email] --- Gerald, digiKam 5.0.0 is published. This problem still reproducible with this release ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |