I set forth on a quest to determine the size of data used by ID3v2 tags. Just because of the question of how large in bytes a Media Library for X3 might be.
The specification for ID3v2 states that the maximum size for all tags, per track, could be 256MB.
WHAT????? 256MB??? Oh, this makes a lot of sense considering track size.... NOT!
OK, so I have been tagging wav files that were modified and exported by Sonar Studio X3 , using Tag&Rename. To get a grip on reality I just went through the process using the song I posted a waveform for, called St. Thomas.
The original rip file is 79,544,876 bytes, and has 'Artist Name' 'Track#' and 'Genre' in what seems to be ID3v1 format. (not sure)
The wav file exported by Sonar Studio, un-processed and still 16bit/44.1Khz is 79,548,876 bytes.
The wav track from Sonar Studio with tags added by Tag&Rename is 79,549,006 bytes. ID3v2 is selected in Tag&Remane and has 'Artist Name' 'Year' 'Track#' and 'Genre'
So what we have is:
Sonar's exported wav track is 3,824 bytes larger than the original rip. If Sonar studio is adding a broadcast wav header (4,400 bytes) then it must be throwing out 576 bytes of tag data from the rip tool.
Tag&Rename tagged track is 306 bytes larger than the exported wav. If the broadcast wav header is what Sonar Studio added to the wav file then Tag&Rename may be using part of (180 bytes reserved for expansion), but not all of the space in the header. This could mean tag data amounting to 486 bytes.
WHEW! What a relief. This of course does not indicate what happens with mp3. So it seems not unreasonable that a 1K byte allocation for each entry in the Media Library table could be used. Space for other tags and file pointer still being available.
If Media Libraries are added to the microSD cards in future fw, space requirements would not be critical. Considering the capacity of these cards.
I hope you're all glad I geeked out on this. Does anybody really care?
BTW St. Thomas play time is 7:30 so it's about twice the size of an average track.