Patrick Tresch
Well-known member
![]()
Mike
DRAGON GETS HOT!!!
Nice shot Mike! Best picture to close that thread!
Pat
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
![]()
Mike
You're not guilty. The issue is that:
1. RED's black shading is unintuitive
2. RED didn't release a clear article like Mark's for users to read
If the user error is caused by a design error... the fault lies with the design error. That's Design 101 - which RED's products repeatedly fail.
The biggest cause for that is simply arrogance.
Someone at RED really needs to start thinking from the humble perspective of: "How are we failing our users? Where are they getting tripped up? How can we redesign things and change the way we work to make it easier for users?"
If you read most comments on the forums here, the attitude is completely wrong. If you get a bad result out of a RED product, it's 500% YOUR FAULT and you are a BAD PERSON for saying so publicly. I hope RED isn't picking up their attitude from that!
Bruce Allen
www.boacinema.com
This image should once and for all settle the "heat issue". I still remember how Jim said the dragon loves heat. Now I see what he meant.
That's just one incident. For all the people shouting users need to learn how Red works and we should Reducate every people, why couldn't Red make the camera more user friendly or set definite guidelines in the manual?
It's been more than seven years we've had this kind of incidents, don't you think Red might have been too vague for people?
Plenty of people I know who are experienced with Red still ask so many questions every time Red has an update. Why??
Also, I don't know if I'm liking Gunliek in yellow. I hope he will remain cool and not trying to defend Red everytime someone has issues.
2. RED didn't release a clear article like Mark's for users to read
Well, of course the long term solution is to just design a sensor that isn't so sensitive to black shading (how do Arri, Sony, Canon, etc do it?).
Thanks for listening. The RED article isn't great.
It is long, yet still fails to explicitly mention all the stuff Mark does - eg that the RED camera itself heats up and is a major factor in this whole thing. And how to make multiple maps ahead of time.
It also doesn't even mention CAL T/E.
It suggests that Black Shading is necessitated mainly by firmware changes, big (eg 1/4 sec) shutter speed changes, or big (15 - 30 degree) AMBIENT temp changes.
RED's guide should start clearly talk about SENSOR temperatures not AMBIENT temperatures.
Also, often you can't stop down to black shade every time the temp changes on a shoot. Well, you can... but then people will say nasty things like "The Epic's gone down, dude. The camera heated itself out of its own sensor range and now we can't shoot for 20 mins. Should have rented an Alexa."
This is a MAJOR reason why RED is perceived as finicky and unreliable.
Mark's solution (creating multiple black shade files for different temperatures ahead of time) is brilliant and needs to be included.
Well, of course the long term solution is to just design a sensor that isn't so sensitive to black shading (how do Arri, Sony, Canon, etc do it?). But Mark's solution is a good guide for now.
Bruce Allen
www.boacinema.com