[ID3 Dev] Accessibilty extension draft is posted

[Chris Newell]

Scott,
At 10:42 22/06/2006, you wrote:
>On Thursday 22 June 2006 11:07, you wrote:
>> I'm warming to the idea of a lookup table mapping strings to audio clips,
>> since this would support any frame type and solves the multiple instance
>> problem neatly. How about using a hash code approach to map strings to
>> audio clips?
>
>What would the hash be for?

To avoid string duplication and to provide an easy lookup mechanism. My background is in digital broadcast so I tend to be rather mean about bits.

>If you mean to avoid string duplication, I think just duplicating the text 
>would be easier to implement and easier to spec.  In terms of sizes, the text 
>"Rolling Stones" including null termination is 15 bytes.  A two second, 96 
>kb/s, 22050 kHz, mono mp3 is going to take around 5000 bytes.  Saving 7 bytes 
>by using an 8 byte hash instead probably wouldn't be worth it, plus it'd make 
>the files harder to read with a hex editor.  :-)

If string duplication and lookup are not issues then the solution can be very simple.

The next question which comes to mind is do need a new frame type or can we use the "GEOB" frame in some way?

Chris
  
____________________________________________ 

Chris Newell 
Lead Technologist 
Technology Group
BBC New Media & Technology
Kingswood Warren, Woodland Way, Tadworth
Surrey  KT20 6NP   UK

Tel:    +44 (0)1737 839659
Fax:    +44 (0)1737 839665
mailto:chris.newell at rd.bbc.co.uk
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20060622/45105914/attachment.html>