Ha ha very funny Canon now get back to work

Image courtesy of Philip Bloom. Click through for his actual coverage of the show.

Canon Expo kicked off with a bang as the venerable imaging giant stunned crowds with its working prototype 4K camera! Is this the future of digital cinema?

Ug. I think I just threw up in my mouth a little.

There’s so much wrong with this prototype “concept camera” (as Philip kindly points out below, it’s important to understand that this is not a camera Canon plans on bringing to market) that I hardly know where to begin. It’s an atrocity of aesthetics and ergonomics. It has a fixed, not-very-special 20x zoom lens. The sensor is only 2/3”. It shoots 60fps. Nothing about this camera reflects any awareness of what digital cinematographers want. It’s as if Canon brass lifted the internet ban on the engineer’s dungeon just long enough for them to visit to RED’s web site, and then shut it down again after they’d read as far as “4K.”

Of course, this isn’t a camera, or even a plan for a camera. It’s a statement by Canon. They meant to say “We get it. We know what’s important.” What they actually said is “Ooh, bigger numbers!” I expect this kind of technology dick-swinging from Sony, but not from Canon.

What’s most troubling about this non-camera is that Canon made it at all. Anyone invested in Canon’s gear should be pissed at Canon for squandering their time and resources building this toy. I look at this thing and see my parents returning from Vegas with a sheepish expression on their faces, saying “Remember your college fund?”

Canon, please stop building fake “4K” video cameras when you can’t even make an SLR that shoots actual 1080p HD.

We’ve discussed the very real aliasing/moiré issue with Canon’s HDSLRs. It is both a real problem and a somewhat workable limitation that many happily accept. What is not in dispute is that these are symptoms of a poorly-sampled, low-resolution image. Readers of this site know that I am not a spatial resolution fetishist, but even I am painfully aware that my 5D and 7D footage is lacking detail.

Canon makes it incredibly easy to demonstrate this, since the 5D Mark II that makes such fuzzy pseudo-HD video also makes ridiculously high-fidelity stills. The frames below are a 1:1 frame grab from a 5D video, and the same scene shot as a still and then scaled down to 1920x1080. I did the scaling in Lightroom, using no Develop or Output Sharpening.

Click for full-sizeClick for full-sizeFeel free to download the full-res originals and compare yourself, or look at the 1:1 comparisons below:

Port of Oakland? Or #### ## #######?Chain-link fence? Or a dirty piece of glass?The difference is staggering. And remember, I don’t even care all that much about spatial resolution. What I do know is this: a sharp 1920x1080 camera can make an image with more detail than most female movie stars are comfortable with for close-ups. So for today we can dispense with a discussion about the merits of mastering at 4K. Canon is nowhere near that conversation with their HDSLRs. They’re still falling way short of HD.

To be clear: What you are seeing above is two different ways that the same camera made a 1920x1080 image. One image was hastily yanked off a sensor (skipping entire rows of pixels) and then compressed to H.264 in realtime; the other was captured as raw 5.6K bayer data, decoded slowly to RGB by an engine optimized for quality, then downsampled to HD using every 5.6K pixel to build a 1920x1080 image with as much detail as appropriate for a true HD image.

Does the latter sound unfeasible for “real” video work? Well it shouldn’t — it’s what we do with our RED One cameras now.

The RED One is more than just a “4K camera.” It’s a 4K sensor, some very clever software, an even more clever compressed raw codec, and then more clever software. Not to mention a decent form factor, decent colorimetry, smart proxy workflows for editorial, and viewfinders that actually help you expose and focus. It’s a full-fledged 4K ecosystem.

And look how painful it was for RED to get all that working.

Canon, you have none of that stuff, you have no idea how to make it, and you don’t even know that you don’t know this.

So stop dicking around with your fake 4K toys and start making cameras we can use. That we want to use.

Build a full-frame DSLR that shoots high-quality HD video at a variety of frame rates and the world is yours.

I’m terrified that you won’t though — because then you’d have to put it on a pedestal at a trade show and say “Look, we finally built a camera that actually does what we claim our current cameras do.”

So much more fun to say “Hey look, 4K!”

“We so get it.”

The Eagle Has Landed

The 24p firmware update for the Canon 5D Mark II is live on Canon’s site.

September 17, 2008, the day of the 5D Mark II’s announcement, when we first learned of its 30p movie mode:

Remember how I said how stunning it was that Nikon chose 24 fps for the D90’s D-Movies? How it could have so easily been anything else? How if Canon came out with a movie-shooting DSLR that shot 30p I’d be less than thrilled?

Well it’s worse than that. Because a 5D that shot 24p at full HD resolution would have been a very important camera. For Canon to have come so close and botched that one detail is almost unbearable.

Maybe we can get Canon to offer a 24 fps mode in a future firmware update.

Yep, maybe.

Update on Thursday, March 18, 2010 at 7:42AM by Stu

Canon has removed the firmware update due to a problem with the manual audio levels feature.

Recently we have discovered a malfunction that occurs with Firmware Version 2.0.3, in which the manual recording levels for C1/C2/C3 are changed and the camera becomes unable to record audio if the power is turned off (or if Auto power off takes effect) after registering “Sound Recording: Manual” in the camera user settings.

We apologize very sincerely for the inconvenience, but we are going to stop making this firmware available for download. For customers who have already updated to the new firmware, when using the camera with the mode dial set to C1/C2/C3, please either set the sound recording settings to Auto.

We are currently preparing firmware that will correct this malfunction. As soon as those preparations have been completed, we will let you know on this Web site. In the meantime, we apologize for the inconvenience this represents, but please wait until the fixed firmware is ready.

Update on Friday, March 19, 2010 at 9:11AM by Stu

2.0.4 is up. Thanks Tom T!

Converting 30p to 24p

As the long-awaited 24p firmware update for the Canon 5D Mark II draws near, I joined Mike Seymour on episode 57 of the Red Centre podcast to talk about how excited I am that it marks the end of painful workarounds for the 5D’s no-man’s-land frame rate of 30.0 frames per second.

For as long as I’ve had my 5D Mark II, I’ve avoided using it for any projects that I could not shoot 30-for-24, i.e. slowing down the footage to 23.976 fps, using every frame. My 5D has been a gentle overcrank-only camera. There are plenty of occasions to shoot 30 frames for 24 frame playback—we do it all the time in commercials to give things a little “float,” or to “take the edge off” some motion. I still do this often with my 7D. Whatever frame rate I shoot—24, 30, 50 or 60, I play it back at 24. Just like film.

Folks ask me about 30p conversions often. Twixtor from RE:Vision Effects is a popular tool for this, as is Apple’s Compressor. Adobe After Effects has The Foundry’s well-regarded Kronos retiming technology built-in. All of these solutions are variations on optical flow algorithms, which track areas within the frame, try to identify segments of the image that are traveling discretely (you and I would call these “objects”), and interpolate new frames based on estimating the motion that happened between the existing ones.

This sounds impressive, and it is. Both The Foundry and RE:Vision Effects deservedly won Technical Achievement Academy Awards for their efforts in this area in 2007. And yet, as Mike and I discuss, this science is imperfect.

In August of 2009 I wrote:

I’m not saying that you won’t occasionally see results from 30-to-24p conversions that look good. The technology is amazing. But while it can work often, it will fail often. And that’s not a workflow. It’s finger-crossing.

On a more subtle note, I don’t think it’s acceptable that every frame of a film should be a computer’s best guess. The magic of filmmaking comes in part from capturing and revealing a narrow, selective slice of something resonant that happened in front of the lens. When you use these motion-interpolated frame rate conversions, you invite a clever computer algorithm to replace your artfully crafted sliver of reality with a best-guess. This artificiality accumulates to create a feeling of unphotographic plasticness.

Of course, it’s often much worse than a subtle sense that something’s not right. Quite often, stuff happens in between frames that no algorithm could ever guess. Here’s a sequence of consecutive 30p frames:

Right-click and select View Image to see full-resNothing fancy, just a guy running up some stairs. But his hand is moving fast enough that it looks quite different from one frame to the next.

Here’s that same motion, converted to 24p using The Foundry’s Kronos:

Right-click and select View Image to see full-resBlech.

Again, don’t get me wrong—these technologies are great, and can be extremely useful (seriously, how amazing is it that the rest of the frame looks as good as it does?). But they work best with a lot of hand-holding and artistry, rather than as unattended conversion processes.

(And they can take their sweet time to render too.)

I’m so glad we’re getting the real thing.

Canon adds 24p to the 5D Mark II and I Blame You

Readers of ProLost, pat yourself on the back.

In the 18 months since Canon announced the Canon 5D Mark II, you’ve written, you’ve called, you’ve left comments here and on Vincent Laforet’s blog. You politely but firmly harrassed Canon personel at trade shows. Perhaps most significantly, you put your money where your mouth is and bought 7Ds, showing Canon that 24p is even better than Bokake.

It delights me to no end to read these words in a Canon press release:

Developed following feedback from photographers and cinematographers, Firmware 2.0.3 further enhances the EOS 5D Mark II’s excellent video performance. The addition of new frame rates expands the camera’s video potential, providing filmmakers with the ability to shoot 1080p Full HD footage at 24fps (actual 23.976fps)—the optimum frame rate for cinematic video. 25fps support at both 1920x1080 and 640x480 resolutions will allow users to film at the frame rate required for the PAL broadcast standard, while the new firmware will also change the 30fps option to the NTSC video standard of 29.97fps.

I underlined a couple bits in there. Do they sound familiar? The wording is almost directly lifted from ProLost posts and my other communications with Canon.

Does it seem like I’m patting myself on the back? Well I am. But you should too. I know that, at best, I played maybe a tiny role in this. But this is a very cool thing that has happened here—we spoke, and Canon listened.

Read the full press release at dpreview.com.

Take a trip down memory lane and view all ProLost posts tagged Canon 5D Mark II.

And heck, buy a 5D Mark II from Amazon and support this site. I love mine, and I’m about to love it even more.

Update on Tuesday, March 2, 2010 at 11:17AM by Stu

Looking back at the 24p for 5D campaign waged here on ProLost, something I never felt I needed to do was explain why 24p was so important, beyond simple technical compatibility. If you’re interested in an artistic discussion of the role 24 progressive frames per second plays in the look and feel of movies, check out part two of my interview by Rick Young of MacVideo. Rick asks one question—“why 24p”—and I talk for about ten minutes. Oops.

Part one of the interview is here.