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 faster read-reset times... WHEN?

Miltos Pilalitos

Well-known member
Joined
Jan 3, 2007
Messages
995
Reaction score
0
Points
16
Age
52
Location
Athens, Greece
Website
www.pilalitos.com
For all of us that upgraded our REDs with Mysterium-X sensors on the promise of improved dynamic range and less rolling shutter it would be really nice to have a slight indication of when the new sensor speeds would be activated.

The improved dynamic range is fantastic and makes me happy but i still want the full potential of my RED M-X.

So, when are we supposed to have it activated guys?
 
The last info was that the tuning of the sensor in regards of DR, color, noise will be done and after that the clock speed. But a higher clock speed will be wormly welcome....
 
But a higher clock speed will be wormly welcome....

It doesn't make sense that almost nobody discusses this MX feature!

I jumped from happiness last spring when i heard it's almost two times faster than the old sensor but judging from this thread it looks like redusers don't really anticipate it. :confused1:
 
I thought it was upgrade-and-play. Thought all M-X Red Ones already had this going on.

Are you sure it isn't active by default from upgrade?
 
Oh, that sucks... Hope they can figure out the other thing soon.

It doesn't sound like this is the case, but maybe there is a limit to what the hardware can handle. Buffer memory? After all, this is a 3-year old camera recording 4.5k... If that's the case we really can't feel bad about it.

Were there any stability issues associated with the faster read speed?

Hope it can come back soon!
 
calibration issues if my memory serves me...

Still curious about some MXcalibration issues and the next MX firmware release, whenever it comes...
 
I guess the other question is, how this will affect the Epic since it's the same chip?

It seems likely that the Epic was designed for the faster read-reset times, and since it's an ASIC, it may actually be "hard-coded" to work with the faster read-reset times. Here's hoping...
 
Back
Top