![]() I have also tried looking at the data in 6-bit increments to see if it's being compressed in some way (9 bytes * 8 bits = 72 = 12 blocks * 6 bits) but have not had any luck stumbling on a pattern yet. I have tried using to run it through all the different formats that would make sense, but nothing it pointing me in the right direction. It looks to me as if something is being done to interpret this raw data to retrieve that Unique ID string, but all my attempts to decode the raw data have not been at all fruitful. When I examine the raw data inside the WAV file, I find a 32-byte block of data - 4 bytes for the chars 'umid' 4 bytes for the size of the following data block - 24 then the 24-byte data block, which, when examined in Hex Fiend, looks like this:Ġ0000000 0000002A 5B7A5FFB 0F23DB11 00000000 00000000Īs you can see, there are only 9 bytes that contain any non-zero information, but this is somehow being used to store the 11 char Unique ID field. Examining a particular file inside Pro Tools, I can see that the file's Unique ID comes in the form of an 11 character string, looking like: rS9ipS!圆Tf. Pro Tools (AVID's DAW software) has a process for managing and linking to all of it's unique media using a Unique ID field, which gets embedded in to the WAV file in the form of a umid metadata chunk. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |