BWF WAV Files Validation (BEXT Chunk Order & Time Reference)

[joe-sciame-wm]

Hi Jerome,

We have been having some issues with BWF WAV files where the The BEXT chunk is at the tail. In Media Trace I can see the order of the Broadcast extension objects inside the Media Trace but can we validate the order of the chunks using Media Conch and fail if WAV has the chunk at the end?

Additionally, we are seeing issues where the value of the Time Reference is different across the various metadata. bext data and the iXML will match but the Adobe XMP does not match. In Media Trace, I see the core and the iXML data but can't the XMP is pulled. Would it be possible to pull time reference from all location and validate.

<block offset="84" name="Broadcast extension" size="610">
        <block offset="84" name="Header" size="8">
          <data offset="84" name="Name">bext</data>
          <data offset="88" name="Size">602</data>
        </block>
        <data offset="92" name="Description"/>
        <data offset="348" name="Originator">Pro Tools</data>
        <data offset="380" name="OriginatorReference">aaOLSJDYz3Ok</data>
        <data offset="412" name="OriginationDate">2024-09-13</data>
        <data offset="422" name="OriginationTime">15:17:54</data>
        <data offset="430" name="TimeReference">171050880</data>
        <data offset="438" name="Version">1</data>
        <data offset="440" name="UMID">060A2B34-0101-0105-0101-0F1013000000</data>
        <data offset="456" name="UMID">8DD9C9D8-EC96-8000-DCBB-64E44D14FCA4</data>
        <data offset="472" name="UMID">00000000-0000-0000-0000-000000000000</data>
        <data offset="488" name="UMID">00000000-0000-0000-0000-000000000000</data>
        <data offset="504" name="Reserved">(190 bytes)</data>
      </block>

I can send you the offending WAV files offline.