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

RELEASED: Beta Build 30 Firmware (v30.6.0)

Brent Carter

Brent Carter

REDUSER.NET
Joined
Aug 22, 2007
Messages
4,992
Reaction score
5
Points
0
Location
Irvine CA
The latest BETA version of RED ONE camera firmware has been posted on www.red.com/support - Build 30 RED ONE Beta Firmware, v30.6.0 (password-protected).

Changes since last release (v30.5.0):
* Resolved Genlock syncing error following return from on-camera clip PLAYBACK.

* Improved Blue channel image quality for RED ONE cameras with Mysterium sensor.

* Improved Blue and Red channel performance under highly saturated green screen.

* Resolved image capture error with 2K resolution recording at 117 - 120 fps.

* Addition of MEDIA MODEL and MEDIA SERIAL number to VIEW STATUS menu.

* Correction of VIEW status in UI when VIEW switched by GPI or User Key.

* Correction of FOCUS false color error when operating in VIEW = RAW.

* Correction of LOG file write confirmation error when no media is attached.

* Preliminary support for Bomb-EVF viewfinder.

* Support for FIXED and SYNC monitor modes with Bomb-EVF

* Support for User Key 3 and 4 functions from Bomb-EVF.

* Support for TALENT tally with Bomb-EVF.

* Support for OPEN GATE mode with Bomb-EVF.

ALWAYS READ ALL INSTRUCTIONS CONTAINED IN THE DOWNLOADED INSTALLATION FILES BEFORE PROCEEDING.

WARNING: AS THIS IS A BETA BUILD, THIS FIRMWARE IS RECOMMENDED FOR PREVIEW AND TESTING PURPOSES ONLY. IT IS NOT RECOMMENDED FOR USE ON COMMERCIAL PRODUCTIONS.

NOTE: After upgrading firmware, a BLACK SHADING calibration should be performed. Detailed instructions are contained in the Operations Guide ( http://www.red.com/support/release_history/12 ).

If you have any questions or feedback, please contact RED Technical Support at www.red.com/support.

Thanks, BC
 
Build difference

Build difference

Is this any different to the non-released 30.5.6?
Click to expand...

Only in regard to the camera error LOG file write bug. Otherwise 100% same.

Thanks for helping test the fix for us.
 
oh, I've seen the 2k over crank issue before, glad it's fixed.
 
I did a quick comparison test to see whether 30.6.0 would fix the blue channel "speckling" issue.

This is no "scientific" test, but rather a quick and dirty one. Regardless, it tells a story.

Notes:
1) The 30.5.0 test was shot a couple of weeks earlier. A different lens was used for the 30.6.0 test. Both lenses were F1.4 and shot wide open, but by different manufacturers (still lenses by Nikon and Sigma)
2) The DSC chart was lit approx. 0.7 stops brighter for the 30.5.0 test, i.e. 30.6.0 test was shot at lower light.
3) Levels of the 30.6.0 jpg were tweaked in Photoshop so it would match the 30.5.0 jpg better; jpg for 30.6.0 was originally quite a bit darker.
4) 30.6.0 jpg looks softer than the 30.5.0. This is most likely caused by 30.6.0 test being shot with a different lens.

Anyhoo, crops from the 4K HD frames. First, 30.5.0:
3050_Blue.jpg


And here's 30.6.0:
3060_Blue.jpg


The "speckling" is gone in 30.6.0. Well done, RED!
 
Might be good to do a resolution test before and after upgrading based on those images. The noise improvement is incredible.
 
Joel Kaye said:
Might be good to do a resolution test before and after upgrading based on those images.
Click to expand...
I wouldn't worry about it, to be honest. The lens I used for 30.6.0 is soft as **** wide open. Too bad I couldn't find the lens I used for 30.5.0 right away and picked another one.

The noise improvement is incredible.
Click to expand...
"Speckles" in 30.5.0 shot aren't actually noise, I think. They're more like compression artefacts or results of a software bug.
 
Gunleik Groven said:
Leads to thoughts around how RAW RAW is...

This is really cool, though!
Click to expand...

Yes it could be of great reference to have real knowledgr insight in the raw world.

Why are there so many different raws if raw is raw? What happens to the BW Values when it is mapped to RGB values? Without speaking about debayer techniques...

Pat.
 
Nice to see someone else's tests Petri :)

We did a little blind test here and came to the conclusion that we can push ISO a touch further under 30.6 on the M sensor. Its more marginal than pixel peeking in the blue suggests, but it stands up to scrutiny.

I've only done casual rather than documented test on green and bluescreen, but it can be make or break if the screen brightness is low.

Full marks to the Red team. I do wonder if this is related to Jim's mysterious 'Major Improvement' thread recently?
 
John Marchant said:
Nice to see someone else's tests Petri :)
Click to expand...
I was actually overjoyed to find Paul Clement's thread about the speckling in 30.5.0 because I'd noticed the same anomaly a couple of weeks ago and thought it was most likely caused by me goofing something up. I'm a know-nothing newbie.

We did a little blind test here and came to the conclusion that we can push ISO a touch further under 30.6 on the M sensor.
Click to expand...
I don't want to derail this thread, but suffice it to say I'm still not 100% sure how the ISO setting actually works on R1. AFAIK it doesn't really alter the sensitivity or gain of the sensor. We shot a music video in the middle of the night and I talked the director into shooting at ISO320 instead of pushing to ISO1000 or above, telling him high ISOs don't work like they do on DSLR cameras. (He's probably going to read this post and tell me off.)

I do wonder if this is related to Jim's mysterious 'Major Improvement' thread recently?
Click to expand...
I was under the impression that the 'major improvement' was for M-X sensor only.
 
The ISO works much the same as on a DSLR, but it isn't baked into the image its just metadata for software to interpret later.

As to the 'improvement' I never really was able to understand whether it was MX only or not. The wording sort of suggested as much, but in saying that the improvement could be applied to old footage it rather implies that it would work across the board to some extent. That said, it would also imply that the change would be more in post tools than camera firmware.... Who knows?!
 
John Marchant said:
The ISO works much the same as on a DSLR
Click to expand...
Hmm. That's not the way I understood it by reading this forum, but let's not take this thread down that road. I'll drag my ignorance to a thread better suited for ISO discussion.

Who knows?!
Click to expand...
THE SHADOW knows... oh yeah, and the folks at RED.

Have to add this: loooove the speckle-free blue channel! :thumbup1:
 
I was thrilled to see the fix for the noisy blue channel in 30.6! So much so that I had a friend upgrade his camera last night , so his green screen shoot today would benefit from those changes. Yes, the blue channel is cleaned up considerabley, but I noticed a couple things.

1) The RAW view and the REDCOLOR view look completely different.
2) The green screen looked almost totally blue under tungsten with the kelvin at 3200 when viewing with REDCOLOR.
3) RAW view looked closer to what my eye was seeing, but still not correct.

I should note that all settings were set to factory settings and black shading was done after the camera was warm. The set was lit with all tungsten lights.

So, is anyone else seeing what I am seeing?
 
You must log in or register to reply here.
Back
Top