UDMA 7 CF Card Performance on Canon 5D Mark III and 1D Mark IV – Soooo worth it!

Now that UDMA 7 card prices are coming down out of the stratosphere I figured it was a good time to pick up some newer/faster cards to replace my aging UDMA 6 media. It also didn't hurt that my Canon 5D Mark III supported the UDMA 7 standard – so I was eager to see if there would be any noticeable upside to the swap.  As I was heading over to a local Austin Thursday night bicycle race at The Driveway, I thought I'd recalled that the Canon 1D Mark IV also might support UDMA 7.

So after parking and prepping my gear, a quick search on my phone showed that the latest firmware upgrade "Improves writing/reading speeds when using UDMA 7-compatible CF cards."  Being fairly diligent about applying new firmware, I figured I'd be good to go – that I'd be able to test both the 5D3 and the 1D4 with UDMA 6 vs UDMA 7…  No dice… my 1D4 was at 1.0.8… D'oh!

Oh well – I figured I still had the 5D3 to play with, so I headed out to shoot; and boy did it help. I was noticing roughly double the shots when I just kept the shutter down and let it shoot – but perhaps more importantly, the time to clear the buffer dropped even more significantly – from 15 seconds to about 4 or 5.  Of course, all of this was with that super scientific timing method of "one one thousand… two one thousand…" LOL  I went ahead and tested the 1D4 as well – curious to see if the firmware would make any difference. The quick tests seemed to indicate that when using firmware 1.0.8 on the 1D4 that there was no gain in performance.

Back at the house, I went and did a bit more "scientific" testing. Yup – broke out the stopwatch feature on my cell phone.  I didn't quite feel like getting out the recorder, then looking at and counting the spikes in the wave image. I figured this was an "area play" of sorts – split seconds wouldn't matter, it was the larger changes that would be very noticeable that would be important to me (and hopefully, you).

I also went ahead and upgraded the firmware in my 1D4 to 1.1.1 to see if that made any difference. Since the testing on the 1.0.8 showed zero improvement (both out at the event, and in my "scientific" testing) I didn't include it in the results below; but yes – 1.1.1 DOES make a difference.

Both my 5D3 and 1D4 are set to just shoot raw files; I only save to one card (the CF) and when it is full, they roll to the SD till I can swap the CF card during a break in the shoot. To avoid AF or exposure settings delaying shutter speed, I went to manual focus, and set the camera to manual mode – 1/500 @ f/4. To test – I held the shutter down until I heard a hesitation in the shutter speed; when that happened, I started the time as I released the shutter, then watched to see when the red "writing" light went out. The same cards were used in both cameras: UDMA 6 – RiData 533x; UDMA 7 – Lexar Professional 1000x 16 GB.  I did three runs of each camera/setup and have averaged the runs. (okay – I know I'm not proving a Doctorial Thesis, but I know folks like to understand the details <chuckle>) Oh – one last nugget of data – when you look through the viewfinder and see the "available shots in buffer" indicated – neither camera's number changed when switching between card speed/technology. The 5D3 showed 13 shots for both cards and the 1D4 showed 23 shots for both cards.

A drumroll please… 

Camera Card  Shots till full   Buffer empty in 
 5D Mark III   UDMA 6  15  15.2 sec 
   UDMA 7 26  3.5 sec 
       
 1D Mark IV  UDMA 6 27  24.5 sec 
   UDMA 7 31  6.1 sec 

Ta da!

So – on the 5D3:

  • roughly 70% more shots on the before the buffer is full
  • buffer fully cleared in roughly 1/4 the time

and on the 1D4:

  • Only a slight gain in shots – 15% more, but again the
  • buffer fully cleared in roughly 1/4 the time

So that is the "numerical" side of things – the practical side of things is that it is very noticeable how much faster I can shoot again – primarily on the 1D4 (mainly because I do more of the rapid high speed shooting on it, but I'm doing more with the 5D3 as well).  It takes 6.1 seconds to completely empty the buffer, but even a 1/2 – 1 second stopping in the shooting can get me a quick burst of another 3-5 shots… a lot more manageable than the older 1.0.8 or UDMA 6 performance of only 1-2 shots after that 1/2 – 1 second hesitation.

So – run, don't walk – to your local retailer or web storefront and load up on some UDMA 7 greatness early and often!

If you have any questions, either comment below or use the "contact" link in the header.

Thanks, as always, for reading!

- Will

 

Canon GP-E2 Review – including tagging CR2 and JPG images from .log files

I'll fess up – I'm a gadget geek. I"ve been a touch surprised at how Nikon had been ahead of the game with a small GPS that could tag images via connection to their cameras via USB.  There were a few attempts at integrating the GPS via USB but you had to have a WFT device – which was super pricey, and you still needed a supported GPS device too – so ~$1,000 to tag images, no thanks.

I had seen other Geo-Tagging devices that would essentially log a trace and would then tag your .jpg files with their locations, but these devices didn't support RAW files, and I shoot exclusively in RAW.

I was a bit happier when the 1D X was announced and along with it was a much smaller GPS tagging device, the Canon GP-E1, that tied into the camera directly, via a utility port on the side of the camera.  Still a touch on the pricey side, but at least this unit wasn't the size of half a battery grip.

Then the 1D X was delayed, the 5D3 announced with availability just around the corner. With it – the GP-E2 was announced. I liked that the device supported both the 1DX as well as the 5D3 from the hot shoe (a curious way to get the connectivity, but it will connect to multiple disparate devices that way), and to the 7D via a usb connection.

So the die was cast. I ordered a GP-E2 with my 5D3, and hoped that it (okay – and the BG-E11 grip) would show up before I headed to California to shoot the Amgen Tour of California last week… no luck.

GP-E2-001-122600

It was here when I got back, however; I soon had it out of its box and was ready to test – but I got broadsided by a nasty cold and have been essentially worthless (some might argue that is *not* atypical – LOL) for the last two days.

First impressions:

The device is a touch larger than I expected.  Most, if not all, of the images I had seen of the Canon GP-E2 were without a camera body in the image. So the fact that it is easily larger than the pentaprism of the camera took me a bit aback.

GP-E2-002-1

I was still also mulling over my reaction to the "hot-shoe" connectivity. While it would give me the most accurate data (including compass direction and angle of the camera, I think) I wondered about how vulnerable it was going to be if I was out on a moto with it in the hot shoe. I've not really had any problems with a flash mounted on a camera from the moto, so this shouldn't be too big a problem, but I'd not be able to use my flash on my 5D3 (which is how I ran things in Cali this year – pending post on that).

The thought of using a USB cable to connect the GPS to the camera seemed even less ideal from the back of a moto.  I think it would a) open the side of the camera (okay – and the GPS) to rain and dust contamination, and b) be easy to knock out of the socket when reaching for the camera, etc. So I started looking into the under mentioned pure "logging" capabilities.

Initial Setup:

So there isn't much to the device. An opening for a single AA battery, a rubber cover over the data connection, and a three position switch. Canon also include a carrying case (so you can attach the device to your belt or camera strap easily, two different lengthed cables to connect your camera to the GP-E2, and a small drawstring bag to carry the lot in. After putting in the battery (not included), sliding it into the hot-shoe of my Canon 5D mark III, and flipping on the power switch. I was able to go into the camera's menus to setup the device. 

It lets you set the date/time on your camera from the satellite signal (very nice, easier than the laptop time-set process – two shakes and my 5D3 was "accurate"). This can be set automatically, manually, or can be switched off. The other "setting" is the ability to define the "position update timing". IMHO, it is a no-brainer to set this at the minimum refresh time of every second; this still allows for over four days of logging on the device before you start overwriting older days' logs. You can view the current GPS info (lat, lon, elevation, date/time and signal strength). The last thing you can do is to calibrate the compass on the device – it shows you three sequences of movement of the camera with the GPS mounted on top to let the device align itself correctly. But compass direction of the photograph is no where on my radar – My main concern, from posting images into various image services, is to get the city, state, zip and country added to the files. This saves me tons of time; as I won't have to remember where a shot was taken while mid stage (where towns are small and go by pretty quickly).

My Strategery/Test:

I didn't think it was too necessary to try connecting the receiver to the camera – it would "just" work as advertised. After a day or two to mull it over, and enticed by statements such as "There is no need to connect the receiver to the camera" – I wanted to test with an "un-supported" camera (For direct tagging – the 1DX and 5D3 work via USB/Hot-Shoe; 7D works via USB). 

So I fired up the GP-E2 into "log" mode, hopped in the car, and did a quick run for some dinner. I had set the time on my 5D3, so I brought up that display and matched the time setting manually on my Canon 1D Mark IV.  On the drive, I shot about 50 images along the way; not really aiming, just actuating the shutter.

Tagging the Files:

The one step in the process that didn't immediately click – was how to get the log file off of the GP-E2 and onto my laptop.  The cables included with the device call the connector on the GPS end a "digital" connector, and the other end is a mini-usb to connect to the camera. I knew this wouldn't connect to my "standard" usb ports on my laptop.  Looking at the port on the GPS itself, it looked different enough that I figured I needed to find an adapter to connect the cable that came with the GPS to the laptop.

I read through the GPS manual, there was zero description on how to accomplish this. Finally, I downloaded the Canon Map Utility manual off of the software disc – it just said to "use the cable included with the camera"… Hmm… could it be that easy? A closer look showed that the outer shape of the socket on the GP-E2 was indeed USB Mini shaped. I gingerly tried it, and voila! It worked.

From there it was pretty easy. I copied the files onto my hard drive into a directory in the "normal" file structure I employ for Lightroom. I then launched the map utility.

A quick "File" > "Add Images…" to select all the files in my latest directory, voila – they now appear in the left column of the app. Then I turned on the GP-E2, connected it to the USB port, clicked the "GPS log files" tab in the utility, and chose "File" > "Import GPS log files from GPS device…" The data is now on your laptop. Now just go back over to the "Images" tab and click "Edit" > "Automatically add location information".

The system now does warn you that "If (Time difference] in the GPS log file is not set correctly…" (it goes on for a while). Essentially, if you time on your camera is off by an hour from the GPS, and you shot for two, your locations may be shifted for one of the hours and the other may not show any gps info.  Just be sure to sync your camera with your GPS before you start your shoot. I'm not sure what you could do at this point – I guess you could hop into some utility to adjust the "shot" time, then come back and refresh the data…. It would be nice if Canon let you set an offset (in both hours and minutes) so you could fix this now… perhaps that will show in a subsequent version of the software.

After you clear the warning, you have the option of reviewing your location info before you commit it to the files. You just need to click the "Save" button below the map (they put it in a very noticible blue area below the map).

The 59 files took about a minute or two to save (I should have, but didn't time it). I'm not sure what he delay was, but it may be looking up specific country, state, city, and "sub-location" aka "neighborhood" info for each image and saving it.  I'll try this again on a larger set to see if this is really a long delay… If so, I may tag the GPS info only into the images I'm pushing to my image-server… those 40-50 may go a LOT faster than 1600-1800 images from a day of shooting a race.

The Results:

The Map Utility actually has a pretty nice display – it shows the trace of the drive I took, and it puts pins in the map where each photo was taken. It is enough to know if your time-sync was on or off and you have plenty of choices on how you want it to display. It leverages Google Map data, so you have the standard "Map", "Satellite" or "Hybrid".

MapUtilityScreenCapture

 

For Lightroom – the trace itself isn't displayed as it only has the individual image info… I guess it could play "connect the dots" but it wouldn't follow the actual path taken (unless you managed to only stay on straight roads and took a pic at each corner – LOL).  It does bring up "sub-location" – which is sort of interesting – it labeled the shopping center I drove through as a neighborhood I had never heard of. Suffice to say – it worked like a champ, and I'm looking forward to my next multi-day stage race to shoot.

LightroomScreenCapture

The Plan:

After this quick test, I will most likely use the GP-E2 attached to one of the cameras I use on a shoot (so that 1/3 or more of the shots will be pre-tagged) and I can then tag the other images via the process above; or I can just tag the shots after exporting selected files from Lightroom if tagging 1600 images takes a long time.  I'm thinking I may just tag all the images this way as I won't have to worry about if I want to mount a flash to the 5D3, etc.

Short version – you should be able to use one GP-E3, attached to your belt, to tag all cameras on any shoot. Just be sure to sync the time on the cameras with the GPS before each shoot.

I'll post again after I've used it a bit more.

Thanks for reading; and as always, let me know if you have any questions.

- Will

 

New Gear: 1D X or 5D III – Decisions Decisions…

I always chuckle a bit when new gear gets announced. The forums get flooded with lots of questions about nit-picky details that can't possibly get answered until the camera is out and someone has some hands on time with them. People seem to love to debate and or disparage the manufacturer (no matter if it is Canon or Nikon) as to why they didn't do "x" or why the felt they had to do "y" or why they couldn't just add in the feature from the top of the line camera to that mid-range product… I think what most people fail to understand is that (no offense) they are not making the camera for you, they are making the camera for the masses.

So it is funny to see posts about how many stops better will the RAW support be (sort of subjective, isn't it?), or which is better for me the 1D4 or 5D3 (um, more than happy to point out differences, but you need to be comfy with your own decision, I'm nobody's scapegoat), or complaints about the price of the 5D3 being more than the D800 (um, very different beasts – IMHO, the prices shouldn't be the same).

To me it comes down to more pragmatic decisions. What will it cost and how will it benefit me?

I wish I had a limitless budget and could have closet full of gear. A pair of 1D4 bodies, a pair of 1DX bodies, a 5D3 and a 7D would be great… along with every lens Canon makes. Yeah – that should just about fit the bill… I could load up with whatever I needed and get the best for whichever client I was shooting for… but that is not the case.

For me, I've loved the IQ, fps, ISO performance, and 1.3 crop (for that little extra reach) of the 1D4, and I've been okay with the 5D2's performance while loving the full frame 21mp images. I do wish it had a better AF system (well, and since it was my main "event" camera, better low light performance is always appreciated) but the other functions have been great for what I (and more importantly, my clients) have needed it for.

Eos1dx_

Enter the 1DX – Back in October when the 1D X was announced, I'll admit I was enamored, I wanted one – and put in a quick pre-order and should receive one in that dealer's first order. I wasn't happy about the price though… Not that I didn't see the value in it – I do think that $6,800 is a great price for all that Canon have packed into that body – but with the 1D4 doing such a great job – I didn't want to feel like I had to give up my 1D4 to have a 1DX. I wasn't longing for a new pro sports body – I was only looking for the improved AF for a FF body. At the time, sure – there were rumors about a 5D2 replacement, but I didn't think they would be announcing it and releasing it so soon. I loved the thought of lots of rich FF images, but my main FPS need is sports and to be candid – the subtle differences between FF and 1.3 crop bokeh in a rip-roaring sprint finish wouldn't have me selling any more images than I do currently. For a sprint – I just need to capture the critical moment with the rider(s) I want in focus… the 1D4 has been doing that for me just fine. Don't get me wrong – I still wanted one – higher ISO, larger files so you could crop a bit more – additional controls for ease of shooting either orientation – increased shutter longevity – improved smaller GPS unit… I could go on… 

So I figured the best bet for me would be to sell my 5D2, buy a 1DX and shoot it with the 1D4 – using the 1DX for scenics for the breadth of the FF, and then picking from two great choices for the sprints – using the 1D4 if I needed a bit more reach based on where I was allowed to be for a given finish…

Eos5dmarkiii

Enter the 5D Mark III – Then the rumors started flying around in Jan/Feb that the 5D3 was on the way… well – it might have been called the 5DX – but suffice to say, a replacement for the venerable 5D2 was on the way.  I began to re-think my stra-tee-ger-ree. Another pre-order placed and my "need" for the 1DX started to wane just a bit.

In looking over the specs for both cameras, so much of the 1DX (that I really wanted/needed at least) was in the 5D3. Sure the metering system is zoned, not color sensor based; yes – the AF speed won't be as impressively fast since the battery isn't as big; sure it'll only do 6 fps… but I now have the AF and improved IQ that I needed/wanted (respectively). I think the 5D3 replacing the 5D2 in my bag – I'll not be feeling as much need for the 1DX as I had initially.

So I'm looking forward to my 5D3's arrival – and just to hedge my bets, I'll be keeping my pre-order in on the 1DX – with it not being released till later next month – this will give me some time to evaluate the 5D3. I can see how well it works as a slightly slower 6fps sports shooter.

So watch this space – I may either be extolling the virtues of the 5D3, or putting it up for sale to help fund the 1DX… and who knows – I may even end up buying them both.  But for now – I feel better that I don't feel like I'm goaded into buying the 1DX just to get the improved FF AF I've been wanting – I now have a choice with the 5D3.  After all, a combo of a 5D3, 1D4 and 1DX could be a hard bag full o bodies to beat!

Thoughts on this? What do you have on order – 5D3, 1DX, or both – and why?

Thanks for reading!

- Will