if test $ac_cv_sys_largefile_source != no; then
CFLAGS=$CFLAGS -D_LARGEFILE_SOURCE
fi
if test $ac_cv_sys_large_files != no; then
CFLAGS=$CFLAGS -D_LARGE_FILES=$ac_cv_sys_large_files
fi
fi
--
Dan Nelson
[EMAIL PROTECTED]
___
mp3encoder
get is screeching!
Lame doesn't recognize mu-law encoding. Try converting it to 16-bit
signed with sox, then pass the wav file through lame.
sox -bU -r 8000 -t raw 44.pcm -uw 44.wav
Watch the frog, indeed.
--
Dan Nelson
[EMAIL PROTECTED
buffering. You can adjust how XP balances
CPU usage from Task Manager (Ctrl-Shift-ESC): go to the Processes tab,
right-click on Lame (or whatever program is doing the encoding), select
Set Priority, and pick BelowNormal.
--
Dan Nelson
[EMAIL PROTECTED
In the last episode (Nov 15), Greg Wooledge said:
Dan Nelson ([EMAIL PROTECTED]) wrote:
I guess the problem might be oggenc's option parser, then. Given a
stereo 22050hz input file, I can't seem to get oggenc to encode less
than 22kbits. The lowest bitrate it will allow on the commandline
In the last episode (Nov 14), Greg Wooledge said:
Dan Nelson ([EMAIL PROTECTED]) wrote:
Unfortunately, ogg is no good for streaming, as its minimum bitrate
is 64k.
That's completely untrue. I've heard of people producing Vorbis
bitstreams as low as 5 kbps (of course, this is a degenerate
,
as the artifacts generated by decoding the first mp3 stream will get
overwhelmed by the artifacts generated by dropping the bitrate down to
streaming levels anyway.
--
Dan Nelson
[EMAIL PROTECTED]
___
mp3encoder mailing list
[EMAIL
bitrates (kbps): 8 16 24 32 40 48 56 64 80 96 112 128 144 160
--
Dan Nelson
[EMAIL PROTECTED]
___
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
the
twinkling artifacts too bad. You might also consider encoding a
separate stream at 50kpbs for the 56k modem users.
You'll never get as good as RealAudio quality (at low bitrates, RA can
encode stereo at the same quality as Lame in mono), but it shouldn't
sound too bad.
--
Dan Nelson
