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?

What's up?

What's up?

To get to the bottom of whatever may have affected that specific camera what we at RED need is:

a) a copy of the camera LOG file and

b) an example .R3D clip that shows the issue.

Without this hard data, we are adrift in the seas of rumor and speculation.
 
Anybody who wants more information about this can contact me via PM. I'm not going to post screen grabs of what the issue looks like as it is the client's footage.

I've been Red Tech on over 50 shoots and have never seen this issue. It was in our last footage of the day and we were wrapped by the time I caught it, so no tests were done in the field to remedy the issue. I presumed it would be something that the camera owner, rental house, RED, and myself would be examining today, but it appears that this forum thing happened instead.
 
What's up?

What's up?

I presumed it would be something that the camera owner, rental house, RED, and myself would be examining today, but it appears that this forum thing happened instead.
Click to expand...

The more appropriate thing however would be to do the above...

If you wish you can send me the appropriate information at stuart@red.com, or you can send it via Brent.
 
I brought thus issue up because I'm using this same camera Friday... If you want to PM me, I'd be happy to get your feedback on it. I'm still taking the camera out. If we have to black shade it, no biggie. The camera house has been testing the body all day with no issues at all.
 
chris i am available friday!
 
CJ Roy said:
A similar issue happened to me with a camera I rented.

Everything seems to be solved now with Dan Duran's help. I'll be going down to Red tomorrow to work with Dan to double check everything. Until then, I don't want to speculate.

-CJ
Click to expand...

Any report back on your day at Red?
 
Didn't get a chance to go down to Red today, but our issue is resolved and the funkiness with the image was a processing error rather than sensor error.

Different issue, but strangely coincidental.

As for the other issue, hearing from several different people, the only way to see line in the image is once it's offloaded. You'll never see it on camera. Pretty scary stuff.

I guess we shouldn't be using Beta Firmware on these shoots.

-CJ
 
As long as the expectations are set with production, I have no problems using beta firmware on real productions.
 
this vertical line problem popped on a last shoot here as well (red1 m sensor). after a new black shading it was solved.
 
I had what may be a similar problem on the weekend with a single, dotted green line running down the extreme left hand side of frame (shooting 4.5K RC42 build 30.3.1):

A009_C110_0307KL.0000059_baseline.jpg


Here's the R3D to verify it yourself (95MB):

http://downloads.visceralpsyche.com/A009_C109_0307CJ.RDC.zip

This is the original sensor on camera #378 and a few of the preceding shots have it also, this was just the smallest take size wise to upload. It disappeared after a restart, prompted by another error where I couldn't get out of 100% pixel zoom mode and had to force shutdown the camera to reset it. I don't have the LOG file with me sorry otherwise I'd post that too.

I'm not sure if it was a heat related issue or not, as the camera had been running for some time prior, though the fan was on auto so that should have kept it within norms. The small studio area wasn't hot at all, just normally warm (it's winter here right now and snowed the other day!).

So, is this similar to what others have seen, or is it another problem being discussed here?

HTH

Paul
 
Until it's not beta rent a back up body. Cheap insurance. Sounds like chances are slim that you'll need it. But you can fulfill your professional obligations.
 
Just as an outside observer the big drag with threads like this is that they push us all back a bit.

I trust a lot of opinions in this thread, but from a perception standpoint it's a bummer.

RED is going out of their way to make EPIC bulletproof, but then we have this kind of thing popping up with firmware builds on the "new great sensor", the one everyone currently wants to have.

This stuff flies around like crazy and the next thing you'll be hearing is that the M-X isn't prime time.

I trust it will all be as close to perfect as things can get, but these nagging problems keep (some) hedging...I love the new images, but I like the idea of a bulletproof EPIC a lot.

David
 
Right David, so better yet, let's leave everyone else in the dark if we experience any issues out there. Certainly wouldn't want to spoil everyone's excitement be sharing useful information, giving others a heads up, or helping someone solve a problem they are experiencing.

Perhaps your job and reputation isn't on the line on costly productions, but personally, I don't want to have ANY issues on my watch. Whether it's unavoidable or not, having unusable footage or having a camera go down on a shoot doesn't make a great impression of your work.

I think I'll stick with the sharing of info and be proactive. Like the Build 30 thread where others having experienced crushed blacks on the original sensor... Well now I know what to look outfit on my shoot tomorrow with a Mysterium R1 with Build 30.
 
I 've seen that on an M sensor camera as well last year, only on 4k, not on 2k, not on the monitor. It appeared to be a faulty CF module, which would still be my guess for this issue.
 
If someone's goal is to get a technical issue solved quickly, the fastest way is to simply take it directly to Red tech support. The round about way is to start a thread and then wait for Red to respond on it. If someone's agenda is to get their problem solved, then why go the long way around to do it?

I've owned multiple Red cameras since the very first ones shipped. When I've had tech issues and questions, I've simply followed what I suggested in the paragraph above, and Red's resolution of my concerns has been extremely quick and very professional. In all this time owning Red cameras I've yet to start a thread about a tech issue - because as a professional working on high-profile productions my time is very limited and valuable, and I need to get answers ASAP - which is why I go directly to Red tech support for them.

Going the public forum thread-starting route with this is not only the slower way to solve your issues, but usually causes unnecessary angst among the Red User community. Red Team has been very quick to analyze and solve issues when they're made aware of them. If an issue turns out to be important for all cameras, they've also been very good about notifying the community quickly about it. If its just an individual camera situation, they've also been equally quick to solve that. I see no need whatsoever when faced with an issue to panic and jump into a starting a public thread strategy.
 
I have to echo Gibby on this one. Going directly to RED is faster and more productive. Posting this kind of thing in an open forum hurts us all. If you have an issue that RED cannot solve in a timely manner or you feel like they're hosing you that's different. It's also reckless to question the functioning of the MX sensor when you have no way of being sure that was the issue. WTF?

Come correct.

Cheers - #19
 
You must log in or register to reply here.
Back
Top