> I just ran a test using "lame /dev/zero /dev/null". Not a very thorough
> test, but it should test all the frame and bit counters. I stopped it
> after it had encoded over 20 million frames.
>
> Can you compile LAME with the asserts turned on
> (add -U NDEBUG to CC_OPTS in the Makefile) and
> see if it displays any error messages before dying.
Alright, I've updated my CVS to the latest (Sat Jul 22 17:56:59 EDT 2000)
and turned on -DNDEBUG, and I've re-enabled the constant streaming on my
program.
I'll let you know how it goes in 4 hours. :)
As a side note, I'm getting a blip inbetween songs, is this because of
headers and such? I would think that since it's raw PCM it shouldn't do
that... Basically, it would be the same as doing:
bash# (lame --decode in1.mp3 && lame --decode in2.mp3) | lame -b 56k out.mp3
...and getting a noise inbetween. Any ideas? Will I be forced to pad
incoming PCM data so it makes a complete frame or something?
--
Ben Reed a.k.a. Ranger Rick ([EMAIL PROTECTED])
http://defiance.dyndns.org/ / http://radio.scenespot.org/
Now playing on Defiance Radio: Thieves Like Us (Instrumental) by New Order
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
