RepairPhotosBookmarks
photokit
| RepairPhotosBookmarks | photokit | |
|---|---|---|
| 1 | 1 | |
| 14 | 5 | |
| - | - | |
| 3.3 | 8.1 | |
| 8 months ago | about 2 months ago | |
| Python | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RepairPhotosBookmarks
-
Looking for workflows for gathering family photos and backing up
I wouldn't keep the originals and the Photo library on the same disk just in case something happened to that disk. Also, it's important to know that if you store a Photos library on an external disk you can't move that Photo library to another Mac due to the way Apple now stores photos (to be "more secure"). I have developed a hack to get around this but I don't recommend using except as a last resort.
photokit
-
Crazy idea: bi-directional sync with Photos?
I'm making good progress with photokit which allows me to use the full private API to make changes to the Photos library. I took a small break to add iPhoto support to osxphotos....because I need to access an old iPhoto library. But I had a crazy thought -- it would be possible with the new code to create a "bi-directional" Photos sync. That is, you could create an export of your Photos library then use another DAM (or just the file system) to manage it and edit photos. These changes would be detected by osxphotos and synced back to Photos. For example, you edit an exported image in Photoshop. The change is detected by osxphotos as an edit and it creates a change request in Photos to add the edit back to Photos. You change a keyword on a photo and osxphotos detects that and adds it back to the original in Photos. You edit a photo in Photos and this is detected and the exported copy updated. This would work best with a background process that monitors for changes. There's a lot of ways this could go wrong but it might be a way to "have your cake and eat it too" -- use Photos for syncing to iPhone, etc. but also be able to manage your photos "manually" in the Finder or using something like Digicam. Does this sound useful?
What are some alternatives?
photos_time_warp - Batch adjust the date, time, or timezone of photos in Apple Photos from the Mac command line.
iBackep - A lightweight GUI backup manager for Apple iPhone and iPad on Linux
osxphotos - Python app to work with pictures and associated metadata from Apple Photos on macOS. Also includes a package to provide programmatic access to the Photos library, pictures, and metadata.
persepolis - Persepolis Download Manager is a GUI for aria2.
add_photo_locations_from_google_history - Python script to add missing location data to photos in your Apple Photos library based on your Google location history. This script can be run stand-alone to add location data to the photos in your library or as a post-processing function for osxphotos to add location data to photos upon export.
appleloops - A utility to deploy the additional audio content packages for Apple's audio editing programs.