AV1 mapping specs issueshttps://code.videolan.org/videolan/av1-mapping-specs/-/issues2021-03-03T20:58:50Zhttps://code.videolan.org/videolan/av1-mapping-specs/-/issues/2Descriptor2021-03-03T20:58:50ZFrançois CartegnieDescriptorReusing the ISOBMFF AV1CodecConfigurationBox as descriptor would ease to pass data around containersReusing the ISOBMFF AV1CodecConfigurationBox as descriptor would ease to pass data around containershttps://code.videolan.org/videolan/av1-mapping-specs/-/issues/1System A / System B2021-02-28T23:42:50ZFrançois CartegnieSystem A / System BThe registration of the identifier mentions SMPTE registry,
which means we target ATSC.
Need to be clear if the spec applies to both System A or B and the different mappings / registration in that caseThe registration of the identifier mentions SMPTE registry,
which means we target ATSC.
Need to be clear if the spec applies to both System A or B and the different mappings / registration in that casehttps://code.videolan.org/videolan/av1-mapping-specs/-/issues/4Stream ID2021-02-26T15:49:59ZChristophe MassiotStream IDThe spec mentions 0x7F which I have never seen in the field. Why not use 0xbd (private_stream_id_1) like other non-MPEG codecs?The spec mentions 0x7F which I have never seen in the field. Why not use 0xbd (private_stream_id_1) like other non-MPEG codecs?https://code.videolan.org/videolan/av1-mapping-specs/-/issues/3Stream type2021-02-26T15:44:27ZChristophe MassiotStream typeUsing stream type 0x6 (private data with PES syntax), like DVBsub, Teletext, AAC, etc. would probably be preferred, especially in the DVB world. Codecs like AC-3 use 0x6 stream type in System B, 0x81 stream type in System A. We could do ...Using stream type 0x6 (private data with PES syntax), like DVBsub, Teletext, AAC, etc. would probably be preferred, especially in the DVB world. Codecs like AC-3 use 0x6 stream type in System B, 0x81 stream type in System A. We could do the same if necessary (feedback needed from ATSC people).