Making an MPEG streamer is trivial.
With Python, it took me about 10 lines of
code. Add an HTML header, it's about 12.
Plug it into inetd, you need 2 more, and
then it lets the system handle processes, zombies,
etc. (this has been running for 1 1/2 years
with a fair number of hits).
Bill
Scott Manley wrote:
>
> heh I'd like to merge Lame Into LiveIce to make it a a standalone streamer
>
> Scott Manley (aka Szyzyg) /------ _@/ Mail -----\
> ___ _ _ __ __ _ | Armagh Observatory |
> / __| __ ___| |_| |_ | \/ |__ _ _ _ | |___ _ _ | Armagh |
> \__ \/ _/ _ \ _| _| | |\/| / _` | ' \| / -_) || | | Northern Ireland |
> |___/\__\___/\__|\__| |_| |_\__,_|_||_|_\___|\_, | | BT61 9DG. |
> http://star.arm.ac.uk/~spm/welcome.html |__/ \=====================/
>
> On Thu, 30 Sep 1999 [EMAIL PROTECTED] wrote:
>
> > Hi all,
> >
> > just wanted to spark a bit of thought on some of the future direction
> > of lame. This occured to me after I read that for the update to lame3.30 we
> > can now do ID3 tags
> >
> > Consider the following ideas related to mp3 encoding
> > - CD-ripping (CD paranoia)
> > - resampling (sox)
> > - ID3 tags
> > - CDDB lookups
> > - mp3 databases
> >
> > Should these features be part of LAME? Or should these be considered "support
> > materials" and use some other program (like GRIP) to combine all these
> > functions?
> >
> > I remember somebody saying about unix programs that each program only does one
> > thing, but does it well.
> >
> > I'm not advocating or dissenting from features being included in LAME, i just
> > wondered what other people think.
> >
> > later
> > mike
> > --
> > MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
> >
> --
> MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
--
Bill Eldridge
Radio Free Asia
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
