Shooting with RED Epic #7: Difference Between REDCODE Data Ratios

Shooting with RED Epic #7: Difference Between REDCODE Data Ratios

The RED Epic, with its 5K resolution and low compression options, can be the biggest enabler of data bloat if you let it. That's why it's crucial to understand the difference between the various REDCODE data ratios that range from 3:1 all the way to 18:1.

From our ongoing exploration of 10 Things You Should Know Before Shooting with RED Epic:

7. The Difference Between REDCODE Data Ratios

Digital cinema data is like a wild plant — it can be beautiful, colorful, and visually impressive — but if you don’t tend to it correctly, it can grow like a weed.

And the RED Epic, with its 5K resolution and low compression options, can be the biggest enabler of data bloat if you let it.

That’s why it’s crucial to understand the difference between the various REDCODE data ratios that range from 3:1 all the way to 18:1.

Don’t know what those numbers mean? No worries because we’re going to dive head first into how to approach REDCODE with Epic in a practical way.

What is REDCODE?

REDCODE is RED’s proprietary compression algorithm that works to make files smaller while retaining resolution, colors, dynamic range, and more to the best of its ability.

(Almost every digital camera uses compression, even if it is labeled as a “RAW” format.)

REDCODE is also a variable codec which means it does not compress at the same rate all the time — it is directly affected by image content.

This is a crucial concept to understand.

The way that REDCODE compression works is by sampling an image and compressing on the fly. The more “going on” in an image, the more data there will be.

That means wide landscapes with many trees, different colors and movement will record more data than simply a black wall.

The Meaning of Different REDCODE Ratios

Different REDCODE Ratios on RED Epic Menu System

With the RED One, REDCODES are referred to as REDCODE 28, REDCODE 36, and REDCODE 42, with the numbers representing their data rates; 42 is the highest quality. With the launch of the Epic, RED changed this naming scheme to ratios (i.e. 10:1, 5:1, 3:1).

The closer the ratio gets to 1:1, the lower the compression, the higher the data rate, and the higher the quality of the image.

To give you a point of reference for these ratios, the equivalent ratios for REDCODE 28, 36 and 42 are 10:1, 8:1 and 7.5:1, respectively. Currently, the Epic supports a REDCODE ratio range of 3:1 to 18:1 with 8:1 being its default.

So I’ll just shoot the highest — 3:1 — all the time then,” you might think.

Well, not so fast.

At such a high data rate, you are going to be shooting through hundreds of Gigabytes per day easily.

Even Jim Jannard, CEO and owner of RED, cautions against such brazen consumption of data:

The truth is that there is a steep curve of improvement with lower compression starting at 20:1 (acceptable) to about 7:1. After that the curve noses over. While there continues to be improvement to 5:1, it becomes almost impossible to see much of a difference from there to 3:1… just more data to deal with.

Brook Willard, a well-known DIT, also supports Jannard’s position:

With the Epic, your compression choice will have a much larger impact on data rates. The data rate difference from 10:1 to 8:1 is not that great… but the data rate difference from 6:1 to 3:1 is HUGE. As such, I think it’ll be more about finding a balance than it will be ALWAYS shooting the best. It’s sure nice to have it when you need it, though…

In the end, your choice of compression ratio is dependent entirely on a number of factors: your resolution, frame rate, the purpose of the finished video, and your visual preferences.

But, for the purposes of practicality, Jannard claims 5:1 is the “sweet spot.” In my experience, 7:1 or 8:1 are also solid ratios to choose as the acceptable compression at those rates is well-established via the RED One.

The Effect of REDCODE Ratios on Data Management

RED Data Management
What this all comes down to, in terms of your RED Epic shoot, is that you will have to take into account the effect these data ratios will take on your data management practices. If you do decide to shoot 3:1, you will need a much more robust and powerful system to ingest, copy, and transcode the footage in a timely fashion. Productions shooting closer to or lower than RED One data ratios will likely be able to treat data management like they’re used to with that camera.

But don’t think that because the REDCODE ratio is an easy setting to change that it can’t have profound effects on your shoot.

(If you’re counting on a PA with a 4-year-old Macbook Pro to transfer data, but you’re shooting at 3:1, you’re going to be in for one hell of a wake up call.)

Because the other end of the data equation — to capturing so many Gigabytes and Terabytes worth of footage — is that you have to transfer it. You have to make redundant backups (if not, shame on you). And you have to do all this in a live produciton environment where, often, the camera will fill cards with fresh footage faster than you can download them onto hard drives.

So, if you’re a producer, think about the consequences of shooting higher ratios without having the infrastructure in place. Is it worth clogging the pipeline with a high data rate versus being able to continuously shoot at a lower data rate?

And if you’re a camera assistant or cinematographer, make sure you prepare for the influx of data with properly sized hard drives and a powerful enough system to pump all the footage through. Adding a D.I.T. to your department’s crew will bring on an expert who can make those calls for you and who can also handle the data safely and securely while on set.

Of course, all of this is moot if you have a big enough budget to buy the systems and personnel to handle the data. I’m only imploring you to be aware of the trade-offs if you are working within a super low-budget.

Further Data Management Resources

There’s much more depth to data ratios, data management, and specifically working with data as it pertains to RED. Here are some articles you should also read to get a stronger idea of it all:

If you know of any other great resources, please share them in the comments!

It’s All in Your Hands Now…

When handled properly, picking a REDCODE ratio and dealing with data management isn’t a huge issue on set. It just takes many parties — director, cinematographer, producer, camera assistants — to comprehend the workflow ahead of time to implement it smoothly on set.

So, while a lot of this article is full of warnings and pitfalls, if you do your homework, the data you record from your Epic will not be a huge deal.

All it takes is a proper understanding of the various different REDCODE ratios and what they mean for YOUR production and, from there, how you choose to handle it.

  • Josh Kade

    Long time reader, first time poster.

    I have never shot with the epic, only the redone but i am finding these posts extremely helpful and will heed your advice for future shoots. Without these posts i wouldve gone into it thinking “oh itll just he like a redone.” so thanks and keep up the great work evan!

    • Evan

      Josh — thanks for the kind words! Glad you finally decided to post :) Hope it’s not too scary and that you’ll be willing to do so again.

      I will say the Epic is a lot like RED One in many ways. The menu structure is fairly similar and a lot of what AC’s learned to deal with on RED One carries over to RED Epic. But, like any camera, it has its own personality.

      I’d say if you have experience with RED One, you just need a few hours with an Epic to get familiar and you’ll be good to go

  • Richard Lacey

    What sort of laptop spec would be recommended for downloading Epic, Red One and Alexa? Hoping to get some downloading work this year and hopefully my rig will suffice.
    I currently have a 3 year old MacBook Pro, 4GB RAM and a 2.4GHZ Core 2 Duo processor.
    Still need to pick up a firewire card reader and e-sata expresscard adapter.

    • Evan

      Richard — I am not totally sure, to be honest. It’s a fine mix of processor power and input/output ports. At the very least, you do want firewire or e-sata and as many of the ports as possible. I am going to try to reach out to some DITs at some point and see if they’ll have interest in posting here about this though. Thanks for the comment!

      • Richard Lacey

        Unless productions suddenly decide to use thunderbolt drives I should be fine on the input/output port front.
        Processor is the main concern. I have no trouble playing back AVCHD clips, which tend to be a pain, the bit rates coming out of RED and co. would likely be a very different story though.
        It’s just something I’ll have to check with DITs next time I’m out on a few shoots.

        • Evan

          If you can afford it, a new MBP with the i7 hyper threading would be awesome.

  • Isaac

    Hi Evan,

    Im looking at shooting some low light stuff on the Red Mysterium X. Does the compression rate have a large impact on low light noise? 8:1 or 10:1 will be our base for the day scenes but we are looking at maybe going to 5:1 or lower if it improves noise performance.

    We are shooting at 5K and projecting in a cinema at 4K so we dont have the 1080P conversion to compress and ‘clean up’ some of the shadow noise.


  • Jose Mario Lagos

    Hello, I really like your blog, I’m a video editor from Honduras, next year I will edit my first feature film and I’m trying to figure out how much space I will need to manage that project, I’m sure that they will go for a Red Scarlet camera for shotting everything (no multicam) 4k , just to give you a background in Honduras there is a tiny budget for feature like this but I want to do it as professional as possible with the budget avaible, Im looking for any advice that you can give me for this indy film, I think that about 24 TB (12 TB main,12TB backup) for this film will be enough, if you can send me a link to a good raid storage solution that I can use to edit directly I will appreciate, Thanks your blog is great! sorry for my english is not my native language.