![]() Smartphone pics are pulled into Dropbox (including any pics I muck around with in VSCO or Autodesk apps) so they're available on the Mac. We take pics on our smartphones and/or the P&S, and/or the DLSR. I've settled into the following, which is mostly working for us, it hinges on: Dropbox, our Mac, and "Silent Sifter" (. Everything as locate-able and cross-platform as possible on the NAS, so pictures stored as files, in a folder structure based on date (we're running Mac, Windows, iOs, Android, Ubuntu, and BSD off the top of my head) ![]() Work in progress stored wherever is easiest for that work. ![]() I don't even qualify as "pro-sumer" IMO, but I've been trying various things for years now to deal with the ever growing waves of digital media my wife and I produce, we both enjoy taking pictures, minor "I don't know what I'm doing, but I'm having fun!" editing, and she's quite into scrap-booking/collages/etc. I have better things to do with my time than manage lots of different services and workflows. She really isn't into any of this organizational stuff, it was amazing how many differet storage locations and duplicates and lost photos we had before I collected everything in OneDrive years back. I will periodically copy "relevant" photos from her OneDrive to mine, so that I have the complete master set. She shares her OneDrive with me, so I can access it directly from my OneDrive account. My wife pretty much just uploads directly to her Onedrive from the phone, and skips having a master local repository. To avoid this pitfall, I could set OneDrive to not replicate with my PC, and stick to the web interface for all my management needs, but my feeling is that the risk of these scenarios is low enough not to make that worthwhile. What makes me a bit nervous in this scenario is that theoretically I or someone else on my PC could do something stupid, like delete all the photos, or maybe bad luck causing file corruption, and I assume the deletions/corruption will be replicated.so its not exactly what can be considered a bulletproof backup scheme. I have everything sorted chronologically, usually one folder/album per month, also some folders dedicated to specific events if I feel the need to call them out. I don't really use any other services, because OneDrive really does everything I need.but my needs are pretty basic, so YMMV. If I feel the need to touch up the photos, I'll do it on the PC, and it replicates up to the cloud automatically. Have a desktop as the master photo repository, and it syncs all photos up with OneDrive. So, how do you keep it all in sync? Do you keep your home NAS as the "master" copy that ties together the various cloud providers, or find one service to rule them all? Do you do your light editing/sorting/tagging on a mobile device, a desktop, or web app? Meanwhile, I assume full-fat apps like Lightroom have continued to iterate. Some cloud services now offer face detection (Facebook, Google), which would be great to leverage, but generally their organizational features are shit compared with photo-centric sites like Flickr and SmugMug. My Nexus syncs to Google Drive (or maybe Picasa? haven't explored the GOOG ecosystem in depth.) My cameras still need to sync via physical miniSD, but the Windows Live apps have been rebooted & redesigned a half-dozen times since the XP days no idea which MS apps support which features, anymore, so I end up doing a braindead drag/drop from Explorer. My Lumia auto-syncs to OneDrive (and thus Windows Explorer) over the air. ![]() Nowadays, as devices and services get "smarter", there are a lot more moving parts to glue together. In the old days, I used Windows Live Photo Gallery to extract them over USB, do some basic editing & face detection, sort into a folder structure on my NAS, then upload to Flickr for proper tagging & off-premises archival. Unfortunately, they've turned me - former power user - into a lazy bum where proper organization is concerned, to the extent I can't claim to have a strategy at all. Phones with decent cameras + wifi sync have given newbs a basic workflow out-of-the-box. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |