similar to: Problems with ices+icecast combination

Hello, I have a weird problem. If I use winamp to stream to my icecast server, I can give it any password (even the incorrect one) and it logs in fine and sends the stream to the server. If I use Ices, if I use the password supplied in the icecast.conf file and give it to the ices configuration file, it kicks this: Failed connecting to server 127.0.0.1, error: Could not login on server.

>> > - Most listeners will have to upgrade to a new client or >> > install a plugin. >> >> I don't see a way around this in the general case, until Ogg is so >> widely used that it would be a bad business idea not to support it. I > >Completely agree. I know it's a chicken-and-egg thing, and I am >competely sympathetic--it's just the

Mike / Karl - I've tried two different ways of setting up the "stream". In one URL, I named the file directly (http://foo.bar.org:8001/stream.ogg), and in the second, I made a stream.m3u file containing the afore mentioned http statement. Neither worked in Winamp. I had downloaded version 3 of WinAmp, so I uninstalled that, and went out and got the JOrbis (Java) player and the

I'm rather new to this. I just set up Icecast and Ices using source from CVS downloaded yesterday (3-20-2003). The box is running RedHat 8.0 with all the required RPMs to compile. Here's my trouble: I have Ices running in live mode, with it connecting correctly to the Icecast server on port 8000 (which is only bound to 127.0.0.1). I'm using Winamp on the client end connecting to port

I have icecast 2.0.0 and ices 2.0.0 working nicely together with no apparent errors. I connect to the URL with winamp and it works get. Problems arise when I try to connect with any other computer other than my own. This includes other computers on my LAN and off it aswell. In the winamp window they get the message: [HTTP/1.0 200OK] http://www.feelthevibe . . . Any suggestions as to why my

I have problems with the stdinpcm module in ices2. The player fills its buffer and doen't play anything and fill the buffer again and this repeats (with winamp). when I download the stream with wget I can play it from hard disk... is this a common problem with ices2 or do only I experience this behaviour? the oss module works. --- >8 ---- List archives: http://www.xiph.org/archives/

Hi there, we use IceCast KH on our webradio, no commercial. We have an issue that we dont know where to look. When listening using WinAmp (but in other players too like JW Player), after 70 or 90 minutes, we realize that the "green square" on top of WinAmp becomes a "red square". About 60 minutes after start, sometimes the "red square" blinks, and then more

* Arc <arc@indymedia.org> shaped the electrons to say... > > I quite agree - it's frustrating to be able to use software that's > > almost there, then have all the development move to a format that 90% > > of the applications/embedded systems don't yet support. > > I'm sorry, but >90% of software does support Ogg.

This is a very general email message. Please don't flame me on lack of information. I don't often get a chance to get into the building where this computer is located and unfortunately had turned logging off on the icecast server to avoid it ever writing to disk. The problem: Simply put, I have an icecast server on Linux that uses ices that needs to stream a signal 24/7 without

In Sweden, where I live, it's snowing like crazy. The Stockholm area is covered in white stuff and there's really no reason to leave the computer and get out anywhere. More white stuff is coming down all the time. Boring. I am sure your weekend is no better - rain, snow or just another boring sunny day. Let's find something cool to do during this weekend! Join the cool crowd

hi probably a simple question, but what commandline switch on ices will make freeamp/winamp display the name of the currently playing SONG? -n seems to name the stream, which is useful, but i'd realy like the display to be the sing, no the stream...? thx --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this

Now my stream seems to be listing in the yp directory, I was hoping there was an easy fix to this issue I am having. My stream is only displaying the name of the mount point in Winamp, it is not showing the full description, genre etc etc. Is this another configuration issue in my ices xml? I've checked the doco and I can't see any other options I've missed.. <p><p>---

I believe that Oddsock is using a Content Type of aacp. Using a .aac extension with this Content Type may present a conflict. This might actually be by design. I will do some further testing with Winamp and report here tomorrow. I will also double-check with the developer of Winamp for complete clarification. FYI, Orban Opticodec-PC allows the use of either Content Type of aac or aacp. aac is

I use Ices with the perl module. I would like to know how to use the function supposed to return metadata, for example to read Id Tag. I didn't find anything in the documentation. Are there commands to get all the fields provided by the IdTag ? I also had strange results when commenting this function (in that case it is supposed to stream the name of the song, by reading the IdTag). With

I've just set up a new collection of streams and one of them is having problems. The clients connecting to this one stream only last a few minutes before getting kicked off. I don't know where to start looking for the problem. I'm running Mandrake 8.1 with Libshout2.0, IceS 2.0a and Icecast2 downloaded from cvs only a few days ago (with the mentioned os.h error included ;-) I get the

On Tuesday, 10 July 2001 at 03:21, Nick Ludlam wrote: > From: "Brendan Cully" <brendan@icecast.org> > > That handles the segfault, I don't know why the stream wouldn't be > > sent fast enough though... > > Tried with winamp, sonique and freeamp. All exhibit the same problem of > stuttering play, and eventually this drops out of the icecast log: >

Hi vorbis dudes, I've been trying to encourage vorbis use for a somewhat well known person who is doing a weekly internet "radio" program. I guess they are finding out that WMA isnt too cross platform :-) Was wondering if someone could help out with these questions... The encoding platform is windows... Is vorbis suitable for 33.6k/56k streaming yet? Would be a good opportunity

I have libxml installed but I get this when I run it. root@webhost1 [/usr/local/icecast]# bin/ices -c etc/ices.conf You have no libxml support. The config file you just specified cannot be used. Ices Exiting... <p><p>> I have to specify the config file with > the "-c" flag, lioke this: > > cd /usr/local/icecast > bin/ices -c etc/ices.conf > > >

Is anyone else experiencing what seems to be a memory leak with Ices? I can have icecast up and running with WinAmp streaming to it from my '98 box for days at a time with no problem. As soon as I start Ices I'll launch top to watch and my free mem starts dropping -fast-. Starting from about 160MB free, in 4-5 hours I have 2MB free with Ices crashed and the memory unrecovered which sends

I'm not sure if this is an icecast issue or oddcast issue or both, but the latest Winamp (v5.22) is not now playing AAC+ streams encoded with Oddcast. Winamp v5.21 and earlier versions work fine. This may be some attempt by Winamp developers to force people to use Shoutcast, or to prevent oddcast from using their enc_aacplus.dll. Right, just took some time to set up the Shoutcast DSP to