> 
> > > Inspecting the files with a Hex editor and File Info function in Winamp,
> I
> > > discovered that if Lame generates no ID3 tag, or a v1.1 tag only, it
> > "pads"
> > > the first 417 bytes of the file with zeros.
> >
> > This is the space reserved to write the info/vbr tag. This tag should be
> > written after encoding is finished. The problem might be that the
> front-end
> > that you are using to encode doesn't properly call the needed function to
> > complete this tag after encoding.
> 

I looked at what little documentation we have, and I think
this is actually our fault - not the application.  

The problem comes from the fact that CBR streams now also
add the VBR tag (since it contains other usefull information
in addition to the VBR TOC).  

Here is what the documentation for our API says:

   7.  Write all remaining data to mp3 file.  If the file was
   encoded using VBR and you want to add a Xing VBR header:

   void lame_mp3_tags_fid(lame_global_flags *,FILE* fid);

The call is manditory, but it might give some the impression
that the call is optional if VBR was not used.  

But now look at the DLL documentation:

   6. And optionally call the beWriteVBRHeader()
   functions, to insert a Xing MP3 Header</p>

Which clearly states the call is optional.  The reality
is that it should *always* be called, unless the
calling program specifically disabled the tag.  



Mark
 



_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder

Reply via email to