As now has become my tradition, instead of the best of the year, I give you the worst. Well probably not the very worst, since those are often deleted immediately. While I had a reason to originally shoot these images, the only reason to keep them is to learn from my mistakes. I present these to let you, as well as I, learn from some of my mistakes. I have been doing this exercise of picking the worst of the year now for four years, and I do have to say, it appears harder each year to pick truly awful photos. Perhaps I’m learning? So, here are some of my worst shots of 2016, one for most months, both out of the camera (with default Lightroom processing) and, in some cases, with Lightroom processing in an attempt to save them (though most are not worth saving).
January – Black Dog, White Snow, Bad Combination. This is Nahla on one of my winter outings last year. She was eating snow and I thought I’d get a shot. It is very hard to get a good shot of a black animal and keep detail in the fur. Add snow, and you have a contrast nightmare. To add to it, she moved as I was taking the shot and my shutter speed was too slow. Why? I don’t know, there was plenty of light. No hope of saving this by processing. Lesson learned – use a high shutter speed to freeze action (you’d think I’d know that by now!); control the contrast (I’m just not sure how in this case).
February – Sunrise on Mount Baker with Sticks and Debris. I was up a Fir Island (see my last post) and saw some beautiful sunrise light on Mount Baker. And I liked the reflection in the pond. But to get the reflection, some foreground sticks got in the way. And what is all that stuff floating on the water? Plus, only later did I notice the walkway and lights on the far side of the pond. Processing in Lightroom brings out the colors on the mountain, and cropping gets rid of the sticks and floating debris, but it also takes the reflection. The end result is okay, but not great,and it certainly isn’t the image I was attempting to shoot. Lesson learned – don’t get so excited by the light to forget to check your foreground.
March – Why Did I Shoot This? I didn’t get out much in March, and of the images I took, I didn’t see any real horrible ones. The best (or should I say the worst) I can offer is this image of a boat at Point Ruston near my home in Tacoma. Not a truly awful image, I’m just not sure why I took it. Lesson learned – take photos for a reason, not just because you have a camera in your hand.
April – Slot Canyon Blues. On a trip to New Mexico in April, Tanya and I visited the Kasha-Katuwe Tent Rocks National Monument. On a hike there, we went through a slot canyon. I enjoyed moon hanging in sky above the canyon walls and was inspired to take the above photograph. Perfectly captures the moment does it not? Not is the correct answer. Shot with a wide-angle lens, you can barely see the moon. And can you tell it is a slot canyon if I hadn’t told you? There are contrast problems as well, but processing fixed that. The processed version cannot save the lack of photographic vision. Lesson learned – some scenes do not translate well to photographic images.
May – Small Flowers, White Sky. Early May brought me a bad case of spring fever. So Tanya, Nahla and I drove to eastern Washington to take a short hike to Umtanum Creek Falls. The route passes through a small black-rock canyon. I liked the yellow flowers blooming on the dark rock wall and took the above shot, including the trees and sky above to give a sense of the scene to the image. Again, because of the large contrast between the rocks and the sky, the sky was totally blown out. And the composition is horrible; the flowers small and insignificant when they are supposedly the subject of the image. Heavy processing brought some detail to the sky, but doesn’t help the composition. Lesson learned – make the subject prominent in the image; minimize the area of sky in the frame when there is a large contrast difference between the sky and the rest of the shot.
June – Rain Forest Contrast. In June we made a day trip to the Olympic coast, visiting the Hoh rain forest and Ruby Beach. The light conditions were not very good that day for photography, and while you still can make some good shots in bad light (see my post about that day for examples), the image above is not one of them. Here I liked the backlighting of the leaves, the look of the water underneath, and the moss hanging above. Unfortunately, the contrast between the sunlit water and grass and the shadowed moss was too much for the camera to handle, even with processing. Additionally, the composition is messy – there’s too much in the scene. Lesson learned – simplify compositions (which admittedly is hard to do in a forest); avoid extreme contrast.
July – Action Unfrozen. On the 4th of July last year, Tanya and I walked down to the annual festival along the Ruston Way waterfront. There we briefly watched bicyclists doing tricks. I grabbed a few shots. Unfortunately, I wasn’t paying attention to my camera settings. The scene was in full sun, and I had no reason why I couldn’t use a fast shutter speed to freeze the action. Shooting hand-held with a 300 mm lens of a moving subject with a shutter speed of only 1/60th of a second is a recipe for failure. And that is what I achieved. It may have worked if I had been panning with the bike motion, but that was not the case here. Lesson learned – pay attention to shutter speed with moving subjects.
August – Blurs in the Sky, Blurs on the Ground. I wrote a post specifically about this photo shoot which I titled Rookie Mistakes. I was attempting to photography the setting crescent moon in the Columbia River Gorge and even taking about 30 images, almost totally failed due to not realizing how quickly celestial objects move when viewed with a telephoto lens and not fully taking into account how much camera shake strong winds cause. This image was worse than most, since I thought the airplane was out of the frame. No amount of processing can save bad blurs, though a small amount can sometimes by saved by Photoshop work. Lesson learned – use faster shutter speeds when shooting the moon and stars with a telephoto lens; use faster shutter speeds in windy conditions.
September – Closed Eye Failure. On our trip to Montreal, Tanya and I visited the Atwater Market which included this bakery. I liked the look of the line of glass cover domes leading to where the gal behind the counter was helping customers. I shot off a quick burst of 3 images to catch the interaction between customer and clerk. Unfortunately, I caught the clerk with her eyes shut. Lesson learned – when shooting people, take a lot of images.
October – Vignetting Ingalls Lake. Last year I purchased some Xune filter holder and lens adapters to use with my polarizer and neutral density filters. I knew there would cause more vignetting than when not using the system when using a wide-angle lens. Even knowing so, I wasn’t paying attention when I took the above wide-angle shot at Ingalls Lake with the polarizer. The vignetting was horrible. It can be solved by cropping, as is shown in the processed version. However, such cropping defeats the purpose of using the wide-angle lens. Lesson learned – watch for vignetting when using filters on a wide-angle lens; if you need the filter and still want the wide-angle view, try stitching two or three non-wide angle shots together.
December – Blurry Shore. No bad shots in November because the camera barely left my bag. In December night, I was down on the shoreline in the Old Town district of Tacoma. I loved the reflection of the moon over the wavy shore. However, the wind was blowing very hard. Knowing the problems I had with wind down in the Gorge (see August above), I tried to keep my shutter speeds relatively fast, but even so I failed to get a non-blurry shot. In hindsight, I should have done more to weigh the tripod down and block the wind. Lesson learned – relearn August’s lesson and take precautions against strong winds.
Summary – We can all learn from our mistakes. Above are several of mine. In reviewing these, there are a couple of running themes – problems from contrast and problems with blurring. Those, and in fact none of the issues I’ve presented here, are new for me. But hopefully, by studying my bad shots, I will make such mistakes less and less.
By writing this post, I suppose I am starting a tradition since I wrote a worst of 2013 post last year.This time of year, there are many “best of” lists, and as I’ve already presented you with most of my best images of 2014, I decided once again to go the opposite direction once again and present the worst of the year.
First off, a disclaimer: the images presented here are not really my worst of the year. The truly worst of the worst get deleted off the memory card before downloading or are so truly horrible that they get deleted prior to my normal editing process. That said, all the images presented here would normally be deleted during my regular editing process without a second thought.
Generally editing and deleting bad images can be an educational experience if time is taken to think about why an image is bad. In other words, you can learn from your mistakes. However, when I took the time to pick the worst of the year and try to “save” them with post-processing, I found it an even more educational experience than just deleting. This is because in trying to “fix” the images, I went more in-depth into why they are bad and learned more about the limits of my post-processing work. You may want to try this exercise yourself sometime.
Now, before I start presenting these bad images, another further explanation. Last year several readers objected to my post, stating that some of my bad images were not actually very bad, and perhaps even likable. That may be true for an individual viewer, but when picking these shots, they were selected in context of my intent when shooting the image and in relation to the other images I took at the same time. For example, last year I presented a poorly exposed image of the Skagit Valley tulip fields that one reader liked. The image was made presentable by work in Lightroom, but when compared to the properly exposed images I took at the time, it was not very good. Further, the post-processing work that made it presentable caused the extreme noise in the image to be quite visible. Another consideration is the limits of presentation on the internet. A poorly focused image might look okay when presented as a 900-pixel wide image on the internet, but when zoomed into at 100%, it would look horrible. So take my word for it, these images are bad.
Okay, enough explanations and on to the bad stuff. Below are 11 of my worst images of 2014, one for each month from January through November. December is excluded because I failed to get out of my house and try to take any serious images. That in itself is a bad mistake, but I’ll leave my preference for a warm house to a rainy, cold day in the field for another post.
Each image below was shot in RAW. Except for the October image, two versions of each are presented, one without any post-processing (other than the default settings in Lightroom needed to convert a RAW file to a jpeg) and the other my attempt to “save” the image by processing in Lightroom. I few could have been further “saved” with extra processing in Photoshop, but that wasn’t worth my time. Proper technique in the field always is better than saving through post processing. With each of these images, a small adjustment in position or a correction in technique would have saved them more than any amount of processing.