I am trying to figure out where in the code the mp3 data is outputted
frame by frame so that I can add an extra header to the frames so that
lame can interface with windows media player.
i looked in empty_buffer and I figured that at the fwrites: tmpbuf was one
frame of mp3 data being outputed. however, then I saw this structure:
#if BS_FORMAT == BINARY
//output routine that outputs tmpbuf which is of
variable size: buf_size-minimum
#else
//output routine that outputs val[2], 2 chars at a time
is this for 2 different stages in the mp3 output piping? or does lame
output the mp3 data differently based on some environment factor.
and, am i snooping in right place for my purpose? or am i off?
thanks.
-kali
ps:
I use lame b/c it beats ass on low bitrates. that web page that rated
bladeenc higher was created by crack smokers. i've listened and listened
and listened to many different types of songs with every encoder that I
could grab, including FHG, and i do hear quantization problems at low bit
rates, but significantly less than from any other mp3 encoder, except
xing. that one is good at low bitrates.
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
