Making Panoramas

Not bad, but I’m not ready to buy yet.

I spent part of Sunday afternoon in Sedona, AZ, on top of a red rock with about 270° views of the red rock cliffs around me. I was playing with panoramic photography.

I’d just bought a new tripod head for my camera. I wanted a ball head set up with a swivel base for panoramas. That means compass points marked off for precision panning. I wound up with another Manfrotto, which makes sense because the tripod is Manfrotto, too. It cost about twice what I wanted to spend, but I figured that between it and the tripod head it was “replacing” I’d have all the tripod heads I’d ever need.

Anyway, I was experimenting with panoramas shot with the camera held vertically, in portrait view. Most folks don’t think of doing panoramas that way, but if you want great big finished photos, you need to maximize your pixels. Do the math. My 10 megapixel Nikon D80 shoots photos that are 2592 x 3872. Shoot that vertically, and your panorama becomes nearly 13 inches tall at 300 dpi. That’s 5 inches taller than if the photos are shot in landscape.

Of course, the drawback is that you need to stitch more photos together to get the final image. Like this one, which is 8 images:

Sedona Panorama

In case you’re curious, the images in this panorama were shot with a 50mm focal length (that’s a 75mm equivalent for standard 35mm film cameras, if that matters anymore). All the shots had the same exposure: f6.3 at 1/160th second. The tripod head was rotated at 15° increments. If you’re looking for a seam, you won’t find one — not even in the full sized image.

This represents my first stitching attempt with Panorama Maker 5, a Mac OS application by ArcSoft. Panorama Maker takes a lot of the guesswork out of creating panoramas by automatically identifying shots taken around the same time (and likely to be part of a panorama) and handling the stitching for you. Just click a photo in its browser and it selects the shots that go with it. Tell it what kind of panorama you want, and let it get to work.

I ran into frustrations with the software immediately. For this particular panorama, even though the software’s browser recognized the images as vertical shots, the stitching component wanted to turn them all sideways before stitching. This would basically attempt to stitch the top of one shot to the bottom of the next. I couldn’t find a way around this — at least at first. But then I just told it to create a vertical panorama. I saved the resulting image and opened it in Photoshop, where I rotated it 90°.

Later I realized that if I used the software to rotate the images 90° and then rotated them back, it properly recognized them for a stitch. Personally, I don’t think that step should be required. I think the software should stitch photos in the same orientation they appear in the browser. Period.

I also tried a 360° panorama. The images were great (if I do say so myself) — 24 shots taken at equal intervals using a tripod with manual exposure settings. The software had a lot of trouble with it. It failed on several attempts and when it finally succeeded, one of the images was shifted way higher than it should have been. I had to manually edit the match points on one shot. That fixed things, but it really did take forever (or almost) on my old 15-inch MacBook Pro, which is what’s with me on this trip. At one point, the fan was screaming. And the resulting QuickTime movie looked like the first effort that it was. (You can click here to download it; didn’t think it worth embedding in this post.)

Panorama Maker is try-before-you-buy software and the folks that make it don’t time-limit it. Instead, they display the usual annoying reminder and limit save size to 1/16 of full size. Perfectly fine for testing purposes. It costs $70 to buy and I’m not 100% sold on it because of the problems discussed here. When I get time — if I ever get time again — I’ll try it on my iMac back at home. I suspect it’ll be a bit quicker and not have to wheeze to get the job done.

If I see any improvements, I’m sure I’ll have more panoramas to show off here.

In the meantime, I’d love to get comments from readers about solutions they’ve found that work on Mac OS.

Going Around

Complacency leads to sloppy flying.

I did a go-around today when landing in Sedona.

It was the second go-around I did in just over a week.

If you’re not a pilot, you might be wondering what I’m talking about. A go-around is a flying maneuver you perform when you realize that you’re botching up a landing beyond what you can smoothly — or perhaps safely — fix.

[To be fair, sometimes it isn’t the pilot doing the go-around who’s botching up the landing. Sometimes the tower tells a pilot to go around when the plane that landed before him is still on the runway. I was in a commercial airliner that did a go-around because of that. There are lots of reasons to do a go-around, but I won’t lean on any of those.]

In both cases, I was expecting a routine landing and simply wasn’t paying as much attention to what I was doing as I should have been.

Last Saturday it was while landing at a helipad at a rides event. I came in too high. If I’d been alone on board, I could have made the landing safely by simply descending from a high hover. But I had three passengers on board and enough fuel to put us right about at max gross weight. I could easily see myself running out of power in an out-of-ground effect hover with that crosswind. Why fight with it? I went around. I joked with my passengers that they were getting a half landing for free.

N630ML

N630ML at Sedona Airport.

Today, I think my brain was out to lunch while I made my approach. The AWOS reported that the wind was 170 at 17 gusting to 28. I came in almost parallel to runway 3. What was that all about? The gusty quartering tailwind had me fishtailing all over the place, dancing on the pedals as I tried to make the pad. All the time, I’m pulling more and more collective. I knew I’d run out eventually — like the guy who landed his R44 there in a bush. So even though I was only 25 feet off the ground, I pushed the nose forward, gained speed, and flew out of there. I came around in on the taxiway parallel to runway 21 (duh-oh!) and had a smooth landing, despite the gusts.

Although I’m not happy about having to go around, I’m glad I had the presence of mind to do so. Too many pilots try too hard to make a sloppy landing work. That’s where you get hard landings, bent rotor blades, chopped off tail cones, and mangled helicopters.

But today’s go-around was a real wakeup call for me. It reminded me that I’m probably not thinking as much as I should be when flying. I’m at about the 2200 hour mark and complacency is rearing its ugly head.

Flying isn’t automatic; there is thought involved. Any “routine” landing can go south at any time for any reason. I should always be prepared. I should see problems before they become problems.

And there’s no excuse for sloppy flying.

So I’m scolding myself, publicly. And I’m hoping a few more experienced pilots scold me, too. (Try to be gentle, though, okay?)

I don’t want to be involved in an accident that gets linked to from someone else’s blog.

Yes, I’m Still Among the Living

And do I hate deadlines!

I’m too busy to blog, so don’t expect much here. I finished a book and immediately flew to Ventura, CA to record a video course. I’m in a soundproof booth all day long. Then I go to my hotel and sit at a desk in front of two laptops, preparing for the next day’s recording sessions.

I’m even too busy to tweet!

On Saturday, I fly home. Then, on Sunday, I start another 6-day helicopter excursion.

Since I apparently haven’t posted anything for at least a week, I thought I’d send this just to let everyone know I’m still alive.

Maybe I’ll have time to blog next week.