Re: [Peep-develop] Shoutcast/Icecast Hookup

[Michael G. <mg...@ee...>]

  Hi August. It would be very cool to extend peep to talk over
shoutcast.  The way the sound archtecture works is that there is a
thin interface that essentially open up a sound device and then writes
raw signed 16-bit data to the device to be passed to the underlying
sound driver for output.  While I'm not familiar with the specifics of
the *casts, it might be possible to have it open a funky device and
have it written to the software or to implement your own thin layer to
tie it in. Please add this as a feature request and we'll see what we
can do once we finally polish up the 0.5.0 release.

                -- Mike

On Sun, Jul 20 @ 18:42, August wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> A common issue that has prevented me and I imagine others from really
> using peep is the client side.
> 
> Generally I like to keep things thick on the server (ie, sysadmin setup)
> and thin on the client (ie, users can use a web browser or existing
> software to get going.
> 
> In my dreams I'd be able to get peep up and running on the server and
> then hook up its midi or other software synth to a shoutcast/icecast
> stream. Any time I wanted to check in on the server I'd just punch up
> the stream from Winamp or any one of the other players that can handle
> these streams.
> 
> Other devs on the box could do the same thing, without jumping through
> any hoops, I'd simply have it become a link they could click.
> 
> Is this possible? Is this probably? Is this way out in left field?
> 
> Looking to see how peep could become the laymans (or at least lazy
> developers) tool for monitoring boxes.

-- 
Michael Gilfix
mg...@ee...

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html