Ryan Chernin
Well-known member
- Joined
- Oct 14, 2020
- Messages
- 214
- Reaction score
- 45
- Points
- 28
Dude….. yes!
I knew your name looked familiar. Small world, let’s chat offline. What’s your IG?
Wild!! Sent you a PM!
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
Dude….. yes!
I knew your name looked familiar. Small world, let’s chat offline. What’s your IG?
Do we think this is going to get resolved or will RED brush it under the rug? I love most things about my raptor but have seen this in a few shoots I've had at this point. It's tough for me to bring this on set with this current flaw.
Oououf. Yeah, it's like a dead pixel: you might not notice in passing but as soon as you do see it, you can't *un*see it (especially on that clip; it's basically centre face, which is where an audience's eyes would go to by default).
Tough to say given RED's track record... I mean, REDusers have been dealing with aperture reflection "red dots" at medium stops (as low as T4 on some of my lenses) with literally every RED camera/sensor to date (except Raptor) and RED's response was always 'just don't shoot like that'. Similarly, they ignored/denied that their ISO was off by a full stop for almost a decade, and when they did fix it they left out older cameras (even though they weren't officially EOL yet). That said, when the OLPF fiasco happened with DSMC1 they did have an optional recall to get it the interchangeable system installed.
Something tells me if it can't be reduced via firmware/debayer tweaks in the SDK or user installable flocking/gasket, they'll do the 'it doesn't happen often/don't shoot like that/real pros use a matte box and control flares' until their next hardware launch (kinda like how they handled Dragon's penchant for CMOS Smear... or timecode issues in general).
...I mean, REDusers have been dealing with aperture reflection "red dots" at medium stops (as low as T4 on some of my lenses) with literally every RED camera/sensor to date (except Raptor) and RED's response was always 'just don't shoot like that'.
Something tells me if it can't be reduced via firmware/debayer tweaks in the SDK or user installable flocking/gasket, they'll do the 'it doesn't happen often/don't shoot like that/real pros use a matte box and control flares' until their next hardware launch (kinda like how they handled Dragon's penchant for CMOS Smear... or timecode issues in general).
i don’t actually need it to be 100% perfect... just nearly as good as a Monstro which also has a stitched sensor. Ryan’s clip above was one of the worst example for me as it was very far from a synthetic test and it was with a signature lens which is pretty telicentric. (Though I do feel the Wooden camera or c7 mounts are far from ideal... maybe Red should make these?
Lots of us shoot into big back lights all the time... the love of flares isn’t going away soon SO I don’t think it would be acceptable from a Red POV.. to leave as is.
On a more hopefully note has anyone diy’d the mount into a much better state?
I have some new flocking material coming this week and will repost back here if it works..
Pretty sure the only reason that helped was because STH was noisy at even mid-ISOs and took a stop from the bottom and put it on top... Meaning you didn't need to stop down as much in bright scenes. But yeah, it still happened on STH far more (and at far lower apertures) than Alexa or any segment Sony/Canon/BMD (Personally, I've never been able to duplicate it on any of those cameras).i thought the responce was shoot skin tone? ... that does work!
i hope you are wrong! I feel they need to make this better by any means... Monstro and Dragon W didn’t have these issues (ok I have heard one example but I have never been able to replicate myself... )
...
I have some new flocking material coming this week and will repost back here if it works..
I don't think they're in cahoots or anything, but I also have a hard time taking the use of 'you mileage may vary' type language without a huge grain salt/skepticism... Like does 'we haven't been able to *provoke* it' mean they haven't been able to duplicate it at all with their mount, or that it's *no worse* than stock-mount Raptor? If it was just flocking/mount~adapter material, you'd think RED would've solved it by now.Looking at the new Strata Mount by Kippertie... seems like because it's build is a "bolt in design" it may help with the issue if it is caused by light bouncing around in the adaptor. There is also a video of how the adaptor works and it seems to mimic the DSMC2 mount design.
In an article they write "In order to achieve high optical performance, the inside of the adapter features optical baffles and flare traps that should minimize internal reflections."
Response from Kipper tie
"we’ve not been able to provoke this issue with the Strata mount. It is very hard to prove a negative however, so there could still be specific circumstances in which that may occur."
Any one else seeing this thinking the same thing? Since they are in cahoots with RED this may be something that has been in the works behind the scenes.
Thoughts??
It seems strange that by using a RF adapting mount is the cause of the sensor split issue. To me the direction of the light hitting the sensor & lens tele-centricity are the main causes.
Regarding the KipperTie ND Filter mount, if this mount doesn't show the issue, I wonder if the glass filter is somehow "filtering" the issue. Hard to imagine but it's a possibility.
My solution was to flock the mount and/or build a light shield as the issue pertains to "stray light rays", which is why the mount can play a roll.
Phil Holland might something like this do the trick? https://www.amazon.com/dp/B087PDD53...t_i_EJ7WCWVC497XDGSV19A3?_encoding=UTF8&psc=1
Or best to use adhesive and flocking powder?
It’ll be interesting to see if the flocking reduces flares in general (and that’s why it “improves” the split from being visible), or if it actually just reduces the visibility of the split while retaining the flares.
Anyway, keep us posted!
Got a shoot tonight in the same location as the vimeo clip, so I'll get a chance to test the exact lighting conditions with the added flocking.
It should be pretty easy to test & recreate without being on an actual shoot. Just get a fresnel style or telescopic spot light beam (doesn't need to be even that powerful) and put it on a stand.
Use a neutral colored backdrop, underexpose a bit and pan through the light source.
Alright, so I tempted fate by joining the "this is hard to replicate" side. Finally happened In a real shooting scenario on set. Pretty much present throughout an entire take while light flared the lens.
https://vimeo.com/673066563/45c75fcefc
Wooden Camera LPL to RF adapter and a 40mm Signature Prime
*Edit: upon further inspection, you can see the artifact anytime there's a substantial lens flare passing through center frame. James is right!
Heartbreaking. Thanks for sharing. It's so frustrating but the sensor doesn't seem reliable at this stage. I'm not surprised to see V-Raptor owners selling off. I truly hope RED is going to address and fix this issue sooner than later. My biggest question is why this is not happening on Monstro or any other FF Sony or Canon cameras. Please let us know if you will be able to send your V-Raptor back for "repair". Cheers.