[ID3 Dev] SEEK frame semantics

[Andy Kernahan]

Pyt,

    I have interpreted the seek offset as the exact number of bytes from the 
end of the primary prepended tag to the start of the secondary tag. Please 
find attached a sample v2.4.0 split tag.

    Andy.
  ----- Original Message ----- 
  From: Pyt
  To: id3v2 at id3.org
  Sent: Wednesday, November 09, 2005 9:21 AM
  Subject: [ID3 Dev] SEEK frame semantics


  From the V2.4 specification, regarding the SEEK frame:

     This frame indicates where other tags in a file/stream can be found.
     The 'minimum offset to next tag' is calculated from the end of this
     tag to the beginning of the next. There may only be one 'seek frame'
     in a tag.

     <Header for 'Seek frame', ID: "SEEK">
     Minimum offset to next tag       $xx xx xx xx

  The wording "Minimum offset" seems misleading. What does "Minimum" mean in 
this case ? The next tag is anywhere *after* the offset  (e.g., offset+1 or 
offset+5 would be valid positions) ? or is it supposed to be exactly *at* 
the offset, as the text seems to imply ?

  Insights welcome.

  By the way, has anybody encountered a file using SEEK frames and multiple 
tags ? If so, I'd be interested in getting my hands on one, for test 
purposes.

  Thanks,

  Pyt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20051109/2f1577e8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 240_split.tag
Type: application/octet-stream
Size: 8597 bytes
Desc: not available
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20051109/2f1577e8/attachment.obj>
-------------- next part --------------
---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org