Metadata in the ALEXA W H I T E
P A P E R
Digital Workflow Solutions, 15 February 2012
Version History Version
Author
Change Note
2012-01-20
Poetsch
Create new document with new structure, add Extended Metadata Content table (2.3.1)
2012-02-07
Poetsch
Added DNxHD Metadata info (2.1.2 & 2.1.4)
2012-02-15
DWS
Added contact information.
Introduction The ARRI ALEXA provides metadata with its images. This additional camera information makes documentation easier 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 5.1 or later.
Table of Contents Version History ................................................................................................................. 2 Introduction ....................................................................................................................... 2 Table of Contents ............................................................................................................. 2 1 Available Camera Info ................................................................................................... 3 2 Technical details ............................................................................................................ 4 2.1 SxS ..................................................................................................................... 4 2.1.1 FCP 7 XML ...................................................................................................... 4 2.1.2 ALE file ............................................................................................................ 7 2.1.3 QuickTime metadata atom .............................................................................. 8 2.1.4 MXF metadata XML ......................................................................................... 9 2.1.5 Proprietary ARRI atom .................................................................................. 10 2.2 .ARI ARRIRAW files ......................................................................................... 12 2.3 SDI .................................................................................................................... 12 2.3.1 Extended Metadata ....................................................................................... 13 2.3.2 Timecode ....................................................................................................... 22 2.3.3 Payload Identifier ........................................................................................... 22 2.3.4 Recorder Control ........................................................................................... 23 3 Reading Metadata ........................................................................................................ 24 3.1 QuickTime clips ................................................................................................ 24 3.2 .ARI ARRIRAW Files ........................................................................................ 24
Metadata in the ALEXA – White Paper
Page 2 of 24
1 Available Camera Info The following table shows which camera settings are available as meta data, sorted by the different image output paths. More information on the different fields in the various output paths is listed in detail below. Content
Description
.XML (SxS)
.ALE (SxS)
META (SxS)
Camera Serial Number
Serial number of camera as on housing
take
take
Camera ID
Camera serial number short form
take
Camera SUP Version
Software version active on camera
take
Sensor Fps
Frame rate of sensor
Shutter Angle
Shutter angle of sensor in degrees
Manufacturer
Camera Manufacturer
Exposure Index
Exposure index value set on camera in ASA
take
White Balance
White balance of camera as a color temperature in Kelvin
take
White Balance CC
Green/magenta correction value of white balance
Gamma Look
ADMD (SxS)
SDI
Grab**
take
take
take
take
take
take
take
take
take
take
take
take
take
take
frame
frame
take
take
take
frame
frame
take
take
frame***
frame***
take
take
frame***
frame***
take
take
take
frame***
frame***
Gamma set on image path
take
take
take
frame***
frame***
Look file information
take
take
take
frame***
frame***
Image Size
Size of recorded image in pixels
take
take
take
take
Camera Model
Type of camera (ALEXA, ALEXA Plus, ALEXA Studio, ALEXA M)
take
take
take
take
Time Code
Time code information (several different time codes are supported)
take
take
frame
frame
frame
User Bits
User bit settings
take
frame
frame
frame
UUID
Universal unique identifier created by camera for each new clip
take
take
take
Camera Tilt*
Vertical deviation of camera in degrees
frame
frame
frame
Camera Roll*
Deviation of camera around optical axis in degrees
frame
frame
frame
UMID
Unique media identifier
Lens Type*
Lens model connected to camera
take
take
Zoom Distance*
Current focal position on zoom lenses
take
take
Focus Distance* Iris Value* Master/Slave Info
Identifies master/slave camera
take
take
Channel Info
Marks left or right channel of 3D setup
take
Reel Name
Name of current SxS reel
Take Name Director name
take
take
take
take
take take
take
frame
frame
frame
Current focus distance of lens
frame
frame
frame
Current iris value of lens
frame
frame
frame
take
take
take
take
take
take
take
take
take
take
frame***
frame***
Counter oftake on SxS card
take
take
frame***
frame***
Name of director as entered by user
take
take
take
frame***
frame***
Cinematographer Name Name of cinematographer as entered by user
take
take
take
frame***
frame***
Location Name
Name of location as entered by user
take
take
take
frame***
frame***
Production Name
Name of production as entered by user
take
take
take
frame***
frame***
User Info 1
Additional info entered by user
take
take
take
frame***
frame***
User Info 2
Additional info entered by user
take
take
take
frame***
frame***
Sound Reel Name
Name of sound reel as entered by user
take
take
take
frame***
frame***
SxS Serial Number
Number of SxS card used for recording
take
take
take
User Date
Date as set by user on camera menu
take
take
take
frame***
frame***
User Time
Time as set by user on camera menu
take
take
take
take
frame***
ND Filter Type
Type of ND filter in camera (0= No ND filter, 1=ALEXA Studio ND type 1)
take
take
take
take
frame***
take
take
take
take
frame***
(not in SUP 6.0) ND Filter Density (not in SUP 6.0) * ** ***
th
Density of ND filter in camera in 1/1000 density values, only when ND filter is active
take
ALEXA Plus or ALEXA Studio Only for .ari frame grabs. Other frame grab formats will have metadata support in a later SUP version. This metadata is updated every frame but might be delayed in the processing chain up to 10 frames.
Metadata in the ALEXA – White Paper
Page 3 of 24
2 Technical details Metadata is implemented in different ways for the different image output options. The following section explains the technical details for all options. 2.1 SxS On SxS cards, metadata is stored in several different ways: Final Cut Pro 7 XML file, Avid Log Exchange (ALE) file, QuickTime metadata atom, MXF metadata XML and the ARRI Digital MetaData (ADMD) atom. 2.1.1 FCP 7 XML This XML file is stored in the reel folder on the SxS card. It is compatible with FinalCutPro (6 or 7) and can be used to batch import the whole set of clips into FinalCutPro directly from the SxS card. The XML contains the following set of metadata: Content
Tag
Prefix
Sensor Fps
Mastercomment1
SensorFps:
Shutter Angle
Mastercomment1
ShutterAngle:
White Balance
Mastercomment1
WhiteBalance:
White Balance CC
Mastercomment1
CCShift:
Exposure Index
Mastercomment1, Clipcommentb
ExposureIndexAsa
Gamma (SxS)
Mastercomment1, Clipcommenta
ColorGammaSxS:
Camera Model
Mastercomment2
Camera:
Camera ID
Mastercomment2
CamID:
Camera Serial Number
Mastercomment2
SerialNumber:
Camera SUP Version
Mastercomment2
SupVersion:
SxS Serial Number
Mastercomment2
SxS-SerialNumber:
Date
Mastercomment2
Date:
Time
Mastercomment2
Time:
Director name
Mastercomment3
Director:
Cinematographer Name
Mastercomment3
Cinematographer:
Location Name
Mastercomment3
Location:
Production Name
Mastercomment3
Production:
User Info 1
Mastercomment3
User1:
User Info 2
Mastercomment3
User2:
Project Fps
Timebase, Ntsc
Circle Clip
Logginginfo>Good
UUID
Metadata>Value
Metadata in the ALEXA – White Paper
Page 4 of 24
Here is an Example of a FCP XML file with 2 clips: B005R002B005C001_110601_R002280FALSE24-1-183078307B005C001_110601_R002TRUEnonenoneB005FALSESensorFps:24.000,ShutterAngle:172.8,WhiteBalance:5600,CcShift:+3, ExposureIndexAsa:800,ColorGammaSxS:LOG-CCamera:ARRI ALEXA,CamID:R002,SerialNumber:0002,SupVersion:4.0beta2:14701, SxS-SerialNumber:1300000000000202,Date:20110601,Time:20h43m27sProduction:THE DOES,Director:JOHN DOE,Cinematographer:JANE DOE, Location:DOE TAVERN,User1:SOME INFO,User2:MORE INFOColorGammaSxS:LOG-CExposureIndexAsa:800B005C001_110601_R002file://localhost/Volumes/B005R002/B005R002/B005C001_110601_R002.mov24280QuickTimecom.apple.finalcutstudio.media.uuid35UTF84792631a-0000-4000-a1fe-480c000000005:00:00:00sourceB005R00205:00:00:00soundDAY_01
Metadata in the ALEXA – White Paper
Page 5 of 24
B005C002_110601_R002232FALSE24-1-186638663B005C002_110601_R002TRUEnonenoneB005FALSESensorFps:24.000,ShutterAngle:172.8,WhiteBalance:5600,CcShift:+3, ExposureIndexAsa:800,ColorGammaSxS:LOG-CCamera:ARRI ALEXA,CamID:R002,SerialNumber:0002,SupVersion:4.0beta2:14701, SxS-SerialNumber:1300000000000202,Date:20110601,Time:20h43m44sProduction:THE DOES,Director:JOHN DOE,Cinematographer:JANE DOE, Location:DOE TAVERN,User1:SOME INFO,User2:MORE INFOColorGammaSxS:LOG-CExposureIndexAsa:800B005C002_110601_R002file://localhost/Volumes/B005R002/B005R002/B005C002_110601_R002.mov24232QuickTimecom.apple.finalcutstudio.media.uuid35UTF877a7e231-0000-4000-9f52-5cc2000000005:00:11:16sourceB005R00205:00:11:16soundDAY_01
Metadata in the ALEXA – White Paper
Page 6 of 24
2.1.2 ALE file The ALE file (Avid Log Exchange) is a file that can be used to import camera specific metadata into the Avid Media 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 ALEXA are custom columns matched to the specific camera metadata. Content
Column
Column type
Clip Name
Name
Standard
File Name
Source File
Standard
Take Name
Clip
Custom
Clip Duration
Duration
Standard
Contained Tracks
Tracks
Standard
Start Timecode
Start
Standard
End Timecode
End
Standard
Project Fps (Timebase)
FPS
Standard
Video Codec
Original_Video
Custom
Audio Format
Audio Format
Standard
Audio Samplerate [kHz]
Audio SR
Standard
Audio Bit Depth
Audio Bit
Standard
Sound Reel Name
Soundroll
Standard
Frame Width [Pixel]
FrameWidth
Standard
Frame Height [Pixel]
FrameHeight
Standard
UUID
UUID
Custom
SUP Version (of camera)
Sup_Version
Custom
Exposure Index [ASA/ISO]
Exposure_Index
Custom
Gamma (SxS)
Sxs_Gamma
Custom
White Balance [K]
White_Balance
Custom
White Balance CC
Cc_Shift
Custom
Look Name
Look_Name
Custom
Look Burned In
Look_Burned_In
Custom
Sensor Fps
Sensor_Fps
Custom
Shutter Angle
Shutter_Angle
Custom
Camera Manufacturer
Manufacturer
Custom
Camera Model
Camera_Model
Custom
Camera Serial Number
Camera_SN
Custom
Camera ID
Camera_ID
Custom
Camera Index
Camera_Index
Custom
Project Fps (same as FPS column)
Project_Fps
Custom
SxS Serial Number
Sxs_SN
Custom
Production Info
Production
Custom
Cinematographer
Cinematographer
Custom
Director Name
Director
Custom
Location Name
Location
Custom
User Info 1
User_Info1
Custom
User Info 2
User_Info2
Custom
User Date
Date_Camera
Custom
User Time
Time_Camera
Custom
Master/Slave Info
Master_Slave
Custom
Channel Info
Eye_Index
Custom
Camera Reel Name
Reel_Name
Custom
UMID
UMID
Custom
Lens Type
Lens_Type
Custom
Lens Focus Unit
Focus_Unit_Lens
Custom
Lens Serial Number
Lens_SN
Custom
Metadata in the ALEXA – White Paper
Page 7 of 24
2.1.3 QuickTime metadata atom In each QuickTime file, a set of static metadata is stored in the QuickTime metadata atom. The metadata atom contains the following set of metadata. Content
Metadata key
Data type
Value range
UUID
com.applefinalcutstudio.media.uuid
Signed Int
16 byte UUID
Camera SUP Version
com.arri.camera.SupVersion
UTF 8 String
SUP version string
Exposure Index
com.arri.camera.ExposureIndexAsa
Signed Int
160-3200
SxS Gamma
com.arri.camera.ColorGammaSxS
UTF 8 String
REC-709, DCI-P3, LOG-C-FilmMatrix, LOG-C
White Balance
com.arri.camera.WhiteBalanceKelvin
Signed Int
2000-11000
White Balance CC
com.arri.camera.WhiteBalanceTintCc
Signed Int
-8 to +8
Active Look File
com.arri.camera.LookFileActive
UTF 8 String
Name of Look File set in camera
Look File Applied
com.arri.camera.LookFileBurnedIn
UTF 8 String
Yes/No
Look File XML
com.arri.camera.LookFileXml
Binary Data
Lookfile XML as binary data
Sensor Fps
com.arri.camera.SensorFps
Signed Int
75-120000 in 1/1000 fps
Shutter Angle
com.arri.camera.ShutterAngle
Signed Int
50-3580 in 1/10 degree
Camera Model
com.arri.camera.CameraModel
UTF 8 String
ARRI ALEXA or ARRI ALEXA PLUS
Camera Serial Number
com.arri.camera.CameraSerialNumber
UTF 8 String
Serial Number String
Camera ID
com.arri.camera.CameraId
UTF 8 String
4 letter string, Base36
Camera Index
com.arri.camera.CameraIndex
UTF 8 String
1 letter, A-Z
Project Fps
com.arri.camera.ProjectFps
Signed Int
23976, 24000, 25000, 29970, 30000 in 1/1000 fps
SxS Serial Number
com.arri.camera.SxsSerialNumber
UTF 8 String
Serial number string
Production Name
com.arri.camera.ProductionInfoProduction
UTF 8 String
User defined String
Cinematographer Name
com.arri.camera.ProductionInfoCinematographer
UTF 8 String
User defined String
Director Name
com.arri.camera.ProductionInfoDirector
UTF 8 String
User defined String
Location Name
com.arri.camera.ProductionInfoLocation
UTF 8 String
User defined String
User Info 1
com.arri.camera.ProductionInfoUser1
UTF 8 String
User defined String
User Info 2
com.arri.camera.ProductionInfoUser2
UTF 8 String
User defined String
User Date
com.arri.camera.UserDate
UTF 8 String
YYYYMMDD
User Time
com.arri.camera.UserTime
UTF 8 String
HHMMSS
Master/Slave
com.arri.camera.MasterSlave
UTF 8 String
OFF, MASTER, SLAVE
Eye Index
com.arri.camera.EyeIndex
UTF 8 String
SINGLE, LEFT, RIGHT
Reel Name
com.arri.camera.ReelName
UTF 8 String
8 letter card reel name by camera
Sound Reel
com.arri.camera.SoundReel
UTF 8 String
8 letter sound reel name by user
Lens Type*
com.arri.camera.LensType
UTF 8 String
String with lens type name
Focus Unit*
com.arri.camera.FocusUnit
UTF 8 String
Feet, Meter
Lens Serial Number*
com.arri.camera.LensSerialNumber
UTF 8 String
String (add offset of 8912896 for Master Prime lenses)
ND Filter Type
com.arri.camera.NdFilterType
Signed Int
No ND Filter ALEXA Studio ND filter type 1
ND Filter Density
com.arri.camera.NdFilterDensity
Signed Int
Density of ND filter*1000
* ALEXA Plus or ALEXA Studio
Metadata in the ALEXA – White Paper
Page 8 of 24
2.1.4 MXF metadata XML The camera specific static metadata inside the MXF file is stored as an XML file. It contains the same fields as the QuickTime metadata atom and the ALE file, except for those that are generated from the file itself and are not camera specific metadata. The XML tags are equivalent to the ALE column names. This metadata set will be imported into the Avid Media Composer automatically by the ARRI ALEXA AMA volume plugin. XML tag
Column
com.applefinalcutstudio.media.uuid
UUID
com.arri.camera.SupVersion
Sup_Version
com.arri.camera.ExposureIndexAsa
Exposure_Index
com.arri.camera.ColorGammaSxS
Sxs_Gamma
com.arri.camera.WhiteBalanceKelvin
White_Balance
com.arri.camera.WhiteBalanceTintCc
Cc_Shift
com.arri.camera.LookFileActive
Look_Name
com.arri.camera.LookFileBurnedIn
Look_Burned_In
com.arri.camera.LookFileXml
--
com.arri.camera.SensorFps
Sensor_Fps
com.arri.camera.ShutterAngle
Shutter_Angle
com.arri.camera.CameraModel
Camera_Model
com.arri.camera.CameraSerialNumber
Camera_SN
com.arri.camera.CameraId
Camera_ID
com.arri.camera.CameraIndex
Camera_Index
com.arri.camera.ProjectFps
Project_Fps
com.arri.camera.SxsSerialNumber
Sxs_SN
com.arri.camera.ProductionInfoProduction
Production
com.arri.camera.ProductionInfoCinematographer
Cinematographer
com.arri.camera.ProductionInfoDirector
Director
com.arri.camera.ProductionInfoLocation
Location
com.arri.camera.ProductionInfoUser1
User_Info1
com.arri.camera.ProductionInfoUser2
User_Info2
com.arri.camera.UserDate
Date_Camera
com.arri.camera.UserTime
Time_Camera
com.arri.camera.MasterSlave
Master_Slave
com.arri.camera.EyeIndex
Eye_Index
com.arri.camera.ReelName
Reel_Name
com.arri.camera.SoundReel
Soundroll
com.arri.camera.LensType
Lens_Type
com.arri.camera.FocusUnit
Focus_Unit_Lens
com.arri.camera.LensSerialNumber
Lens_SN
Note: Custom column names appear as Start case inside Media Composer (e.g. Date_Camera)
Metadata in the ALEXA – White Paper
Page 9 of 24
2.1.5 Proprietary ARRI atom For dynamic metadata, a block of 256 bytes is stored for every image in both QuickTime and MXF files. In the QuickTime file, this atom is labeled ‘admd’ (ARRI Digital MetaData) and contains 256 bytes of binary data. 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 These 256 bytes are structured as following: Content
Info
Offset
Size
(Bytes)
(Bytes)
0
4
reserved
4
4
LTC
Coded as: hhmmssff (4 bit=1 int digit)
8
4
User Bits
Coded as: hhmmssff (4 bit=1 hex digit)
12
4
Rec Run TC start@0
Coded as: hhmmssff (4 bit=1 int digit)
16
4
Rec Run TC start @ offset
Coded as: hhmmssff (4 bit=1 int digit)
20
4
reserved
n/a
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°
32
34
reserved
n/a
64
4
ArriFileHeaderV3.CameraDeviceInformation.SysImageCreationTime.Date
n/a
68
4
ArriFileHeaderV3.CameraDeviceInformation.SysImageCreationTime.Time
n/a
72
4
ArriFileHeaderV3.CameraDeviceInformation.UserDate.Date
n/a
76
4
ArriFileHeaderV3.CameraDeviceInformation.UserDate.Time
n/a
80
4
ArriFileHeaderV3.CameraDeviceInformation.ExposureTime
Coded as: units of 1 ms
84
4
ArriFileHeaderV3.CameraDeviceInformation.ShutterAngle
Coded as: units of 1/10°
88
4
ArriFileHeaderV3.CameraDeviceInformation.SpeedRampStartFrame
n/a
98
4
ArriFileHeaderV3.CameraDeviceInformation.SpeedRampEndFrame
n/a
96
4
ArriFileHeaderV3.CameraDeviceInformation.SensorFps
Coded as: units of 1/1000 fps
100
4
ArriFileHeaderV3.CameraDeviceInformation.Master_TC.TimeCode
Coded as: hhmmssff (4 bit=1 digit)
104
4
ArriFileHeaderV3.CameraDeviceInformation.Master_TC.FrameCounter
Coded as: Int32 translation of TC
108
4
ArriFileHeaderV3.CameraDeviceInformation.Ext_LTC_FreeRun.TimeCode
n/a
112
4
ArriFileHeaderV3.CameraDeviceInformation.Ext_LTC_FreeRun.FrameCounter
n/a
116
4
ArriFileHeaderV3.CameraDeviceInformation.Ext_VITC_FreeRun.TimeCode
n/a
120
4
ArriFileHeaderV3.CameraDeviceInformation.Ext_VITC_FreeRun.FrameCounter
n/a
124
4
ArriFileHeaderV3.CameraDeviceInformation.IntFreeRunToD_TC.TimeCode
n/a
128
4
ArriFileHeaderV3.CameraDeviceInformation.IntFreeRunToD_TC.FrameCounter
n/a
132
4
ArriFileHeaderV3.CameraDeviceInformation.IntFreeRunUserDefined_TC.TimeCode
n/a
136
4
ArriFileHeaderV3.CameraDeviceInformation.IntFreeRunUserDefined_TC.FrameCounter
n/a
140
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunEdgeCode_TC.TimeCode
n/a
144
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunEdgeCode_TC.FrameCounter
n/a
148
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunClipCode_TC.TimeCode
n/a
152
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunClipCode_TC.FrameCounter
n/a
156
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunRegen_TC.TimeCode
n/a
160
4
ArriFileHeaderV3.CameraDeviceInformation.RecRunRegen_TC.FrameCounter
n/a
164
4
ArriFileHeaderV3.CameraDeviceInformation.DigitalKeykode[0]
n/a
168
4
ArriFileHeaderV3.CameraDeviceInformation.DigitalKeykode[1]
n/a
Metadata in the ALEXA – White Paper
Page 10 of 24
172
4
ArriFileHeaderV3.CameraDeviceInformation.DigitalKeykode[2]
n/a
176
4
ArriFileHeaderV3.CameraDeviceInformation.DigitalKeykode[3]
n/a
180
4
ArriFileHeaderV3.CameraDeviceInformation.FocusDistance
ALEXA PLUS only Coded as: units of mm for FocusUnit=Metric units of 1/1000 inch for FocusUnit= Imperial Special values: 0: invalid/ no value -1: focus distance infinite
184
4
ArriFileHeaderV3.CameraDeviceInformation.FocalLength
ALEXA PLUS only Coded as: Units of µm Special value: 0: Invalid/ no value
188
4
ArriFileHeaderV3.CameraDeviceInformation.Aperture
ALEXA PLUS only Coded as: units of 1/1000 linear iris** Special values: -3: nearly close -2: closed -1: Invalid/ no value
192
4
ArriFileHeaderV3.VfxInformation.GpsLatitude.North
n/a
196
4
ArriFileHeaderV3.VfxInformation.GpsLatitude.Latitude
n/a
200
4
ArriFileHeaderV3.VfxInformation.GpsLongitude.East
n/a
204
4
ArriFileHeaderV3.VfxInformation.GpsLongitude.Longitude
n/a
208
4
ArriFileHeaderV3.VfxInformation.X
n/a
212
4
ArriFileHeaderV3.VfxInformation.Y
n/a
216
4
ArriFileHeaderV3.VfxInformation.Z
n/a
220
4
ArriFileHeaderV3.VfxInformation.Pan
n/a
224
4
ArriFileHeaderV3.VfxInformation.Tilt
ALEXA PLUS only Coded as: units of 1/10 degree
228
4
ArriFileHeaderV3.VfxInformation.Roll
ALEXA PLUS only Coded as: units of 1/10 degree
232
24
reserved
**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
Metadata in the ALEXA – White Paper
Page 11 of 24
The above code is mathematically correct but does not match the rounding conventions established in film and photography for centuries. A tabled approach prints what you would expect: 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<=fullApertureIdx && fullApertureIdx<18) { if(apertureTenth == 0) { printf("%.1f\n",fNumberScale[fullApertureIdx]); } else { printf("%.1f + %d/10\n",fNumberScale[fullApertureIdx],apertureTenth); } } else { printf("out of bounds\n"); } }
From Byte 64 on, this metadata has the same fields as the dynamic section of the V3-header.
2.2 .ARI ARRIRAW files The .ari file format for ARRIRAW files stores metadata in the header of the file. The so-called V3-header has a size of 4KB. Details on the header fields and how it shall be represented by software is embedded into the file ArriFileV3.h, which can be obtained from [email protected]. 2.3 SDI Different types of metadata are embedded into the HD-SDI. Metadata refers to all data besides image content. This data is located in the HANC and VANC space of the HD-SDI signal. The following table gives an 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. VariFrame)
All Lines
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, c’d -1-
Line 11 {573}
VANC
Y
A
P + Psf
Extended Metadata 4K, c’d -2-
Line 13 {575}
VANC
Y
A
P + Psf
Extended Metadata LUT
Line 14 {576}
VANC
Y
A
P + Psf
Extended Metadata LUT, c’d -1-
Line 15 {577}
VANC
Y
A
P + Psf
Extended Metadata LUT, c’d -2-
Line 16 {578}
VANC
Y
A
P + Psf
Extended Metadata LUT, c’d -3-
but not 8 (570)
Metadata in the ALEXA – White Paper
Page 12 of 24
Remarks •
Line numbers with an ( )-addition, e.g. (571), indicate that in all cases of Psf-transport (not Ptransport) a second 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 and second field carry different sensor frames (e.g. Dual Link 60p) a second insert shall take place in the second field 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 of the remaining items is shifted towards EAV. There are no gaps between different items in HANC space.
•
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 to the default values given here. E.g. for Sony SRW-1 via: and / Others / Meta Data / Data 1, 2, 3 = 9, 10, 11.
2.3.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
Key
Length of Value
Value
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 of Value
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 10 00 (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 of Value
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 is as follows: LUT index i
Byte offset o
Byte content
0
0
E0/11
0, 1
1
E0/3 _ _ E0/0, E1/11_ _
E1/8
1
2
E1/7
______
E1/0
2
3
E2/11
______
E2/4
2, 3
4
E2/3 _ _ E2/0, E3/11 _ _E3/8
…
…
…
4095
6143
E4095/7_ _ _ _ _ _ E4095/0
______
E0/4
The LUT is referenced by the accompanying Metadata block (see before).
Metadata in the ALEXA – White Paper
Page 13 of 24
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
K16
11 / 01
General Metadata / Universal 4K Metadata Block
A1 / 01
Look and LUT Metadata / Tonemap LUT
01
Version of the ARRI Metadata definition. Incremented only if no more downwards compatible.
ANC Packet Assembly for Metadata The complete KLV encoded Metadata block (length = 16 + 4 + 4096 = 4116 bytes) is packed into SMPTE 291M Ancillary Data packets (ANC packets). Since ANC packets have a maximal payload size of 255 bytes the Metadata block has to be segmented. This is done according to SMPTE RP 214-2002, “Packing KLV Encoded Metadata and Data Essence into SMPTE 291M Ancillary Data Packets”. 18 ANC packets are needed. ANC Packet Structure for Metadata ANC Packet #1 ADF (3)
DID, SDID(2)
DC(1)
MID(1)
PSC(2)
Key(16)
Length(4)
DC(1)
MID(1)
PSC(2)
Value, subsequent parts(230)
DC(1)
MID(1)
PSC(2)
Value, last part(206)
Value, first part (210)
CS(1)
ANC Packets #2 … #17 ADF (3)
DID, SDID(2)
CS(1)
ANC Packet #18 ADF (3)
DID, SDID(2)
„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 all packets 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 for the 4116 bytes 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 just by MID, PSC.
packet #18
carries the last part of “Value” and “zero padding” (24) up to the packet end
CS (1)
checksum to be calculated according to SMPTE 291M
ANC Packet Assembly for LUT
The complete KLV encoded LUT (length = 16 + 4 + 6144 = 6164 bytes) is packed into SMPTE 291M Ancillary Data packets (ANC packets). The segmentation is done in the same way as for Metadata. 27 ANC packets are needed here. Metadata in the ALEXA – White Paper
Page 14 of 24
ANC Packet Parameters for LUT The structure and length of each ANC packet is the same as before (see previous page). The parameters are 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 of this 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 for the 6164 bytes 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 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 are needed if a LUT is included, else three lines. The user can give the lines for insert. For compatibility with some recording devices only the Y-stream is used (corresponds to G in case of Dual Link). Packets are inserted 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
Metadata in the ALEXA – White Paper
Page 15 of 24
Packet No.
Link ID
Stream ID
Line No.
Of HD-SDI
PSC [1 … 18]
Sample No. at start
Sample No. at end
of ANC Packet
of ANC Packet
Data Index in KLV wrapped object at start of packet
Data Index in stripped object at start of packet
[A|B]
[Y|C]
[9 … 20 for psf]
[~ 0 … 1919]
[~ 0 … 1919]
[~ 0 … 4115]
[~ 0 … 4095]
(*4)
(*5)
[9 … 41 for p] (*6)
(*7)
(*8)
(*9)
(*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
3660
18
A
Y
15
240
479
3910
3890
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
Metadata in the ALEXA – White Paper
Page 16 of 24
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 Packet Count(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. For Details 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 1 byte of the “UDW-payload”
(*10)
Index pointer in the “Value” field of the KLV encoded block [0 … 4095] on the 1 byte of the “UDW-payload”
st
st
Extended metadata content Not all fields of the 4 KB block are filled with content by the camera. The following table gives an overview which data the camera provides and what a recorder that captures the data has to do. Offset (Bytes)
Content
From camera?
Recorder action
0x00000x0003
MagicNum
Yes
Clone
0x00040x0007
ByteOrder
Yes
Clone if Byte-order is kept
0x00080x000B
HeaderSize
Yes
Clone
0x000C0x000F
VersionNumber
Yes
Clone
0x00100x0013
Valid
-
-
0x00140x0017
Width
Yes
Clone
0x00180x001B
Height
Yes
Clone
0x001C0x001F
DataType
Yes
Must be set by recorder
0x00200x0023
DataSpace
Yes
Clone
0x00240x0033
ActiveImage
Yes
Clone
0x0034-
FullImage
Yes
Clone
ImageDataOffset
Yes
Clone
ImageDataSize
Yes
Clone
Reserved
Yes
Clone
Valid
-
-
Version
Yes
Clone
WhiteBalance
Yes
Clone
GreenTintFactor
Yes
Clone
Overwrite if Byte-order is changed
0x0043 0x00440x0047 0x00480x004b 0x004c0x0053 0x00540x0057 0x00580x005B 0x005C0x005F 0x00600x0063
Metadata in the ALEXA – White Paper
Page 17 of 24
0x0064-
WhiteBalanceFactorR
Yes
Clone
WhiteBalanceFactorG
Yes
Clone
WhiteBalanceFactorB
Yes
Clone
WBAppliedInCameraFlag
Yes
Clone
ExposureIndex
Yes
Clone
BlackLevel
Yes
Clone
WhiteLevel
Yes
Clone
ColorMatrix
Yes
Clone
ColorMatrixDesatGain
Yes
Clone
ColorMatrixDesatOffset
Yes
Clone
HighlightDesaturationFlag
Yes
Clone
TargetColorSpace
Yes
Clone
Sharpness
Yes
Clone
PixelAspectRatio
Yes
Clone
Flip
Yes
Clone
LookFile
Yes
Clone
LookLutMode
Yes
Clone
LookLutOffset
No
Generate
LookLutSize
Yes
Clone
LookLutCRC
Yes
Clone
LinearSaturation
Yes
Clone
CdlSlope
Yes
Clone
CdlOffset
Yes
Clone
CdlPower
Yes
Clone
PrinterLights
Yes
Clone
Valid
-
-
CameraTypeID
Yes
Clone
0x0067 0x00680x006B 0x006C0x006F 0x00700x0073 0x00740x0077 0x00780x007B 0x007C0x007F 0x00800x00AF 0x00B00x00B3 0x00B40x00B7 0x00B80x00BB 0x00BC0x00BF 0x00C00x00C3 0x00C40x00C7 0x00C80x00CB 0x00CC0x00EB 0x00EC0x00EF 0x00F00x00F3 0x00F40x00F7 0x00F80x00FB 0x00FC0x00FF 0x01000x010B 0x010C0x0117 0x01180x0123 0x01240x0129 0x01600x0163 0x01640x0167
Metadata in the ALEXA – White Paper
Page 18 of 24
0x0168-
CameraRevision
Yes
Clone
FirmwareVersion
Yes
Clone
CameraSerialNumber
Yes
Clone
CameraID
Yes
Clone
CameraIndex
Yes
Clone
SysImageCreationTime
Yes
Clone
UserDate
Yes
Clone
ExposureTime
Yes
Clone
ShutterAngle
Yes
Clone
SpeedRampDuration
Not active
Clone
SpeedRampStartFrame
Not active
Clone
SpeedRampEndFrame
Not active
Clone
SensorFps
Yes
Clone
ProjectFps
Yes
Clone
Master_TC
Yes
Clone
Ext_LTC_FreeRun
Yes
Clone if present
0x016B 0x016C0x016F 0x01700x0173 0x01740x0177 0x01780x017B 0x017C0x0183 0x01840x018B 0x018C0x018F 0x01900x0193 0x01940x0197 0x01980x019B 0x019C0x019F 0x01A00x01A3 0x01A40x01A7 0x01A80x01B7 0x01B80x01C7 0x01C8-
If not present, must be set to 0 Ext_VITC_FreeRun
Not Active
IntFreeRunToD_TC
Not Active
IntFreeRunUserDefined_TC
Not Active
RecRunEdgeCode_TC
Not Active
RecRunClipCode_TC
Yes
RecRunRegen_TC
Yes
0x02280x0267
TC_Reserved
Not Active
0x0268-
MagazineSerialNumber
No
Create
DigitalKeykode
Not active
Free to use
SMPTE_UMID
Not active
Free to use
CameraType
Yes
Clon
RecorderType
No
Create
0x01D7 0x01D8-
If not present, must be set to 0
0x01E7 0x01E8-
Clone if present If not present, must be set to 0
0x0217 0x0218-
Clone if present If not present, must be set to 0
0x0207 0x0208-
Clone if present If not present, must be set to 0
0x01F7 0x01F8-
Clone if present
Clone if present If not present, must be set to 0
0x0227
Clone if present If not present, must be set to 0 Clone if present If not present, must be set to 0
0x026B 0x026C0x027B 0x027C0x029B 0x029C0x02A3 0x02A40x02C3
Metadata in the ALEXA – White Paper
Page 19 of 24
0x02C4-
MirrorShutterRunning
Yes
Clone
VariFrame
Yes
Clone
ReservedFlags
Yes
Clone
ExposurePhase
Yes
Clone
SubSecondFrameCount
Not active
Clone
UUID
Yes
Clone
Reserved
Not active
Clone
Valid
-
-
FocusUnit
Yes
Clone
FocusDistance
Yes
Clone
FocalLength
Yes
Clone
LensSerialNumber
Yes
Clone
Aperture
Yes
Clone
ND_Filter
Yes
Clone
UV_Filter
Yes
Clone
IR_Filter
Yes
Clone
IR_BlackFilter
Yes
Clone
LensModel
Yes
Clone
Reserved
Not active
Clone
Valid
-
-
GpsLatitude
Not active
Free to use
GpsLongitude
Not active
Free to use
X
Not active
Free to use
Y
Not active
Free to use
Z
Not active
Free to use
Pan
Not active
Free to use
Tilt
Yes*
Clone or create
Roll
Yes*
Clone or create
0x02C5 0x02C50x02C6 0x02C60x02C7 0x02C80x02CB 0x02CC0X02CF 0x02D00x02DF 0x02E00x036F 0x03700x0373 0x03740x0377 0x03780x037B 0x037C0x037F 0x03800x0383 0x03840x0387 0x03880x038B 0x038C0x038F 0x03900x0393 0x03940x0397 0x03980x03B7 0x03B80x0437 0x04380x043B 0x043C0x0443 0x04440x044B 0x044C0x044F 0x04500x0453 0x0454 0x0457 0x04580x045B 0x045C0x045F 0x04600x0463
Metadata in the ALEXA – White Paper
Page 20 of 24
0x0464-
MasterFlag
Yes
Clone
ChannelInfo
Yes
Clone
PartnerId
Not Active
Clone
Reserved
Not active
Clone
Valid
-
-
CircleTake
Yes
Clone
ReelName
Yes
Clone
SceneName
Yes
Clone
TakeName
Yes
Clone
Director
Yes
Clone
DoP
Yes
Clone
ProductionName
Yes
Clone
Company
Yes
Clone
Notes
Not active
Free to use
Reserved
Not active
Clone
Valid
-
-
SoundTC
Not active
Free to use
SoundFileName
Not active
Free to use
SoundRollName
Yes
Clone
SceneFileName
Not active
Free to use
TakeFileName
Not active
Free to use
Info
Not active
Free to use
0x07CC0x07CF
AudioDataOffset
No
Generate
0x07D00x07D3
AudioDataSize
No
Generate
0x07D4-
Reserved
Not active
Clone
Reserved 2
Not active
Clone
0x0467 0x04680x046B 0x046C0x046F 0x04700x04EF 0x04F00x04F3 0x04F40x04F7 0x04F80x04FF 0x05000x050F 0x05100x0517 0x05180x0537 0x05380x0557 0x05580x0577 0x05780x0597 0x05980x0697 0x06980x0717 0x07180x071B 0x071C0x072B 0x072C0x074B 0x074C0x076B 0x076C0x078B 0x078C0x07AB 0x07AC0x07CB
0x07F3 0x07F40x0FFF
Metadata in the ALEXA – White Paper
Page 21 of 24
2.3.2 Timecode Timecode (ATC) is embedded in the HD-SDI stream according to SMPTE 12M. It represents the timecode of the 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 Extended Metadata (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-transport additionally 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 the implementation follows the “preferred implementation” in paragraph 12.1 of SMPTE 12M-1. This basically says: the frame counter should increment every second image. ATC_LTC and ATC_VITC also carry the “Vari-Frame” flag. Panasonic Vari-Frame A so-called “Vari-Frame Flag” or “Active Frame Flag” is generated according to the Panasonic Specification for 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 this case the cameras internal frame buffer delivers “duplicated” frames to meet the HD-SDI link speed. All duplicated 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. Dual Link 60p). Every sensor image is attended by a timecode packet that identifies the image as active or inactive.
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. It is recommended to use the ARRI Extended Metadata and to switch off the Vari-Frame insert into the Timecode User Data Words. This keeps the User Data Words completely under user control. ANC Insert •
Insert into bit 4 and 5 of Timecode User Data Word 2 (UDW2) in ATC_LTC and ATC_VITC (see Basic Metadata)
Insert into Timecode User Data Words is dependent on user settings: “Panasonic Vari-Frame Insert into Timecode UDW: yes / no”. Included also in ARRI Extended Metadata. This should be the preferred source. Insertion into ARRI Extended Metadata always takes place. •
Metadata in the ALEXA – White Paper
Page 22 of 24
2.3.3 Payload Identifier Payload identification, according to SMPTE 252M-2002, gives information regarding frame rate, kind of sampling, bit quantization and number of links. In case the imager frame rate is not equal to the HD-SDI frame 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 that is 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 572 for “Psf” and line 10 for progressive [SMPTE 352, page 8, 9].
2.3.4 Recorder Control Introduction For a very basic remote RECORD START/STOP function with the ALEXA/D-21, the recorder should recognize 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 a checksum 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 go into REC PAUSE or STOP when the STOP trigger (column 2) is received. When in REC PAUSE/STOP mode the recorder must deliver an EE signal on the output (viewing through recorder). In the recorders setup (menu system etc.) this RECORD START/STOP function should be referred to as “SDI REMOTE” with the 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 able to record, i.e. HD 1920x1080 422, 444, 422 dual stream (Highspeed and D-21 Mscope), ARRI RAW T-Link. The recorder must be transparent to the ANC data packet; it should be present on all outputs in order to have more slave recorders connected behind it. This should be true in STOP/EE and RECORD. The recorder should not record the ANC data packet to prevent unwanted recording on slave recorders when playing back material. Note: Ideally the recorder features a MON OUT with status information (RECORD and TIMECODE) burn-in and bright TALLY lights, which will act as a confirmation of i.e. recording. ANC data packets and code values (cv) ANC data
ANC OFF smpl:cv Y, cv Cb/Cr
ANC ON, STOP smpl:cv Y, cv Cb/Cr
ANC ON, RECORD smpl:cv Y, cv Cb/Cr
ADF ADF ADF DID SDID DC UDW UDW UDW UDW UDW UDW UDW UDW UDW UDW UDW CS
1928:0001000000,1000000000 1929:0001000000,1000000000 1930:0001000000,1000000000 1931:0001000000,1000000000 1932:0001000000,1000000000 1933:0001000000,1000000000 1934:0001000000,1000000000 1935:0001000000,1000000000 1936:0001000000,1000000000 1937:0001000000,1000000000 1938:0001000000,1000000000 1939:0001000000,1000000000 1940:0001000000,1000000000 1941:0001000000,1000000000 1942:0001000000,1000000000 1943:0001000000,1000000000 1944:0001000000,1000000000 1945:0001000000,1000000000
1928:0000000000,1000000000 1929:1111111111,1000000000 1930:1111111111,1000000000 1931:0101010010,1000000000 1932:1001001101,1000000000 1933:0100001011,1000000000 1934:1000000001,1000000000 1935:1000000000,1000000000 1936:1000000000,1000000000 1937:1000000001,1000000000 1938:1000000000,1000000000 1939:1000000000,1000000000 1940:1000000001,1000000000 1941:1000000000,1000000000 1942:1000000000,1000000000 1943:1000100000,1000000000 1944:1000000000,1000000000 1945:1011001101,1000000000
1928:0000000000,1000000000 1929:1111111111,1000000000 1930:1111111111,1000000000 1931:0101010010,1000000000 1932:1001001101,1000000000 1933:0100001011,1000000000 1934:1000000001,1000000000 1935:1000000000,1000000000 1936:1000000000,1000000000 1937:1000000001,1000000000 1938:1000000000,1000000000 1939:1000000000,1000000000 1940:1000000001,1000000000 1941:1000000000,1000000000 1942:1000000000,1000000000 1943:1000100000,1000000000 1944:1000000010,1000000000 1945: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, the horizontal position is shifted.
Metadata in the ALEXA – White Paper
Page 23 of 24
2.3.3 Audio Two audio channels (48 KHz, 24 Bit) are embedded in the HD-SDI stream 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 SMPTE [SMPTE 299, page 18 and 24].
3 Reading Metadata 3.1 QuickTime clips ClipMetaView To view the QuickTime metadata atom content, an application named ClipMetaView can be downloaded from the Apple App-Store for free. ARRI Meta Extract Besides just viewing the metadata, there is a command line tool ARRI Meta Extract for both Mac and PC, which extracts the metadata and writes it in a .csv file. This file can then be used to import the metadata in other applications. It contains all static metadata (per take) as well as all dynamic metadata (per frame) including a possible used Look File (which will be exported to a separate*.xml file). ARRI Meta Extract is available via the ARRI Homepage (http://www.arri.de/.../arri_meta_extract.html). XML Reader Any XML reader can be used to read the FCP 7 XML file. Apple FinalCut Pro will transfer the metadata from the XML into the matching columns.
3.2 .ARI ARRIRAW Files The ARRIRAW Converter (ARC) can show all camera metadata of .ari ARRIRAW files.
If you have any questions about the general process, please send an email to [email protected].
Metadata in the ALEXA – White Paper
Page 24 of 24
