Welcome to our community

Be a part of something great, join today!

Log in
  • 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 issue / "Beta" use only?

Christopher Probst

Christopher Probst

Well-known member
Joined
Nov 12, 2009
Messages
1,424
Reaction score
3
Points
38
Location
Los Angeles, Ca
I've booked a Mysterium-X upgrade R1 for next week but apparently there is some random issue with the new sensor? Some vertical line or noise that people have encountered? Apparently the camera (name deleted as per request) just used and that I booked just had the problem and Keslow has seen it as well... My rental house told me they called Red about the issue and they are saying the Mesterium-X sensor is to be considered Beta only and not for use on commercial productions?

What gives? Can anyone give me more info on what the issue really is, possible situations where it occurs, ect.

Of course I'm excited to use the upgraded R1s in the field, but I ONLY use them on professional productions. At what point is this sensor/build going to be released as certified for real world use. To be honest, I feel like we've been baited and switched... Here's this great improvement, here's how to use it to see greatly improved performance, but oh wait, just don't use it on any professional jobs...

I have high hopes to still use the new sensor next week.

Help and info please.

Chris
 
Last edited:
Are you perhaps using a beta firmware build? I know that's considered as a no no for commercial projects, the mx sensor shouldn't be beta though, no more hardware upgrades will be done to it, it's all on the firmware side now.
 
This post just gave me a heart attack. My red is down there now getting the upgrade.
 
Yeah, I think there is confusion between "beta firmware" - which M-X firmware is - and the M-X sensor hardware. Big, big difference.

BC
 
sounds like the same issue the original M Reds had that could be fixed with a simple re-do of the black shade calibration. Can red confirm?
 
Standard house rules apply - fill out a trouble ticket and we'll work it out. But, yes, Shawn, try a black shade cal. Next step, firmware re-install if black shade does not resolve....

BC
 
Obviously you can't shoot the M-X with anything BUT the Beta firmware... So I guess that is one aspect, what I'd like to know is if the Line issue is with the sensor, firmware or both.
 
Filed that trouble ticket, Christopher? Tried the black shade cal? Firmware reinstall? My money is on those steps - not it being a sensor issue.

BC
 
we have done 15 jobs and 25 days with red#0031 MX and we have not had one problem. not one. all commercial jobs and some very high profile.

dino
 
This issue occured on others jobs, not mine, but it's raising an issue on my rental of an M-X R1... Just trying to get to the bottom of the issue.
 
Christopher, I think you're blowing this out of proportion, this issue occurred on M cameras and can be fixed in <10 min with black shade cal and maybe ~15 min for firmware reinstall and blackshade combined (if blackshade only doesnt work).
 
Christopher Probst said:
This issue occured on others jobs, not mine, but it's raising an issue on my rental of an M-X R1... Just trying to get to the bottom of the issue.
Click to expand...

Christopher - to get to the "bottom of the issue" - you need to define an "issue". You seem to be making an issue based on some second hand information with a general lack of detail.

We've wrapped an entire feature film shooting on MX in freezing cold, underwater, etc. - zero issues. We have two features shooting on MX now. Zero issues so far.

We test lots of builds. We were able to re-create a rare bug on a previous beta build - a vertical line would appear after a rocketIO error which would sometimes happen ONLY when starting to roll the camera while the 1:1 magnify was still engaged. Re-installing the firmware/black shading would eliminate the issue. We reported this issue to RED, sent LOG files, tested a new, revised build - and have never seen that error since. I strongly suspect that is what you are hearing about. If it is - it's already history. If it's something else ... our cameras have not hit the "issue" and our cameras really never rest.

Take a deep breath.
 
It's not me, it's my rental house that raised a red flag... They've been dealing with Red with the issue directly as well. I just was looking for another avenue of info. I used M-X R1 two weeks ago with no issues. The other DP had a problem, Keslow had a problem... Looking for more info to avoid issues on my set. When you have hundreds of thousands of dollars of production dollars on the line, it's always wise to cover all bases... Especially if the camera you're using is only to be considered "Beta Use Only".

I'm willing to roll the dice in favor of having the better sensor.
 
Last edited:
For the record, I did not do the crash job, nor was my camera on that job. i was previously booked on another and had to replace myself for crash's job.

maybe i am just lucky, but my camera has always done well with the alpha and beta firmware and hardware.

i think we have shot about 10 terabytes with the MX so far without any of these issues you speak of.

dino
 
The issue as I understand it is a large vertical line (or more than one) several pixels wide... Apparently, this is different than the overheating lines that appear. I assume the normal black shading/reboot should do the trick, but to be on the safe side, I'm going to carry a standard R1 as a backup body as well...
 
Christopher, you don't have any examples of this phenomenon do you? Video and/or still?
 
I just spoke with the tech whom i hired to replace me and he said it was a vertical line one pixel wide going through the image from top to bottom. when queried by red about the body temperature he was unable to give a definitive answer as he was not at camera for the last two takes of the day, which is when this occurred. my guess is that it was a body temp issue.

i do know that the camera was upgraded a couple of days before with the newest build, which i have not loaded i am still on 30.2.4.

dino
 
This all seems very weird and the fact that it is coming second hand, maybe even third makes it even more suspect. If they had a frame of this line and posted it on here I'm sure many of us could identify it as a Black Shade problem.

When I first got my RED One over two years ago I interrupted the calibration and there was a line of noise in the picture that ran horizontally. I ran the calibration again and the camera was good to go.

BTW, my MX'ed RED has been running fine with no problems what-so-ever.
 
You must log in or register to reply here.
Back
Top