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

Prismatic error, not lens

Sarah C.

Well-known member
Joined
Aug 15, 2008
Messages
463
Reaction score
0
Points
0
Location
Joined REDUser while sitting at a desk for Fast an
This happened this morning: camera (a RedMX) was fine for first half hour, then we discovered this artifact/error. We swapped lenses, rebooted, it is also found on the R3Ds. What do you guys make of it? (see images below--photos of monitor screen, NOT from files)

ps. we swapped Vlad's 87x body in at lunch. Thanks again, Vlad, you hero! :)

edit: the effect is like light coming through a raindrop.. that's what I mean by "prismatic". *There was NO lens change between not there.. and there. In fact, the lens was on from the night before. The owner/AC says the sensor was clean.

EDIT: (2/20/11) As suggested by CJ Roy, after cleaning the sensor (the low pass filter in front of it) we did try the firmware update and a single black shade. FIXED. A cam is now our backup today. Thanks for the quick responses, saving grief and repair hiatus.

thanks all!
~s

Error_01.jpg


Error_02.jpg
 
Last edited:
I doubt it was anything wrong with the camera other than some smudge or dirt on something optical. This is an optical looking artifact, not an electronic looking artifact. It could be a piece of dust or tiny drop of water on the sensor or back of the lens. Since a body swap fixed the problem I would say highly likely that at one point there was something on the OLPF or on the lens that was noticed during the body change.

Tim
 
ANSWER: Firmware update, one black shade = FIXED.
Crazy!

No sun involved, not pointed at lights either. This camera was on a green screen stage the night before and shoot day.

thanks everyone, CJ Roy called it!
~Sarah
 
Very bizarre. I've only seen it once. Glad you got it fixed.

Remember, firmware re-installation should solve the majority of puzzling issues. Which, I'm sure RED would tell you themselves.

It sounds like it may have been black shaded with out a lens cap and just stopped down.
 
It sounds like it may have been black shaded with out a lens cap and just stopped down.

The instance that occurred that I know of, happened spontaneously. Camera was fine one minute, then aimed at the sun and then had a strange spot on it until re-installing the firmware.

Haven't had it happen to me personally, but I believe I can get you the original R3D when I get back to the US, if you're interested.
 
It sounds like it may have been black shaded with out a lens cap and just stopped down.

I wasn't standing next to the camera when they set it up first thing in the morning. This team is very experienced, not students. The problem began after a half hour into the shoot, confirmed by the recorded R3D files. Considering we were on a green screen stage and the camera was on a very solid Fischer dolly that was not doing any dolly moves at the time, it would be reasonable to believe we didn't create the problem? All the same gear/accessories were used when we swapped in Vlad's 87x camera body and it was fine.

Update(while I was writing the above): the camera was running an old firmware update 30.5.0, but had all these months with no issues! Something came along and caused this hiccup, and it wasn't the sun. Be good to know, since not always will a camera be near the internet for a firmware download and update, and what's to stop this from happening at a seemingly random unpredictable opportunity even with a new one(firmware update)?

--I ask as neither a Red owner or AC, hoping the information will help all.

thanks guys,
Sarah

ps. We have R3D files here in LA if you want copies to study.
 
Note to self, do not put a marker on the talent's forehead. Sorry, I couldn't resist.
 
Back
Top