(Page 1 of 2 pages for this article  1 2 >)

Friday, March 21, 2008

Filed under: Post Production

Working with RED Footage

Adam Wilt | 03/21

RED’s postproduction tools, and some pitfalls of learning them.

For my unfair comparison of three cameras, I had to process RED clips to a greater degree than I had previously, including dealing with odd overexposure artifacts. I relate my experience, both to describe the steps I took to decide on the processing parameters I did, and to show what I ran into when learning to use RED’s tools.

To begin with, the RED shoots R3D files: wavelet-compressed raw data with no in-camera processing applied. The R3D files store metadata—effective ISO rating, white balance (blue/orange balance, as in any video camera) and tint (green/magenta balance, roughly orthogonal to blue/orange balance, so you can really fine-tune white point)—along with the raw image data, so that you have a starting point for grading / color-correction. RED also writes a set of QuickTime reference files (MOVs) alongside the R3Ds, which utilize the R3D codec to extract “proxy-quality” images for quick verification of the shot or direct editing.


RED file structure: each shot has its own directory. The R3D file is the REDCODE raw file; the MOVs are QuickTime proxies at 4k, 2k, 1k, and .5k resolutions. The TXT files were created by R3D Data Manager when copying the CF card to hard disk.

However, the proxy QuickTimes are “one-light” decodes of the R3D data (you can’t tweak the raw data to correct exposure or color); they’re slow to play on the FCP timeline; and their fixed sizes may not match the scale you need. If you’re serious about image quality or editing speed, or you want an output format other than QuickTime, you’ll want to use one of the “digital darkrooms” that RED provides to pull clips out of R3D files, grade and resize them as needed, and write them to another format, whether it’s a QuickTime movie or a sequence of DPX or TIFF frames (of course, you can use the R3D files directly in a finishing program like Scratch, in which case you can skip this article!).

[Edited 2008-03-22 22:30 PDT: I originally said the QT proxies were only 8-bit, and of lower than full quality, based on what I’d gleaned from reduser.net. Graeme Nattress wrote me and said that saying these were 8-bit was “not strictly correct.” So I tweaked it to say “8 bit (in FCP)”, which prompted Graeme to enlighten me further, saying, “in FCP it will decode them as 32bit float YCbCr if you have 10bit or high precision rendering enabled in the timeline”, which is pretty impressive IMHO. I verified that this is the case, and I stand corrected. Thanks, Graeme!] 

I started off by downloading the latest versions of tools from RED’s support page: RED ALERT!, REDCINE, and (if you’re a Mac user and you want to play the proxy files) the Final Cut Studio 2 REDCODE plugin.

Observe that the support page sections for both RED ALERT! and REDCINE have the following cautionary warning:

BETA RELEASE. Support at reduser.net.

The first part states just what RED has been saying all along, and translates to, “use at your own risk.” The latter part effectively means, “no written documentation to speak of; no help files; support has been crowdsourced—again, use at your own risk!”

RED ALERT! is a clip-at-a-time processor. You can pick one of several gammas, tweak de-Bayering parameters. change ISO, white point, and color matrix, and fine tune both the tonal scale and color. RED ALERT! offers both a three-color histogram and superimposed zebras to help you judge your grade. You can save your settings for use on another clip, or transfer them to REDLine, the bundled command-line utility for batch-processing use. You can export 2k or 4k DPXs or TIFFs, DPX or TIFF image sequences, or QuickTime reference movies.


RED ALERT! version 1.5.6 with histogram and zebras shown.

REDCINE does much the same thing, only with the ability to load multiple shots into a timeline; make multiple versions of shots; transcode to any QuickTime codec you have; and zoom, reposition, and crop your clips to any desired output size.


REDCINE build 90, color tab shown, with superimposed histogram.

One initially puzzling thing about REDCINE and RED ALERT! is that they use different language for similar controls. It turns out that RED ALERT! started life as a diagnostic tool written by RED’s image-processing supremo, Graeme Nattress, and was pressed into service when REDCINE—written by the folks behind Assimilate’s Scratch—was delayed. Different tools written by different people, hence the different terminology. They also have different strengths, and some folks find that one works on their system a lot better than the other, so it’s worth downloading both.

RED ALERT has no documentation supplied with it. REDCINE has only a single page of UI shortcuts (displayed when you press the “H” key). But if you poke about on reduser.net long enough, you’ll find these tutorial videos:

http://red.cachefly.net/redcine/interface_overview.mov

http://red.cachefly.net/redcine/project_settings.mov

http://red.cachefly.net/redcine/shot_settings.mov

http://red.cachefly.net/redcine/color_settings.mov

http://red.cachefly.net/redcine/output_settings.mov

http://red.cachefly.net/redcine/library.mov

These are excellent as far as they go, but they are only introductions, and they do leave out a critical bit of information… but between the tutorials and just playing around with the controls, it’s possible to figure out most of what’s needed to get generally-acceptible images out of either program.

Next: Stumbling ahead, one mis-step at a time…

(Page 1 of 2 pages for this article  1 2 >)

               



You must be registered to comment. This is an effort to reduce spam. Please REGISTER HERE.

Perhaps someone’s already pointed out to you one trick to get audio out of the r3d. For the time being, you can use the QuickTime proxy file and QuickTime Pro to extract the sound (i.e., open the QuickTime proxy and then go to Movie Properties in QuickTime Pro). 

Then you get to synch up your audio to your picture manually! Isn’t it all so 2008?!

Posted by .(JavaScript must be enabled to view this email address)  on  03/24  at  09:37 PM


Great article Adam… very helpful!

I totally agree that it is very unproductive to read through tons of posts @ reduser.net to find the needle in the hay, so to speak.

Would be great if RED would offer a Wiki. Probably the best way to build a solid knowledge base in the Web 2.0 world wink

cheers
totti

Posted by .(JavaScript must be enabled to view this email address)  on  04/01  at  09:36 AM


We’ve been thinking of adding a RED Wiki here.  Would folks add to it regularly?  It’s really a community effort.  Thoughts?

Posted by .(JavaScript must be enabled to view this email address)  on  04/01  at  03:20 PM


How’s this for service - Check out the new (and empty so far) RED wiki.

RED WIKI

Posted by .(JavaScript must be enabled to view this email address)  on  04/01  at  03:30 PM


There is an (yet incomplete, but already helpful) wiki for RED related stuff: http://www.redhax.net/wiki

The Self-Reliant Film blog has a good collection of recent sources:
http://www.selfreliantfilm.com/?p=328

Posted by Patrick Renner  on  04/05  at  07:42 AM


Ok, I’m going to make a simple request here… and it’s directed to all of the PVC and RED community: Just precisely because this is all in a constant state flow and change, this kind of article needs to specify a very important nugget of information: the specific build and version of the firmware and Red tools in use.

I’m sitting here reading about the DRX slider bug in redcine and wondering if the build I’m using has the same bug…  but I don’t know which one the author has.

Furthermore, just recently I read on reduser a post concerning just this problem and Graeme Nattress confirmed that his last build has solved this problem. Has he released it? Dunno, but I hope so.

And a last comment on wading through irrelevant posts on reduser: after a while you start to know who’s who and you can generally directly jump to the knowledgeable people: the RED employees, the gurus, the true owners, and skip the fanbois and the newcomers.

Posted by .(JavaScript must be enabled to view this email address)  on  04/07  at  10:08 AM


“I’m sitting here reading about the DRX slider bug in redcine and wondering if the build I’m using has the same bug… but I don’t know which one the author has.”

I’m sorry, I thought that labeling the screenshots with “RED ALERT! build 1.5.6” and “REDCINE build 90” would make the versions I was using clear enough. I was using RED ALERT build 1.5.6, and REDCINE build 90.

Posted by Adam Wilt  on  05/05  at  02:50 PM


WOW…  was that there all the time? I’m really sorry if I sounded harsh, that was my mistake :(

Posted by .(JavaScript must be enabled to view this email address)  on  05/05  at  04:42 PM


Name:

Email:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

Submit the word you see below:











How to Edit Red Footage with Adobe Premiere Pro

Matt Jeppsen | 03/23

“Accelerate your RED workflow with Premiere Pro” hour-long seminar recording and notes

image

RED Digital Cinema and Adobe teamed up recently to do a live online seminar and tutorial on the RED R3D workflow with Adobe Premiere Pro. The recording of that event is available free at…

ARRI’s DNxHD Alexa update, Sorenson Squeeze Pro and OP this, OP that

Scott Simmons | 03/15

Understanding the different DNxHD MXF formats and getting that into Media Composer

image

ARRI has begun to ship its DNxHD update for their Alexa camera. This announcement that the Alexa…

Kicking the tires on The Foundry’s Storm beta

Scott Simmons | 12/05

It’s in beta, it’s buggy but you can see a powerful, well-designed tool inside. Oh the future ...

image

It was a busy week this past week as November changed to December and The Foundry released their long discussed…

Using RED Footage Proxies in After Effects

Chris Meyer | 11/21

Take advantage of those auto-generated low-resolution proxy files to speed up your work before rendering.

Many people like to shoot RED source footage these days, even if the final destination is lower-resolution video. I agree, it’s nice to have all of those extra pixels to play with - except when you have to actually read them off disk and…

To be considered for listing, contact pr (at) provideocoalition (dot) com


Copyright © 2012, HD Expo, LLC a division of Diversified Business Communications. DBA Createasphere

All rights reserved. HD EXPO, High Def EXPO, Createasphere, E-Tech, Entertainment Technology Exposition, 3D Production Workshop, VariCamp, P2 Camp, ColorCamp 101, and Lighting, Filters & Gels for HD are all trademarks of HD Expo, LLC.

Terms of Use  |  Privacy Policy

Check PageRank