search for: myplayer

One possibility is that Lame is using the wrong endianess for your system try changing NUMBER_LITTLE_ENDIAN to NUMBER_BIG_ENDIAN in liveice.h and rebuilding. The default distribution of Lame uses big endia samples on IO, which means that in raw input mode it needs the -x arg to be set. However - some 'helpful' people have made this the default on some distributions.... so when liveice

Hi, A simple question, that I would appreciate some opinions on: What are the advantages for using Icecast to stream static MP3 files rather than just letting Apache handle the streaming? Many thanks, Glen Scott --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

> I'll be posting some basic protocol ideas soon as I think I've finally > figured out how I want to handle stats and future admin functionality. I've written a mini liveice streamer/encoder built around the vorbis library, I need to know what connection protocol the new server will work around. (I'd get the icecast 2.0 sources, but once again the icecast source control

Decided to switch to OpenBSD 2.8 as I'm a bit more familiar with it. Everything seems to compile just fine except liveice. I get this error when running make. gcc -g -02 -I. -DHAVE_CONFIG_H -c -o streams.o streams.c streams.c:39 machine/soundcard.h: No such file or directory *** Error code 1 Stop in /usr/src/liveice (line 42 of Makefile). Now it seems pretty obvious why this failed, but I

> > liveice is still virtually unmaintained. it's no longer relevant with > > ices 2 for vorbis things, if anyone wants to maintain this or has > > patches, Scott Manley is the person to talk to. > > I don't have a place to put up web pages about LiveIce et al, and with > all the myplay stuff taking my time my maintenance has been > non-existant. is

So I've been doing this myself for far too long, I'm glad to have some good help these days. ices 1.x is now going to be maintained by Brendan Cully. Brendan has also done most of the network/imap code in mutt, and is working on multistreaming in ices 1.x. Hopefully we'll see some good stuff. ices 2.x (the vorbis version) is coming along very nicely and is maintained by Michael

So I've been doing this myself for far too long, I'm glad to have some good help these days. ices 1.x is now going to be maintained by Brendan Cully. Brendan has also done most of the network/imap code in mutt, and is working on multistreaming in ices 1.x. Hopefully we'll see some good stuff. ices 2.x (the vorbis version) is coming along very nicely and is maintained by Michael

> SOURCE $mountpoint ICE/1.0\n > ice-password: $password\n > ice-name: $name\n > ice-url: $url\n > ice-genre: $genre\n > ice-bitrate: $bitrate\n > ice-public: $public\n > ice-description: $description\n\n > Cool - I'll code this in right now.... There's no brains to this code right now, it just modifies the encoder example to read from teh soundcard and send

Bryan Walls wrote: > > I've set up Liveice on a Yellowdog Linux laptop (YDL 2.0). I'm trying > to stream to an icecast server on another YDL 2.0 system. > > Streaming seems to be fine, but encoding is pure garbage. When I > listen to the stream, it basically sounds like white noise. The > intesity of the hum depends on the strength of the sound being > encoded,

Thanks William and Scott, I appreciate the help.. Liveice and Icecast Rock! Ive had one stream running, non stop @ 128k for over 60 hours without a reset, restart, or a reload of anything.. Is this par for the course? And about that keepalive script.. Would you (or someone) be willing to send me a sample so as I change whats needed and implement it? Thanks a bunch! Scott W. On Mon, 12 Mar

> I'm sure Icecast (unlike Shoutcast) doesn't care what user-agent string > is provided. If the stand-alone player works without modified headers, > this can't be the problem. This is correct: we send a user-agent header (for compatibility with shoutcast when doing relaying), but the only thing we do with that header is report it when requested (including logging). >

Hi, For my application there's been some talk of people hiding viruses in Vorbis files. While the possibility's remote, I'm exploring ways to verify that a give file really is a Vorbis file, and doesn't even have long streaches of executable code in the middle of it. If a file has valid Ogg page structure, and a valid Vorbis header, but somewhere in the file a packet has been

Can anyone share some ideas or point me to some documentation on how I can easily begin streaming live audio? My input would be /dev/audio (my microphone or soundcard input). Is there some type of small HTTP server that can use this /dev/audio piped through oggenc (or the ogg vorbis library built into the httpd)? Or do I use a FIFO and any regular httpd? (I am running NetBSD.) Thanks,

...mps, it's hard to even > guess at what might be being done differently. I'm using icecast 1.3 and flash plug-in to play back the streams. It works great, as I said yesterday, and you can test it yourself downloading the little player I made (4Kb). http://www.sardegnaoggi.it/downloads/myplayer.zip maybe I could provide network dumps of a working system (icecast 1.3) and one from a not working system (icecast 2.0) if you tell me exactly what you need. Do you need a network dump from the server or from the client side? And how do I make a network dump on Linux or Windows? --- >8 ---...

This is a stupid question... Why would one use a streaming audio server versus just a web server to stream static files like a juke box? Here are some reasons I came up with: 1) A web server won't concatinate songs together, but if someone is only downloading say a one-off clip, perhaps a web server is exactly what is needed 2) Titles (or rather meta-data) don't get inserted into the

Hi all: One of the things that struck me immediately about the OGG vorbis codec and the OGG project in general were the names. When I was browsing the 2 websites some time ago, I failed to find mention of the relevance of either of these. Since names often have some significance in the opensource movement and these are somewhat unusual, I was wondering if someone could comment on on OGG and

Hi Thomas, It's a crazy idea if you are storing a few gig's, raid 5 would do, but we could be storing TBytes of audio and video, then using raid's or san's becomes more of a problem. That's why we are looking into using the cluster management of Oracle, but pull the audio data out and stream using Icecast instead of using intermedia. This solution abstracts us from the

Hello everybody... I figure this is not exactly an icecast question, but maybe someone might be able to help. Icecast runs nicely as far as I can see, and so does liveice, apart from the fact I don't get any input signal fed into it. I think it's due to the fact it expects the signal on line in by default and the souncard only has a mic in. So I tried to use the built in mixer mode,

Ok, is this possible: I want to have a 128k and a 24k stream of a particualr audio program, plugged into the line in of my Ensoniq AudioPCI 128 (es1370 chipset) Is there any way to do this with just one soundcard, or do I need two? Thanks Scott W --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

Hi all, Didn't get any replies to my previous query, so I thought I'd try again. Since I last emailed out, my station has appeared on yp.icecast.org, so I really don't know what was going on there.... This time, however, I'm hot on the trail of a generally crappy output stream from icecast/streamcast/ices. It stutters; it halts on track changes; it causes the little red