Making the Canon 5D Mark IV Soup

The following is a satirical look on how Canon designed the Canon EOS 5D Mark IV – followed by a little more serious discussion.

Sitting on the old, weathered coffee table in my office, the camera is waiting for the validation tests for Kuuvik Capture 2.5

Sitting on the old, weathered coffee table in my office, the camera is waiting for the validation tests for Kuuvik Capture 2.5. It makes a killer combo with the EF 35mm f/2 IS lens, just like the 5D Mark III did.

Ok, so let’s begin with the ingredients:

The recipe is pretty straightforward, anybody having access to these quality ingredients can cook it after a few years of making soups like this.

Take the EOS 5DS R, and replace the sensor with a new one based on the current generation design with on-chip ADC (like the ones in the 80D and 1D X Mark II). Since the sensor is a bit smaller resolution than the one it replaces, frame rate can be increased a bit. Peel the 7D Mark II and add its weather sealing and a slightly modified version of the AF point selector switch to the bowl.

Crush the 1D X Mark II, but be careful that both the GPS unit and the AF sensor remain unharmed, we’ll need them. Unfortunately crushing the body will destroy the red AF point illumination and the CFast card slot, so there’s no chance to improve our soup with those extremely fine parts. Yes, use the GPS unit from the 1D X II, since the 7D II’s unit has a digital compass, and that might cause disorientation and dizziness even in small doses.

Cut the 80D in half, pull out the touchscreen and the Wi-Fi. But be extremely careful to clean the Wi-Fi thoroughly, otherwise the soup will taste like crap. Add these to the bowl. Season to taste with Dual Pixel RAW.

— ooo —

Tech companies (and Canon is no exception, just like us) love to reuse existing components in new products. This greatly improves return on investment (good for the company) and reliability (good for the customer).

The 5D Mark IV is a premier example of smart cooking from these components. It’s a serious upgrade for anyone using the 5D Mark III and doesn’t need high resolution or high frame rate. That is, a highly versatile generalist camera.

But since I own and love a 5DS R and a 1D X Mark II, this soup is not for me. I have been using a high res + high speed combination for years, and I prefer it to a single generalist camera, or even a pair of those cameras (I had a 5D Mark III for years, but life is much better now).

Stringent Look - Canon EOS 5D Mark III with EF 500mm f/4L IS USM + 1.4x III

Stringent Look – Canon EOS 5D Mark III with EF 500mm f/4L IS USM + 1.4x III

Photos in this post were made with the 5D Mark III years ago – despite having a rental body for adding it to Kuuvik Capture, I had no time to go out and shoot (not to mention that the weather was dull). But since the Mark IV is s direct replacement of the Mark III, they illustrate the kind of images I usually make with a body like this.

There are things that I really miss, however:

  • CFast 2.0. The 1D X Mark II showed that they are in a completely different league in speed and user experience compared to CF. With CFast the Mark IV’s smallish buffer (21 shots) would not be an issue at all.
  • UHS-II for the SD card slot. UHS-II would be a lower cost alternative to CFast 2.0 (but still faster than CompactFlash: speed ratings are 633x for UHS-I, 1066x for CF, 2000x for UHS-II, 3500x for CFast).
  • USB Type-C socket. The USB3 Micro-B socket the Mark IV (and all USB3 Canons) uses is the worst connector plug I ever saw (only Apple’s 30-pin dock connector comes close). Fragile, hard to insert properly with cold fingers, etc, etc. Canon (and everyone) should use the reversible USB3 Type-C plug these days. With A-to-C cables for legacy computers only having an A socket.
  • Red AF point illumination. See my former opinion about the crappy solution used in every contemporary Canon except the 1D X Mark II.
  • Usable Wi-Fi. The 5D Mark IV shares the snail-like Wi-Fi implementation of the 6D/70D/80D. Come on Canon, 9MB/s peak transfer speed over 802.11n for a 30mp camera? In 2016? To make things worse, you can’t use a much faster WFT-E7 external transmitter to speed up wireless tethering.
Window Remnants - Canon EOS 5D Mark III with EF 50mm f/1.4 USM

Window Remnants – Canon EOS 5D Mark III with EF 50mm f/1.4 USM

Would I recommend it to a friend?

It boils down to a pair of points: if you need ultra high resolution and are willing to spend a small fortune on lenses that actually can deliver the resolution, then no. In this case get a 5DS R, which is prominently usable even for birding. Or if you need a high-fps camera, then don’t fret about the Mark IV’s frame rate, go get a 1D X or 7D II for yourself.

But in all other cases I can recommend the Canon EOS 5D Mark IV – it’s a really nice camera and a joy to use. Well, it’s not a surprise as all professional Canons I happened to use since (and including) the 5D Mark III were exceptional tools. And I totally agree with Canon’s philosophy to please actual photographers and not tech journalists and bloggers (you know, the kind harshly complaining about “lack of innovation”).

Shameless plug

If you are upgrading from an older camera, such as the 5D Mark II, 5D Mark III or either 7D, you’ll probably need my ShutterCount app to let the buyer know how many shutter actuations your old camera has.

Kuuvik Capture 2.5 with 5D IV Support Available

The latest update to Kuuvik Capture is now available on the Mac App Store. It brings complete Canon EOS 5D Mark IV support, including the ability to shoot and display Dual Pixel RAW files. I’d recommend to check out my former notes on 5D Mark IV RAW files.

This release also boosts RAW decoding and camera communication performance – you can find more details on these improvements in my previous post.

A new preference

As a first step toward JPG support, you can now shoot RAW+JPG (Large/Fine) in the camera. Since Kuuvik Capture works from the RAW file only to display the histogram and highlight/shadow warnings, just the RAW files are downloaded even if you shoot RAW+JPG. JPG files are saved to the memory card.

The new "Image quality" preference

The new “Image quality” preference

You can switch between RAW (the default) and RAW+JPG Large/Fine in Preferences.

Notes on macOS 10.12 Sierra

Usually I’m not doing this, but this time I highly recommend NOT to upgrade to macOS 10.12. At the time of writing the new OS has way too many bugs, two of which affecting Kuuvik Capture users specifically.

1) Connecting the 5D Mark IV via USB to an app, and then quitting the app will leave the camera in an inconsistent state, and no app will be able to connect to the camera until the USB cable is disconnected and plugged in, or the camera is turned off and back on, or the memory card door opened and closed.

This only happens with the 5D Mark IV and on macOS 10.12 with the USB connection. The same camera on 10.11 works fine, all other cameras we’ve tried on 10.12 work fine. Even the Wi-Fi connection works fine – well, it’s not a surprise since it doesn’t use the flaky macOS PTP/IP stack.

It seems that macOS forgets to close the session with the camera. There is no workaround to the issue, other than the things mentioned above that actually break the session on the camera side.

2) On some computers (MacBook Pro 15″ Retina Mid-2012 for example) 5DS/R files are not displayed at all.

This is due to a bug in the macOS video driver, and thus happens only on some machines. There’s a workaround, however. Kuuvik Capture can downsize there files to be just 24 megapixels for display. Just open the Terminal app, and enter the following command:

defaults write com.direstudio.KuuvikCapture forceLargeImageDownsizing 1

Once Apple fixes the bug, you can turn downsizing off by the following command:

defaults write com.direstudio.KuuvikCapture forceLargeImageDownsizing 0

Of course we are working on to get these issues fixed, but until then the best remedy is to avoid upgrading.

Update 10/26/2016: macOS 10.12.1 does not resolve these issues.

Availablity

The update is free for existing Kuuvik Capture 2 customers. New users can download Kuuvik Capture 2 from the Mac App Store for $79.99 / €79.99 / £59.99.

For more information about the app, please visit it’s microsite, or check out my posts.

Dual Pixel RAW and Kuuvik Capture

Dual Pixel RAW is Canon’s new invention that will see its first release with the EOS 5D Mark IV. There’s some vague marketing info floating around, but haven’t seen a concise description of these files yet. So while updating Kuuvik Capture’s (websitemy posts) RAW decoder to support the 5D Mark IV, I had a chance to dig deeper into Dual Pixel RAWs.

To understand the following discussion, you need to know how Canon’s Dual Pixel AF works, especially how these Dual Pixels are divided into two separate photodiodes. This article by Dave Etchells gives you a thorough explanation.

What is a Dual Pixel RAW file?

Normal CR2 files contain the following sections:

  • Metadata
  • Previews
  • RAW data

The DPRAW file is a CR2 file that contains one more additional section:

  • Metadata
  • Previews
  • RAW data
  • DPRAW data

This organization have a very important implication. Any RAW processing software that does support the normal 5D Mark IV files will be able to open DPRAWs. If the app is unable to interpret the DPRAW data part, it will simply ignore it and will work with the file as a normal RAW. There’s no risk or penalty in taking DPRAWs (besides the huge buffer drop from 21 to 7 frames).

The DPRAW file contains the normal RAW data section to make this compatibility possible, plus one side of each pixel in the DPRAW data section.

The RAW data section contains pixel values with the sum left and right sides of the photodiode, while the DPRAW section contains pixel values from just one side of each photodiode.

The RAW data section contains pixel values with the sum of left and right side photodiodes, while the DPRAW section contains pixel values from just one photodiode of the two.

But how do we get the other side of each pixel to let Dual Pixel aware processing apps do their tricks? It’s easy: since the RAW pixel value is the sum of left and right pixel sides, just subtract the DPRAW pixel value from the RAW pixel value.

This is an unusually clever implementation from Canon, where I’m used to see all kinds of inflexible hacks that look like as if they were designed in the 1980s.

Size-wise, DPRAW files are slightly less than double the size of normal RAWs (since metadata and preview images are stored only once).

How will Kuuvik Capture 2.5 handle DPRAWs?

Not being a RAW converter, Kuuvik Capture needs the RAW data for two purposes: the RAW histogram as well as shadow/highlight warnings (the image displayed on the screen comes from the preview embedded in each CR2 file). For these the RAW data section is totally sufficient, and the app will ignore the DPRAW data section if present in a CR2 file.

The app will display normal RAW and DPRAW files equally fast, but downloading DPRAW files from the camera will take almost twice as much time as normal RAW (because of their larger size).

I assume that there will be a possibility to switch the camera into DPRAW mode remotely (I can’t be sure until my rental unit arrives). If that is the case, then a new preference will let you specify whether you’d like to shoot RAWs or DPRAWs.

5D Mark IV File Support Added to Kuuvik Capture

5d4rawisobugThis morning I had finished adding EOS 5D Mark IV file support to Kuuvik Capture (websitemy posts), and would like to share a few observations with you.

In short, all bugs introduced with the latest Canon camera releases are present in the RAW files.

First, just like the 1D X Mark II, ISOs above 51200 recorded in the EXIF incorrectly as 65535 by the camera. The screen shot on the left shows an ISO 102400 file from the 5D Mark IV. This is something that affects users and can’t be corrected in Kuuvik Capture. So if you are running into this: it’s a problem with the camera firmware, not with the app.

Second, internal lossless jpeg headers are corrupt exactly the same way the 5DS/R screws these up. Kuuvik Capture works around this bug, so it’s not something you’ll notice, just annoying to witness.

Third, the whole question of ISO 32000. Since 1/3 stop ISO values are digital trickery, the camera’s top ISO is still 25600. But it seems that marketing folks were not satisfied with that. So the fake top ISO was born. I saw this in the 7D Mark II for the first time (ISO 16000), and it seems that they are so fond of this that the 5D Mark IV also got it. The app handles it correctly, it’s just something you need to be aware of as an informed user.

Of course the upcoming version 2.5 will have full 5D Mark IV support, just wanted to share the progress with you. We plan to release version 2.5 later this fall. It will be a free update for all Kuuvik Capture 2 users.