INTRODUCTION... 3 OVERVIEW... 4 DAILIES CREATION STEPS... 5 ADDITIONAL METADATA USING ALE ONE STEPALE RE-LINK ADDITIONAL RESOURCES...

Transcription

1

2 TABLE OF CONTENTS INTRODUCTION... 3 OVERVIEW... 4 DAILIES CREATION STEPS... 5 ADDITIONAL METADATA USING ALE ONE STEPALE RE-LINK ADDITIONAL RESOURCES APPENDIX... 17

3 INTRODUCTION This guide details the steps required to transcode RED R3D files - the native recording format of the RED ONE camera - through an HD post production process using Avid Media Composer v3.0.5 and later or Avid Symphony v3.0.5 and later. Avid DS Nitris 10.2 and later offers native R3D support and total conform via the AAF/AFE file interchange. For additional workflow information and tools visit: ROCKETCINE-X is available from: 3

4 OVERVIEW ROCKETCINE-X from the RED Ditigal Cinema Company combines the features of RED Alert and REDrushes into a single application while adding functionality such as support for syncing audio for double system workflows in an easy-to-use UI for the creation of dailies. When combined with the REDROCKET accelerator card, the dailies process becomes real time even when working in 4K and full debayer quality. This simplifies the dailies process by always working from the highest quality files shot into an offline proxy or a mastering Avid DNxHD format. The application is currently available for Mac OS X; a Windows version is planned for the future. The RED Digital Cinema Company also has released a beta version of REDCINE-X. While that application has AAF/MXF support for export, the application is currently designed for dailies viewing, and is not for file-based dailies creation. The figure below shows the basic steps for using ROCKETCINE-X with Avid editing systems. 4

5 DAILIES CREATION STEPS This guide describes the steps related to creating native Avid DNxHD media; it is not intended to describe the entire feature set of ROCKETCINE-X. Please refer to ROCKETCINE-X documentation for a full description of its functionality and feature set. 1. Launch ROCKETCINE-X application. 2. At bottom of screen, select Open Folder to add all R3D files from the shoot. ROCKETCINE-X will look into all subfolders as needed. 5

6 3. Select directory of R3D files. This will result in all files being loaded and displayed in the viewer: 4. Once clips are loaded, render presets can be created for the Avid DNxHD formats of your choice. Click the + button in the render section of the application. 6

7 5. In the settings window, select AAF/DNxHD and the correct data rate settings from the drop down menus. Other settings should be 1920 x 1080 (matches the Avid DNxHD format chosen). Select aspect ratio as desired by the production (fit width, etc,). 720p formats are not recommended at this time for and 24 frame formats because the proper timecode conversion is not being done. It is possible to use 720p formats for matching frame rates such as 25fps source to 720p/25. 7

8 Select Output Location/Filename for desired destination. Values in the Crop tab do not need to be changed. Audio tab can reference R3D files with embedded audio (single system) or external audio as found in double system audio workflows. Please refer to ROCKETCINE-X documentation on how this is used. When using external audio files, there will be no reference to audio filename or additional metadata should it be needed. It is recommended that users working with double system sound use the AutoSync function within Media Composer. Burn In tab is up to the user to define size, look and location as needed for the production itself. Once settings are complete, save out a name for future use: 1. Now the files in the clip list window are ready for batch processing. Select individual files for the transcode process, or just select all. 8

9 7. In the Render pane, select the Avid DNxHD preset created and click the Export Sel (selection) button to start the transcoding process. 8. Activating the batch process will prompt for the ALE filename and directory. Name the ALE as needed to identify later with the batch process itself. 9

10 9. Clicking the Batch tab in the clip list pane will display the progress of the transcode process. 10. Once complete, the resulting folder will contain a folder named AAF that contains the AAF files, and a folder named MXF that contains the native MXF wrapped Avid DNxHD files. In this example, the ALE file was also saved to this folder keeping all the related files in an easy to manage location. 10

11 The AAF and MXF folders contain their related files. 11. Depending on workflow, the folders and files will be sent to another system for editing to begin. If on the same system, copy the contents to the Avid MediaFiles folder. 12. Launch Media Composer and create a project matching the frame rate of the R3D files shot. Although not required, creating a 35mm, 4 perf project will allow re-syncing of audio to the ¼ frame level. This is commonly used in double system workflows to guarantee the tightest sync possible. 11

12 13. Once in the project, open the AAF folder created by ROCKETCINE-X. Select all and drag and drop into an open bin. The AAF file format automatically links to the MXF media found in the Avid MediaFile folder. 14. At this point, AutoSync can be used to sync audio from a double system audio workflow or editing can start right away. Clip names can be changed to more editor friendly or descriptive ones like 1/1 for Scene 1/Take 1, etc. Metadata available to editorial and post processes at this point are: Tape (16 character filename), Start and End timecode. For many productions, this may be enough. For workflows that need the additional metadata available via the ALE file the following steps can be performed. 12

13 ADDITIONAL METADATA USING ALE There are some workflows that will benefit from the additional metadata afforded via the ALE file exported from ROCKETCINE-X. This will include the edgecode, and filename in the shortened 8 character format favored by Final Cut Studio should that be part of the process. Avid s superior metadata management easily handles all the metadata available ensuring you can finish your project within the Media Composer or any other system downstream. The full description of metadata available is listed in the Appendix section of this document. The table reflects metadata created by ROCKETCINE-X which differs slightly from the ALE created by REDrushes. 1. After the AAF import, highlight all the clips in the bin (notice amount of metadata available before the merge). 2. Select Import from the file menu. Click on the Options button and select the Shot Log tab in the window and set the preferences to the last item as seen here (Merge events with known master clips). 13

14 3. Click OK and navigate to the ALE created by ROCKETCINE-X. 4. The result will be all the metadata from the ALE file now merged into the exiting clips. 14

15 ONE STEPALE RE-LINK If you want to bypass the two merge functions via the AAF then ALE process, it is possible to import the ALE file only to start the process after copying the MXF files to the Avid MediaFile folder. In this process, the clips created by the ALE import are offline until you do a Relink function. This method goes through the following steps: 1. Import ALE. Clips will be offline. 2. Select all clips in bin so they are highlighted 3. Go to the clip menu and select Relink. 4. Make sure the relink settings look like the following: 5. Clicking OK will relink all media in the bin ready for editing. 15

16 ADDITIONAL RESOURCES The technology and workflow described in this reference guide are new and evolving. Improvements will continue over time. Be sure to check back to for the latest information and tools for your Avid workflow. For ROCKETCINE-X downloads, FAQs, and additional support information, please visit the RED support page at 16

17 APPENDIX ROCKETCINE-X automates the creation of an ALE file as part of the batch export process.. This creates a streamlined workflow when the additional metadata is needed. ROCKETCINE-X will export all the metadata extracted from the R3D files allowing it to be preserved throughout the editorial process to final conform. Metadata from ROCKETCINE-X maps in the following way: Avid Example of Imported Data Comment Frame Rate 23.98, 24, 25, etc. This frame rate is added to the global heading of the ALE file. Frame rate is defined in Redline from R3D file. Name A001_C007_0802GX Name of original R3D file Tape A001_C007_0802GX Full 16 characters (including underscores) Camera A Derived from characters 1st of filename as per RED definition of filename. Camroll A001_C007_0802GX Added as additional metadata allowing flexibility in EDL generation from 4 characters (see Tape) to full 16 Labroll A001C007 Added as additional metadata in the 8 character format supported by Apple Final Cut Studio and some third party applications Clip 007 Derived from characters 7-9 of filename as per RED definition of filename. Start 11:30:53:05 Time of Day timecode at start of R3D file or ABS as labeled in RECINE X 17

18 Avid Example of Imported Data Comment End 11:31:09:09 Time of Day timecode at end of R3D file Original_Start 11:30:53:05 Redundancy of Start timecode value to preserve consolidation workflows Original_End 11:31:09:09 Redundancy of Start timecode value to preserve consolidation workflows Auxiliary TC1 01:00:38:14 Edgecode from R3D file Tracks V Identification of tracks from R3D file V A1A2A3A4 total tracks DPX A001_C007_0802GX Combination of filename as prefix and as exported by ROCKETCINE-X Shoot Date Shoot Date as defined within the R3D file metadata. Filename A001_C007_0802GX Name of file TimeStamp From R3D file FrameWidth 2048 From R3D file FrameHeight 1024 From R3D file ColorSpace 3 From R3D file/red ALERT 18

19 Avid Example of Imported Data Comment GammaSpace 1 From R3D file/ RED ALERT Kelvin From R3D file/ RED ALERT Tint From R3D file/ RED ALERT ISO Exposure 320 From R3D file/ RED ALERT Saturation From R3D file/ RED ALERT Contrast From R3D file/ RED ALERT Brightness From R3D file/ RED ALERT GainRed From R3D file/ RED ALERT GainGreen From R3D file/ RED ALERT GainBlue From R3D file/ RED ALERT Black X From R3D file/ RED ALERT Black Y From R3D file/ RED ALERT 19

20 Avid Example of Imported Data Comment Toe X From R3D file/ RED ALERT Toe Y From R3D file/ RED ALERT Mid X From R3D file/ RED ALERT Mid Y From R3D file/ RED ALERT Knee X From R3D file/ RED ALERT Knee Y From R3D file/ RED ALERT White X From R3D file/ RED ALERT White Y From R3D file/ RED ALERT UNC /Users/michael/Desktop/A008_080225/ A001_C007_ RDC/ A001_C007_080225_001.R3D UNC field in Media Composer is a live hyperlink. Control-Click in this field will take user to the directory containing the R3D file Avid Technology, Inc. All rights reserved. Product features, specifications, and system requirements are subject to change without notice. AutoSync, Avid, Avid DNxHD, the Avid logo, Media Composer, Nitris, and Symphony are either trademarks or registered trademarks of Avid Technology, Inc. in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners. 20