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 :)

RED Engineers are awesome.

My guess is that a lot of these new firmware updates are the result of requests for MX that were hardware limitations. REDOne was a special case because it was so dependent on FPGA which is incredibly flexible but larger, hotter and slower. It isn't as easy to backport ASIC features.
 
Y0 what about us Epic owners? Why can't we at least get the fancy swappable OLPF's? Surely they have nothing to do with the processing power.
And if the camera is shooting 5K but the compression on the dragon is better why can't we have a tethered view thingymajiggy over Gig-E like
the dragon owners! There's still tons of life left in the Epic MX don't just leave us out to dry. (I might upgrade but I'm still on the fence)
 
Y0 what about us Epic owners? Why can't we at least get the fancy swappable OLPF's? Surely they have nothing to do with the processing power.
And if the camera is shooting 5K but the compression on the dragon is better why can't we have a tethered view thingymajiggy over Gig-E like
the dragon owners! There's still tons of life left in the Epic MX don't just leave us out to dry. (I might upgrade but I'm still on the fence)

Not really a processing power thing, but it is actually a combination of the sensor itself and the OLPF. And actually the calibration/profiling stuff internally might be Dragon specific due to memory and processing limitations (same for the new LUT stuff that Jarred recently teased). Sensitivity of the Dragon CMOS plays a huge role here as well as IR tuning on the sensor level and not just the OLPF. Also the OLPF design and sensor box in general are wildly different between Dragon and Mysterium-X brains. It's not really just "slap a different piece of glass in there" sort of thing.

The Gig-E stuff is actually something that does come from having more processing power however. Just like the Black Shade memory has increased. Though I haven't read the the Gig-E stuff is officially not for MX. I think we're fairly early in those days.

REDCODE had to essentially be rewritten to optimized differently for Dragon and that's a combination of what the sensor is dishing out and the processing power. MX has been tried and true, the main advantage over the compression schemes is the higher compression ratios/faster frame rates and retaining detail and Dragon squeezes out a few drops more basically.

A lot of the new features that are coming to Dragon are coming to Dragon because it's not just a sensor upgrade. They end up swapping out a good chunk of the brain.
 
So when will we know if this is regarding 3d LUTs. If it is, it is a huge deal. Phil what is your hunch? Or, let me ask this, why wouldn't loading 3d LUTs be possible into cam?
 
It's a very good tease, I must say.

Any 3D LUT loaded into the camera would maybe have to be read by RCX as well. Maybe RCX would need to be made 3D. lut aware, I imagine that might take some coding. Plus, if they were to move to this system then all the other color science would maybe have to be tweaked to map the color science as it as now.

I think a LUT applied to the output would be good, but if that is applied in the r3d sidecar then it would have to work in the entire workflow.

battistella
 
So when will we know if this is regarding 3d LUTs. If it is, it is a huge deal. Phil what is your hunch? Or, let me ask this, why wouldn't loading 3d LUTs be possible into cam?

I've sent suggestions over to Red from time to time regarding various things like LUTs in and out of camera as well as a billion other things.

My hunch is this is good news. How good? Time will tell.
 
The RED's conseption about upgrading sensor, not the whole camera is of course a fantastic thing! Thanks!
 
Back
Top