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

Mysterium X Build, vs. Build 21

Build 30 (Mysterium-X)

Build 30 (Mysterium-X)

if you rate the camera at iso 320 with the FLUT™™™ at zero, the difference between RAW and RedColor is VERY little, just a touch more contrast and more color saturation it seems.

some at read have generalize that iso and FLUT™™™ are interchangeable..?

To get more highlight protection I'd suggest that you re-rate to ISO 800.

As to ISO and FLUT™™, yes technically they are both inputs to the FLUT™™ algorithm, but calibrated to different step sizes - 1/3 stop v's 1/10 th stop.
 
Mysterium-X camera

Mysterium-X camera

do the new upgraded MX R1s have the same resolution, bitrate, and framerate, as well as FLUT™ controls and REDcolor viewspace?

That is correct.
 
Am I not going to underexpose too much if I go to ISO 800? If it's "red" in false colors it's gone anyways or not? Maybe we can get a revive the "exposure 1, 2, 3" thread, it's a bit confusing.

Wouldn't 640 be safer? (And it's exactly one stop higher than 320!)
 
To get more highlight protection I'd suggest that you re-rate to ISO 800.

As to ISO and FLUT™™™, yes technically they are both inputs to the FLUT™™™ algorithm, but calibrated to different step sizes - 1/3 stop v's 1/10 th stop.

Okay, gotcha, in order to separate what you see in RedColor vs. Raw, rate the sensor higher to build in your protection that way. It's a little bit different way of thinking about it, but I get the idea. On the particular job, I was full sunlight, day exterior, so rating at 800 iso seemed a little fool-hearty. However, by not rating higher, my highlights were borderline... As it was I had a Pola, ND 1.2 and a hot mirror.... Oh well here's to stacking on the filters!
 
Stuart,

Are you still fine tuning the False Color 'Video' color index? In that mode the 'Maximum Exposure' color is yellow. Orange and Red aren't present.

If you are judging exposure solely on False Color Video , thinking you still had some room in RAW you would be wrong (although the RAW Color bar shows you have maxed out)

As far as I can tell the Maximum Exposure in RedColor/Video, Yellow, is the same as Red in Raw/Exposure and 105 Zebras.
 

Attachments

  • Exposure_Tools 001.jpg
    Exposure_Tools 001.jpg
    96.5 KB · Views: 0
  • Exposure_Tools 003.jpg
    Exposure_Tools 003.jpg
    79.4 KB · Views: 0
Exposure check

Exposure check

If you are judging exposure solely on False Color Video , thinking you still had some room in RAW you would be wrong (although the RAW Color bar shows you have maxed out) .

With FLUT color science that would be poor operational practice given that you have got RAW exposure tools available to you.

Which build are you on btw?
 
With FLUT™™™ color science that would be poor operational practice given that you have got RAW exposure tools available to you.

I understand that Stuart.

As Chris has pointed out those use to exposing based on RedSpace or REC709 and a stop of safety based on the False Color reading would be caught out with the Yellow reading currently provided by False Color Video in Build 30. There is no Orange or Red.

The RAW color bar does clip out at Red when RedColor Video shows yellow and this does correspond with Exposure False Color Red. This is what lead me to crosscheck what was happening with False Color Video.

Do you plan to introduce the highlight protection function back into RedColor False Color 'Video'?

From my own experience the False Color mode has been largely ignored by our users with the Red One. Operators still preferring their meters, ETTR Histogram or Zebras.

I think with the changes that have been introduced with MX False Color we now have an excellent tool to give them. Combined with the Multi-key I hope it becomes the first choice in judging exposure with the Red MX.

FWIW I preferred the original Build 22 labels Video and RAW for False Color. Currently running Build 30 on Red MX #23
 
False Colors in Build 30

False Colors in Build 30

Hi Scott. Video False Color does include the Orange and Red bars as before - if you enable the LUMA RAMP test signal you can see that.

The key difference is that these color bands are above the IRE level that the FLUT™ color science normally delivers in the RGB domain.

But if you push the RGB video level using EXPOSURE (compensation) or R G B Gains - which are post FLUT™ - then you will see them.
 
Last edited:
False Colors in Build 30

False Colors in Build 30

Am I not going to underexpose too much if I go to ISO 800?

If it's "red" in false colors it's gone anyways or not?

Wouldn't 640 be safer? (And it's exactly one stop higher than 320!)

Well you should do a test and satisfy yourself that it isn't. In our opinion ISO 800 is a very comfortable rating for the Mysterium-X sensor to work at.

As discussed above - you normally won't "see red" with RGB false color as the FLUT™™ color science very nicely rolls off the RGB domain highlights.

So on Build 30 you check your Exposure (RAW) false color rather than your Video (RGB) false color overlays.

It's got just two colors -red and purple - if you don't see red anywhere in the image then you are NOT clipped.
 
Thanks for the reply Stuart.

If that is the case could I suggest some other multi-key options that could be selected?
M1:Default, FC Video, FC Exposure, Focus
M2:FC Exposure, Focus
M3:FC Video, Focus (for those only processing RC/RG)

Not sure if your monitor path is set up to do that but combined with Magnify on User 1, all possible options can be quickly accessed by the operator.
 
That is correct.

Thank You!

Hi Scott. Video False Color does include the Orange and Red bars as before - if you enable the LUMA RAMP test signal you can see that.

The key difference is that these color bands are above the IRE level that the FLUT™™ color science normally delivers in the RGB domain.

But if you push the RGB video level using EXPOSURE (compensation) or R G B Gains - which are post FLUT™™ - then you will see them.

Does false color read correctly in Raw viewspace? I usually use that to check highlights anyway, but it is also nice to see the difference in clipping from Rec 709 to RAW. Is there a way around the FLUT roll-off in false color mode so we can get a better idea of our clipping in a contrast range that is closer to the final look? I have preset the look in camera before for just such a purpose. If we don't touch the FLUT controls in the look menu, will false color work as normal?
 
Back
Top