jpviollet
commented
1 year ago Below are the values that work on our equipment:
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
Location | DataDefinition Value -- | -- Timecode Sequences and Timecode Components | 060e2b34.04010101.01030201.01000000 Picture Sequences and Picture SourceClips | 060e2b34.04010101.01030202.01000000 Sound Sequences and Sound SourceClips | 060e2b34.04010101.01030202.02000000 Data Sequences and Data SourceClips in Timed Text Track Files | 060e2b34.04010101.01030202.03000000 Data Sequences and Data SourceClips in Aux Data Track Files | 060e2b34.04010101.01030202.03000000 DM Sequences and Segments – we don’t seem to use DM SourceClips, however the same value as DM Segment would make sense, by analogy with how previous items work. | 060e2b34.04010101.01030201.10000000
Following the discovery for ST 429-14 (see https://github.com/SMPTE/st429-14/issues/1) that Data Definition property value of Data Track "Sequence" is specified in ST377:2004, and is NOT specified in ST377-1, I see that the same difference exist for:
I also started process of checking which values are used/expected in Dolby D-Cinema implementations, and it is already confirmed that using different values than expected ones would trigger MXF file rejection in some cases - making the specification of these values even more important.
As discussed during February 2nd 2023 27C Documentation Maintenance meeting, ST429-20 feels the right place to address these differences and specify what are the expected values - instead of adding them in ST429-14, ST429-3, ST429-5, ST429-6, and ST429-18.
I’ll indicate which values work for our implementations when done with my internal checks – the value proposed in ST429-14 for Data Track Sequence seems appropriate so far. Thank you.