Rarevision's 5DtoRGB - A Better Way to Convert Canon 5D Mark II Footage?
This morning I came across Rodney Charter's tweet about Rarevision's5DtoRBG converter for Canon 5D Mark II and Canon 7D H.264/MOV footage to Apple ProRes. When Rodney speaks I tend to take note. So I was curious about this new (at least to me) tool for converting Canon EOS footage that he tweeted about. I briefly used the Canon E1 movie plugin for Final Cut Pro, but soon went back to using the ever faithful utility belt tool every Canon DSLR editor has - MPEG Streamclip. It's familiar workflow, easy batch list, versatility, and speed are hard to match. However, MPEG Streamclip, the Canon E1 movie plugin and Compressor uses Quicktime to handle the YCbCr to RGB color conversion. Unfortunately Quicktime does not do the best job possible. Adding insult to injury, QT adds noise to mask the compression artifacts.
"The main problem with all this is that you have to trust your NLE or compositing app to do a good job of performing the YCbCr to RGB conversion. Many programs use QuickTime internally to perform YCbCr to RGB conversion which, according to our testing, does only a mediocre job. I suspect this due to a performance compromise, in that "well enough" is suitable for most users (remember, QuickTime is designed for real time playback of those 1080p movie trailers as well). This is probably OK for general use, but unacceptable when trying to maximize the quality of highly compressed H.264 footage for visual effects work, green screen compositing or film outs. To add insult to injury, QuickTime adds noise to its H.264 output (and so does any program that uses QuickTime to decompress H.264) in what looks like an attempt to cover up H.264 compression artifacts. And guess what? There's no way to disable this. You're stuck with it if you've converted your footage with Final Cut Pro, Adobe After Effects, MPEG Streamclip or Canon's Movie Plugin-E1 for Final Cut Pro -- all of them use QuickTime to decompress H.264."
Rarevision makes a rather bodacious claim:
"5DtoRGB gets you as close as possible to the original data off the camera's sensor while putting the brakes on any additional quality loss. In short, it'll make your footage look just plain amazing!"
5DtoRGB's features include:
- Panasonic Lumix GH1 support (video only)
- Full support for Canon 5D Mark II and 7D
- Higher quality output than Canon's E1 plugin [compare]
- Higher quality output than QuickTime Player or FCP [compare]
- ProRes 4444, 422 HQ/LT/Proxy Support
- DPX output for visual effects / green screen work
- Raw YCbCr output option for unprocessed luma channel extraction
- Output luminance matte as an alpha channel (ProRes 4444 only)
- Timecode support (extracts Exif timestamp from THM files)
I ran a few clips through 5DtoRGB in an informal test. Pixel peeping is not my specialty so please don't expect this to be an exhaustive or empirical test. Is there a difference between Quicktime conversion and Rarevision's 5DtoRGB conversion? Yes. Of course, your mileage may vary. Still, my first tentative experiments with 5DtoRGB are interesting.
Original Canon EOS 5D Mark II H.264 Movie File
MPEG Streamclip (Quicktime Conversion) to Apple ProRes 4444
Rarevision 5DtoRGB Conversion to Apple ProRes 4444
Rarevision 5DtoRGB Conversion to Apple ProRes 4444 with Add Noise Option
The first thing I noticed right away is that the output from 5DtoRGB is not as dark or contrasty as the MPEG Streamclip output. The Apple ProRes 4444 footage from 5DtoRGB is more faithful to the gamut of the original footage. 5DtoRGB does allow you to select either a 1.8 or 2.2 output gamma. By the way, you know all those .THM files associated with your Canon footage? Don't throw those away! 5DtoRGB needs those files to get the start timecode values.
One other observation: the conversion process is much slower than what you get out of MPEG Streamclip. Rarevision acknowledges this and says it's by design. You cannot batch the files for processing either. This is what they say about the conversion process:
"5DtoRGB takes a no-compromise approach to quality, ignoring any concerns about speed. 5DtoRGB bypasses QuickTime decoding altogether, works internally at 10 bits and uses double-precision floating point math for its YCbCr to RGB conversion. It also recognizes Canon's full range 8 bit YCbCr values (0-255), avoiding clipping and the resulting loss of picture information. The resulting files are the absolute highest quality you'll ever get out of the camera. In fact, you could argue that they're even better than the camera originals since they've undergone high quality chroma smoothing (which you can disable if you want, but you shouldn't)."
I'd like to hear from other editors and DSLR shooters out there that have used 5DtoRGB. I'll do more extensive testing in the near future. I want to get your opinion on this. So, what do you think? Is 5DtoRGB a better way to convert 5D Mark II or Canon 7D footage?