Possibility to use 5K Mysterium-X Epic with 6K Dragon Epic for 3D?

[Asif Limbada]

I am thinking not to upgrade my EPIC-M to 6K, I might just get a EPIC-X 6K when it comes out and keep my EPIC-M 5K for time being.

The reasons are simple, FOV on 6K sensor if using 5K res, would be more tele & editing bottlenecks to work with 6K footage would be a pain. Lets hope the computers keep up with 6K footage, so should the software (Its was a pain working on CS5.5 for the past 8 months...to buggy. CS6 = Awesome).

Current RED Rockets do not handle 5K multi track timeline. One 5K track per RED ROCKET (that costs USD4000+). Lets not get me started with 5K HDRX multi track timeline. Also we are whining about Mac Pro and its connections, I think RED ROCKET is PCE 1.1 or something (correct me if I am wrong)

But I would get a 6K EPIC nevertheless. I love to have that Dynamic range and resolution. And would love to do some 3D. But when I think about it, in my head it feels impossible to do 3D with 5K MX Epic and 6K Dragon EPIC at lets say both set at 5K. Will it be compaitable.

Guys I am just thinking out loud. Would love some input.

[Matt Ryan]

No it won't. Even though resolution will match, Field Of View will be slightly different due to the new sensor. On top of that the sensors are different therefore they will not match image wise for 3D. Dragon is supposed to have more DR which is impossible to add to the MX. Also, there are more pixels in the Dragon sensor which will give a sharper image vs. the current MX. So it would be tough to do 3D with a mixed setup.

[Asif Limbada]

Ok then, why isn't RED making the camera capture the whole sensor and down converting it to lower res rather than allowing the sensor to be sensitive to light on a smaller area (or zoom) each time we go lower in resolution. Wouldn't the whole idea of using S35 or larger sensor seems pointless.

if you are shooting 4K on a 6K sensor, it does become a smaller sensor (figuratively speaking), noise floor becomes more evident (especially using 800ISO on 2KWS on the 5K Epic).

From what I understand the higher the resolution, the more bandwidth is required to transfer data from the sensor to the SSD. But if we let the whole sensor to capture light and only allow it to send 3K or 4K data through the bus, wouldn't it more practical.

I know I am not a technical guy when it come doing engineering of a camera and all the science of it, I just want to understand the logic to why RED is doing this and why can't it be possible to down convert the whole data???

[Asif Limbada]

I need to know why can't we get full FOV at any resolution, why does it "zoom" in. I spoke to DOP recently, who had the same query when we were renting the EPIC. He knew about it, but was very interested to know why do not we get full FOV at any res.

The only thing I can think of is that its something to do with fps and bandwidth of each res.

Anyone????

[Gunleik Groven]

As to your 1st question.

You can get the same FOV on both cameras, but they shouldn't match dynamically and probably not totally colorwise either, as the sensors are different.

But S35 downsampled to 2k/1080 should be the same FOV.

Also you are confusing things a bit (or maybe I am... :)
But the pixel density is supposed to be higher on the Dragon, which means that 6k FOV could well be = 5k FOV

Downsampled to 2k the resolution difference is probably insignificant.
I'd guess you'd be hard pushed to see a difference of significance on resolution even at 4k.
BUT the sensor lightresponse will be different, and that would make them quite bad as a matched pair for 3D

Just me speculating and interpolating here.

[Doug Beatty]

I would hazard a guess and say that cropping is much much less processing intensive vs. scaling in camera when you are dealing with raw images.

[Gunleik Groven]

Scaling is not like RAW....

When you record RAW you record the pixels available for that FOV.

Scaling is done in the next step.

Many reasons for cropping. Highspeed is one of them...

[Asif Limbada]

Thanks Gunleik for joining in.

But I still am confused. Why can't we have the option to down sample the footage with FF5K to 2K or 3K or 4K with max 96fps without losing the FOV.

I think that should be my final question. Is it because of the bandwidth bottleneck from the data of the sensor or the downsampling is processor hungry etc.

This is just eating my head :-)

[Gunleik Groven]

Simply because it is RAW...
It wouldn't be, if one did what you sugest in-camera.

Easilly done in post, though.

Cheers!

G

[Asif Limbada]

Simply because it is RAW...
It wouldn't be, if one did what you sugest in-camera.

Easilly done in post, though.

Cheers!

G

Yeah, but some people just don't want 5K (or 6K when it will come) when they really want is 4K native. Why compensate on FOV

There are many different ways to do downsample in post, I do it all the time. But I want to know the reason why RED is using cropping rather than downsampling.