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

Noise on the low end but even worse scary megenta lines

Status
Not open for further replies.
Gavin Greenwalt said:
Jarred do you guys have seats of Nuke at RED? I've been playing with a gizmo for CMOS correction on and off for some time. If so I could send you the code when it's a bit more reliable. Ultimately though I feel like RED would be best equipped to handle this since you could really mathematically characterize the noise as a function of clipping more accurately. To really properly correct this you would also need access to the RAW bayer pattern data which we lowly users no longer can touch. To handle it in post is a bit tricky because of the way bayer channels are laid out. The best place to apply the correction would be prior to debayer since the additional voltage/gain is per-row and obviously on bayer pattern different clipping rows have different colors so in a very worst case scenario you might only get a streak in the RG or BG rows. Then when debayering you'll get a colorful streak. Also in the case where you have very strong primary colored lights you're going to get unpredictable correction if it's performed post-debayer.
Click to expand...

We work very closely with the Nuke guys ;)
 
Zeb B said:
Why do the charts from yesterday show noise that I have never seen in a chart posted on RU in the past? Is it a different testing method?
Click to expand...

I'm fairly certain that the charts in the past were not with portions set to ISO 12800.

(Jared beat me to it as well.)
 
David Battistella said:
Thanks mark,

its like that that high speed thing. What you showed was normal, like what my camera would reproduce, but the op never posted the problem, so it's hard to figure out what is the problem and what is the expectation.

I think if anyone wants to post problems they need to post their own r3d and examples otherwise this runs the risk of being giant speculation.

Battistella
Click to expand...

Agreed - frustrating.
 
Gunleik Groven said:
We should make a tune and a very geeky musicvid... :)

I am in!
Click to expand...
Grrrrrr-aeme, *aeme, aeme, aeme, aeme
Gentle as a lamb *amb, amb, amb, amb
Unless he's codin' for Dragon, *agon, agon
Then his braveheart is in nohhh wayyyy laggin'.

* denotes echo
 
A little bit of Graeme Masala makes everything better!

graemeMasala.jpg
 
Bob Gundu said:
A little bit of Graeme Masala makes everything better!

graemeMasala.jpg
Click to expand...

I think before he will endorse that product, it will have to have been soaked in Single Malt Whiskey.
 
A.D.D export with GPU + CPU encoding with Adobe Encoder would be a mind blowing feature (just throwing that out there.)
 
So is this fix comming before the end of the week.... our camera is going to be the main camera on a high budget deep see diving expidition next week... I have to cancel if this is red noise is not solved before friday night. I rather have a no now than a yes and then it does not happen. The only reason they use my camera was due to it's splendid low light capability.. but now I got the new olpf....


I have not follow this tread to closely so let me know if I'm asking the obvious.
 
Bjorn,

the word at this moment seems to be by the end of this week, but my guess is that it would be a beta build.

Battistella
 
David Battistella said:
Bjorn,

the word at this moment seems to be by the end of this week, but my guess is that it would be a beta build.

Battistella
Click to expand...

And the SDK isn't going to trickle immediately into Resolve, Premiere, or FCPX either. But I'm sure Redcine will be released at the same time.
 
Jarred Land said:
Gavin and Rob are correct.. this is a relatively normal CMOS thing.. kinda like the black sun dot all cameras used to have ( i think some cameas from other manufacturers still do ) its been there since the R1 since we do use CMOS technology like almost everyone else. If you take a small source highly clipped a bunch of stops against almost black and it crosses the edge of the frame or just off the edge of frame ( most cases ) you will see what looks like a streak. People call this the "phantom blinds" effect because the easiest way to replicate this is to open slit blinds into daylight in a pitch dark room. Of course you will see this at higher ISOs, and most post houses have developed a post fix from dealing with it over the years from many cameras. Its a silicon thing.

The company that makes the dynamic range charts we use actually have added a little flag that goes over the clipping square now, because if your shooting a CMOS camera and you get that flare it can actually trick you into thinking you have more DR... since the streak replicates the shape of the highlight and lifts everything with it.
Click to expand...

Hi Jarred,

I am just a little confused that the Dragon seems to have that vertical line problem a little more than the MX...here are two shots...one taken with our new Dragon and one with the Scarlet. Both using the same lens, same F-stop, same lighting etc... As you can see it appears on the dragon and not the scarlet
Also the Dragon is abviously noisier in the red channel...but that's been covered to death and I know RED has a fix for it so I am not too worry about it.

On the positive side...the color and skintones on the Dragon are simply amazing!!!!!! Blown away by the amount of detail and subtleties the Dragon brings! Very excited and happy about it!
 

Attachments

  • dragon.jpg
    dragon.jpg
    68.9 KB · Views: 0
  • scarlet.jpg
    scarlet.jpg
    60.3 KB · Views: 0
Status
Not open for further replies.
Back
Top