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

POSTED: Release Build 30 (30.6.0) & Beta Build 31 (v31.6.9)

Brent Carter

REDUSER.NET
Joined
Aug 22, 2007
Messages
4,992
Reaction score
5
Points
0
Location
Irvine CA
We have moved RED ONE camera firmware Build 30 (v30.6.0) from "beta" to "release" firmware version. All new RED ONE cameras will ship with this firmware version...

Changes from v30.5.0 to v30.6.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.

We have also posted the latest BETA version of RED ONE firmware on www.red.com/support - Build 31 RED ONE Beta Firmware, v31.6.9 (password-protected).

Changes since last release (v30.6.0):
* Increased reliability and capability of Master / Slave operation.
* Support for hot plug of Master / Slave communication USB cable.
* Indication of Master / Slave status in UI.
* Slave camera prevented from initiating a record operation.
* Slave camera clip name forced to use Master camera's I.D.
* Addition of POSITION function to set Master camera as CENTER, LEFT or RIGHT.
* Updated metadata in .R3D file to record Master / Slave and camera Left / Center / Right position status.
* Updated metadata in .R3D file to record User Action and Title area / positions.
* Common media FORMAT, CHANGE and RESET commands across Master and Slave cameras.
* Common media UNMOUNT command across Master and Slave cameras.
* Common PROJECT RESOLUTION, QUALITY and REDCODE command across Master and Slave cameras.
* Common VARISPEED and RAMP commands across Master and Slave cameras.
* Common TIMELAPSE commands across Master and Slave cameras.
* Common MAGNIFY command across Master and Slave cameras.
* Common AUTO WHITE BALANCE calculation command across Master and Slave cameras.
* Common MANUAL WB command following Tungsten or Daylight or Auto WB fictions.
* Common TINT setting across Master and Slave cameras.
* Addition of TRIM sub-menu to COLOR TEMP menu.
* Common GENLOCK enable / disable command across Master and Slave cameras.
* Command JAM SYNC enable / disable command across Master and Slave cameras.
* Common Shutter MODE and SYNCRO commands across Master and Slave cameras.
* Common ISO rating command across Master and Slave cameras.
* Common LOOK commands across Master and Slave cameras (excluding FLUT parameter)
* Common LOOK EXPORT and IMPORT for Master and Slave cameras.
* Common USER KEY 3, 4 and 5 set up and enable / disable command across Master and Slave cameras.
* Common Zebra set up and enable / disable commands across Master and Slave cameras.
* Common Frame guide and User Area setup commands across Master and Slave cameras.
* Common TEST SIGNAL commands across Master and Slave cameras.
* Addition of Auto WB as a selectable GPI trigger option.
* Addition of Auto WB as a selectable GPO tally option.
* Support for INTENSITY parameter with Bomb-EVF.
* Transfer of DARK DETAIL parameter to EVF-MENU, and INTENSITY parameter to VIEWFINDER menu.

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
 
There's a fancy new thing going on called 3D.

Unfortunately, as I have only full sight on one eye, I wouldn't know what all that is about, but apparantly they rent two cameras and hook them up with an USB to make arms come into the room...
 
There's a fancy new thing going on called 3D.

Unfortunately, as I have only full sight on one eye, I wouldn't know what all that is about, but apparantly they rent two cameras and hook them up with an USB to make arms come into the room...


Haha:cheers2: Gunleik I have the same problem/blessing with my left eye and my twin sister with her right eye... One eye looks like 4k and the other looks like dv lol...
 
Build 31 / 3D tests

Build 31 / 3D tests

Sorry to hear that you guys can't join the 3D fun, as this build has proven to be very popular with the crews testing it ...
 
Sorry to hear that you guys can't join the 3D fun, as this build has proven to be very popular with the crews testing it ...

POTC4?? :reddevil:

Thanks RED, every one of these firmware updates increases the value of our RED ONE. Maybe not in monetary value but certainly as a tool. The easier RED makes it fit in various workflows the easier it is to sell the RED ONE to DPs, ACs and Producers that the R1 is the right tool for the job.

Keep em coming :-)

All the best,
 
Can't wait to try it out.

Aside from the master/slave updates this little gem caught my eye:

* Updated metadata in .R3D file to record User Action and Title area / positions.
 
User Action / Title metadata.

User Action / Title metadata.

Updated metadata in .R3D file to record User Action and Title area / positions.

Yes, for example. Shoot 4K 16:9, but set User Action to equal 4K HD. Have REDCINE-X extract (crop) to the User Action size....

Advantage is you still have 2:1 downscale to 1080p, but also have extra recorded area for image stabilization / reframing etc..
 
Yes, for example. Shoot 4K 16:9, but set User Action to equal 4K HD. Have REDCINE-X extract (crop) to the User Action size....

Advantage is you still have 2:1 downscale to 1080p, but also have extra recorded area for image stabilization / reframing etc..

This is useful?

thanks

M
 
User Action / Title metadata.

User Action / Title metadata.

Well if you have a need for image stabilization / reframing - yes. :-)
 
Build 30.6.0

Build 30.6.0

.. for us who installed 30.6.0 when it was in Beta, do we need to reinstall it now it's been moved to Release...

No need to re-install Jordi.
 
User Action Guides

User Action Guides

Updated metadata in .R3D file to record User Action and Title area / positions.

You may also have noticed that when in Master / Slave mode, the X and Y offset for User Actions are linked.

As an example, a +5 X Offset on the Master camera, becomes a -5 X Offset on the Slave camera.

This provides an additional benefit for 3D imaging in addition to the image stabilization feature mentioned above.
 
Thanks a lot, Stuart! Not that it was a lot of work to re-install, but if it's the same, then job done!

Let me congratulate all of you for the Blue Channel improvment. With all the good thing in the usability within Build 30 it would have been a pain in the @$$ to get back to 21 for a clean image with the M sensor.

Thanks!
 
a little bit off topic, but does anybody know how to get a 30.5 release build - can't find it on the red support page anymore.

best wishes,
martin
 
a little bit off topic, but does anybody know how to get a 30.5 release build - can't find it on the red support page anymore.

best wishes,
martin

Hey, Martin, I've noticed it's not available from the support page. Now, don't get me wrong, just curious. Why would you want Build 30.5 instead of 30.6?

In my case (still stuck with the M sensor) it's been a huge improvement with image quality (Blue Channel) and the rest was exactly all the same.

Did you notice some other changes?

Cheers.
 
Back
Top