Replies: 3 comments 2 replies
-
First, I wouldn't use Second, using
I don't know; you'd have to look at the report for the missing photos to see what they are, do they appear in Photos, etc. Are the missing photos also hidden? If so, they won't show in the album. It's also possible that the missing photos are syndicated photos (shared via Messages, etc) that haven't been imported to the library yet. If so, they can't be added to an album. You can run
The time stamp is in the output so you can search by date of most recent export. You can also use the
This may be due to use of
This sometimes happens with photos imported from or edited in a 3rd party app. The only solution is to export the image, fix it, the re-import as a new image and delete the old one. This is not an osxphotos issue -- the warning is coming from exiftool.
Yes. Finally, you don't need |
Beta Was this translation helpful? Give feedback.
-
Rhet, thanks for your quick and detailed reply.
Okay, will remove it. I was hoping it would fix the "Duplicate Orientation tag" issues.
Oh, I thought it is suggested to use this option to ensure that resolved errors are backuped properly?
Thanks. Looking through the generated (30k lines) report it seems many have
All 1400 lines are from the last export. I ran two exports today, the first crapped out 1 image before completion, meaning no
I've seen that. But my issue is the sheer amount of errors that might not be errors but just warnings, as the return string has
It's not, as I used
Thanks. I will have to deal with these manually.
Today I realised that I had tons of duplicates saved on the NAS, all with filenames with suffixes (1) and (2). Maybe |
Beta Was this translation helpful? Give feedback.
-
Okay, so I should usually not use
Maybe a
Yeah, 1375 lines. That's 8% of all photos.
I will look into the documentation for grep to see how to skip all lines containing a specific string, thanks!
Are you suggesting not to use
I understand. The confusing part is that osxphotos logs 28 errors but the errors list contains 1400 errors, most of which aren't errors by exiftool definition, they all are
Yeah, it duplicated a ton of photos. I was using |
Beta Was this translation helpful? Give feedback.
-
I'm using osxphotos to backup my photos to a NAS (which is then synced to the cloud), using the command below. There's a few issues I don't know how to solve though and hope someone can provide a solution:
The report of the last run is:
Processed: 16926 photos, exported: 1, updated: 16925, skipped: 0, updated EXIF data: 16926, missing: 24, error: 28, touched date: 16926
(seems my NAS disconnected 1 photo before completion on the first run).osxphotos exportdb --errors
generates a file with 1400 issues. Nearly all have the error "Warning: Duplicate Orientation tag in IFD0", is it suggested to manually go through 1400 lines searching for the "other" errors?2009/12/13/2009-12-13--img_0662--1746.jpg, E8969663-89A0-4DB3-804E-84849CEC6A84, 2024-03-11 13:29:35.734, {"error": [], "exiftool_error": [], "exiftool_warning": [["/Volumes/nas/…/2009/12/13/2009-12-13--img_0662--1746.jpg", "Warning: Duplicate Orientation tag in IFD0 - /var/folders/ry/p178jh7j7qx7km2phb94r1c80000gn/T/osxphotos_export_g55qqge5/E8969663-89A0-4DB3-804E-84849CEC6A84_exiftool.jpeg"]]}
-m
onexiftool
, but that did not help.Error: Not a valid JPEG (looks more like a PNG)
, so I wonder how to fix that issue? I can't find a way to rename the file in Photos.app, do I need to export the images, delete them from the db, change the extension in the finder, then reimport them into the db?Here's the command I'm using:
Thanks for any suggestion. And @RhetTbull: This is an awesome project. I'm very thankful for your work on it.
Beta Was this translation helpful? Give feedback.
All reactions