ALEXA Metadata White Paper SUP8

7/23/2019 ALEXA Metadata White Paper SUP8

1/29

Metadata in the ALEXA

For ALEXA SUP 8.0 DRAFT

Digital Workflow Solutions

May 16th

, 2013

W H I T E P A P E R


2/29

Metadata in the ALEXA White Paper Version 2.0 Page 2 of 29

Version History

Version Author Change Note

2012-01-20 Poetsch Create new document with new structure, add Extended Metadata Content table

2012-02-07 Poetsch Added DNxHD Metadata info

2012-11-26 Stangl Restructuring, added SUP 7.0 extensions

2013-05-16 Stangl Incorporated changes for ALEXA SUP 8.0

Table of Contents

! "#$%&'()$" ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ,

- %./.01. #&$.1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ,

, 020"/03/. "#4&%50$" +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ,

6 $.)7#")0/ '.$0"/1 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 8

"#$ %&'()*+,) ,+(-,.%&/############################################################################################################################################ 0

!"#"# $%& ( )*+ """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" ,

!"#"- .+/ $012 """""""""""""""""""""""""""""""""""""""""""" """"""""""""""""""""""""""""""""""""""""""""" """""""""""""""""""""""""""""""""""""""""""" """"""""""""""""""" 3

!"#"4 5607890:2 *2;B;C>1 """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" -,

!"-"? .6=0> """"""""""""""""""""""""""""""""""""""" """"""""""""""""""""""""""""""""""""""""""""" """""""""""""""""""""""""""""""""""""""""""" """"""""""""""""""""""""" -,

9 %.0'"#: 5.$0'0$0 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -;

4#$ ),,%*+5) +65,)(5########################################## ############################################# ############################################ ########## 17

4#1 89%(:5%*+ ;%


3/29


1 Introduction

The ARRI ALEXA provides metadata with its images. This additional information makes documentationeasier as the metadata is stored within the image files so it cannot get lost.This document reflects the support of metadata for all ALEXA cameras running SUP 8.0 or later.

2 Release Notes

The following table describes all metadata that have changed or that have been added with SUP 8.0. It alsodescribes known issues for certain metadata fields. For more information about single items, refer to theoverview table in Section 3, or to the output-specific sections below.

ID Name Note

ICI25 Look Saturation"LinearSaturation" was renamed to "Saturation" since the term does not apply correctly to CDLcompatible looks.

ICI31 CDL Mode New field added

CDI26 Storage Media Serial Number

1. MagazineSerialNumber was extended from 4 bytes (U32) to 8 bytes (U32[2]).For Codex Capture Drives, it is a globally unique number associated with the backplane in thedrive. The actual serial number label of the device is not stored electronically.2. QT and ALE files recoded on Codex Capture Drives have an invalid MagazineSerialNumber.Only the SxS card MagazineSerialNumber is correct in QT header and ALE file.

CDI28 SMPTE UMID SMPTE UMID byte order was changed from U32 [8] to U8 [32] as specifed in SMPTE 330.

CDI29 Camera Type Camera Type is always ALEXA for ARRIRAW files.

CDI31 Mirror Shutter Running Mirror Shutter Running is always 0/No in Raw and 1/Yes in ProRes, for every camera model.

CDI36 UUID ARRI_UUID was a string and is now a 16 byte binary value.

LDI02 Lens Focus Unit Focus unit for imperial has changed from "feet" to "inch".

LDI21 Lds Lag Type New field added

LDI22 Lds Lag ValueNew field addedNote: Lag of calibrated LDS values is automatically fixed when using AME (see Section 5.1)

CID04 Scene New user-settable field added

CID05 Take

Now settable by user.If not set manually, it is automatically filled with clip count (e.g. C001).In the SDI signal, the clip count is always filled in, even when a Take is manually entered.

CID09 Production Company New user-settable field added

CID14 Notes New user-settable field (Camera Operator) added

SID04 Sound Roll Sound Roll is not available in SDI signal.

3 Available Information

The following table shows which information is available as metadata, sorted by the different image outputpaths.

In the first column, the unique ID of each metadata is given. The second column states since which SUP therespective metadata is available.

The third column shows the character Dwhenever metadata is dynamic metadata, which means that thevalue may change from frame to frame. All other metadata is static metadataand carries the same value fora whole clip.

The fourth and fifth column give the name and description of the metadata.

The sixth column is mostly relevant to users of the ARRIRAW SDK and determines whether metadata isconsidered as Basicinformation that should be displayed to end users in any case, or might be hidden fromthe end user unless they wish to seeAllavailable information.

The last six columns give an overview about whether the respective metadata is available in Quicktime MOVfiles, MXF files, ALE files, Final Cut XML files, ARRIRAW files and files that have been captured via SDI.


4/29


More information on how the metadata is stored in the various output paths is given in the subsequentsections.

IDSinceSUP

Dy

namic

Name DescriptionViewin SDK

QT MX

F

AL

E

FC

PXML

RA

W

SD

I

Image Data Information

IDI02 6.1 Image Width

Total horizontal pixel count of the image area (e.g. includingoverscan and non-image pixels) that is stored in this file Basic

IDI03 6.1 Image HeightTotal vertical pixel count of the image area (e.g. includingoverscan and non-image pixels) that is stored in this file Basic

IDI06-1 7.0Active ImageWidth

Width of rectangle within the stored pixel data representingthe active image (e.g. framing selected during record) insensor photo sites. Basic

IDI06-2 7.0

Active Image

Height

Height of rectangle within the stored pixel data representingthe active image (e.g. framing selected during record) in

sensor photo sites. Basic

IDI06-3 6.1 Active Image Top

Top coordinate in Y of rectangle within the stored pixel datarepresenting the active image (e.g. framing selected duringrecord) in sensor photo sites. All

IDI06-4 6.1 Active Image Left

Left coordinate in X of rectangle within the stored pixel datarepresenting the active image (e.g. framing selected duringrecord) in sensor photo sites. All

Image Content Information

ICI02 6.1Color ProcessingVersion

Version of the color processing. Since SUP 4.0 we haveversion 4 All

ICI03 6.1 White BalanceValue of the white balance in Kelvin, calculated from the R,G and B factors Basic

ICI04 6.1 White Balance CC GreenTintFactor Basic

ICI05 6.1 WB Factor R Value of the white balance R factor All

ICI06 6.1 WB Factor G Value of the white balance G factor All

ICI07 6.1 WB Factor B Value of the white balance B factor All

ICI08 6.1WB Applied InCamera

Flag indicating whether the White Balance has been appliedto the data or not / 0 = was not applied, 1 = was applied Basic

ICI09 6.1Exposure Index

ASA Value of the exposure index in ASA rating Basic

ICI16 6.1Target ColorSpace

ID of the desired target color space / 0 = REC 709, 1 = ITUP3, 2 = ArriFilmColor Basic

ICI17 6.1 SharpnessValue for sharpening within a range from 100 to 300. (100 =no sharpening) Basic

ICI18 6.1 Aspect Ratio

Width to height pixel aspect ratio (for anamorphic lenses).Factor that has to be applied to get a visual correct aspectratio Basic

ICI19 6.1 Image Flip

Flag indicating whether the image is horizontally and/orvertically flipped or not / 0 = No flip, 1 = H flip, 2 = V flip, 3 =H+V flip Basic

ICI20 6.1 LookString for the ARRI Look File file name, up to 32 letters (to beapplied after White Balance and Color Matrix) Basic

ICI21 6.1 Look LUT Mode

Type of the Look LUT data included in this file /ARRI_LOOK_LUT_NOLUT = file contains no Look LUT,ARRI_LOOK_LUT_MONO = file contains a monochromaticLook LUT All

ICI22 6.1 Look LUT OffsetOffset to the Look Lut data in bytes from start of file (bedefined from recorder) All


5/29


IDSinceSUP

Dynamic


QT

MXF

ALE

FCPXML

RAW

SDI

ICI23 6.1 Look LUT SizeSize of the Look LUT data in bytes (be defined fromrecorder) All

ICI24 6.1Look LUT CRCChecksum

CRC of the complete Look LUT (including all color channels)(be defined from recorder) All

ICI25 8.0 Look Saturation

Saturation is applied. Semantics: in linear RGB or LogC RGBand can be ARRI CDL or ASC CDL conform / 0.0 =monochrome, 1.0 = default, larger values increasesaturation. Basic

ICI26-1-2-3 7.0 CDL Slope RGB ASC conform Color Decision list parameters for slope Basic

1

ICI27-1-2-3 7.0 CDL Offset RGB ASC conform Color Decision list parameters for offset Basic

1

ICI28-1-

2-3 7.0 CDL Power RGB ASC conform Color Decision list parameters for power Basic 1

ICI29-1-2-3 7.0 Printer Lights RGB Printerlights correction Basic

1

ICI31 8.0 CDL Mode

Describes which CDL Saturation is used (ARRI LOOK CDLor ASC CDL mode) and in which colorspace the CDL isapplied0 = ARRI_LOOK_NONE (No Look active),1 = ARRI_LOOK_ALEXA_VIDEO (in-camera ARRI LookFile),2 = ARRI_LOOK_CDL_VIDEO (ASC CDL-conformparameters applied to REC709 image, parameters providedvia external CDL server),3 = ARRI_LOOK_CDL_LOGC (ASC CDL-conformparameters applied to LogC image, parameters provided viaexternal CDL server) Basic

Camera Device Information

CDI02 6.1 Camera Type ID

Number defining the type of the camera(e.g. ARRI_CAM_TYPE_D21 or ARRI_CAM_TYPE_ALEXA)This must match with the string specified hereunder inCameraType Basic

CDI04 6.1Camera SUPVersion Firmware version as a number (= software revision) Basic

CDI05 6.1Camera SerialNumber Camera serial number Basic

CDI06 6.1 Camera IDCameraID Prefix (L or R, R is default) plus camera serialnumber translated to Base36. Basic

CDI07 6.1 Camera Index User defined camera index A-Z Basic

CDI08-1 6.1 DSystem ImageCreation Date Image creation date and time. Basic

CDI08-2 6.1 DSystem ImageCreation Time Image creation date and time. Basic

CDI10 6.1 D Exposure Time Exposure time in microseconds (10^-6 seconds) Basic

CDI11 6.1 D Shutter AngleShutter angle in degree * 1000. Shutter Angle =(ExposureTime * SensorFps)/1E9 * 360.0 Basic

CDI15 6.1 D Sensor FPS Sensor speed for this image in FPS * 1000 Basic

CDI16 6.1 Project FPS Playback/post framerate in FPS * 1000. Only sync sound Basic

1These values are not stored separately, but the complete ARRI Look File (in XML format) is stored in the Quicktime header. For more

information about ARRI Look Files, refer to the ARRI Look Files White Paper athttp://www.arri.com/camera/digital_cameras/downloads.html.


6/29


IDSinceSUP

Dynamic


QT

MXF

ALE

FCPXML

RAW

SDI

FPS allowed.

CDI17-1 6.1 D Master TC Time code as HH:MM:SS:FF (BCD: 1 digit -> 4 bits) Basic

CDI17-2 6.1 DMaster TC FrameCount

Time code translated to frame counter using the time baseTimeBase All

CDI17-3 6.1Master TC TimeBase Time base in FPS * 1000 Basic

CDI17-4 6.1Master TC DropFrame

Flag for Drop Frame TC mode. 0 = no drop frame TC, 1 =drop frame TC All

CDI17-5 6.1Master TC UserInfo SMPTE 12M user bits All

CDI26 8.0Storage MediaSerial Number Storage media serial number. Basic

CDI28 8.0 SMPTE UMID SMPTE 330M UMID Basic

CDI29 6.1 Camera Type Camera type, 8 letters Basic

CDI30 6.1 Recorder TypeRecorder name, or storage media name (ADM/SxS), as a 32letter string Basic

CDI31 6.1Mirror ShutterRunning

Flag telling if the mirror shutter of the camera was running / 0= No, 1 = Yes Basic

CDI32 6.1 D VariFlag for variframe indication: valid image or duplicated imagethat can be discarded / 0 = Valid Image, 1 = Duplicate Image All

CDI36 8.0 UUIDUUID created by camera for each clip. Same UUID is storedin Quicktimes recorded on camera SxS cards Basic

CDI37 7.0

Camera SUP

Name Name of installed camera software update package Basic

Lens Data Information

LDI02 6.1 Lens Focus Unit Lens Focus unit flag / 0 = Inch, 1 = Meter Basic

LDI03 6.1 DLens FocusDistance

Distance in the specified focus unit (1/1000 inch or mm).There are two special values:0: Focus distance invalid (or not available yet)

-1: Focus distance infinite Basic

LDI04 6.1 D Lens Focal Length Focal length in 1/1000 mm or 0 if no value is available Basic

LDI05 6.1Lens SerialNumber Lens serial number Basic

LDI06 6.1 D Lens Iris

Aperture in units of 1/1000 in linear range (log of optical

aperture indicated on lens ring) Basic

LDI07-1 6.1 ND Filter TypeType of ND filter used / 0 = No Filter, 1 = ALEXA Studio NDType 1 Basic

LDI07-2 6.1 ND Filter Density Optical density of ND filter * 1000 (0 - 65) Basic

LDI11 6.1 Lens Model Lens model as a 32 letter string Basic

LDI12-1 7.0 DRawEncoderFocusRawLds Raw LDS encoder value of focus axis All

LDI12-2 7.0 DRawEncoderFocusRawMotor Raw motor encoder value of focus axis All

LDI13-1 7.0 DRawEncoderFocalRawLds Raw LDS encoder value of focal length All

LDI13-2 7.0 DRawEncoderFocalRawMotor Raw motor encoder value of focal length All


7/29


IDSinceSUP

Dynamic


QT

MXF

ALE

FCPXML

RAW

SDI

LDI14-1 7.0 DRawEncoderIrisRawLds Raw LDS encoder value of iris All

LDI14-2 7.0 DRawEncoderIrisRawMotor Raw motor encoder value of iris All

LDI15-1 7.0EncoderLimFocusLdsMin Lower limit of LDS encoder focus All

LDI15-2 7.0EncoderLimFocusLdsMax Upper limit of LDS encoder focus All

LDI16-1 7.0EncoderLimFocalLdsMin Lower limit of LDS encoder focal length All

LDI16-2 7.0EncoderLimFocalLdsMax Upper limit of LDS encoder focal length All

LDI17-1 7.0EncoderLimIrisLdsMin Lower limit of LDS encoder iris All

LDI17-2 7.0EncoderLimIrisLdsMax Upper limit of LDS encoder iris All

LDI18-1 7.0EncoderLimFocusMotorMin Lower limit of motor encoder focus All

LDI18-2 7.0EncoderLimFocusMotorMax Upper limit of motor encoder focus All

LDI19-1 7.0EncoderLimFocalMotorMin Lower limit of motor encoder focal length All

LDI19-2 7.0EncoderLimFocalMotorMax Upper limit of motor encoder focal length All

LDI20-1 7.0 EncoderLimIrisMotorMin Lower limit of motor encoder iris All

LDI20-2 7.0EncoderLimIrisMotorMax Upper limit of motor encoder iris All

LDI21 8.0 D Lds Lag TypeSpecifies the type of lag that is inherent to calibrated LDSvalues / 0 = no lag, 1 = constant lag All

LDI22 8.0 D Lds Lag Value

Specifies the lag of the calibrated LDS valuesFocusDistance, FocalLength and Aperature in frames. Avalue of +1 means the values have one frame delay (as it isin Alexa FW since 7.0). Thus the correct calibrated LDSvalues are found in the next frame. All

VFX Information

VFX08 6.1 D Camera Tilt

Camera tilt angle in degrees*10 (interpret 16 LSBs as signed

short) Basic

VFX09 6.1 D Camera RollCamera roll angle in degrees*10, positive rotating clockwise(interpret 16 LSBs as signed short) Basic

VFX10 6.1Master SlaveSetup Info

Flag for indicating if the camera is master or slave in a multi-camera setup / 0 = independent, 1 = master, 2 = slave All

VFX11 6.1 3D Eye InfoImage channel information / 0 = single, 1 = Left Eye, 2 =Right Eye All

Clip Information Data

CID02 6.1 Circle Take Flag for marking good takes / 0 = No, 1 = Yes Basic

CID03 6.1 Reel Reel name as an 8 letter string Basic

CID04 8.0 Scene Scene name as a 16 letter string Basic

CID05 8.0 Take Take number/name as an 8 letter string Basic


8/29


IDSinceSUP

Dynamic


QT

MXF

ALE

FCPXML

RAW

SDI

CID06 6.1 Director Director name as a 32 letter string Basic

CID07 6.1 Cinematographer Cinematographer name as a 32 letter string Basic

CID08 6.1 Production Production name as a 32 letter string Basic

CID09 8.0ProductionCompany Production Company name as a 32 letter string Basic

CID10 6.1 Notes Additional production information about the clip (Location ) Basic

CID11 6.1 Notes Additional production information about the clip (User Info 1) Basic

CID12 6.1 Notes Additional production information about the clip (User Info 2) Basic

CID14 8.0 Notes Additional production information about the clip (Operator) Basic

CID13 7.0 Camera ClipName Clip name as created by camera Basic

Sound Information Data

SID04 6.1 Sound Roll Sound roll name as a 8 letter string Basic

4 Technical Details

Metadata is implemented in different ways for the different image output options. The following sectionexplains the technical details for all options.

In-camera recording4.1When recording files in-camera, metadata is stored in several different ways: Final Cut Pro 7 XML file, AvidLog Exchange (ALE) file, QuickTime metadata atom, MXF metadata XML and the ARRI Digital MetaData(ADMD) atom.

4.1.1 FCP 7 XML

This XML file is stored in the reel folder on the media. It is compatible with Final Cut Pro (6 or 7) and can beused to batch import the whole set of clips into Final Cut Pro directly from the media.

The XML contains the following set of metadata:

ID Content Tag Prefix

CDI15 Sensor Fps Mastercomment1 SensorFps:

CDI11 Shutter Angle Mastercomment1 ShutterAngle:

ICI03 White Balance Mastercomment1 WhiteBalance:

ICI04 White Balance CC Mastercomment1 CCShift:

ICI09 Exposure Index ASA Mastercomment1, Clipcommentb ExposureIndexAsa

ICI16 Gamma (SxS) Mastercomment1, Clipcommenta ColorGammaSxS:

CDI29 Camera Type Mastercomment2 Camera:

CDI06 Camera ID Mastercomment2 CamID:

CDI05 Camera Serial Number Mastercomment2 SerialNumber:

CDI11 Shutter Angle Mastercomment1 ShutterAngle


9/29


ID Content Tag Prefix

CDI17-1 Master TC Time Code Timecode

CDI17-3 Master TC Time Base Rate>Timebase

CDI37 Camera SUP Name Mastercomment2 SupVersion:

CDI26 SxS Serial Number Mastercomment2 SxS-SerialNumber:

CDI08-1 Date Mastercomment2 Date:

CDI08-2 Time Mastercomment2 Time:

CID06 Director Mastercomment3 Director:

CID07 Cinematographer Mastercomment3 Cinematographer:

CID10 Location Mastercomment3 Location:

CID08 Production Mastercomment3 Production:

CID11 User Info 1 Mastercomment3 User1:

CID12 User Info 2 Mastercomment3 User2:

CDI17 Project Fps Timebase, Ntsc

CID02 Circle Take Logginginfo>Good

CID13 Camera Clip Name Masterclipid

CDI36 UUID Metadata>Value

SID04 Sound Roll Sound

4.1.2 ALE File

The Avid Log Exchange (ALE) file is a file that can be used to import camera specific metadata into the AvidMedia Composer. It is stored in the reel folder together with the media clips and the FCP XML file.

For details on the ALE structure, please refer to the AVID documentation.

Most columns used by the ALEXA are custom columns matched to the specific camera metadata. The ALEfile also contains some metadata that is only available in the ALE file. Information about this data is listed atthe end of the table.

ID NameALE ColumnName

ALE ColumnType ALE List sample value

IDI02 Image Width FrameWidth Custom 2048

IDI03 Image Height FrameHeight Custom 1152

ICI03 White Balance White_Balance Custom 5600

ICI04 White Balance CC Cc_shift Custom +0

ICI09 Exposure Index ASA Exposure_Index Custom 800

ICI16 Target Color Space Sxs_Gamma Custom LOG-C

ICI20 Look Look_Name Custom tabacco_LCC

CDI02 Camera Type ID Camera_Model Custom ARRI ALEXA PLUS

CDI05 Camera Serial Number Camera_SN Custom 4011

CDI06 Camera ID Camera_ID Custom R33F

CDI07 Camera Index Camera_Index Custom A

CDI08-1 System Image Creation Date Date_Camera Custom 20120923


10/29




CDI08-2System Image CreationTime Time_Camera

Custom10h09m28s

CDI11 Shutter Angle Shutter_Angle Custom 1728

CDI15 Sensor FPS Sensor_Fps Custom 24000

CDI16 Project FPS Project_Fps Custom 24000

CDI17-1 Master TC Start Standard 01:00:00:00

CDI17-3 Master TC Time Base FPS Standard 24

CDI26Storage Media SerialNumber Sxs_SN

Custom9E+14

CDI28 SMPTE UMID UMIDCustom

0x060A2B340101010501010F001300000084FB584E00004000B10F66A300000000

CDI29 Camera Type Camera_Model Custom ARRI ALEXA PLUS

CDI36 UUID UUID Custom 84fb584e-0000-4000-b10f-66a300000000

CDI37 Camera SUP Name Sup_Version Custom 7.0beta:20640

LDI02 Lens Focus Unit Focus_Unit_Lens Custom Metric

LDI05 Lens Serial Number Lens_SN Custom 13135

LDI11 Lens Model Lens_Type Custom Fujinon Alura AZ30-80 T2.8

LDI15-1 EncoderLimFocusLdsMin Focus_Abs_Min Custom 0

LDI15-2 EncoderLimFocusLdsMax Focus_Abs_Max Custom 0

LDI16-1 EncoderLimFocalLdsMin Zoom_Abs_Min Custom 0

LDI16-2 EncoderLimFocalLdsMax Zoom_Abs_Max Custom 0

LDI17-1 EncoderLimIrisLdsMin Iris_Abs_Min Custom 0

LDI17-2 EncoderLimIrisLdsMax Iris_Abs_Max Custom 0

LDI18-1 EncoderLimFocusMotorMin Focus_Mot_Min Custom 0

LDI18-2 EncoderLimFocusMotorMax Focus_Mot_Max Custom 0

LDI19-1 EncoderLimFocalMotorMin Zoom_Mot_Min Custom 0

LDI19-2 EncoderLimFocalMotorMax Zoom_Mot_Max Custom 0

LDI20-1 EncoderLimIrisMotorMin Iris_Mot_Min Custom 0

LDI20-2 EncoderLimIrisMotorMax Iris_Mot_Max Custom 0

VFX10 Master Slave Setup Info Master_Slave Custom OFF

VFX11 3D Eye Info Eye_Index Custom SINGLE

CID03 Reel Reel_Name Custom A001R33F

CID04 Scene Scene_Name Custom 220

CID05 Take Take_Name Custom 10

CID06 Director Director Custom John Doe

CID07 Cinematographer Cinematographer Custom Jane Roe

CID08 Production Production Custom YX FILM PROD

CID10 Notes Location Custom Munich


11/29




CID11 Notes User_Info1 Custom Filter ND GRAD .6

CID12 Notes User_Info2 Custom Second unit

CID13 Camera Clip Name Name Custom A001C001_YYMMDD_R33F

SID04 Sound Roll Soundroll Standard DAY001

Name of the file Source File Standard A001C001_YYMMDD_R33F.mxf

Clip counter Clip Custom 1

Duration Duration Standard 00:00:02:03

Tracks Tracks Standard VA1A2

End timecode End Standard 01:00:02:03

Codec Original_Video Custom DNxHD 220x (HD1080p)

Audio format Audio Format Standard WAVE

Audio SR Audio SR Standard 48000

Audio Bit Audio Bit Standard 24

Destructive Look Application Look_Burned_In Custom No

4.1.3 QuickTime Metadata Atom

In each QuickTime file, a set of static metadata is stored in the QuickTime metadata atom. The metadataatom contains the following set of metadata:

ID Name QT Header key Example

ICI03 White Balance com.arri.camera.WhiteBalanceKelvin 5600

ICI04 White Balance CC com.arri.camera.WhiteBalanceTintCc 0

ICI09 Exposure Index ASA com.arri.camera.ExposureIndexAsa 800

ICI16 Target Color Space com.arri.camera.ColorGammaSxS LogC

ICI20 Look com.arri.camera.LookFileActive tabacco_LCC

ICI26-1-2-3 CDL Slope RGB com.arri.camera.LookFileXml

ICI27-1-2-3 CDL Offset RGB com.arri.camera.LookFileXml

ICI28-1-2-3 CDL Power RGB com.arri.camera.LookFileXml

ICI29-1-2-3 Printer Lights RGB com.arri.camera.LookFileXml

CDI05 Camera Serial Number com.arri.camera.CameraSerialNumber 4011

CDI06 Camera ID com.arri.camera.CameraId R33F

CDI07 Camera Index com.arri.camera.CameraIndex A

CDI16 Project FPS com.arri.camera.ProjectFps 24000

CDI17-3 Master TC Time Base QT native metadata field 24

CDI17-4 Master TC Drop Frame QT native metadata field no

CDI26 Storage Media Serial Number com.arri.camera.SxsSerialNumber 900000000000206

CDI29 Camera Type com.arri.camera.CameraModel ARRI ALEXA PLUS

CDI36 UUID com.apple.finalcutstudio.media.uuid 84fb584e-0000-4000-

b10f-66a300000000


12/29


ID Name QT Header key Example

CDI37 Camera SUP Name com.arri.camera.SupVersion 7.0beta:20640

LDI02 Lens Focus Unit com.arri.camera.UnitPreference Metric

LDI05 Lens Serial Number com.arri.camera.LensSerialNumber 13135

LDI07-1 ND Filter Type com.arri.camera.NdFilterType 1

LDI07-2 ND Filter Density com.arri.camera.NdFilterDensity 1400

LDI11 Lens Model com.arri.camera.LensType Fujinon Alura AZ30-80 T2.8

LDI15-1 EncoderLimFocusLdsMin com.arri.camera.LdsEncFocusMin 629

LDI15-2 EncoderLimFocusLdsMax com.arri.camera.LdsEncFocusMax 10351

LDI16-1 EncoderLimFocalLdsMin com.arri.camera.LdsEncZoomMin 1679

LDI16-2 EncoderLimFocalLdsMax com.arri.camera.LdsEncZoomMax 5510

LDI17-1 EncoderLimIrisLdsMin com.arri.camera.LdsEncIrisMin 2142

LDI17-2 EncoderLimIrisLdsMax com.arri.camera.LdsEncIrisMax 3418

LDI18-1 EncoderLimFocusMotorMin com.arri.camera.ClmEncFocusMin 105

LDI18-2 EncoderLimFocusMotorMax com.arri.camera.ClmEncFocusMax 20083

LDI19-1 EncoderLimFocalMotorMin com.arri.camera.ClmEncZoomMin 105

LDI19-2 EncoderLimFocalMotorMax com.arri.camera.ClmEncZoomMax 6885

LDI20-1 EncoderLimIrisMotorMin com.arri.camera.ClmEncIrisMin 105

LDI20-2 EncoderLimIrisMotorMax com.arri.camera.ClmEncIrisMax 3796

VFX10 Master Slave Setup Info com.arri.camera.MasterSlave OFF

VFX11 3D Eye Info com.arri.camera.EyeIndex SINGLE

CID03 Reel com.arri.camera.ReelName A001R33F

CID04 Scene com.arri.camera.SceneName 220

CID05 Take com.arri.camera.TakeName 10

CID06 Director com.arri.camera.ProductionInfoDirector John Doe

CID07 Cinematographer com.arri.camera.ProductionInfoCinematographer Jane Roe

CID08 Production com.arri.camera.ProductionInfoProduction XY FILM PROD

CID10 Notes com.arri.camera.ProductionInfoLocation Munich

CID11 Notes com.arri.camera.ProductionInfoUser1 Filter ND GRAD .6

CID12 Notes com.arri.camera.ProductionInfoUser2 Second unit

CID13 Camera Clip Name com.arri.camera.CameraClipName A001C001_YYMMDD_R33F

SID04 Sound Roll com.arri.camera.SoundReel DAY001

Dynamic Metadata Version com.arri.camera.DyamicMetadataVersion 3

Destructive Look Application com.arri.camera.LookFileBurnedIn No

4.1.4 MXF Metadata XML

ARRI DNxHD conforms to SMPTE 379M-2004 "MXF Generic Container" including timecode, picture, sound

and metadata, video conforms to SMPTE 2019-4-2008 "Mapping VC-3 Coding Units into the MXF GenericContainer".


13/29


The camera specific static metadata inside the MXF file is stored as an XML file. It contains the same fieldsas the QuickTime metadata atom and the ALE file, except for those that are generated from the file itself andare not camera specific metadata.

The XML tags are equivalent to the ALE column names. This metadata set is imported into the Avid MediaComposer automatically by the ARRI ALEXA AMA volume plugin.

The key of the XML inside the MXF file is: 06.0e.2b.34.01.01.01.05.03.01.02.20.01.00.00.00ID Name MXF Header key

ICI03 White Balance

ICI09 Exposure Index ASA

ICI16 Target Color Space

ICI20 Look

CDI02 Camera Type ID

CDI05 Camera Serial Number

CDI06 Camera ID

CDI07 Camera Index

CDI16 Project FPS

CDI17-3 Master TC Time Base MXF native metadata field

CDI26Storage Media SerialNumber

CDI29 Camera Type

CDI36 UUID

CDI37 Camera SUP Name

LDI02 Lens Focus Unit

LDI05 Lens Serial Number

LDI07-1 ND Filter Type

LDI07-2 ND Filter Density

LDI11 Lens Model

LDI15-1 EncoderLimFocusLdsMin

LDI15-2 EncoderLimFocusLdsMax

LDI16-1 EncoderLimFocalLdsMin

LDI16-2 EncoderLimFocalLdsMax

LDI17-1 EncoderLimIrisLdsMin

LDI17-2 EncoderLimIrisLdsMax


14/29


ID Name MXF Header key

VFX10 Master Slave Setup Info

VFX11 3D Eye Info

CID03 Reel

CID04 Scene

CID05 Take

CID06 Director

CID07 Cinematographer

CID08 Production

CID10 Notes

CID11 Notes

CID12 Notes

CID13 Camera Clip Name

SID04 Sound Roll

Dynamic Metadata Version

Destructive Look Application

Note: Custom column names appear as Start case inside Media Composer (e.g. Date_Camera)

4.1.5 Dynamic Metadata in Proprietary ARRI Atom

For dynamic metadata, a block of 256 bytes is stored for every image in both QuickTime and MXF files. Inthe QuickTime file, this atom is labeled admd (ARRI Digital MetaData) and contains 256 bytes of binarydata.

In the MXF files, it is stored with each frame as a KLV structure with a total size of 303 bytes. The key is:06.0e.2b.34.02.43.01.01.0d.01.03.01.04.01.03.02

As the layout of the dynamic metadata might change over time, both Quicktime and MXF contain a staticmetadata field com.arri.camera.DynamicMetadataVersionthat determines the layout version of the dynamicmetadata.

The current version 3is as follows:

ID Offset(Bytes)

Size(Bytes)

Content Info

0 4 reserved

4 4 LTC Coded as:hhmmssff (4 bit=1 intdigit)

CDI17-5 8 4 User Bits Coded as:

hhmmssff (4 bit=1 hexdigit)

12 4 Rec Run TC start@0 Coded as:

hhmmssff (4 bit=1 intdigit)

16 4 Rec Run TC start @ offset Coded as:

hhmmssff (4 bit=1 intdigit)

20 4 reserved n/a


15/29


ID Offset(Bytes)

Size(Bytes)

Content Info

24 4 Sensor fps (fps*1000) Coded as:

units of 1/1000 fps

28 4 Shutter angle (angle*1000) Coded as:

units of 1/10

CDI08-1 64 4 ArriFileHeaderV3.CameraDeviceInformation.SysImageCreationTime.Date n/a

CDI08-2 68 4 ArriFileHeaderV3.CameraDeviceInformation.SysImageCreationTime.Time n/a

CDI09-1 72 4 ArriFileHeaderV3.CameraDeviceInformation.UserDate.Date n/a

CDI09-2 76 4 ArriFileHeaderV3.CameraDeviceInformation.UserDate.Time n/a

CDI10 80 4 ArriFileHeaderV3.CameraDeviceInformation.ExposureTime Coded as:

units of 1 ms

CDI11 84 4 ArriFileHeaderV3.CameraDeviceInformation.ShutterAngle Coded as:

units of 1/10

CDI15 96 4 ArriFileHeaderV3.CameraDeviceInformation.SensorFps Coded as:

units of 1/1000 fps

CDI17-1 100 4 ArriFileHeaderV3.CameraDeviceInformation.Master_TC.TimeCode Coded as:

hhmmssff (4 bit=1digit)

CDI17-2 104 4 ArriFileHeaderV3.CameraDeviceInformation.Master_TC.FrameCounter Coded as:

Int32 translation of TC

LDI03 164 4 ArriFileHeaderV3.LensDataInformation.FocusDistance ALEXA PLUS only

Coded as:

units of mm forFocusUnit=Metric

units of 1/1000 inchforFocusUnit=Imperial

Special values:

0: invalid/ no value

-1: focus distanceinfinite

LDI04 168 4 ArriFileHeaderV3.LensDataInformation.FocalLength ALEXA PLUS only

Coded as:

Units of m

Special value:

0: Invalid/ no value

LDI06 172 4 ArriFileHeaderV3.LensDataInformation.Aperture ALEXA PLUS only

Coded as:

units of 1/1000 lineariris**

Special values:

-3: nearly close

-2: closed

-1: Invalid/ no value

LDI12-1 176 2 ArriFileHeaderV3.LensDataInformation.RawEncoderFocus.EncoderValueRawLds

LDI12-2 178 2 ArriFileHeaderV3.LensDataInformation.RawEncoderFocus.EncoderValueRawMotor

LDI13-1 180 2 ArriFileHeaderV3.LensDataInformation.RawEncoderFocalLength.EncoderValueRawLds


16/29


ID Offset(Bytes)

Size(Bytes)

Content Info

LDI13-2 182 2 ArriFileHeaderV3.LensDataInformation.RawEncoderFocalLength.EncoderValueRawMotor

LDI14-1 184 2 ArriFileHeaderV3.LensDataInformation.RawEncoderAperture.

EncoderValueRawLds

LDI14-2 186 2 ArriFileHeaderV3.LensDataInformation.RawEncoderAperture.EncoderValueRawMotor

LDI21 188 1 ArriFileHeaderV3.LensDataInformation.LdsLagType

LDI22 189 1 ArriFileHeaderV3.LensDataInformation.LdsLagValue

VFX08 224 4 ArriFileHeaderV3.VfxInformation.Tilt ALEXA PLUS only

Coded as:

units of 1/10 degree

VFX09 228 4 ArriFileHeaderV3.VfxInformation.Roll ALEXA PLUS only

Coded as:

units of 1/10 degree

How to calculate regular Iris values from linear iris values:

nt16 n = (LinearIris + 50) / 1000;

// now n equals the index + 1 of the correct T-stop without fraction (because n is an integer

value)

// +50 is just because of rounding

n -= 1;

// subtract an offset of -1 to get the correct index

double FullAperture = exp2((double)n / 2);

// now calc 2^(n/2). n/2 has to be calculated float, result FullAperature is also floating point

To get the [1/10] of Aperture Stop out of the fraction do the following:

int16 FractionAperture = (LinearIris + 50) % 1000; // get the fraction

int16 ApertureTenth = FractionAperture / 100; // get the Aperture Tenth

While the above code is mathematically correct, it does not match the rounding conventions established infilm and photography for centuries. A tabled approach prints the more familiar values:

void printApertureValue(U32 apertureValue)

{

// Standard full-stop f-number scale

// (conventional rounding of sqrt(2.0^N) N=-1,0,1,2,...,16)

double fNumberScale[18] = {0.7,1.0,1.4,2,2.8,4,5.6,8,11,16,22,32,45,64,90,128,180,256};

int linearIris = apertureValue + 50; // + 50 for rounding

int fullApertureIdx = linearIris / 1000;

int fractionAperture = linearIris % 1000;

int apertureTenth = fractionAperture / 100;

if(0


17/29


{

printf("%.1f + %d/10\n", fNumberScale[fullApertureIdx], apertureTenth);

}

}

else

{

printf("out of bounds\n");

}

}

4.1.6 ARRIRAW Files

When recording ARRIRAW to a Codex Capture Drive with the Extended Recording module, images andmetadata are stored in a Virtual File System on the Capture Drive. Upon offloading, the Codex softwarecreates ARRIRAW files, which contain both image content and metadata. For more information about

ARRIRAW workflows, please refer to the ALEXA XR Module Workflows White Paper, available athttp://www.arri.com/camera/digital_cameras/downloads.html.

For proper metadata handling during offloading, Codex software version 2013.r1.2501 or later needs to beused.

The .ari file format for ARRIRAW files stores metadata in the header of the file. The so-called V3-header hasa size of 4 KB. Details on the header fields and how it shall be represented by software is embedded into thefile ArriFileV3.h, which can be found in the ARRI Partner Program ARRIRAW section.

SDI4.2

Different types of metadata are embedded into the HD-SDI. Metadata refers to all data besides imagecontent. This data is located in the HANC and VANC space of the HD-SDI signal. The following table givesan overview of the insert positions in the HD-SDI.

Line Position Stream Link P / Psf Content

Line 9 (571) HANC after EAV Y A P + Psf Audio Control

Line 9 (571) HANC after Audio Y A + B P + Psf HD-SDI Record Start/Stop

Line 9 (571) HANC after Start/Stop C A P + Psf Timecode ATC_VITC (incl. Vari-Frame)

All Lines

but not 8 (570)

HANC Y A + B P + Psf Audio Data

Line 10 (572) HANC after EAV Y A + B P + Psf Payload ID

Line 10 {572} HANC after Payload ID Y A P + Psf Timecode ATC_LTC (incl. Vari-Frame)

Line 9 {571} VANC Y A P + Psf Extended Metadata 4K

Line 10 {572} VANC Y A P + Psf Extended Metadata 4K, cd -1-

Line 11 {573} VANC Y A P + Psf Extended Metadata 4K, cd -2-

Line 13 {575} VANC Y A P + Psf Extended Metadata LUT

Line 14 {576} VANC Y A P + Psf Extended Metadata LUT, cd -1-



Remarks:

Line numbers with an ( )-addition, e.g. (571), indicate that in all cases of Psf-transport (not P-transport) asecond insert shall take place in the second field in the given line (offset is 562).

Line numbers with an { }-addition, e.g. {572}, indicate that in cases of Psf-transport where the first andsecond field carry different sensor frames (e.g. Dual Link 60p) a second insert shall take place in the secondfield in the given line, otherwise not.

The presence of some items is dependent on user settings. If an item is not available the insert position ofthe remaining items is shifted towards EAV. There are no gaps between different items in HANC space.

For some external recording devices (e.g. Sony SRW-1), the line numbers for the Extended Metadata(default 9-11, 13-16 in VANC space) can be changed by the user. Preferably the recording device is set tothe default values given here. E.g. for Sony SRW-1 via: and / Others / Meta Data / Data

1, 2, 3 = 9, 10, 11.


18/29


4.2.1 Extended Metadata

Extended metadata is camera specific information, which is embedded into the HD-SDI as ANC packets.It has the same length and structure as the ArriFileV3 header, split into several packets.

KLV Encoding of the Metadata Block

The ARRI metadata block is wrapped into a KLV structure according to SMPTE 336M-2007.

Key Length of Value Value

Key is a 16 byte SMPTE Universal Label (UL) that allows identifying data.All Extended Metadata are registered under a class 14 node as ARRI Metadata.

The key is: 06 0E 2B 34 02 05 01 0D 0E 17 00 00 00 11 01 01 (hex)

Length ofValue

is a 4 byte field that gives the byte length of Value (BER Coding)Length of Value is 4096 (dec) and represents the length of the ARRI Metadata block. The coded value is: 83 00 1000 (hex)

Value is the payload.It represents the ARRI Metadata block consisting of 4096 bytes.It is defined in the document ArriFileV3.h.

KLV Encoding of a LUT

Key The key is: 06 0E 2B 34 02 05 01 0D 0E 17 00 00 00 A1 01 01 (hex)

Length ofValue

for a 12 bit LUT is 6144 (dec).(4096 entries each 12 bit wide and packed without gaps)The coded value is: 83 00 18 00 (hex)

Value is the LUT in binary format. It is packed in a byte array as follows:E0/11 is the MSB of the first element, E4095/0 is the LSB of the last element; the relation o(i) for even and odd i isas follows:

LUT index i Byte offset o Byte content

0 0 E0/11 _ _ _ _ _ _ E0/4

0, 1 1 E0/3 _ _ E0/0, E1/11_ _ E1/8

1 2 E1/7 _ _ _ _ _ _ E1/02 3 E2/11 _ _ _ _ _ _ E2/4

2, 3 4 E2/3 _ _ E2/0, E3/11 _ _E3/8

! ! !

4095 6143 E4095/7_ _ _ _ _ _ E4095/0

The LUT is referenced by the accompanying Metadata block (see before).

KLV Key Structure

The 16 byte Key (K1.. K16, left to right) has a structure according SMPTE 336M-2007.

K1..K4 06 0E 2B 34 SMPTE

K5..K7 02 05 01 Data structure = Defined Length Pack (4K Block and LUT)

K8..K10 0D 0E 17 SMPTE definition for ARRI

K11..K16 ARRI

K11..K13 00 00 00 Reserved for future extension

K14 / K15 Main-category / Sub-category of ARRI Metadata

11 / 01 General Metadata / Universal 4K Metadata Block

A1 / 01 Look and LUT Metadata / Tonemap LUT

K16 01 Version of the ARRI Metadata definition. Incremented only if no more downwardscompatible.

ANC Packet Assembly for Metadata

The complete KLV encoded Metadata block (length = 16 + 4 + 4096 = 4116bytes) is packed into SMPTE291M Ancillary Data packets (ANC packets). Since ANC packets have a maximal payload size of 255 bytesthe Metadata block has to be segmented. This is done according to SMPTE RP 214-2002, Packing KLV


19/29


Encoded Metadata and Data Essence into SMPTE 291M Ancillary Data Packets. 18 ANC packets areneeded.

ANC Packet Structure for Metadata

ANC Packet #1

ADF (3) DID,SDID(2)

DC(1) MID(1) PSC(2) Key(16) Length(4) Value, first part (210) CS(1)

ANC Packets #2!#17

ADF (3) DID,SDID(2)

DC(1) MID(1) PSC(2) Value, subsequent parts(230) CS(1)

ANC Packet #18

ADF (3) DID,SDID(2)

DC(1) MID(1) PSC(2) Value, last part(206) 0-padding(24) CS(1)

ANC Packet Parameters for Metadata

ADF (3) = 000, 3FF, 3FF (hex) Ancillary Data Flag (packet header)

DID, SDID (2) = 44, 04 (hex) Packet Id for VANC space (vertical ancillary data space)

DC (1) = 233 (dec) length of User Data Words (UDW) is 233 for all packets

MID (1) = e.g. 1(dec) Message ID for all metadata packets; it is an arbitrary but identical number for allpackets of this KLV object.

PSC (2) = 1 .. 18 (dec) 18 packets are needed, numbered from 1 to 18.

payload (230) each ANC packet has a segmented payload of 230 bytes. 18 packets are needed forthe 4116bytes KLV block.

packet #1 carries Key, Length of Value and the first part of Value (as shown above)

packet #2!#17 carry subsequent parts of Value. Key and Length is not repeated. Identification justby MID, PSC.

packet #18 carries the last part of Value and zero padding (24) up to the packet endCS (1) checksum to be calculated according to SMPTE 291M

ANC Packet Assembly for LUT

The complete KLV encoded LUT (length = 16 + 4 + 6144 = 6164bytes) is packed into SMPTE 291MAncillary Data packets (ANC packets). The segmentation is done in the same way as for Metadata. 27 ANCpackets are needed here.

ANC Packet Parameters for LUT

The structure and length of each ANC packet is the same as before (see previous page). The parametersare given below.

ADF (3) = 000, 3FF, 3FF (hex) Ancillary Data Flag (packet header)

DID, SDID (2) = 44, 04 (hex) Packet Id for VANC space (vertical ancillary data space)

DC (1) = 233 (dec) Length of User Data Words (UDW) is 233 for all packets

MID (1) = e.g. 2(dec) Message ID for all LUT packets; it is an arbitrary but identical number for all packets ofthis KLV object.

PSC (2) = 1!27 (dec) 27 packets are needed, numbered from 1 to 27.

payload (230) each ANC packet has a segmented payload of 230 bytes. 27 packets are needed forthe 6164bytes KLV block.

packet #1 carries Key, Length of Value and the first part of Value

packet #2!#26 carry subsequent parts of Value

packet #27 carries the last part of Value and zero padding (46) up to the packet end

CS (1) checksum to be calculated according to SMPTE 291M

ANC Packet Insert


20/29


The Extended Metadata packets are inserted in the same way in all modes of the camera (YUV / RGB /Raw, Single Link / Dual Link, progressive / segmentedframe, ..).

All ANC packets are inserted in the VANC space (vertical ancillary data space). Seven VANC lines areneeded if a LUT is included, else three lines. The user can give the lines for insert. For compatibility withsome recording devices only the Y-stream is used (corresponds to G in case of Dual Link). Packets areinserted just into one link. In case of Dual Link, Link B is unused.

On the next page the content and the position of each ANC packet within the VANC space is given.

Length of KL-Header (*1) Length of ANC packet complete (*2) Length of ANC packet payload (*3)

20 240 230

PacketNo.

PSC

Link ID

Of HD-SDI

Stream ID Line No. Sample No. atstart

of ANC Packet

Sample No. atend

of ANC Packet

Data Index inKLVwrappedobject at start ofpacket

Data Index instrippedobject at startof packet

[1!18] [A|B]

(*4)

[Y|C]

(*5)

[9!20 for psf]

[9!41 for p] (*6)

[~ 0!1919]

(*7)

[~ 0!1919]

(*8)

[~ 0!4115]

(*9)

[~ 0!4095]

(*10)

Metadata (4kb, MID = 1)

1 A Y 9 0 239 0 -20

2 A Y 9 240 479 230 210

3 A Y 9 480 719 460 440

4 A Y 9 720 959 690 670

5 A Y 9 960 1199 920 900

6 A Y 9 1200 1439 1150 1130

7 A Y 9 1440 1679 1380 1360

8 A Y 9 1680 1919 1610 1590

9 A Y 9 0 239 1840 1820

10 A Y 10 240 479 2070 2050

11 A Y 10 480 719 2300 2280

12 A Y 10 720 959 2530 2510

13 A Y 10 960 1199 2760 2740

14 A Y 10 1200 1439 2990 2970

15 A Y 10 1440 1679 3220 3200

16 A Y 10 1680 1919 3450 3430

17 A Y 11 0 239 3680 3660

18 A Y 11 240 479 3910 3890

LUT (6kb, MID = 2)

1 A Y 13 0 239 0 -20

2 A Y 13 240 479 230 210

3 A Y 13 480 719 460 440

4 A Y 13 720 959 690 670

5 A Y 13 960 1199 920 900

6 A Y 13 1200 1439 1150 1130

7 A Y 13 1440 1679 1380 1360

8 A Y 13 1680 1919 1610 1590

9 A Y 14 0 239 1840 1820

10 A Y 14 240 479 2070 2050

11 A Y 14 480 719 2300 2280

12 A Y 14 720 959 2530 2510

13 A Y 14 960 1199 2760 2740

14 A Y 14 1200 1439 2990 2970

15 A Y 14 1440 1679 3220 3200

16 A Y 14 1680 1919 3450 3430

17 A Y 15 0 239 3680 366018 A Y 15 240 479 3910 3890


21/29


19 A Y 15 480 719 4140 4120

20 A Y 15 720 959 4370 4350

21 A Y 15 960 1199 4600 4580

22 A Y 15 1200 1439 4830 4810

23 A Y 15 1440 1679 5060 5040

24 A Y 15 1680 1919 5290 5270

25 A Y 15 0 239 5520 5500

26 A Y 15 240 479 5750 5730

27 A Y 15 480 719 5980 5960

6210 6190

Remarks:

(*1) UL Label = 16 Bytes, Length = 4 Bytes

(*2) total length of ANC Packet

(*3) total length 10 (ADF(3) + DID(2) + Data Count(1) + Segment Message ID(1) + Segment PacketCount(2) + Checksum(1))

(*4) relevant in case of Dual-Link(*5) Stream Y in Single-Link corresponds to stream G in Dual Link, Link A

(*6) default values are 9-11, 13-16; effective values depend on user settings

! In case of Psf-transport of 2 sensorframes a second inserttakes place in the second field. ForDetails see appendix A1.

(*7) Sample No. at ANC packet ADF Flag (000)

(*8) Sample No. at ANC packet checksum

(*9) Index pointer in the complete KLV encoded block [0!4115] on the 1stbyte of the UDW-payload

(*10) Index pointer in the Value field of the KLV encoded block [0!4095] on the 1stbyte of the UDW-

payload

Extended metadata contentNot all fields of the 4 KB block are filled with content by the camera. The following table gives an overviewwhich data the camera provides and what a recorder that captures the data should do with it.

The ALEXA transmits metadata via its MON OUT and REC OUT connectors, no matter if the REC OUT isset to ARRIRAW or HD-SDI. The metadata on MON OUT is always a clone of the metadata on REC OUT,which means that in case of ARRIRAW output on REC OUT, the image width and height (IDI02 and IDI03)refer to the ARRIRAW image.

Note that this table lists more metadata than what has been introduced in Section 2. The additional fields,however, might not carry sensible values and are subject to change without further notice. Only metadatafields that have been introduced in Section 2 may be relied on.

ID Offset

(Bytes)

Content From camera? Recorder action

RID01 0x0000-0x0003

MagicNum Yes Clone

RID02 0x0004-0x0007

ByteOrder Yes Clone if Byte-order is kept

Overwrite if Byte-order is changed

RID03 0x0008-0x000B

HeaderSize Yes Clone

RID04 0x000C-0x000F

VersionNumber Yes Clone

IDI01 0x0010-0x0013

Valid - -

IDI02 0x0014-

0x0017

Width Yes Clone

IDI03 0x0018-0x001B

Height Yes Clone


22/29


ID Offset(Bytes)


IDI04 0x001C-0x001F

DataType Yes Must be set by recorder

IDI05 0x0020-0x0023

DataSpace Yes Clone

IDI06 0x0024-0x0033 ActiveImage Yes Clone

IDI07 0x0034-

0x0043

FullImage Yes Clone

IDI08 0x0044-

0x0047

ImageDataOffset Yes Clone

IDI09 0x0048-

0x004b

ImageDataSize Yes Clone

0x004c-

0x0053

Reserved Yes Clone

ICI01 0x0054-

0x0057

Valid - -

ICI02 0x0058-

0x005B

Version Yes Clone

ICI03 0x005C-

0x005F

WhiteBalance Yes Clone

ICI04 0x0060-

0x0063

GreenTintFactor Yes Clone

ICI05 0x0064-

0x0067

WhiteBalanceFactorR Yes Clone

ICI06 0x0068-

0x006B

WhiteBalanceFactorG Yes Clone

ICI07 0x006C-

0x006F

WhiteBalanceFactorB Yes Clone

ICI08 0x0070-

0x0073

WBAppliedInCameraFlag Yes Clone

ICI09 0x0074-

0x0077

ExposureIndex Yes Clone

ICI10 0x0078-

0x007B

BlackLevel Yes Clone

ICI11 0x007C-

0x007F

WhiteLevel Yes Clone

ICI12 0x0080-

0x00AF

ColorMatrix Yes Clone

ICI13 0x00B0-

0x00B3

ColorMatrixDesatGain Yes Clone

ICI14 0x00B4-

0x00B7

ColorMatrixDesatOffset Yes Clone

ICI15 0x00B8-

0x00BB

HighlightDesaturationFlag Yes Clone

ICI16 0x00BC-

0x00BF

TargetColorSpace Yes Clone

ICI17 0x00C0-

0x00C3

Sharpness Yes Clone

ICI18 0x00C4-

0x00C7

PixelAspectRatio Yes Clone

ICI19 0x00C8-

0x00CB

Flip Yes Clone

ICI20 0x00CC-

0x00EB

LookFile Yes Clone


23/29


ID Offset(Bytes)


ICI21 0x00EC-

0x00EF

LookLutMode Yes Clone

ICI22 0x00F0-

0x00F3

LookLutOffset No Generate

ICI23 0x00F4-

0x00F7

LookLutSize Yes Clone

ICI24 0x00F8-

0x00FB

LookLutCRC Yes Clone

ICI25 0x00FC-

0x00FF

LinearSaturation Yes Clone

ICI26 0x0100-

0x010B

CdlSlope Yes Clone

ICI27 0x010C-

0x0117

CdlOffset Yes Clone

ICI28 0x0118-

0x0123

CdlPower Yes Clone

ICI29 0x0124-

0x0129

PrinterLights Yes Clone

ICI31 0x0130-0x0133

CdlApplicationMode Yes Clone

CDI01 0x0160-

0x0163

Valid - -

CDI02 0x0164-

0x0167

CameraTypeID Yes Clone

CDI03 0x0168-

0x016B

CameraRevision Yes Clone

CDI04 0x016C-

0x016F

FirmwareVersion Yes Clone

CDI05 0x0170-

0x0173

CameraSerialNumber Yes Clone

CDI06 0x0174-

0x0177

CameraID Yes Clone

CDI07 0x0178-

0x017B

CameraIndex Yes Clone

CDI08 0x017C-

0x0183

SysImageCreationTime Yes Clone

CDI09 0x0184-

0x018B

UserDate Yes Clone

CDI10 0x018C-

0x018F

ExposureTime Yes Clone

CDI11 0x0190-

0x0193

ShutterAngle Yes Clone

CDI12 0x0194-

0x0197

SpeedRampDuration Not active Clone

CDI13 0x0198-

0x019B

SpeedRampStartFrame Not active Clone

CDI14 0x019C-

0x019F

SpeedRampEndFrame Not active Clone

CDI15 0x01A0-

0x01A3

SensorFps Yes Clone

CDI16 0x01A4-

0x01A7

ProjectFps Yes Clone

CDI17 0x01A8-

0x01B7

Master_TC Yes Clone


24/29


ID Offset(Bytes)


CDI18 0x01B8-

0x01C7

Ext_LTC_FreeRun Yes Clone if present

If not present, must be set to 0

CDI19 0x01C8-

0x01D7

Ext_VITC_FreeRun Not Active Clone if present


CDI20 0x01D8-

0x01E7

IntFreeRunToD_TC Not Active Clone if present


CDI21 0x01E8-

0x01F7

IntFreeRunUserDefined_TC Not Active Clone if present


CDI22 0x01F8-

0x0207

RecRunEdgeCode_TC Not Active Clone if present


CDI23 0x0208-

0x0217

RecRunClipCode_TC Yes Clone if present


CDI24 0x0218-

0x0227

RecRunRegen_TC Yes Clone if present


CDI25 0x0228-0x0267

TC_Reserved Not Active Clone if present


CDI26 0x0268-

0x027B

MagazineSerialNumber No Create

CDI28 0x027C-

0x029B

SMPTE_UMID Not active Free to use

CDI29 0x029C-

0x02A3

CameraType Yes Clon

CDI30 0x02A4-

0x02C3

RecorderType No Create

CDI31 0x02C4-

0x02C5

MirrorShutterRunning Yes Clone

CDI32 0x02C5-

0x02C6

VariFrame Yes Clone

CDI33 0x02C6-0x02C7

ReservedFlags Yes Clone

CDI34 0x02C8-

0x02CB

ExposurePhase Yes Clone

CDI35 0x02CC-

0X02CF

SubSecondFrameCount Not active Clone

CDI36 0x02D0-

0x02DF

UUID Yes Clone

CDI37 0x02E0-

0x02F7

SUP Version Yes Clone

0x02F8-0x036F

Reserved Yes Clone

LDI01 0x0370-

0x0373

Valid - -

LDI02 0x0374-

0x0377

FocusUnit Yes Clone

LDI03 0x0378-

0x037B

FocusDistance Yes Clone

LDI04 0x037C-

0x037F

FocalLength Yes Clone

LDI05 0x0380-

0x0383

LensSerialNumber Yes Clone

LDI06 0x0384-

0x0387

Iris Yes Clone

LDI07 0x0388-

0x038B

ND_Filter Yes Clone


25/29


ID Offset(Bytes)


LDI08 0x038C-

0x038F

UV_Filter Yes Clone

LDI09 0x0390-

0x0393

IR_Filter Yes Clone

LDI10 0x0394-

0x0397

IR_BlackFilter Yes Clone

LDI11 0x0398-

0x03B7

LensModel Yes Clone

LDI12-1 0x03B8-0x03B9

RawEncoderFocus.EncoderValueRawLds Yes Clone

LDI12-2 0x03BA-0x03BB

RawEncoderFocus.EncoderValueRawMotor Yes Clone

LDI13-1 0x03BC-0x03BD

RawEncoderFocal.EncoderValueRawLds Yes Clone

LDI13-2 0x03BE-0x03BF

RawEncoderFocal.EncoderValueRawMotor Yes Clone

LDI14-1 0x03C0-

0x03C1

RawEncoderIris.EncoderValueRawLds Yes Clone

LDI14-2 0x03C2-0x03C3

RawEncoderIris.EncoderValueRawMotor Yes Clone

LDI15 0x03C4-0x03C7

EncoderLimitsFocusLds Yes Clone

LDI16 0x03C8-0x03CB

EncoderLimitsFocalLds Yes Clone

LDI17 0x03CC-0x03CF

EncoderLimitsIrisLds Yes Clone

LDI18 0x03D0-0x03D3

EncoderLimitsFocusMotor Yes Clone

LDI19 0x03D4-0x03D7

EncoderLimitsFocalMotor Yes Clone

LDI20 0x03D8-

0x03DB

EncoderLimitsIrisMotor Yes Clone

LDI21 0x03DC-0x03DC

LdsLagType Yes Clone

LDI22 0x03DD-0x03DD

LdsLagValue Yes Clone

0x03DC-

0x0437

Reserved Not active Clone

VFX01 0x0438-

0x043B

Valid - -

VFX02 0x043C-

0x0443

GpsLatitude Not active Free to use

VFX03 0x0444-

0x044B

GpsLongitude Not active Free to use

VFX04 0x044C-

0x044F

X Not active Free to use

VFX05 0x0450-

0x0453

Y Not active Free to use

VFX06 0x0454

0x0457

Z Not active Free to use

VFX07 0x0458-

0x045B

Pan Not active Free to use

VFX08 0x045C-

0x045F

Tilt Yes* Clone or create

VFX09 0x0460-

0x0463

Roll Yes* Clone or create

VFX10 0x0464- MasterFlag Yes Clone


26/29


ID Offset(Bytes)


0x0467

VFX11 0x0468-

0x046B

ChannelInfo Yes Clone

VFX12 0x046C-

0x046F

PartnerId Not Active Clone

0x0470-

0x04EF


CID01 0x04F0-

0x04F3

Valid - -

CID02 0x04F4-

0x04F7

CircleTake Yes Clone

CID03 0x04F8-

0x04FF

ReelName Yes Clone

CID04 0x0500-

0x050F

SceneName Yes Clone

CID05 0x0510-

0x0517

TakeName Yes Clone

CID06 0x0518-

0x0537

Director Yes Clone

CID07 0x0538-

0x0557

Cinematographer Yes Clone

CID08 0x0558-

0x0577

ProductionName Yes Clone

CID09 0x0578-

0x0597

Company Yes Clone

CID10-CID12,CID14

0x0598-

0x0697

Notes Yes Clone

CID13 0x0698-0x06B0

CameraClipName Yes Clone

0x06B1-

0x0717

Reserved Yes Clone

SID01 0x0718-

0x071B

Valid - -

SID02 0x071C-

0x072B

SoundTC Not active Free to use

SID03 0x072C-

0x074B

SoundFileName Not active Free to use

SID04 0x074C-

0x076B

SoundRollName Yes Clone

SID05 0x076C-

0x078B

SoundSceneName Not active Free to use

SID06 0x078C-

0x07AB

SoundTakeName Not active Free to use

SID07 0x07AC-

0x07CB

AudioInfo Not active Free to use

SID08 0x07CC-0x07CF

AudioDataOffset No Generate

SID09 0x07D0-0x07D3

AudioDataSize No Generate

0x07D4-

0x0FFF



27/29


4.2.2 Timecode

Timecode (ATC) is embedded in the HD-SDI stream according to SMPTE 12M. It represents the timecode ofthe camera. This timecode is also available in the Extended Metadata as Master TC with identical content.

The camera can also deliver additional timecode with different content. These are part of the ARRI ExtendedMetadata (see below).

Timecode is inserted as ATC_LTC and ATC_VITC at the preferred locations in HANC space.This is line 9 for ATC_VITC and line 10 for ATC_LTC [SMPTE 12M-2, page 15], in case of Psf-transportadditionally in line 571 and 572. For further details, see appendix A1.

Every sensor image has an ATC_LTC and ATC_VITC packet. For camera frame rates above 30 fps theimplementation follows the preferred implementation in paragraph 12.1 of SMPTE 12M-1. This basicallysays: the frame counter should increment every second image. ATC_LTC and ATC_VITC also carry theVari-Frame flag.

Panasonic Vari-Frame

A so-called Vari-Frame Flag or Active Frame Flag is generated according to the Panasonic Specificationfor Vari-Frame. This flag is inserted into the User Data Words (UDW) of the timecode ATC_LTC and

ATC_VITC packet, as specified before.

Vari-Frame allows running the camera imager at frames rates below the frame rate of the HD-SDI link. In thiscase the cameras internal frame buffer delivers duplicated frames to meet the HD-SDI link speed. Allduplicated frames are marked as inactive and shall not be recorded.

The Vari-Frame Flag consists of two bits that can indicate the status separately for both fields of a frame.Since ARRI cameras always deliver progressive captured sensor frames just two states appear.

This is also true for Psf-transport modes where both transport fields carry different sensor images (e.g. DualLink 60p). Every sensor image is attended by a timecode packet that identifies the image as active orinactive.

UDW2 UDW2 Interpretation of the Vari-Frame Flag Bits

Bit 5 Bit 4 Status

0 0 Frame is inactive

0 1 Not defined

1 0 Not defined

1 1 Frame is active

The Vari-Frame Flag is also part of the ARRI Extended Metadata. From SUP 7.0 on, the Vari-Frame Flag isalways active in the UDW.

ANC Insert

Inserted into bit 4 and 5 of Timecode User Data Word 2 (UDW2) inATC_LTC and ATC_VITC (see BasicMetadata)

The Vari-Frame Flag is also included in the ARRI Extended Metadata. This can be used to determine anycloned frames that have been captured accidentally.

4.2.3 Payload Identifier

Payload identification, according to SMPTE 252M-2002, gives information regarding frame rate, kind ofsampling, bit quantization and number of links. In case the imager frame rate is not equal to the HD-SDIframe rate, the HD-SDI frame rate is indicated.

In case of ARRI T-Link, the RGBA 10 Bit container format is indicated irrespective of the 12 bit payload thatis carried in the 10 bit container.

The Dynamic Range field in Dual Link [SMPTE 352, page 16] is set to zero.

Payload identification is inserted in the Y-stream in HANC space immediately after EAV of line 10 and 572for Psf and line 10 for progressive [SMPTE 352, page 8, 9].


28/29


4.2.4 Recorder Control

Introduction

For a very basic remote RECORD START/STOP function with the ALEXA/D-21, the recorder shouldrecognize a flag in the HD-SDI signal.

This flag lives in the HANC data packet in line 9, samples 1928 to 1945 (data dumps from LEADER LV 5330,

binary mode in table below). The actual RECORD START/STOP trigger is sample 1944; sample 1945 is achecksum of the ANC data packet.

Note: When Audio is embedded in the HD-SDI, the horizontal position of the data packet is shifted.

Requirements for the recorder

The recorder should immediately go into RECORD when the RECORD trigger (column 3) is received and gointo REC PAUSE or STOP when the STOP trigger (column 2) is received. When in REC PAUSE/STOPmode the recorder mustdeliver an EE signal on the output (viewing through recorder). In the recorderssetup (menu system etc.) this RECORD START/STOP function should be referred to as SDI REMOTE withthe options ON and OFF (ignore RECORD START/STOP trigger if present).

The recorder should support this RECORD START/STOP function in all ALEXA/D-21 output modes it is ableto record, i.e. HD 1920x1080 422, 444, 422 dual stream (Highspeed and D-21 Mscope), ARRI RAW T-Link.The recorder mustbe transparent to the ANC data packet; it should be present on all outputs in order tohave more slave recorders connected behind it. This should be true in STOP/EE and RECORD. Therecorder shouldnotrecord the ANC data packet to prevent unwanted recording on slave recorders whenplaying back material.

Note: Ideally the recorder features a MON OUT with status information (RECORD and TIMECODE) burn-inand bright TALLY lights, which will act as a confirmation of i.e. recording.

ANC data packets and code values (cv)

ANCdata

ANC OFFsmpl:cv Y, cv Cb/Cr

ANC ON, STOPsmpl:cv Y, cv Cb/Cr

ANC ON, RECORDsmpl:cv Y, cv Cb/Cr

ADFADF

ADFDIDSDIDDCUDWUDWUDWUDWUDWUDWUDWUDWUDWUDWUDWCS

1928:0001000000,10000000001929:0001000000,1000000000

1930:0001000000,10000000001931:0001000000,10000000001932:0001000000,10000000001933:0001000000,10000000001934:0001000000,10000000001935:0001000000,10000000001936:0001000000,10000000001937:0001000000,10000000001938:0001000000,10000000001939:0001000000,10000000001940:0001000000,10000000001941:0001000000,10000000001942:0001000000,10000000001943:0001000000,10000000001944:0001000000,10000000001945:0001000000,1000000000

1928:0000000000,10000000001929:1111111111,1000000000

1930:1111111111,10000000001931:0101010010,10000000001932:1001001101,10000000001933:0100001011,10000000001934:1000000001,10000000001935:1000000000,10000000001936:1000000000,10000000001937:1000000001,10000000001938:1000000000,10000000001939:1000000000,10000000001940:1000000001,10000000001941:1000000000,10000000001942:1000000000,10000000001943:1000100000,10000000001944:1000000000,10000000001945:1011001101,1000000000

1928:0000000000,10000000001929:1111111111,1000000000

1930:1111111111,10000000001931:0101010010,10000000001932:1001001101,10000000001933:0100001011,10000000001934:1000000001,10000000001935:1000000000,10000000001936:1000000000,10000000001937:1000000001,10000000001938:1000000000,10000000001939:1000000000,10000000001940:1000000001,10000000001941:1000000000,10000000001942:1000000000,10000000001943:1000100000,10000000001944:1000000010,10000000001945:1011001111,1000000000

Note: The positions of the samples given are only valid without audio in the HD-SDI. When audio is embedded in the HD-SDI, thehorizontal position is shifted.

4.2.5 Audio

When audio is active on the camera, two audio channels (48 KHz, 24 Bit) are embedded in the HD-SDIstream as a stereo pair in channel 1 and 2 of the Audio Group 1. Channel 1 is left.

The insert positions of the audio data and audio control packets are compliant with the SMPTE specification[SMPTE 299, page 18 and 24].


29/29

5 Reading Metadata

ARRI Meta Extract5.1

ARRI provides a software called ARRI Meta Extract, which runs on both Mac and PC. It is available as a GUIapplication for direct viewing of metadata, and a command line application for extraction of metadata. ARRI

Meta Extract reads Quicktime, DPX, and ARRIRAW files; MXF file support will be added at a later time.

The command line application extracts both static and dynamic metadata from a clip and writes it to acomma separated value (CSV) file. The CSV file can be used to feed metadata into other applications or toview it directly, either in plain text or with help of a spreadsheet application. Whenever an ARRI Look Filehas been applied during recording (either destructive or non-destructive), it will be dumped to a separateXML file.

For proper handling of metadata that has been recorded with an ALEXA SUP 8.0, ARRI Meta Extract version2.1 or later needs to be used.

Previous AME versions show the following errors when reading metadata from files generated with SUP 8.0:

1. CID11: Value in field User Info 1 is: Operator: XXXX2. CID12: In User Info 2: User Info 1: XXXX3. CDI26: Storage Media Serial Number: value is incorrect

4. CDI36: UUID: value is not existing5. Metadata fields established with SUP 8 are not available: Prod. Company (CID09), CDL Mode

(ICI31), LDS Lag Type (LDI21), and LDS Lag Value (LDI22)

ARRI Meta Extract is available from the ARRI webpage athttp://www.arri.de/camera/digital_cameras/tools/arri_meta_extract.html.

QuickTime Files5.2

5.2.1 Clip-MetaView

To view the QuickTime metadata atom content, an application named Clip-MetaView can be downloadedfrom the Apple AppStore for free.

5.2.2 XML Reader

Any XML reader can be used to read the FCP 7 XML file. Apple Final Cut Pro will transfer the metadata fromthe XML into the matching columns.

MXF Files5.3

5.3.1 ARRI AMA Plugin

The ARRI AMA plugin for AVID Media Composer reads static metadata from the MXF files and adds it ascolumns to the Media Composer.

When using the standard AMA plugin, static metadata can also be added to Media Composer by importingthe ALE file which is written by the camera together with the MXF files.

The ALE file can be opened with any text editor.

ARRIRAW Files5.4

The ARRIRAW Converter (ARC) can show all camera metadata of ARRIRAW (.ari) files. It is available fromthe ARRI webpage at http://www.arri.de/camera/digital_cameras/tools/arriraw_converter.html.

For proper handling of metadata that has been recorded with an ALEXA SUP 8.0, ARRIRAW converterversion 3 or later needs to be used. For earlier versions, the restrictions mentioned for AME above apply.

6 Contact

If you have any questions regarding metadata in the ALEXA, please feel free to contact us via email at

[email protected].

ALEXA Metadata White Paper SUP8

Documents

Transcript of ALEXA Metadata White Paper SUP8