Photographing Grebes with the 5DS R

The 5DS R became my main camera the instant I got my hands on it. Honestly, I thought that it will somehow augment either the 7D Mark II or the 5D Mark III as a high-res landscape camera, while one of those will remain my wildlife camera. I was wrong.

The 5DS R has so many seductive qualities that I tend to forget all its shortcomings and difficulties (more on those later).

Colors are bold and thanks to the anti-aliasing cancellation filter it can produce lovely crisp images. Such as the following one.

aaa

A moment before diving

It was taken in early morning light with the Canon 500/4 IS II lens and the 1.4x III teleconverter. It’s a moderate crop of about 26 megapixels – still enough for a 40×60 cm print. Yes, you can crop the hell out of these files, and still retain a huge amount of details due to the lack of AA filtering.

Some of my former grebe images are 6-8 megapixels from the 1D Mark II… So its a huge increase in usage flexibility.

Of course those huge files have a few consequences you have to live with. First, the 5DS R feels like a medium format camera. From the sound of the mirror to the time it needs to display an image on the LCD. It feels like you travel a decade back in time… Press the play button and wait… Also I haven’t experienced buffer full issues since the 1D Mark II – but run into that quite a lot even using 1066x Lexar CF cards.

You also need more time to cull a shoot. Fortunately I have an app for that: with Kuuvik Capture 2 I can sift the daily crop of 1500-2000 images pretty quickly. An old friend of mine was sitting besides me last morning and was surprised how fast the app deals with 50 MP files (and this was on a 1.4GHz 11″ MacBook Air I use as a field computer).

The next one is cropped from the sides for the rectangular composition. Same lens and converter combo. I stop down to f/6.3 with this combination, which is a bit below the f/6.7 diffraction limit of the camera. So unlike landscapes, one doesn’t have to deal with the depth of field versus diffraction issues here.

bbb

Curious visitor

Surprisingly, I found ISO 800 images a bit sharper than ISO 400 ones, so all of these were made on 800. I’ll have to investigate this further before I can draw serious conclusions. But until then, ISO 800 seems to be perfectly usable with no need for extra noise reduction.

The images in this post are the tranquil ones (the action shots are saved for another post). The 5 fps maximum speed turned out to be usable with a little anticipation of what’s going to happen (which also helps your photographs and in the understanding of the behavior of the species you are photographing). But for fast paced action I still reach for the 7D Mark II.

I tend to like to include a bit of the bird’s habitat in my images (maybe I should call them birdscapes), for which the full frame sensor is a real boon. And I can crop the surroundings away if a tight composition is what I’m after.

ccc

Breakfast for the nestlings

AF is superb. The best I’ve ever found on a Canon camera (excluding the 1D X, because of it’s faster focus driving speed). The only thing I miss is the AF mode selection lever of the 7D Mark II. I find myself reaching for the lever and cursing who’s responsible for this omission quite often.

A hot topic is the dynamic range of current Canon sensors. Well, while sometimes I would need more (maybe a handful of times during the last 12 years), what the 5DS R offers usually pretty much enough. Especially that I print my images where I have just 6 or 7 stops, and usually expose my images properly with no need to recover from the shadows. Also I like to utilize clipped highlights and shadows as artistic tools… So I’m not complaining on this front.

ddd

Good night!

As you may already think, I really like the 5DS R. It’s not the absolute fastest and the most suitable camera for bird photography, but those limitations are igniting my creativity and are not in the way of image making. It’s an exceptional tool for making the kind of photographs I have in mind.

Kuuvik Capture 2 Beta 2: Performance

As Beta 2 of Kuuvik Capture 2 is nearing completion, I felt it’s time to talk about the incredible performance improvements of the product.

Beta 2 switches away from Canon’s EOS SDK in favor of my EOS Extensions library. EOS Extensions powers ShutterCount since its first day, and now Kuuvik Capture uses a heavily expanded version.

This change brings several improvements to the app. It is now 64-bit, sports a more fluid WiFi pairing experience, and occupies less than 10% of the disk space needed for Beta 1. But the most prominent improvements are in the energy consumption and processing speed areas.

Let’s jump right in. The following chart shows the relative energy consumption of the Beta 1 and the Beta 2 (as well as Canon’s EOS Utility for reference) while running live view. The Beta 1 figure is roughly the same as Kuuvik Capture 1 was.

All performance figures are calculated from measurements done on my 2012 15″ Retina MacBook Pro, and may change in the final product – but I think they are pretty much indicative of what you could expect.

kc2b2-energyimpact

Even the previous Kuuvik Capture incarnations were no slouch, but the improvement in Beta 2 is huge. It’s energy impact (which is a number OS X calculates mostly based on CPU utilization) is a tad less than 40% of EOS Utility! Actual energy consumption may be a little different as other parts of the system also draw power, but I would realistically expect 2x longer battery life on my MacBook than what’s possible with EOS Utility.

Also take into account that Beta 2 does a lot more number chrunching during live view than even the pervious beta: it’s output is visually better and now always color manages the live view stream. Because of the latter, the color management section has been removed from Preferences.

I mentioned that Kuuvik Capture 2 ditched libraw (an open-source RAW processing library), and now uses my own code. I cited some 2.2x processing speed improvements then. I’ve hand-optimized the RAW decoder in EOS Extensions, and image processing is now up to 5x faster than Kuuvik Capture 1.

kc2b2-processingtime

In other words, the Beta 2 loads and processes a huge 5DS R file on my MacBook Pro in about 1.6 seconds.

Yes, Kuuvik Capture 2 will support the 5DS and 5DS R. Raw decoding support is complete, and the cameras will be characterized and enabled as soon as my 5DS R arrives.

We have a few places left in the Kuuvik Capture 2 beta program. If you would like to participate, please download and complete the Beta Application and NDA form, and send it back to beta@direstudio.com. If your application is accepted, you will receive download instructions within a couple of days.