I’m a huge fan of Google Photos. It’s an amazing service that lets me quickly share photos with particular people, creates interesting images from my photos and it’s a convenient way to bring my photo archive with me on my phone.
However, the new “Backup & Sync” app from Google that replaced the old uploader is problematic.
As well as uploading my photos to Google Photos it would backup to Google Drive. I don’t care about this feature because I use Backblaze for backups. I didn’t really realise what this meant when I first installed the app.
I told it to sync my “2018” folder and it dutifully started backing up to Google Photos but I soon noticed that the storage used in my Google account was decreasing. Eventually I found the computers section of Google Drive. All my files were backed up there.
It appears that “Don’t sync to this computer” doesn’t mean “don’t sync this computer to Google Drive”. However it does mean that any files deleted in the synced “Computers” section of Google Drive will be deleted locally. I found this out when I tried to save some storage space by deleting files off Google Drive. Later that day I fired up Lightroom and it reported that a large number of files were unavailable. I opened the folder in Finder only to see the images magically disappear before my eyes.
It was “Backup & Sync” deleting my local files. It was syncing deletes “to this computer”. Thankfully the files were still in the Trash so I could restore them quickly.
So, instead of wasting my storage I need to upload things manually. I see two options:
Drag and drop files on to a Google Photos browser window.
Sync one temporary folder where I copy duplicates of my photos. I need to periodically delete those files off Google Drive which won’t matter locally because they’ll be duplicates that are deleted immediately after upload.
It’s disappointing that Google merged the backup and sync functionality. Google Photos is not a backup service unless you pay for storage and upload full size images. For that reason I can see why they did it.
Lightroom Classic CC supports a wide range of lenses but if you're not shooting in RAW you'll probably be out of luck if you want to apply a lens profile. All the built-in lens profiles were made with RAW files in mind. If you're shooting Jpeg then you're out of luck.
I usually shoot RAW but a few weeks ago I used Jpeg to do some street photography. All was well until I tried to correct the lens distortion. Lightroom couldn't find any lens profile! I thought my Lightroom install had been corrupted somehow. The list of lenses only included one Tamron lens, and not the right one.
After much searching and testing I figured out what to do. Paths are for a Mac. You'll find Mac and Windows paths in this blog post by the Lightroom Queen but the ideas are the same. Copy file, rename, edit, restart Lightroom.
Custom lens profiles go in the directory ~/Library/Application Support/Adobe/CameraRaw/LensProfiles/1.0/
The built in lens profiles are packaged with Lightroom, so find Lightroom in Applications, right click on it and then "Show Package Contents" to browse into it. You'll find the lens profiles in Contents/Resources/LensProfiles/1.0/
Look for the profile for your lens and copy it into the same camera/lens/ directory structure in the ~/Library/Application Support/Adobe/CameraRaw/LensProfiles/1.0/ directory.
Rename the new lens profile file, removing the " – RAW" string from the end of the filename.
Edit that file in a text editor and change every instance of stCamera:CameraRawProfile="True" to stCamera:CameraRawProfile="False". There will be quite a few of them for a zoom lens.
Restart Lightroom, apply lens profile to your Jpeg file.
The 17th of March this year was a very cold day. It was overcast and dreary. A bitterly cold wind blew. Ireland were playing England in rugby at the same time most parades were taking place, which makes it all the more extraordinary that people turned out at all to watch and cheer on the parades around the country.
The Blarney parade was smaller than previous years, and the crowd was definitely smaller too but they made up for it in sheer enthusiasm and good cheer. I have to salute those of the parade who walked the route dressed in uniforms or costumes. I could not have done it!
There are many articles out there that explain how best to store your photo archive if you use Lightroom. I was going to write one too but I don't think the world will really benefit from me rehashing what other writers have already said.
You may have read elsewhere or seen YouTube videos that encourage you to put descriptive titles in the folders where you store your photos, but I would urge you to keep the folder names as simple as possible. I agree with Peter Krogh that you keep the directory names simple but instead of using project names as he did above, I use dates. I use YYYY/YYYY-MM-DD as the folder name when importing. Using project based folder names makes things complicated. Occasionally I won't bother copying photos off my camera, especially if they're just snapshots, so it would be an extra hassle importing first my cat photos from Friday, and then my street photos on Saturday. It's much easier to go into "Previous Import" and add a few keywords. This won't happen that often, but I guarantee it will.
When you're looking through your photo archive it probably won't be through a file manager, it'll be in Lightroom, so the folder names don't matter, but the dated folder names provide a logical and predictable naming convention that will always be the same.
Instead of relying on folder names use keywords and collections to sort your photos. Use ratings or colours to refine further. You can then use Lightroom filters to quickly find whatever photo you need. This short tutorial on collections explains how to use them.
Use Import Presets
As well as DSLR photos, I import photos from my phone into Lightroom, and now that I'm doing a 365 day photo project too I'll be importing fully edited photos from my phone. I use Snapseed to edit those photos so I wanted some way of identifying those photos. Import Presets were the answer!
I use import presets to configure import options like destination folder, file renaming, metadata information, keywords, and even develop settings:
Away: used when I'm not at home with my laptop. Usually on a work trip or holiday. The destination folder is on the local drive. Everything else goes to an external one. When I get home I move the files to external storage and tell Lightroom where the missing files are.
Jacinta's Photos: my wife's camera phone photos go in a specific directory with different keywords and metadata.
Mobile Import: import photos I've already synced from my phone. Adds the keyword "phone" and puts the photos into a different directory structure.
SD Card: settings used when I'm importing DSLR photos.
Snapseed: my newest import preset. This adds the keyword "snapseed" and moves photos into the same folder as the Mobile Import preset. I use the keyword to
identify these files.
Use Publish Actions
These allow you to export photos with particular settings. This allows you to tailor your photos for different sites. For example, Instagram uses 1080×1080 pixel images. Your blog will have a different width. Facebook has other restrictions.
Use the WordPress Lightroom Plugin
The Lightroom Exporter for WordPress allows you to export photos from Lightroom into your WordPress.com or self hosted WordPress site (if you're using Jetpack).
There has been so much written about Adobe Lightroom it's not hard to find answers to whatever questions you have. This was just a short summary of my thoughts about photo organization. I have a photo archive going back to 2001 and it has worked well for me. It'll probably work well for you too.
How many backups do you have of your important files? I have several backups of my photo archive:
* A local rsnapshot (incremental) backup made every six hours.
* A local copy of my photos directory, which is a straight copy, including deletions. Synced daily.
* A copy on another server synced daily.
* An online cloud backup on Backblaze.
And I still managed to lose a few days worth of photos.
Late last month I took delivery of a new 8TB external drive. I benchmarked it and it was just a bit better than any of my existing drives so I decided to make that the primary location for my photos. I called it “cats”.
Previously my photos lived on a drive imaginatively called “data”, but that would now become my secondary copy.
With my photo archive copied over (all 2.3TB of it), I edited my backup script so it would not accidentally erase my photos on cats, especially not any newly imported photos. I updated rsnapshot so it used cats rather than data, and made sure that Backblaze was backing up cats too. It all looked like it would work perfectly!
The next day I didn’t take any photos, or the next, I took a couple of photos with my phone but didn’t transfer them to my laptop immediately. Then one morning I took a photo of the sunrise, and the following day I did the same.
I edited a few of the images and uploaded one on the same day. Nothing wrong at all.
The next day I went into Cork to photograph Glow Cork and got some nice long exposure photos of the lights. I went in the next day on December 3rd and did the same.
I worked on a couple of shots, but I was busy, and didn’t have time to work on photos until this evening when my world fell apart as Lightroom reported it only had the smart previews for my latest photos. With a sinking feeling and forced calm I checked the 2017 folder. It all looked good, until 2017-11-19 that is. Nothing there after that.
I frantically checked my backup script again and again, poring over each line to make sure the right files were being copied to the right place but it looked ok.
I checked my rsnapshot folder. That should surely have the missing files. No. No, it didn’t.
I checked my other server and the files weren’t there either. They stopped at 2017-11-19.
I checked Backblaze, and the backup made today ended in 2017-11-19 too.
Dumbfounded and a little desperate I started clicking on the end date in Backblaze, going back a few hours, then a day, and another day when I found something weird. I found my December 1st and 2nd photos, but not in the cats drive, but in the data drive!
I’d forgotten to update my Lightroom import preset. Lightroom was still copying my images into the data drive, and then my backup script would delete them the next day. Rsnapshot wasn’t backing them up either because it was now looking at the cats drive.
I started a restore of my December photos off Backblaze. The 3.7GB of data is still downloading. Luckily I hadn’t formatted my camera SD card so my December 3rd photos were still there too, waiting to be copied over again. Once converted to DNG, copied into place, renamed and metadata data updated, Lightroom was happy with those files.
I learned a lot about Backblaze. Without it I would have completely lost my December photos, including this one and the photo at the top of this post.
However, I could not find backups of photos shot from November 20th to 30th. Most of those were sunrise photos, copied to the laptop after the daily backup script had run so Backblaze should have had a day to back those photos up. The restore process offers hourly backups over the last two days, then daily for the next 7 days, then weekly going back a month.
I suspect that Backblaze considered the daily backup done sometime around 7am UTC right after my backup script had deleted the files but that doesn’t explain how I was able to find my December shoot because that was past the hourly deadline. I need to contact Backblaze to find out why.
I still recommend using Backblaze. Last week several factors conspired to make my backup fail:
1. My DSL has a relatively slow 1Mbps upload.
2. I had my laptop unplugged from my external drives for several hours.
3. Backblaze doesn’t immediately back files up.
Then there’s the bad luck to find this problem after more than a week when Backblaze changes to weekly snapshots. It has it’s limitations but it still saved a bunch of my photos and I am very thankful to have it!
I’ve already changed my backup script so it won’t mirror deletions. If I’m going to delete files I’m going to do it soon after copying them onto my laptop and I remove files so rarely it’s not needed in the backup script.
Last September almost 600 employees of Automattic travelled to Whistler in Canada for our annual Grand Meetup. As is now a company tradition a photograph was taken of everyone who attended. It’s a challenge taking a photograph of that many people. Remember how hard it was taking that family photo? The difficulty of getting everyone to look at the camera at the moment the shutter closed, or even just getting everyone in one place is multiplied when you have this number of people.
The last company photo was also taken in Whistler and we took a photo in the that same location again but it wasn’t good enough. The camera wasn’t up high enough, so people in the back were all but invisible in the photo. This photo was taken around the corner, where the photo was taken from a first floor balcony. Plenty of height and a perfect vantage point.
Taking the photo was one challenge, but then came development of the image. The camera had to be handheld because of the location on the balcony but the photographer took plenty of shots so I had a lot of material to work with.
The first issue was lining up the photos and I tried using Affinity Photo. Unfortunately it wasn’t quite up to the job (at least with the knowledge I have, it’s an excellent tool otherwise) but I learned a lot about working with layers and layer masks as I swapped parts of different images around.
Eventually I used Photoshop, loaded 3 photos in a stack and the auto align did a great job of correcting for changes in each photo.
What turned out to be the biggest pain point in developing a photo like this was removing people from the background. Here’s a few of them:
I’m already planning for next year. We’ll get some shots of the background to make it easier to to clone bystanders out, and have more volunteers to help organise the shoot so we make best use of the available space.
The Google blog announced that Google Photos will now allow you to share whole albums or just the photos of particular people with someone else.
I tried it this morning and it works, but there’s one big stumbling block. Too many photos.
When I take photos I’ll take 2 or 3 photos of the same scene sometimes, or if there are people in the photo I’ll take photo a few times just so everyone is looking at the camera. Or if kids are involved they’ll be looking every which way except at the camera.
So, what should really be one representative photo it’s really five or six images.
No. Using machine learning and image recognition is a huge step, but what a lot of non photographers want is a curated collection of “the best” photos.
I’m sure it’s only a matter of time before Google learns how to select from near identical photos to create this “best of” album. Their daily albums are a good indication that they can do this already.
The other problem with machine learning is that it might try too hard. This morning it suggested i share street photos I took a few weeks back. Unfortunately one of the suggested people was a former colleague who lives in Colorado and was not in Cork on the day. Another suggestion was my niece who also was not roaming the streets!
Anyway, I love Google Photos. The image recognition is amazing. I’ll search that for an image I need before diving into Lightroom 5 to edit it. 🙂
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.