When creating mezzanine content, the proposal is to generate the following metadata for each mezzanine stream:
.json
_avsync.json
The <mezzanine_stream_name>.json file would contain the following metadata:
Mezzanine:
name
label
URI
command_line
md5
properties = MezzanineProperties
source = MezzanineSource
MezzanineSource:
name
URI
license
MezzanineProperties:
width
height
scan
sub_sampling
bit_depth
frame_rate
colour_primaries
transfer_characteristics
matrix_coefficients
duration
frame_count
start_frame
start_indicator
end_indicator
qr_positions
codec
The <mezzanine_stream_name>_avsync.json file would contain the timing information related to the AV sync flashes/beeps (adapted from https://github.com/BBC/dvbcss-synctiming), which includes the following metadata:
Following a suggestion from Thomas, based on what is done by 3GPP e.g. here: http://dash.akamaized.net/WAVE/3GPP/5GVideo/ReferenceSequences/AOV/AOV.json
When creating mezzanine content, the proposal is to generate the following metadata for each mezzanine stream:
The
<mezzanine_stream_name>.jsonfile would contain the following metadata: Mezzanine:MezzanineSource:
MezzanineProperties:
The
<mezzanine_stream_name>_avsync.jsonfile would contain the timing information related to the AV sync flashes/beeps (adapted from https://github.com/BBC/dvbcss-synctiming), which includes the following metadata: