Just a Thought...

In the process of trying to coerce a working system in my darkroom, I purchased the book “Beyond the Zone System” because I know it has a lot to help understand sensitometry. What appeals to me is the ability to both test the speed of your film and the development time within 6 sheets. Since Ansel Adam’s film speed test takes seven sheets and an unknown amount of sheets for the dev test (at least one but in practice a few more), I’m all about conserving resources. The cost of the sheet of film is only one part of the cost—it’s the investment in time that I’m most concerned about.

BTZS starts out with a nice little overview of how paper and film work together to make the finished image. It also has a review of all the types of math and graphing theory that pertains to this testing process. The math’s not that hard, but the problem is in the way it’s presented. You can tell the author has a wealth of information, and he tries to make it accessible all in one or two chapters, but you almost end in confusion.

Where my head really starts swimming is when he gets in to calculating film speed. With Ansel Adams, it’s simply a density of 0.1 over film base+fog. The author covers the history and the pros and cons of how film speed was calculated over time, instead of just choosing one and teach how to do that one. It’s useful information, but the alternatives could be moved to an appendix to make that section more accessible.

With a proper handle of the basics of how the film and paper relate to each other, you can intelligently make decisions on exposure, development, and printing decisions. The road to understanding taken in the BTZS approach is very technical, which is not for the feint of heart. However, once you’ve learned the basics, you learn useful bits of information. For example, changing development times is similar to changing apertures—they both follow the same geometric progression of numbers (4, 5.6, 8, 11, 16…) to produce the same changes in final density. Shutter speed times and film speed numbers follow the same progression of numbers.

If you are serious about understanding more about how your materials work and respond to light, this book is definitely something you should have in your library. It will take time to “get it”, but once you do it will help you with your final results. You have a better understanding of why you choose a particular density for your print materials. You also have a better understanding of how zones don’t equal stops of exposure—yet the two still relate predictably.

I’ve been playing with the Adobe Lightroom tool lately, mainly because I have a lot of pictures to manage. When it comes to sports photography, you end up taking hundreds of pictures a game. Even with 6 fps you get close to that critical moment, but many times just a bit off. A typical high school basketball season lasts for three months with roughly two games a week, rarely with a night off. Some of you are doing the math right now, let me save you some time: the season isn’t over yet and I have 1,872 pictures. That’s a lot to go through. I thought that in order to help me out I needed a system to weed out the not quite good enough and get a top 10 for each game, and then from there further refine to the top however many I decide. That task proved ridiculous when I used Photoshop Elements, but to be fair it really wasn’t designed for the purpose.

I’m happy to report that Adobe Lightroom is a very powerful and useful tool for your digital photography needs. I really don’t need a full Photoshop package, and at $650 US it’s a little out of reach anyways. Lightroom is a more manageable $299 US, which is still on the expensive side but it does everything I need—including the light touch ups I do for color correction and cropping. Aperture is equally powerful from what I hear, and based on whatever you get comfortable with first you tend to like. O’Reilly sponsored a week long review of an Aperture user learning and using Lightroom and vice versa. The result is both authors had legitimate reasons for their preferences, and neither was wanting to switch… Even though they gave the other app mad props and even recognized when things were done better. Bottom line is that whatever fits the way you do things, that’s what you want. Both have free 30 day evaluations, so take advantage of it and properly decide.

The main point wasn’t a comparison of Lightroom, Aperture, Photoshop Elements, or Picassa. The point was whether the claims of digital camera salesmen hold up. It also affects how we design user interfaces, but more on that later. The salesman will tell you how digital provides “instant feedback”, “lots more room than a roll of film”, “you can always fix it later”, etc. Sure, my DSLR provides instant feedback but I find that annoying, so I turn that feature off. I have to concentrate on what’s going on around me, not the toy in my hand. I need to be ready for a fast break, a drive to the basket, a beautiful no-look pass. I’ll miss it if I’m constantly distracted by that screen shining off of my cheekbone. Sure, it’s convenient to not have to change rolls in the middle of a game, but I tend to take too many pictures—most of which are good, but not great. I found that when I was using film I would budget 36 pictures per quarter (one roll per quarter), and that worked. Of course, scanning them to manage them was a pain. Now I have anywhere between 175 to 300 pictures in a game. I’m more wasteful instead of better. Of course, fixing it later is a major pain. I’d rather get it right, or at least really close at the time I take the picture.

Lastly, we have to really think about what the purpose of photography is. It’s to have pictures. You know these images on hard paper with a nice finish… I find that when you have 90% of the pictures you take never see paper, you have to wonder if you really need to manage the pictures. If it really wasn’t memorable, then why hold on to it? I’m sure you can tell me many reasons why, but these are legitimate questions you have to answer. The big one, of course, is what is the purpose of what I’m doing? Why is it that I have so many pictures to manage, but there’s no actual picture? Who’s going to look at these and actually enjoy them? People only have so much attention span, so a top 20 might be the limit of someone’s attention span for a slide show.

The bottom line is that better disciplines make you a better photographer, not better gadgets. If you can’t appreciate what a feature can do for you, you don’t need it. Far too much attention has been placed on the gadgets on not on helping someone do what they really want to do. If the idea is to focus on photography, then get out of the user’s way and let them do what they want to do—and no more.

In the analog world, the focus has always been on the hard picture. If you have to print the pictures yourself, you’ll be a lot more conservative about what you believe is worth taking. There’s a fair amount of work involved in getting a good print. It’s rewarding work, but work nonetheless. People have discovered that they are more drastic with their adjustments in the analog world than they are in the digital world, and the picture is better for it. I think a large part of that has to do with the delayed feedback. As we make changes in the digital world, we see every little thing and intermediate step immediately, and the more drastic changes scare us, so we don’t complete what we were originally thinking. In the analog world, you make the changes and prepare everything you need at once without seeing it appear in front of you. When you develop the print, you are pretty happy with the work you did. In a way, the instant feedback hurts more than it helps.

Have you ever started typing in a password for one of the many resources that require one and right in the middle, the focus is snatched away by another program? It’s particularly troublesome while the operating system is starting up. Talk about a security risk. What if the thing that stole focus from my email password prompt was going to broadcast my keystrokes somewhere else? It should be illegal to steal focus while the user is typing into any text box. It’s just sheer rudeness, and I’m tired of it. Here I am trying to get something productive done and the operating system that is supposed to be helping me do my job is interrupting me with stuff I don’t care about.

I can answer the prompt telling me that my monitor is past due for a recalibration after I type in my email password. Why steal my focus from what I’m typing in right now while a new window is popping up in the background? Shouldn’t that stay in the background? I’ll start a few things at once knowing they’ll take some time to finish up, but that doesn’t mean I want them to jump in front of me when they are ready. I’m a grown a** man, I can decide for myself what and when I want to do things on my own computer. Tell my why it’s so important to grab my attention while I’m typing in a URL?

Listen Microsoft, Apple, Linux, and any other wannabe contenders out there: I want a polite operating system. Get out of my way and let me do my job the way I want to do it. If an application doesn’t need my attention at the moment, don’t grab it. If an application does need me to do something, let me finish what I’m doing in the application right now. Make it illegal to steal focus if I’m typing in a text box—especially if it is a password box. How hard can it be? Heck, I don’t mind you flashing the application button on the task bar until I address the need, but don’t allow any application to usurp control whenever it wants to. Only allow applications to request control.

Lastly, make sure that your scheduling system will make sure there are enough resources for me to continue typing in what I’m typing in without background processes interrupting me. Why should an application ignore keystrokes just because another application is loading in a butt-load of libraries? Why should I have to restart typing in my passwords because the operating system can’t keep up with me and simply ignores the keys I’m typing in? It’s the 21st century for crying out loud. These annoyances should be a thing of the past.

Sure it’s cheap for me to complain, and it’s cheap for you to say “build it yourself if you don’t like the way we do things”. But there is a free market economy. We specialize in different things. I do application work, but if you want to pay me to do operating system work I’ll be happy to take on the challenge. If Apple OS X is a polite operating system let me know, when I upgrade my machines I’ll switch. But to date, I haven’t run across one single operating system that can behave properly in this regard.