Closed GoogleCodeExporter closed 8 years ago
In the Metadata section, did you click on "Export GPS data"?
Also, iPhoto imports only the GPS latitude and longitude. iPhoto does not
import place names for example.
Original comment by tsporkert
on 1 Aug 2010 at 7:33
To separate Phoshare export from iPhoto import issues, please do this:
After exporting the image with Phoshare, open the image with Preview, then
bring up an Inspector window. Switch to the GPS tab, and check if the GPS
coordinates are shown there.
Original comment by tsporkert
on 2 Aug 2010 at 3:35
In my case this problem on seems to occur with photos in raw format. If I
export a photograph in raw format as jpeg then reimport, Phoshare succeeds in
exporting the gps data. But if I tag the location of a photo in raw format, it
fails (even though it is exporting as jpeg). (Yes, I have "Export GPS data"
clicked and I verify the presence or absence of GPS data by opening in Preview
as advised.)
Original comment by william....@gmail.com
on 2 Oct 2010 at 7:25
I'll double check the handling of metadata when exporting RAW images.
Original comment by tsporkert
on 2 Oct 2010 at 9:02
I am not able to reproduce this problem. Could you make an album with just one
of your raw images that has this problem, then use Phoshare to export just that
one album, and send me the output from the export run? Just copy-and-paste the
text from the big text area at the bottom of the app. It should look like this:
Reading iPhoto database from /Users/tilman/Pictures/iPhoto Library...
Version 8.1.2 library with 24082 images
Scanning iPhoto data for photos to export...
Scanning existing files in export folder...
Exporting photos from iPhoto to export folder...
...
Updating IPTC for /Users/tilman/Temp/Album3/Test2/20091224 Christmas Eve - 01
copy.jpg because of GPS (, ) vs (41.849998, -87.650101)
...
New file: /Users/tilman/Temp/Album3/Test2/Originals/20091224 Christmas Eve - 01
copy.nef (copy)
New file: /Users/tilman/Temp/Album3/Test2/20091224 Christmas Eve - 01
copy_1.jpg (copy)
...
Done!
Original comment by tsporkert
on 2 Oct 2010 at 11:26
I couldn't reproduce the problem this way either. Creating the test album
seemed to trigger the correct behavior. The following seems to be reliable way
of reproducing the error (reliable in that I tried it twice).
1) Move your iPhoto Library out of the way and force iPhoto to create a new one
2) Take a picture of your kitchen with your Cannon Digital Rebel and import it
into the new library
3) Export it using Phoshare, with "Events, Albums, and Smart Albums" set to .
in the Events field and blank elsewhere, and "Export GPS data" checked
4) Add a location to your photo in iPhoto
5) Export again using Phoshare with the same settings
On the second export, Phoshare does not recognize the change:
Reading iPhoto database from /Users/wgmccallum/Pictures/iPhoto Library...
Version 8.1.2 library with 1 images
Scanning iPhoto data for photos to export...
Scanning existing files in export folder...
Exporting photos from iPhoto to export folder...
Done!
And the exported photo is not geotagged according to Preview.
Note: If you add the location in iPhoto before the first Phoshare export, then
everything works just fine. But if you change the location after that it will
not take. So it seems to have something to do with exporting after modifying
the photo, not the original export.
Here, for the record, is what I get when I try your test. As you can see, it
works:
Reading iPhoto database from /Users/wgmccallum/Pictures/iPhoto Library...
Version 8.1.2 library with 8718 images
Scanning iPhoto data for photos to export...
Scanning existing files in export folder...
Creating folder /Users/wgmccallum/Desktop/Test/Test
Exporting photos from iPhoto to export folder...
New file: /Users/wgmccallum/Desktop/Test/Test/IMG 0532.jpg (copy)
Updating IPTC for /Users/wgmccallum/Desktop/Test/Test/IMG 0532.jpg because of
keywords ( instead of Family,Australia,Sydney,Daniel McCallum,Christmas,Raw,New
South Wales)
Updating IPTC for /Users/wgmccallum/Desktop/Test/Test/IMG 0532.jpg because of
GPS (, ) vs (-33.896805, 151.16861)
Done!
Original comment by william....@gmail.com
on 3 Oct 2010 at 2:17
By default, Phoshare does not check for metadata changes if there are no edits
to the image itself. Enable the "Verify existing images" checkbox to have it
double check all images for meta data changes.
This option is not enabled by default because it requires opening and reading
all previously exported images to check the metadata, and that can slow things
down quite a bit.
Original comment by tsporkert
on 3 Oct 2010 at 4:26
Ah, thanks. It's not clear to me when something I do in iPhoto is just "editing
the metadata" and when it is "editing the image." (In fact, I'm not sure I
understand the distinction even now. Is it that metadata is not stored in the
file itself?) I have been adding keywords, locations, and faces, and Phoshare
has been exporting some but not all of these changes. But anyway, it's nice to
know how to solve the problem.
Original comment by william....@gmail.com
on 3 Oct 2010 at 5:52
Anything you do after you click on the "Edit" button changes the image: crop,
rotate, straighten, red-eye, enhance, adjust, etc. Metadata is all the stuff
you do in the "Information" panel (name, title, rating, keywords, comments),
plus places and faces. Metadata can be stored in the image, but iPhoto does not
update the metadata in the image file. It only saves you metadata changes in
its internal database. That's where Phoshare comes in handy - it not only
copies the edited image files out of iPhoto, but it also knows how to read the
metadata edits from the iPhoto database, and applies them to the exported image
files. By default, this only happens if the image has to be exported, either
because it is a new image, or because you edited the image. Any metadata edits
made later will not get applied to the already exported image file unless you
clicked on "Verify existing images". Let me think about making that a bit more
clear.
Original comment by tsporkert
on 3 Oct 2010 at 6:13
Thanks, and by the way, I've been wanting something like Phoshare for years,
thanks also for writing it.
Your explanation is clear, and it's more or less what I understood initially,
but I then became confused because Phoshare seemed to be exporting metadata
changes without me having edited the image (and without the "Verify existing
images" checked). But in retrospect I think this must have been in cases where
I had in fact modified the file by doing a batch change in iPhoto with the
"modify original files" button checked.
Checking "Verify existing images" has revealed another issue. When I run
Phoshare twice there are certain files which it keeps re-exporting even though
they have not been changed. And in fact the exported files do not have any of
the meta-data that Phoshare said it was adding. I think the problem is that
they are all old scans that do not have the DateTimeOriginal field set, causing
exiftool to fail (for reasons I don't quite understand, but I've seen it happen
with geotagging). The problem goes away when I reset the time and date in
iPhoto using the batch change feature with the "modify original files" checked.
But these are all photos for which iPhoto has the correct date and time in its
database, so I guess it should be possible to make Phoshare check for the
absence of the field and write it into the file as it is exporting. (Not that I
am asking you to do more work on this!)
Original comment by william....@gmail.com
on 3 Oct 2010 at 3:29
What is happening here is that some of your images have metadata that is not
properly formatted. You cannot just change one field in the meta data. Instead,
you have to read/modify/write operation on the entire block of metadata. So
first the metadata are read from the file, parsed into individual values, then
some values are modified (like the date), and then the entire set of metadata
is written back into the image file. If the metadata are not properly formatted
in the image file, then such a cycle can cause some values to get lost or
corrupted. So to be safe, Phoshare (through Exiftool) will not update the
metadata if there is a problem with the existing data. Some cameras, and some
programs, sometimes don't properly format the metadata.
If you change the data in iPhoto and click on "Modify original files", then
iPhoto will rewrite that section of the metadata. I don't know if it ignores
the formatting problem, or if it is more flexible than exiftool. In any case,
afterwards, the metadata are all reformatted, and Exiftool/Phoshare can read it
without problems.
I just noticed that Phoshare is set up to ignore minor errors or warnings when
checking existing metadata, but not when it tries to make changes. I'll
investigate if it's safe to use that mode for updates, as I've come across this
particular problem myself many times.
Original comment by tsporkert
on 3 Oct 2010 at 11:55
Just a followup which might be of use to people who find this thread. After
exporting from Phoshare with "Verify exiting images" checked I had about 3000
photos which failed to update as described in the Oct 3 post. Most of those
were fixed by setting the date in iPhoto with "modify existing files" checked,
as explained by tsporkert in reply to this post. There is an applescript that
does this in a batch here:
http://discussions.apple.com/thread.jspa?threadID=2279577.
This left about 30 photos which fell into the following three conditions, which
I had to fix by hand:
1. Photos with .tif extensions that were in fact jpg files (detectable by
opening in Preview and bringing up the information panel). Solution: change the
extension to jpg and reimport into iPhoto, deleting the original.
2. Photos that go black when you zoom in in iPhoto and won't open in Preview.
Solution: open them in Graphic Converter and save as a different file (jpg),
import that and delete the original.
3. Three remaining photos taken with my iPhone recently, which were in the
middle of a bunch of similar photos that worked fine. I couldn't figure out
what was different about them, but I eventually just edited them gratuitously
in iPhoto (a slight cropping never does any harm) and then Phoshare exported
them correctly.
Original comment by william....@gmail.com
on 8 Oct 2010 at 5:29
Also, I've updated the latest version of Phoshare (1.2) to be a bit more
aggressive when updating the metadata, and not bail out on minor errors with
the existing metadata. That should reduce the number of images exported with
incorrect metadata significantly.
Original comment by tsporkert
on 8 Oct 2010 at 5:34
Original comment by tsporkert
on 14 Oct 2010 at 5:00
Original issue reported on code.google.com by
chris...@gmail.com
on 11 Jul 2010 at 10:36