On 06/01/15 19:01, Mark Reid wrote: > On Tue, Jan 6, 2015 at 12:03 AM, tim nicholson < > nichot20-at-yahoo....@ffmpeg.org> wrote: > >> On 05/01/15 20:41, Mark Reid wrote: >>> Hi, >>> This patch exports the full umid of packages as metadata. ffmpeg >> currently >>> only exports the material number portion of the umid. >>> >>> The new format is >>> <ISO label>-<length>-<instance number>-<material number> >>> example: >>> 060a2b340101010101010f00-13-000000-53dc416b9a770251060e2b347f7f2a80 >>> >> >> I think this is a good idea, but if we are going to make the change can >> we make the exported format be SMPTE330 compliant? Annex C (normative) >> states:- >> >> "By default, the hexadecimal representation should be preceded by the >> identifier ‘0x’. This default method of identification will result in 66 >> hexadecimal characters to represent a basic UMID as follows: >> 0x060A2B340101010501010D13 ... etc. >> The hexadecimal letters should be encoded as upper case (A...F)." >> >> > sounds like the right thing to do to me. > > so if I understand correctly > 060a2b340101010101010f00-13-000000-53dc416b9a770251060e2b347f7f2a80 > > should be just > 0x060A2B340101010101010F001300000053DC416B9A770251060E2B347F7F2A80 > > easy enough, I'll submit a new patch doing that instead. > _______________________________________________ > [..]
That's right. drop the '-' add the 0x prefix and upper case it. Saves a byte :) -- Tim. Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
