Hello,
In order to give that idea I had last month about an "album-header",
in order to complete (imho) mp3 as a platform to encode all kinds of
cds seamlessly, as opposed to only non-live/mix cds given current
implementation, a chance, I'd like to get some information :) [yes, it
is english]
I looked at the source of lame concerning the xing VBR tag, and I get
what's in the 140 bytes past "Xing".
My questions:
-what's in the header data, in order to get a good mp3
frame, that plays .03secs of silence instead of garbage?
(where do I look in the lame code for this?)
-the xing VBR-tag frame is a 64kbit/s frame. What's the usable
content (bytes)?
-How big would the maximum info content be in a 44.1 320kbit/s frame
(so everythinig beside header I assume?, and 320being the largest
possible mp3 frame?).
-What about 48kHz and alikes (does this interfere with info-content)?
-Imagine I define a record structure containing all info I need for my
header thingy, would it be possible/adviseable to use that huffman
code in order to get the text fields smaller? Pro's / Cons? (I'm
thinking no because of the relative (as compared to filesize) small
gain vs the increased complexity/no plaintext.)
sorry for all the basic nagging Q's, but I'm conducting my own
feasibility study eh :)
thanks
--
Best regards,
Roel mailto:[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
