Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Opinion: Why Redcode is the future of RED?

David Battistella

Well-known member
Joined
Apr 30, 2007
Messages
10,003
Reaction score
6
Points
38
Bear with me, this is a long post

I’m writing this post in a public forum because I know the RED team reads this stuff and because I firmly believe that the improvement of REDCODE will have more of an impact than the further improvement of the cameras themselves. I also want to flush out what I don’t know or understand.

With all of this talk about new camera’s and the potential of new cameras, I wanted to take things in a different direction and back toward post production. The most attractive thing to me about the entire RED system is not the Camera. It’s not the RED One, it’s not the EPIC or the Scarlet, in fact it is not any of the camera offerings of RED. What I love about the RED system id REDCODE RAW.

The very idea of RED is fantastic. The whole system, as it is laid out is really intelligent and that is what attracted me and many of the other early adopters to it in the first place. The camera records REDCODE, then through a de-bayering process gives you access to the files through some RED software or you can watch your footage quickly and easily with QuickTime and you can (not really) edit those proxy files in Final Cut Pro, etc.

Shooting RAW gives RED the advantage over many systems, but the disadvantage has been a lack of REALTIME performance of REDCODE. This lack of performance has been the bane as well. The potential is still amazing.

I think that the single thing that will make RED a stronger force in all it’s marketplaces is the improvement and optimization of REDCODE on different platforms.

But REDCODE, the cornerstone of the program and the one that people rely on for the post production half of RED, is not real time. I know that there are those who will say that a scratch system plays back redcode real time but please hear me and read on before you jump all over me on this.

Imagine if the R3D debayering was realtime all the time?

Here is what I mean. I know that REDROCKET helps accomplish this but read on to see how great it could be if it was truly a realtime system.

The Scarlett -
If the fixed lens Scarlett was released with a realtime REDCODE codec I think that would make a much more attractive platform for people who want to go the DSLR route. You’d get RAW motion image in REALTIME instead of a baked in H264 codec that the current DSLR’s offer. Attractive and powerful tool.

RED ONE -
Jim has stated that with the release of EPIC they want to avoid the “beta” problems they faced with the release of the RED One program. I would ask RED to seriously not underestimate how much of those growing pains can be attributed directly toward workflow, post production, the lack of realtime performance and the fears producers had about shooting RED because the post tools were lagging so far behind the camera department. This forced people into complex workflows involving third party software did not match the elegance of the rest of the system.

Having a post background and owning a RED is a major advantage, but we can all agree that the early days of having to transcode footage using Apple compressor, creating DPX files, rendering out of REDCINE or REDALERT, all of which were clunky and unsophisticated ways of extracting images from RED and, dare I say, completely defeats the purpose of shooting RAW.

EPIC -
The high end future is bright, but I wonder about what bringing 5K into post will do and how that will tax existing storage and backup workflows. We all want the best image quality, more latitude and better images. I think there is a great need to push the optimization of REDCODE even further. Why? We are pretty capped out right now in terms of computer speeds, RAM and processors and even a REDROCKET card (a very great move forward) still taxes systems and puts things at their limit. I actually believe that this is exactly what the EPIC program and future camera offering should do.

What I’d like to see:

Release SCARLET with and out-of-the-box optimized REDCODE that is real time. It would be nice if the CORE of the Scarlett program was to give users all of the functionality of P2 or SRS data based cameras but with an optimized REDCODE that works the same way as these systems.
So I would shoot R3D files copy them to my system and edit in realtime in FCS, Premiere. Think of it as the high end DV codec of the future, offering RAW in Realtime would widen the use of the RED system.

For RED ONE and EPIC owners release a version of REDROCKET that works with all of our existing tools. This means that if I shoot on my REDONE and have a REDROCKET, I can edit R3D natively in FCP or premiere, etc. FCP has over a million legal licenses sold. The ability to interact directly with these applications in REAL TIME would be a giant leap forward.

Release CAMERA builds and post tool, QT updates less frequently and simultaneously.

Make transcoding OBSOLETE. I want to shoot the footage, back it up, edit the footage in R3D in FCP and finish it right there or send and XML and the r3d files to any high end system from discreet systems, Flame, Smoke, etc. to baslight, Apple Color, or any number of finishing solutions.
Transcoding to DPX is a major drawback. Do everything to encourace the use of R3D from shoot to finish. Make it the number one priority of the SDK program to ensure R3D implementation is as many systems as possible. Be on top of this as much as you are at releasing camera firmware builds.

Along with MAX mode, introduce a MIN mode that would allow for more realtime performance if I want it.

I know that these are things that many people have asked for but I think it is important to open up the discussion on what kinds of things would repair some of the myths and bad karma put out there about workflow.

As always I am sure this might spark debate. If you agree or want these features please include that too. I am hopeful the RED team will respond.

David
 
Some of the experts told us that R3D is based on Motion JPEG 2000, a wavelet-based image compression standard and coding system.

If it was true than R3D is also carrying some of a basic "good and bad" connected to that existing image compression format.
 
Hi David, not to be too negative but how exactly could this be achieved without a marked hit to quality, which negates the whole point of RAW shooting .

And when talking abouit real time playback, it's not like R3D's aren't 'optimized' already (in a given workflow). They are - that's why you can get realtime playback of the proxies on a low end machine - because they are already optimized for down scaled, quick access rather than always having to uncompress and read all the data.

But to get the benefit of the RAW workflow you need the full options of debayering, and that's hugely processor intensive, so you either need custom hardware (RED ROCKET) or processor speed to burn with no additional bottle necks (a highly spec'd system, running specialist/turnkey software).

REDCODE is the key, and it's always getting better, and with hardware specs increasing at an ever climbing rate I really don't think that R3D need to worry about compromising towards speed OVER quality any more than they already do, because speed will increase over time naturally, but quality is burned in at acquisition.

That's why someone will eventually just HAVE to upgrade their EX1 because the codec just doesn't cut it anymore compared to the competition, whereas the owner of a RED ONE will simply not face that same problem.
 
Hi David, not to be too negative but how exactly could this be achieved without a marked hit to quality, which negates the whole point of RAW shooting.

I think that in a 3K fixed lens Scarlett it might just be possible depending on how much they can squeeze out of the existing technology.

I agree with a lot of your points and I am not an engineer, so I can not comment on how that might be executed.

I do think that from a user perspective I'd like to see these features, but how that gets accomplished (or whether it actually can) is another story.

If you look at something like SHEER video, they use a compression scheme that is faster than real time within the codec and results in lossless image quality. That's attractive and if it could be applied to REDCODE that would be very cool.

David
 
David,

I wonder if what you are asking for is where RedcineX is heading. On a one year old Powerbook pro I manage to view R3D in realtime (alas in 1/4 resolution) - which I find amazing. With computers getting faster every month, we are not too far away from realtime playback in even the most basic system.

And who knows, maybe there'll come a day where R3D playback is part of the better graphic cards?
 
David,

I wonder if what you are asking for is where RedcineX is heading. On a one year old Powerbook pro I manage to view R3D in realtime (alas in 1/4 resolution) - which I find amazing. With computers getting faster every month, we are not too far away from realtime playback in even the most basic system.

And who knows, maybe there'll come a day where R3D playback is part of the better graphic cards?

I know it takes A LOT of power to process r3d, but realtime would make us all cry.

We need it in more than REDCINE X, we need to use the power of the REDROCKET to do the calculating within QT and other apps.

David
 
What we need is more support for Open GL. Using CPUs to debayer is waste
 
What we need is more support for Open GL. Using CPUs to debayer is waste

In the works I hope. Also keep in mind that I think fixed lens Scarlett in Realtime just might be doable. I know that R1 and EPIC are most likely impossible without hardware help.

David
 
This may be the goal of the FF1080p feature, a realtime RGB redcode, which would be incredible. I guess we'll have to wait for this. OpenCL also has real potential to do this, even on older graphics cards.
 
what if you could somehow connect the camera to the computer and use the camera as the debayering processor for redcode.....maybe I am reaching here....I really don't know what I am talking about... lol
 
I remember sometime in the mid-'90s, working for a company that purchased some sort of accelerator card for Adobe Premiere, and running a special edition of that software called RT, that was capable of real-time effects like crossfades on standard-def footage. These days, most cell phones can do that. So, it really is only a matter of time before computing power catches up to REDCODE.
 
I remember sometime in the mid-'90s, working for a company that purchased some sort of accelerator card for Adobe Premiere, and running a special edition of that software called RT, that was capable of real-time effects like crossfades on standard-def footage. These days, most cell phones can do that. So, it really is only a matter of time before computing power catches up to REDCODE.

I'm really not so sure about that as computer chips are really getting to their max. and it seem no matter how many processors you throw at REDCODE typically eight cores in a Mac, that it just ain't enough.

Maybe when a breakthrough technology like quantum computing comes around, but not in our current intel land.

david
 
I'm really not so sure about that as computer chips are really getting to their max.

david


Exactly right. Chip makers are no longer able to ramp up the clock speeds like they once could as the power cycles can no longer keep up once you get into the 4ghz range. Also, it's getting to the point where adding cores is trivial and has little added benifit.

We are in a very weird computer age right now where processing power is absolutely abundant but software makers are just learning how to utilize it. On the OS side technologies like OpenCL and Apples Grand Central Dispatch are helping to take advantage of this processing power. This takes a huge weight off of software makers (Red) because they dont't have to worry as much on how to optimize their software for multi-cores (i.e. how many threads and what to put in each thread) they just have to add a few lines of code that ensure the technologies (OpenCL, GCD) take advantage of the cores. So.... I think we are going to finally see all that processing power get put to use in the next little while.

It may be easy to say that processors are the bottleneck are aren't getting any faster, but it is actually the exact opposite. Processing power is abundant, we just have to take advantage of it. I'd be willing to bet that even our 2 core processors still have tonnes of juice locked away that we will be able to take advantage of when software makers start optimizing their programs to take advantage of said technologies.
 
I'd be willing to bet that even our 2 core processors still have tonnes of juice locked away that we will be able to take advantage of when software makers start optimizing their programs to take advantage of said technologies.


This is why I hope that they focus a lot more resources toward optimizing the code. REDCODE 42 is great, but a REDCODE RT would kick some ass.

David
 
This is why I hope that they focus a lot more resources toward optimizing the code. REDCODE 42 is great, but a REDCODE RT would kick some ass.

David

I may be confused here but a RT Redcode would be more (?) compressed right?
So... it would obviously be better for Red to offer more resource intensive codecs (RC 42,100,250,etc) knowing that the technology would catch up fast enough, especially with new technologies that optimize CPUs and GPUs to process the codecs faster. I mean, Redcode 250 will be realtime one day when the processing power (optimization) catches up, correct?
 
What we need is more support for Open GL. Using CPUs to debayer is waste

Not going to happen. I remember that Graeme said something like about this, that they'd tried decoding on the GPU early on and it was far less efficient than using the CPU.

Also, as far as I can tell, the reason REDCODE takes so much power to decode is that it not only has to decompress the image but also demosaic it and interpolate the colour channels and then add the gamma curve, white balance and other colour correction. If you wanted a real time REDCODE, it wouldn't be raw anymore, so you'd lose most of its advantages. It'd be better to just transcode to ProRes after shooting it, so you could go back to the original RAW files than doing it on the camera.
 
I may be confused here but a RT Redcode would be more (?) compressed right?
So... it would obviously be better for Red to offer more resource intensive codecs (RC 42,100,250,etc) knowing that the technology would catch up fast enough, especially with new technologies that optimize CPUs and GPUs to process the codecs faster. I mean, Redcode 250 will be realtime one day when the processing power (optimization) catches up, correct?

Optimization would not only involve lowering compression rates. There are more factors to deal with. If the code itself is optimized to be more efficient with resources, be faster within the codec , etc, then you could theoretically maintain image quality and get near realtime.

If the code is not or can not be further optimized then it would be important to make sure that any hardware acceleration (REDROCKET) can interface easily with existing programs (FCS, Premiere, etc.) So if I have a REDROCKET then I can run realtime 2K and 4K editing in Final Cut Studio, for example.

But as it stands right now, I'm not sure this is possible.

David
 
i think that's basically the idea of the RED Rocket™...

I agree but in the context of the fixed lens SCARLET I would suggest it might be hard to get users to buy a camera and PCI card to go along with it.

David
 
Not going to happen. I remember that Graeme said something like about this, that they'd tried decoding on the GPU early on and it was far less efficient than using the CPU.

That sounds about right. Open CL has a lot of potential, but there are a lot of tasks that a GPU isn't suited for... I guess this is one of them!
 
Back
Top