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.
Here's to deep, rich blacks!
cant believe how the color fidelity holds at that ISO.


nice work guys.

battistella
 
Jarred Land said:
Ok the guys need to take a break.. still have some more tests to do but here is the test I was talking about wanting earlier, the Dynamic Range chart @ ISO 800 on the left and @12800 ISO on the right. The left side have Graeme's clip markers overlay so you can see the stops that don't count ( red squares )

Gives a great one-shot overview of whats going on.

Top chart is the Epic MX. Pretty damn good still.

Bottom one is the Dragon before Graeme's new calibration/color science.

The Middle is Graeme's new work. Graeme can add explain the nuances.

This chart is shot @ 5000k... There is also a great improvement in tungsten with all this, hope to show that on monday when the tungsten chart shows up.


http://www.redgrabs.com/up/1403423374.jpg

Click to expand...

THX!
 
Jarred Land said:
We have a couple more tests to do on Monday so will not know till those are done. After that its off to Rob to button up Graeme's code and put inside RCX and the SDK as well as the camera guys roll into a build ( which the work is already done on that side ) .
Click to expand...


Just so I understand, will this fix immediately work though the entire pipeline as soon as the firmware is updated on the camera and the camera is calibrated or does the post software (Resolve) need an update as well to fully see the results?

Thanks for the effort. This fix can't come soon enough for those of us losing thousands every week from having our Dragon's sidelined.
 
Paul J Steinberg said:
Thanks for the effort. This fix can't come soon enough for those of us losing thousands every week from having our Dragon's sidelined.
Click to expand...


What?

thats a tad drastic and over dramatic no? Plenty of people are getting stunning results from the dragon.

Battistella
 
Paul J Steinberg said:
Just so I understand, will this fix immediately work though the entire pipeline as soon as the firmware is updated on the camera and the camera is calibrated or does the post software (Resolve) need an update as well to fully see the results?

Thanks for the effort. This fix can't come soon enough for those of us losing thousands every week from having our Dragon's sidelined.
Click to expand...

RCX and the SDK need to be updated which means for Resolve to use it they will need to update their SDK. Obviously RCX will be immediate.
 
Paul J Steinberg said:
Absolutely, lots of people are getting great results. There are also a number of cameras out there that have such noisy shadows that they can't be used (mine included, noise confirmed by Red tech support). If you're busy the cost adds up quickly.
Click to expand...

but wait, is this a FW fix or does your camera have to go back. RED tech support told you, "you dragon is one with noisy shadow problem?" I don't get it. Can you post some samples.

Battistella
 
We've been told many, many times that this is a FW upgrade.
 
Mark Wilkinson said:
We've been told many, many times that this is a FW upgrade.
Click to expand...

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
 
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?
 
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.
 
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...

because they are at 12800 ISO...
 
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...

BC it is focused on making noise visible?
Like seriously underexposing at 12800 ISO :)

(jarred beat me 2 it...)
 
Status
Not open for further replies.
Back
Top