Byte 2 of an AAF PackageIDs (aka MobID) is 0x0c but
it should be 0x0a to be a SMPTE compatible UMID.
This was identified by Gareth Sylvester-Bradley (Sony)
when comparing AAF generated UMIDs with MXF
generated ones.
byte 2 change from 0xC to 0xA -> 12 byte UL has L=10
byte 5 change from 2 to 1 -> Dictionaries registry category
byte 6 change from 5 to 1 -> Metadata dictionaries
byte 7 change from 0x11 to 1 -> Dictionary standard
byte 10 change from 4 to 1 -> Globally unique identifiers
byte 11 change from 0x10 to 0xf -> Material type not
identified
fix the bug in bytes 17-20 so it really is seconds since
1970/1904 etc, and not seconds into the day.
Phil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=162067
Proposed resolution:
byte 2 change from 0xC to 0xA -> 12 byte UL has L=10
byte 5 change from 2 to 1 -> Dictionaries registry category
byte 6 change from 5 to 1 -> Metadata dictionaries
byte 7 change from 0x11 to 1 -> Dictionary standard
byte 10 change from 4 to 1 -> Globally unique identifiers
byte 11 change from 0x10 to 0xf -> Material type not
identified
fix the bug in bytes 17-20 so it really is seconds since
1970/1904 etc, and not seconds into the day.
Phil
Logged In: YES
user_id=692703
Fixed in ref-impl/src/impl/AAFUtils.cpp v1.48 by asuraparaju
(BBC R&D). This brings the AAF PackageID generation into
compliance with SMPTE 330M.