Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Do all HDtracks.com aif files have four bytes of trailing nulls at end
06-11-2017, 22:43
Post: #3
RE: Do all HDtracks.com aif files have four bytes of trailing nulls at end
(06-11-2017 19:14)simoncn Wrote:  Are these 4 null bytes included in the form size? if not, MinimServer would never read these bytes as it stops reading at the end of the specified form size. I don't think it is an error to have extra data in the file following the form data.

So for HDtracks the size recorded in the FORM chunk is 8 less then the end of the APPL chunk (the last chunk), then there are four null bytes after that (i.e difference to end of file is 12). In comparison for the files downloaded from Qobuz the size recorded in the FORM chunk is also 8 less than the end of the SSND chunk size. AFAIK QOBUZ is correct and size is size without including the 'FORM' and FORM size bytes, i.e 8bytes difference ?

So it does seem to be what you say, extra data after the form data length.

OKay I will have to make amendements to take that into account. Do you know of any cases where real data is put after the FORM size other than just null padding ?
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Do all HDtracks.com aif files have four bytes of trailing nulls at end - paultaylor - 06-11-2017 22:43

Forum Jump:


User(s) browsing this thread: 1 Guest(s)