File and workflow management...

...have become the major new issues now that I'm shooting with my new Canon EOS 1D Mark IV, and in fact for major sports events, shooting with both the 1D M4 and with my EOS 5D Mark II as well.

For field sports the 1D M4 has the 70-200mm f2.8.L zoom, often with the Extender EF 1.4 II for an effective focal length range of 98-280mm, while the 5D M2 has the 24-70mm f2.8L zoom for closeups.

Setups for both cameras is as identical as I can get it regarding ISO, White Balance, Exposure Mode, Metering Mode, and Focusing Mode and focus point.

Since I'm shooting in Continuous Shooting mode while the game is underway the 1D M4 is taking something less than 10 shots per second, while the 5D M4 is taking something less than 4 per second.

I'm shooting in M-RAW on the 1D M4 which is spec'ed at "9.0 mB 3672x2448" and in S-RAW-1 on the 5D M4, which is spec'ed at "9.9 mB 3861x2574".

Despite the fact that Canon says both of these produce files roughly in the 9.0-10.0 mB range, most of the RAW files I get seem to end up somewhere north of 15 mB each.

Go figure.

So I shot 2,341 photos in a Saturday of Vashon Island Soccer Club games.

(As a matter of policy I shoot *everyone* -- not just the "star" players -- on any team I photograph).

That comes out to 38.26 gB (that's gigabytes, folks) of photos as they came off the Compact Flash cards and onto a hard drive.

So my old method:

1) move Canon RAW files from CF card to hard drive on a Ubuntu Linux box,
2) burn to DVD,
3) copy off the DVD onto the hard drive on one of the two Win XP boxes I use for post-processing,
4) post-process on the Win XP box,
5) generate jpegs and web pages back on the Ubuntu Linux box that contains the local copy of my web site,
6) archive the DVD

has become:

1) move Canon RAW files from CF card to hard drive on a Ubuntu Linux box I'm now using as a file server,
2) review and tag acceptable RAW files over the network from a Win XP box,
3) move the tagged files to a new directory on the file server,
4) post-process the tagged RAW files over the network from a Win XP box,
5) generate jpegs and web pages on the Linux box that houses my web site,
6) delete unused RAW files that never made the cut, and
7) burn the tagged RAW files and the tiffs produced by post-processing onto a DVD for off-line archiving

It's taken a little thinking and fiddling to get this down and streamlined, but so far it seems to be working.

And it may be more separate steps, listed out like this, but in actual practice doing RAW conversion and post-processing using two instances of BreezeBrowser running on each of two Win XP boxes means I'm really able to keep things moving.

And one major advantage is that I'm no longer even keeping photos that never make the cut, which I did in the old method.

Although I'm paying only about $0.66 per DVD/c-shell case for storage, I don't need to keep something I've only looked at once and will never look at again...