Camera wishlist

Since all of the big Photokina camera announcements seem to be out (Canon 1Ds, Nikon D2X, Fuji S3, and a couple thousand point-and-shoots), I figure it’s time for me to post my list of what I’d like to see the camera industry provide. I’ve been thinking about most of these for years. In that time, I’ve seen new cameras come and go, but I haven’t seen a whole lot of real innovation, particularly in the DSLR space, where all of the manufacturer’s effort has been focused on image size and speed.

None of these ideas are mind-bogglingly fantastic; some of them are admittedly a bit marginal. Some of them may well be bad ideas–I’d be amazed if at least some of these haven’t been tried out in the labs and found wanting. I haven’t seen any of these discussed widely online, though, so I figured I should probably share them.

In-body multiflash support.

I’d like to see in-body multiflash support. Canon and Nikon’s high-end flash systems support master/slave operation, with support for multiple flash units. Once unit goes onto the camera itself, and the others can be set up anywhere nearby, as long as they have a good view of the on-camera flash. It’s a nice concept, but it’s never worked very well for me in practice. Part of the problem is that you need multiple $300 flashes to make it work.

What I’d like to see is support for using the camera’s built-in flash as the master. You could control the flash system using the camera’s LCD instead of the small nasty LCD controls on the flashes. The big problem would be the angle of coverage of the built-in flash, but there are some easy fixes for that, too.

None of Canon’s higher-end bodies have ever included a flash, largely because pros don’t have much use for small flashes, but partially because pop-up flashes aren’t very rugged and they’re hard to weather seal. If you’re just planning on using the built-in flash as a multiflash controller, then you can get around all of this. Just make it IR-only, don’t include a pop up, and make the entire top of the prism hump IR-transparent. Just shoot the flash straight up. Since there are no moving parts, it’s easy to seal and fairly rugged. Since it has 360° coverage, it should work great indoors. And since it’s IR, it won’t interfere with your other lighting.

Bluetooth

I like Bluetooth–I have a Bluetooth phone, a headset, a GPS receiver, and a USB Bluetooth dongle for my Mac. It works great as a low-bandwidth, low-power communications mechanism. I’d love to see it on a camera.

What it’s not:

  • a way to download pictures. It’s way too slow. It makes USB 1 look dangerously fast.

What is is:

  • A wireless way to use GPSes with the camera. Nikon supports serial GPS units, but then you’re suffering from dangling wires. With a bluetooth GPS, it’d be easy to annotate each frame with the location that it was shot.
  • An alternative to on-camera microphones for voice annotation. Better weather sealing on the camera.
  • A remote-control system. You could set exposure and trigger the shutter wirelessly from a laptop, PDA, or even phone.
  • An improved system for multiflash systems. Instead of using optical signals, the body could talk to the flashes using Bluetooth. This would let the body query the flashes directly, one at a time, allow a lot more flexibility, and cut down on the need to have a line of sight between the master flash and each slave.

Of course, you could use nearly any cheap, low-power wireless standard for any of these. Bluetooth has the advantage of being available on the market today and being fairly easy to work with.

Floating-point image formats

Dynamic range is the last big hurdle facing digital photography. Traditional film media can handle a much wider range of light and dark then digital image sensors. Black and white film is traditionally viewed as recording 10 stops of contrast; color negative film is around 7 stops. Color slides and digital cameras are usually closer to 4 or 5 stops of usable contrast. The eye, unaided, is good for well over a dozen stops.

There are two sides to this problem. First, current imaging chips aren’t very good at handling especially bright light, and they tend to clip the brightest parts of the image off. The Nikon D2X and the Fuji S3 both have technologies designed to combat this.

However, even with an ideal sensor, current cameras are limited to 7 or 8 stops, simply because they use 8-bit JPEGs to store their images. Unless you’re willing to use RAW mode on the camera and spend a couple minutes tweaking each image and then dump it into Photoshop in 48-bit color, eating 30–80 MB per image, you aren’t going to go beyond 8 stops.

The pain doesn’t stop once you get the image into Photoshop, though. The problem is that the normal representation for color images in cameras and PCs uses one fixed-size integer per color. Typically, you have either 8 or 16 bits of information per color, with 3 colors per pixel, for a total of 24 or 48 bits of data. The problem is that the information that you care about (lightness vs. darkness) isn’t spread over those bits in any sort of optimal pattern. With an 8-bit integer, the brightest stop of light uses values from 128–255, or half of the total range. The next-brightest stop goes from 64&ndash127, then 32&ndasah-63 for the third-brightest stop. After peeling off the three brightest stops, there are only 32 color levels left for the remaining 3 or 4 stops. If you do much processing at all, you’re going to find banding and noise lurking in the shadows.

There’s an easy way around this, and movie special-effects types have been using it for years. Instead of using integers for color values, use floating-point numbers. Floating point is what computers generally use whenever they’re dealing with real-world numbers, like measurements or sizes. Generally, any time you see a decimal point on a computer, you’re using floating point numbers. Internally, they’re stored in the computer in a form kind of like this: M * 2^E. The computer keeps track of M and E (technically known as the mantissa and the exponent), and the rest of it is just implied. So, for example, a 32-bit integer can represent numbers from 0 to roughly 4 billion. A 32-bit floating point number can represent numbers from -10^38–10^38, but at the cost of a bit of accuracy. Fortunately for us, the accuracy comes where we care about it the least–in the lower-order bits where sensor noise lies.

Instead of using a 32-bit float for each color, we can even cheat a bit. We could get by with a 16-bit float for each color, with an 11-bit mantissa and a 5-bit exponent; that’d be enough to cover 32 stops with nearly as much color detail as modern sensors can record for their brightest stop. Or, we could cheat and share the exponent between the three colors; done this way, we could fit three 14-bit mantissas and a 6-bit exponent (64 stops) into 48 bits, or three 9-bit mantissas and a 5-bit exponent (32 stops) into 32 bits.

The advantage of any of these formats is that they’d hold the same amount of detail in each stop, rather then bunching it all up in the brightest bit of the image. This would allow a number of small improvements and one very large one: we could finally represent colors brighter then white. Even if the screen or printer can’t reproduce a specific bright color, you can still represent it in the image.

(Apparently Apple has some support for this in Tiger, and nVidia’s newer graphics cards can do 16-bit float displays)

Built-in hard drive

I’d love to have a DSLR with a fixed 1.8 inch (iPod-sized) hard drive instead of a CF slot. You can easily get 40 GB drives in that form-factor today, with 60 GB drives on the horizon. A 40 GB drive would hold almost 3,000 1Ds mk II raw images, or over 10,000 D60-sized JPEGs. In other words, you could shoot almost any event without needing to worry about storage. Just shoot, and sort it all out later. No card swaps, no dropping them in the mud, no dust in the CF slot, just shooting.

If you drop the camera, the drive might have problems, but I’ve dropped my iPod from waist level without it croaking. What would a 3-foot drop onto a hard surface do to most camera bodies? Drive failure could be a problem, but it’s probably no less likely then shutter problems or stuck apertures, and people have dealt with those for decades: you bring more then one camera.

If you’re worried about crashes eating the images that you’ve already shot, then either keep an assistant handy to do downloads when you swap bodies, or use a wireless adapter like Nikon or Canon’s and have it download images onto a laptop while you’re shooting. The in-camera drive just turns into a big buffer and a backup for your laptop’s copy of the images. Done correctly, you’d end up with two copies of every file in fairly short order; try that with CF cards, and compare that to the dear lab please don’t eat my film this time fear that we all used to have.

That doesn’t even touch the performance factor–the specs for Toshiba’s 40 GB drive suggest that it should be able to sustain around 20 MB/sec on the outer edge of the drive. Compare that to 5 MB/sec for CF cards or 7 MB/sec for SD cards. Shooting 15 MB RAW images (1Ds mk II-sized), that’s 1.3 fps sustained. Shooting 5 MB JPEGs, that’s around 4 FPS. With a camera like Canon’s 20D, you’d be able to shoot 1,000-JPEG bursts.

Of course, it’d have a big battery hit, but I don’t see that as a big problem right now. The latest generation of pro cameras can shoot over 1,000 frames per battery, and battery technology and low-power electronics are boosting that around 50% per generation. We’ve reached the point where you can shoot 15 GB of data per battery swap, but you have to go through a dozen or so flash cards. Trading battery life for storage capacity doesn’t seem like a bad trade-off to me.

Digital Rangefinder Camera

I’d love to see a small, interchangeable-lens digital rangefinder camera. Like film rangefinders (Leica, etc), it can be tiny because it doesn’t need a SLR’s mirror. Unlike film rangefinders, you’d have the options of doing autofocus using the image chip for AF. Unlike digital point-and-shoots, you’d still be able to focus manually, even in low light, which is where rangefinders have always excelled. And unlike film rangefinders, you’d be able to see through the lens if you feel the need–think long lenses or parallax. It be a great mixture.

This would be a great market for one of the smaller manufacturers, like Olympus, Pentax, or Minolta. They really can’t compete with Canon or Nikon with DSLRs right now, but they can produce a smaller body that takes small lenses and then produce an adapter that will let them use some 35mm SLR lenses with the body. Its a niche, but it’s one that Canon and Nikon can’t move into without cannibalizing their DSLR market, so it’s probably fairly safe.

Epson has started down this road with their R-D1, but it takes Leica lenses, so it can’t do autofocus. To do this right, you’d really need a new lens mount with electronic controls and a really short focus distance; to the best of my knowledge, no current lens mount combines the two. I had hopes for the 4/3 people, but they don’t seem to be headed down this road (or anywhere else, either).

Posted by Scott Laird Wed, 22 Sep 2004 22:59:14 GMT


Nikon D2X?

I’m a Canon guy, but one of my Nikon friends forwarded me some specs for Nikon’s latest DSLR, the D2X. Allegedly, these were released by Nikon Denmark:

  • 12.4 MP, 5 FPS, 16 shot raw buffer
  • reduced-frame 6.8 MP, 8 FPS, 29 shot raw buffer
  • Everything else basically similar to the current D2H.

The specs seem kind of weird to me–the buffer size and frame rates are closer to a sports camera (like the D2H) then a studio camera. The buffer sizes, particularly, seem aimed at people shooting lots of frames in a row, which isn’t the market the the DnX series has went after in the past. On the other hand, having a dedicated mode that only uses the center pixels of the image chip sounds like a decent way to please sports shooters–you get higher magnifications, which is fine when you’re using long lenses anyway, higher frame rates, and smaller files, all in one.

I’d wait to see official confirmation of this before I thought about ordering one. Of course, I’m not really in the market for a new Nikon.

Comparing the D2X to Canon’s two top-end cameras in interesting:

  • The 1Ds (11 MP, 3 FPS) is slower with slightly lower resolution, but it has a much larger imaging chip which gives it better wide-angle performance and probably lower noise levels. Also, the 1Ds is rumored to be replaced soon.
  • The 1D mk II (8 MP, 8 FPS) is in between the two D2X modes. It’s higher resolution then the lower-resolution mode and faster then the high-resolution mode. It also has a larger imaging chip, which gives better wide-angle performance, and a larger buffer.

Most likely, Canon will introduce a 1Ds mk II in a week or two, and Nikon’s new body will be left by the wayside again, just like the D2H was when the 1D mk II came out.

Posted by Scott Laird Wed, 15 Sep 2004 21:02:27 GMT


Ilford going down the tubes

PhotographyBLOG mentions that Ilford is having trouble. I was a big fan of their black and white film for a while; I loved Delta 3200, even though it was happier at 1200-1600 then at 3200. Most of my favorite B&W shots were on Delta 3200.

They’ve apparently been pushing their way into digital photography with a line of paper products, and they’re a big OEM supplier of inkjet ink, but that doesn’t change the fact that their traditional product line is dying.

I’d love to have the time and money to shoot black and white film, but I’m happy enough with the results of running digital images through Photoshop’s channel mixer, and it lets me deal with color filters after I shoot, not before. Maybe someday I’ll get a 4x5 camera and go back to B&W, but it’s not going to be this decade.

Posted by Scott Laird Tue, 24 Aug 2004 19:51:42 GMT


Canon 20D

It looks like Canon is just about to announce a new DSLR. I can’t find the specs on their website yet, but they’ve posted a press kit full of pictures. There are some specs floating around on the net:

  • EOS-20D
  • 8.2 MegaPixels
  • DIGIC II
  • 1:1.6x Crop
  • 9 Point focusing
  • 1/8000s Max Shutter speed
  • 5fps Continuous speed
  • 25 frame buffer
  • EF-s support
  • E-TTL II support
  • 0.2sec startup time
  • 50g lighter than 10D

I’m not sure what’s up with the AF system, but the rest of the specs look just about right to me. I’d love a camera with a slightly faster frame rate then my D60, about twice the buffer capacity, and faster startup times, and that’s about what this provides. They even threw in a couple extra pixels, not that it really matters. The rumored price is $1,600 MSRP, $1,300 street, which is pretty good. The official announcement is due on Friday.

There’s also a rumor of a 10-22 EF-S zoom. EF-S lenses only work with the 300D (“Digital Rebel”) and the new 20D, so the new lens isn’t very useful on my D60, but wow–10mm is wide. Sigma and Nikon both make 12-24mm zooms, but 10mm is a new record, at least on a 35mm-like body. Unfortunately, since the Nikon 12mm zoom is over $1,000 and the Sigma is up around $700, the Canon lens will probably be kind of pricey.

Posted by Scott Laird Wed, 18 Aug 2004 12:36:18 GMT


The wedding pictures are out of my hands!

The pictures from the wedding that I shot almost two weeks ago are now in the posession of the bride and groom. I’m done with the whole project, so I finally have time to get to some of the other tasks on my to-do list. Like checking out Rails.

Posted by Scott Laird Thu, 12 Aug 2004 04:25:49 GMT


Custom Photo Postage Stamps

This is so cool. Boing Boing is reporting that Stamps.com has launched a custom photo stamp printing site, photo.stamps.com. For around $1 per stamp, you can have them make custom US postage stamps for you. Here’s a quick sample, using one of the images from the wedding I shot a couple weeks ago:

Just the thing for thank-you notes.

Posted by Scott Laird Tue, 10 Aug 2004 20:50:42 GMT


So close, yet so far yet to go

I’ve spent all day today split between two tasks. On one hand, I’ve been trying to finish all of the wedding pictures; at this point the web gallery is complete, and C1 is almost done rendering all of the printable images. Considering that it started at 11:00 last night, it’s a clear sign that I need to go buy a G5.

Unfortunately, that was the easy job. With the help of my brother-in-law, I’ve been pulling Ethernet cable through the house all day. So far, we’ve pulled wire and terminated plugs in 6 rooms, but actually getting to all of those rooms was a major pain. We have wire running through two different attics, both garages, a crawl space, and into rooms on three different floors of the house. We’re both exhaused, and I’m not quite done yet–I need a RJ11 keystone jack, one more keystone coverplate, and some drywall repair goop. Oh, plus an extra Ethernet switch. Fun stuff. I wonder if any of it works right.

Update: Yeah, it works. Mostly. I killed our home phone service for an hour or so while trying to shoehorn the kitchen’s legacy POTS line into a keystone jack; in the end, I hand-twisted the red and green wires together for the night; tomorrow I’ll go buy something more suitable that will let me splice together a working phone system. Other then that, everything’s good. The Cisco 7940 in the kitchen is up and pingable, and that’s an improvement over our recent wireless networking performance.

Asterisk logs whenever a SIP phone becomes unreachable. It’s looked like this recently:

MonthNumber of unreachables
April114
May112
June187
July319
August245

Clearly, whatever’s been causing problems has been getting worse. Since each of these events is enough to kill an in-progress phone call, I now understand why my wife has been pushing me to fix the phone.

Posted by Scott Laird Sun, 08 Aug 2004 02:10:58 GMT


Wedding pictures complete!

Last weekend’s wedding pictures are completely sorted and adjusted in C1. The last batch of them is now processing. All in all, I ended up with 292 images. I was aiming for 200, but at this point, I don’t have time to find another 92 to remove. It’s easier to just spend the time and money to process and print proofs of the extra 92 frames.

Actually, that’s cheating slightly–there are around a dozen shots that I want to open up in Photoshop and convert to B&W. That shouldn’t take long though, and I can’t do that until C1 finishes rendering another 1,400 of so images–fill-size TIFFs and web JPEGs for the final 98 frames, plus 4 different printable color-corrected JPEGs for all 292 images.

I really enjoy photography, and shooting weddings in particular, but the image editing time is killing me. That seems to be a common sentiment among photographers.

Posted by Scott Laird Sat, 07 Aug 2004 06:08:12 GMT


Another wedding in the bag, and some comments on C1

As mentioned a while back, I shot another wedding this weekend. This was the first wedding that I’ve really enjoyed shooting–it was outdoors in Kirkland early in the day, the weather was great (if a bit bright for outdoor pictures), and everyone was happy to be there. Somehow, this felt smaller and more laid back then my sister’s dinky island wedding in Antigua a couple years ago, and that’s saying something. The couple clearly belongs together, and their family and friends were there to celebrate it. That’s supposed to be the point of the whole affair, but it’s been known to get lost in the middle of all of the planning.

Now that the wedding’s over, I have 750 or so pictures to take care of. That’s an improvement over the 2,000 frames that I shot at each of the two previous weddings, but I was shooting for 600. I’ll blame the happy couple and their family–I couldn’t resist the urge to take a couple extra shots here and there.

I’ve been using PhaseOne’s C1 image-processing software to process images from the wedding, and I’m mostly happy. It’s reasonably fast, easy to use, and it produces great images. I’m really impressed with the tools that it provides for tweaking your images without requiring you to jump into Photoshop.

Unfortunately, it’s pretty clear that the cheap model, C1 LE, isn’t going to cut it for processing 750 wedding pictures. It’s limited to processing 20 pictures at a time in the background, and it can only spit out one type of output file per input file. So, late last night, I downloaded the C1 Pro trial version, and it seems quite a bit more useful–it’ll let me batch up hundreds of images at a time for overnight processing, and I’m having it spit out a full-resolution 16-bit TIFF file, a half-resolution web JPEG, and a set of color-corrected 4x6, 5x7, and 8x12 JPEGs for a local lab, all automatically.

That left just one little problem–C1 seems to leak memory. It’s currently using 335 MB of RAM on my laptop, and the total’s growing. It makes it really hard to leave C1 running in the background while I work on other work. I guess that’s the price of progress.

Posted by Scott Laird Mon, 02 Aug 2004 14:35:00 GMT


PhaseOne C1 LE for the Mac

I just received some very pleasant vendor email–the “LE” level of PhaseOne’s C1 DSLR raw image processing software is now available for OS X. C1 comes in 3 flavors: LE, SE, and Pro. The SE ($250) and Pro ($500) versions have been available for the Mac for a while, but not the LE ($99) version. I’ve been tempted to buy C1 for a while, but I just can’t see paying $250 for it. If I was a Windows user, then I’d have bought the LE version a year or so ago.

I’m off to download the free trial…

Posted by Scott Laird Fri, 30 Jul 2004 01:50:29 GMT