Jeff Beard

This article was originally posted in response to a query on the Nature Photographers Network web site with regard to “capture sharpening”.

Being new to digital photography, my post prompted some educational responses. I’ve included some links to books and articles at the end of this post that I found with some follow-on research. I should point out that the most significant information information about sharpening workflow is that it is typically broken up into three parts:

• Input
• Creative
• Output

The bulk of this article is about “output” sharpening.

Anyway, I had read a few articles about sharpening images in Photoshop recently and while they were very helpful in figuring out how to use the sharpening filters available in Photoshop, I found that making an adjustment to my workflow had the biggest impact in the final output.

As I’ve become more serious about my photography hobby recently, one of the biggest issues I’ve struggled with is sharpening images for web consumption. I see thousands of marvelous images every week and felt like mine didn’t compare in terms of clarity, which seems like a pretty basic attribute of a good landscape photograph. I had assumed that because I wasn’t using professional equipment I just wasn’t going to get the clarity I wanted. While that’s probably still true, I’ve found that for the web, I can work around that.

My workflow had been to use the “Clarity” control in the ACR (Adobe Camera Raw) utility then as soon as I open the image in Photoshop sharpen it. The “Clarity” control made discernible changes to the image whereas the Sharpening did not. This worked better than not sharpening but when I reduced the image size and exported it as a JPEG, it didn’t look great; just “better” than they did as a RAW image file.

(The term “capture sharpening” or “input sharpening” refers to using the sharpening controls in ACR to sharpen the RAW file. This sharpening is subtle, requires viewing the image at full resolution.)

I decided to experiment with the steps I used and some of the settings applied. What I came up with is using a different algorithm for sizing down and doing the sharpening after all other adjustments are done and before I export as a JPEG.

The last couple of steps that I use are:

• Flatten the image
• Resize the image (select “bicubic sharper” from the dropdown menu)
• Change the Mode (under the “Image” menu) to “Lab”,
• Click the “Channels” tab and select the “Lightness” channel
• Apply the sharpening filter
• Change the Mode back to RGB
• “Save-As” a JPEG

The sharpening filters are under the “Filter” menu item in Photoshop. I typically use the Unsharp Mask filter (amount 100-300 [depending], radius .5, masking: default). Sometimes Unsharp Mask seems to be a big harsh so I use Smart Sharpen (amount: 100, radius .5, select “Remove Gaussian Blur” and check the “More Accurate” box). If I’ve sharpened in an earlier step, I will use only Smart Sharpen but put the level at 30-50. Sometimes there will be a bit too much sharpening, so after using one of the sharpening filters, an option becomes available under the “Edit” menu that allows you to “fade” the effect; I usually set that to 50-90. Note that for all sharpening I have the “Lightness” channel selected and that includes when I use the “Fade…” feature.

After I’ve done the sharpening, I press “ctrl+shift+~” which switches on all channels and turns the color back “on”. If I see that I need to adjust the sharpening, the I can press “crtl+1″ to select the “Lightness” channel again. Then I’ll either readjust the sharpening or take the “Fade Unsharp Mask” route described above.

I have found that by doing all color and tone adjustments, resize, then sharpening at the very end of post, the results are far, far better than when I was sharpening at the beginning or middle of processing.

Note that saving as a JPEG for the web can ruin the sharpness so you’ll need to experiment to get everything setup just right for great web images.

The most informative article I read was one by Bruce Fraser here and a more recent follow-on article by Conrad Chavez, here.

Also Bill Pelzmann from NPN who is substantially responsible for my new understanding of the art of sharpening recommended Real World Image Sharpening with Adobe Photoshop, Camera Raw, and Lightroom (2nd Edition).

Sunrise above a fog bank covering Boulder, CO

I got up early on Monday morning thinking that there might be an inversion happening since it occurred on Sunday as well. An inversion is when a layer of air pushing another down on the ground. Historically, in the Denver Basin, this has meant poor air quality. And while that may have been the case, the scene above the clouds is completely different.

I’ve been hoping that I get to see this weather event and even more so to photograph it. I think it’s a particularly unique and beautiful situation and some of my favorite photographs have been of this.

The back-range the day before the sunrise image

Having had the intuition that the fog in Boulder might have been part of an inversion, I got up early and headed out with extra strong coffee in hand. I decided that since I may be wrong about the inversion that somewhere close by would be best so I chose to drive up to Sugarloaf Mountain. You can hike to the top and there are some pretty spectacular views of the whole Front Range as well as The Plains.

I knew I had made the right decision when, after driving for 20 minutes in fog, I broke through the clouds and saw stars in a clear sky. That was a good moment.

I parked, put on my pack and hustled up to the summit. I sat down for a few to minutes to catch my breath and contemplate the beauty of what I was seeing. The fog below was actually receding, the wind was blowing and it looked like a roiling sea of clouds, always in motion. Although there were some large, yellow glowing areas where the local towns were, the clouds blocked a lot of light pollution so the sky and all it’s stars were clear and bright. These are the moments that keep me walking into the mountains year after year. They are a profound gift which is also why I like to share them.

Indian Peaks Wilderness Area

After a while, I stumbled around in the dark to find some reasonable compositions then setup my camera and started shooting. I moved around to play with the burned, dead trees and some other foreground subjects. I even shot some images of the back range too (I’ll have to head back up now that I have a feel for the location). But the call to parenting duty got stronger so I packed it in at 8 a.m. and headed back to town.

What a great morning!

As it turns out, Facebook can use your profile photo in ads. You can disable this easily enough but if you use AdBlock Plus, you’ll need to disable it before adjusting your Facebook settings. If you do not, you won’t be able to see the form.

From Jim M. Goldstein’s blog, this is the series of steps required for you to

All you have to do to prevent this is sign in to Facebook and click through to (get ready) -> Settings -> Privacy -> News Feed and Wall -> Facebook Ads -> Appearance in Facebook Ads and click “no one.”

And remember, if you use Firefox and AdBlock Plus you will need to disable AdBlock Plus in order to actually see the settings to disable the use of your photo in advertisements.

Of course, if you want to see your smiling face in online dating ads, just leave things the way they are.

Read more: http://www.jmg-galleries.com/blog/2009/07/19/your-photos-now-featured-in-facebook-ads

I recently purchased the Sigma 10-20mm F/4-5.6 EX DC HSM wide angle lens for shooting landscape photographs with my Canon EOS 40D. I rented the Tokina 11-16mm F/2.8 and the Canon EF-S 10-22mm f/3.5-4.5 USM lens before making my purchase for a reasonable comparison. (I recommend LensProToGo for renting camera equipment.)

Rocky Mountain National Park with the Sigma 10-20mm f/4-5.6

The Sigma 10-20mm lens is a reasonably well built lens compared to it’s Canon counterpart. The Canon just felt very cheap, the body was plastic, tolerances weren’t great and it felt lightweight. The Tokina, by comparison, is built like a tank so it fit well into my build quality standard. It’s bigger, well constructed and has great optics. The Sigma is in between the Tokina and the Canon in terms of construction. It’s lighter but doesn’t leave one with the sense that it’s built poorly that the Canon 10-22mm did.

For optical performance the Tokina was superior to both lenses. The f/2.8 aperture didn’t hurt either. There seemed to be more barrel distortion on the Tokina and the zoom is limited but I didn’t find that to be a big detraction since ultra-wide angle lenses make objects look pretty small anyway. The Canon and Sigma do have more zoom which is a nice but not critical feature for me.

Where I have a problem with the Sigma is with lens flare when shooting the sun. Whenever I’m shooting sunrises and sunsets, there isn’t a nice clean star burst like I’m used to with better lenses, such as the Canon EF 17-40mm f/4L. It has a unique splitting effect at the ends of the starburst that is unattractive. Further, and more importantly, the flare isn’t a nice, tight and manageable effect, it blows out the entire frame. A technique that I learned where you use your finger to block the sun in one frame then shoot another with the sun fails to resolve this issue. It’s just ugly. Note that when I get this effect I’m shooting f/16-f/22 with a polarizing filter and graduated neutral density filters.

I have not tried the Tokina in these conditions for comparison.

Sunset on Long's Peak

The last comparison is price. The Sigma is the least expensive of the three UWA lenses I tried. I ultimately made the purchase based on price and the fact that I could easily get back 80% of it on craigslist.org if it just wouldn’t work. It doesn’t seem like a risky gamble at all. And I do get some reasonably nice pictures from it. The Canon didn’t present me with a compelling reason for it’s higher price (the Canon brand isn’t important to me for this type of lens).

Regardless, if you avoid the situations where the Sigma fails, it’s price point makes it a good choice for APC-S sensor Canon cameras.

It seems that Ubuntu, one of my favorite Linux distributions, is embracing Amazon EC2 styled cloud computing in an upcoming release.

Ubuntu has included the Eucapyptus project in the aptly named Karmic Koala release 9.10 project in order for mere mortals to be able to install and manage their own cloud. Considering that some important people recommend keeping your data on your own hardware to avoid vendor lock-in and privacy issues, this allows companies to avoid the issues while getting some of the advantages of the cloud. Of course, companies will still need a team, albeit much smaller, of crack infrastructure managers but they will have the advantages provided by the abstraction of hardware and it’s associated management tools.

Besides, what could possibly be cooler than having a compute cloud in your basement data center running on a bunch of cheap PC servers? I’m sure nothing can quite compare.

I just found the Command Line Fu command repository via reddit.com. Tons of very useful commands for a variety of tasks.

For those that might not be a *nix sysadmin, you’re missing the joy of firing off scripts from the command line that can do an extraordinary amount of work in a short amount of time. I was a veritable hero early in my career when I was able to help a client replace a copyright string in some 5000 files and create backups with this one:

find . -type f -name '*.html' | xargs grep -l '©' | xargs perl -pi.bak -e 's/©1997/©1999/g'

Or something like that.

Regardless, the client was amazed and happy that one could work such magic in just a few minutes and the content in the Command Line Fu repository looks chock full of opportunities to amaze folks with your wizardry.

I’ve setup a new blog on a new server for a variety of reasons, mostly having to do with it being a terrible idea to host on my home network. I’ve chosen a hosting service provider rather than hosting it on my own hardware. I’m using Slicehost for now. It’s fairly inexpensive (not the cheapest by far), has a good amount of positive buzz around it and they use operating system virtualization. This is cool since I get full control of my “slice” (Ubuntu) just like a regular server but upgrades are done through a web-based management console so I don’t have to drive to a Denver hosting facility to do maintenance. If I need to upgrade memory or storage I can do so with a click or two. Plus I can take snapshots of the entire slice which can be used to rebuild the whole VPS through a nifty administrative console. They don’t offer much storage but I plan to use Amazon S3 for storage on the cheap.

Anyway, so far so good.

Next up is moving my 25 web sites to the new server! (Who knew I was so rich in Internet property!)

Anyway, I’ll be posting up my old articles and files over the next couple of weeks but in the meantime here’s a nice picture: