RED ONE Operation Guide

REDONE Build 31 v31.6.16 May 20, 2011

Notes:

• After upgrading to Build 31, on-camera playback of media recorded by earlier builds may not be possible, nor can you add additional clips to digital media formatted under an earlier build.
• MYSTERIUM-X sensor based cameras may not use firmware prior to Build 30.
• MYSTERIUM sensor based cameras may be downgraded, but not to firmware prior to Build 16.
• Ensure you reformat any digital media and Black Shade before shooting under Build 31.
• Download the latest versions of REDCINE-X and/or ROCKETCINE-X from www.red.com/support
• Third party post tools may need to be updated to reflect FLUT and REDcolor color science.

Installation Instructions:

• This upgrade is fully contained in the folder “build_31_v31.6.16”
• In that folder is a copy of this Read Me file and the folder named “upgrade”
• The “upgrade” folder includes the camera firmware upgrade file “redone.su”
  • DO NOT rename this folder, the camera only opens a folder named “upgrade”
  • DO NOT decompress the “redone.su” file, the camera will perform that task.
• For MYSTERIUM sensor based cameras, format a CF or SSD card using Build 20, 21, or Build 30
• For MYSTERIUM-X sensor based cameras, format a CF or SSD card using Build 30 or 31.
• Connect the CF or SSD card to your P.C or Macintosh via a CF or SSD card reader.
• Copy the folder called “upgrade” onto the CF or SSD card.
• Unmount the CF or SSD card from your computer (drag to the trash can).
• Ensure your camera is powered down.
• Insert the CF or SSD card into the CF or SSD card slot of your RED-ONE camera.
• Power up the camera.
• After booting up, the camera rear status display will report “New Firmware” and the RED-EVF or RED-LCD will report “A software update is available for your system”
• Press the joystick to confirm, and the rear status display will report “Upgrading”
• During the upgrade process, a blue progress bar will be visible on the RED-EVF or RED-LCD. This bar will continue for the duration of the upgrade, which is approximately five minutes.
• At the end of the upgrade process, the rear status display will report “O.K. Cycle Power” The RED-LCD or RED-LCD will report “Upgrade complete. Power cycle the camera to continue.”
• Power down the camera, wait five seconds, then power up the camera.
• Verify that the camera rear status display and or monitors report back – PIN (value specific to camera) Build 31 Version 31.6.16
• Installation is now complete.
  Note: After the firmware upgrade, it is mandatory that you re-format a CF or SSD card and perform a BLACKSHADING calibration. At the end of Black Shading remember to power cycle the camera. Operation without performing a BLACKSHADING calibration after firmware updates or downgrades usually creates significant color errors.

Significant changes since Build 30 series firmware:

• Resolution of 3k 16:9 codec error at high frame rate.
• 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.
  • Note: Cameras will take up to 10 seconds after hot plug of USB cable to establish communication, during which time the UI will display a blinking “M” and “S” respectively on the Master and Slave camera. Once the communications link is established and verified the “M” and “S” icons will stop blinking. To reverse the Master / Slave relationship, reverse the USB cable physical connection.
• 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.
  • Note: When Master is set to CENTER, Master and Slave clips are both labeled “C”, if Master is set to LEFT, Master clips are labeled “L” and Slave clips are labeled “R”, if Master is set to RIGHT, Master clips are labeled “R” and Slave clips are labeled “L”.
    • For example, If Master is LEFT and it’s camera I.D letter is B, the first clip recorded will be : Master : B001_L001_******.RDC Slave : B001_R001_******.RDC (where ****** are wildcard + day + date).
    • For example, If Master is RIGHT and it’s camera I.D letter is B, the first clip recorded will be : Master : B001_R001_******.RDC Slave : B001_L001_******.RDC (where ****** are wildcard + day + date).
• Updated metadata in .R3D file to record Master / Slave and camera Left / Center / Right position status.
• Common media FORMAT, CHANGE and RESET commands across Master and Slave cameras.
• Common media UNMOUNT command across Master and Slave cameras.
• Common PROJECTRESOLUTION, 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 AUTOWHITEBALANCE 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 COLORTEMP menu.
  • Note: TRIM sub-menu displays TINT if camera is not in Master or Slave mode when powered up, or displays TINT, S-TINT, S-W.BAL and S-FLUT if camera is in Master mode when powered up.
  • Note: S-TINT, S-W.BAL and S-FLUT provide an offset for Slave camera TINT, W.BAL and FLUT relative to the common TINT, W.BAL and FLUT values programmed from the Master camera. This compensates for monitor path color differences between the transmitted and reflected light path camera when using an optical beam-splitter.
• Common GENLOCK enable / disable command across Master and Slave cameras.
• Command JAMSYNC 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)
  • Note: Auto White Balance value and FLUT parameters are not locked between cameras in order to permit in-camera correction of color shift and transmission loss through beam splitter mirror.
• Common LOOKEXPORT and IMPORT for Master and Slave cameras.
  • Note: When in Master / Slave mode, only the Master requires an SD Card to be installed. Following an EXPORT command from the Master camera UI, the Master camera writes a .RLK file to its SD Card. Following an IMPORT command from the Master camera UI, the Master camera reads the sleeted .RLK file from its SD Card and transfers the LOOK parameters to the Slave camera.
• Common USERKEY 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.
  • Note: X POSN and Y POSN offset programmed for User Action or Title from the Master camera will result in an equal but opposite offsets for the Slave camera.
• Updated metadata in .R3D file to record User Action and Title area / positions.
• Common TESTSIGNAL 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 adjustment on Bomb-EVF : range +/- 1 stop from reference.
  • Note: Bomb-EVF can display upper 784 lines or lower 784 rows of 1280 × 848 pixel viewfinder output.
    • To toggle between these, press both User Key 3 and User Key 4 on the front surface of the Bomb-EVF.
• Transfer of DARKDETAIL parameter to EVF-MENU, and INTENSITY parameter to VIEWFINDER menu.
• Support for RED-SSD Media of 64GB, 128GB, 256GB capacities.
  • Note: Requires Side SDD Media Module to operate the above media. Maximum QUALITY is REDCODE 42.
• Resolved codec error in 4K 16:9 record for Mysterium-X sensor based cameras at 25fps TIMEBASE.
• Enhanced system performance when operating in 4K 16:9 record mode.
• Support for .RMD files generated by REDCINE-X.

General operational notes regarding Build 31 series firmware:

• MYSTERIUM-X sensor based camera may not be downgraded to firmware prior to Build 30.
• MYSTERIUM sensor based camera may not be downgraded to firmware prior to Build 16.
• Non Build 31 formatted media may report as “INCOMPATIBLE”. If so, reformat to clear.
• Non-speed verified CF cards are limited to 2K record resolution.
• Image Magnify is available during preview, but not during according or playback.
• LOOK (.RLK) file format updated at Build 30, not compatible with Build 21 or earlier.
• GUI on HD Preview is limited to LOOKAROUND if both EVF and LCD ports are active.
• FLUT parameter remains independent on Slave camera when in Master / Slave mode.
• Audio parameters remain independent on Slave camera when in Master / Slave mode.
• Under GPI trigger, Slave camera will enter record within +/- 1 frame of Master.
• Using RECORD key, Slave camera will enter record within +/- 2 frames of Master.
• HD-SDI and HDMI are True Progressive, no support for 1080i or 1080 PsF formats.
• Selecting V Flip or H + V flip VIDEO mode will delay the HD-SDI output by 1 frame.
• Timecode in GUI is not frame accurate, always reference to HD-SDI or .R3D timecode.
• If using Master / Slave mode, ensure that both Master and Slave cameras are using identical size media and when formatting media, ensure that both the Master and Slave cameras have media attached.
• RECORD tally in HD-SDIHANC indicates “in record” earlier than the first frame of the recorded .R3D file, and stays enabled a few frames after the last frame of the recorded .R3D file.
• Monitor path outputs may experience a temporary disturbance when:
  • Enabling first / disabling last audio channel
  • Entering and exiting Image Magnify
• RED-EVF in SYNC refresh mode will experience a temporary video blanking when:
  • Exiting OPENGATE mode
  • Exiting MAGNIFY at 4K resolution
  • Changing Project RESOLUTION
  • Changing Varispeed frame rate
• Bomb-EVF in SYNC refresh mode will experience a temporary video blanking when:
  • Exiting MAGNIFY at 4K resolution
  • Changing Project RESOLUTION
  • Changing Varispeed frame rate

Copyright © 2004-2017 RED.COM, LLC. All rights reserved.