similar to: some features of icecast2 beta

Michael Smith wrote: > Relaying (done already) and mp3 streaming (done already - but the support > for that is pretty limited. No metadata, for example). Serverside stream > dump doesn't seem terribly important - but if it's something you care > about, adding it should be easy. Patches welcome. This is a convenient feature, used by me & other live streamers to archive

relaying a shoutcast stream via icecast2 is pretty much unlistenable -- it constantly stutters. for example, shoutcast relay -- http://205.188.234.1:8030/listen.pls icecast2 relay -- http://liveradio.indymedia.org:8001/sf-hifi.mp3.m3u --mark --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

well, don't get me wrong, I am not generally opposed to progress, but speaking as a coder of source clients, providing yet another authentication mechanism is a bit frustrating.... I guess it wasn't too bad having to deal with Shoutcast/Icecast/Icecast2 specific connection protocols (yes they are ALL different!) but I am NOT going to support Shoutcast/ICecast/Icecast2 (ICE

btw i just noticed that the icecast2 relay sounds fine in whamb (mac os x mp3/ogg client). so it does seem that some clients don't have the problem. here's the relay configs we're using: <relay> <server>server.to.be.relayed</server> <port>8000</port> <mount>/</mount>

oddsock wrote: > yep, it's in there...you give it a master server ip and port and the > relay functionality will connect to the master server and relay all > connected mountpoints. cool > yep, Michael added that a bit ago...Shoutcast style streaming titles (or > any streaming titles for that matter) is not supported however. You > will now need to provide a

Greetings, I have some confusion. I've seen it mentioned, somewhere in some docs, that Icecast2 does not (as yet) support Push relaying. Is this actually the case? Should I be looking at icecast1 (which does support push relay, I believe) until such capability is implemented on icecast2? Or should I be creating a combination of both? Or what? Here's my situation: I have a customer

Hi all there. I am trying to set up an icecast2 server (wich is already running) to send some stream mount point to another server. I mean, my server is streaming at /radio1.mp3 mount point. We can listen it at http://myserver:8000/radio1.mp3; so, i want to know if is there any way to "clone" that strem and send it to another server, such as http://giss.tv:8000/radio1.mp3 I have been

To all: I am running FreeBSD v7.03 and using icecast2 which is happily relaying a shoutcast MP3 stream. I want to play (mix)a pre-recorded "Stream ID" file to the existing stream once per hour. I've tried ices0 but no luck. Any help will be much appreciated. Mike

Leo Currie wrote: > Greg Trounson wrote: > >> Gidday, >> >> I have a winamp 2.95 source that cannot upload the stream to my >> icecast server. > > > I'm assuming you're trying the Nullsoft Shoutcast DSP plugin. That's the one. >> Since icecast is compatible with shoutcast surely a winamp source >> should be able to connect? >

Hi, I just updated my CVS copy of icecast2, and saw that the default login protocol now is HTTP basic authentication, which ICE/1.0 still selectable through the config file (by inserting an <icelogin>1</icelogin> element). My question is: what is the intended future login protocol for icecast2? Will ICE/1.0 be phased out in favour of HTTP basic auth? <p>Akos --- >8

gtgbr@gmx.net wrote: > Aaron Gaudio wrote: > >>Where is it released? Telling me I have to set up cvs to download > > > http://www.xiph.org/~msmith/ > > This has been said before. This is no good. This is by far not the first time someone has pointed out, that icecast2 is not mentioned _anywhere_ where one would expect to find it. By this I mean locations like

At 11:00 PM 8/19/2002 +0200, you wrote: >I'm inquiring about some possible features of icecast2, that are important >to me: > >- stream relay yep, it's in there...you give it a master server ip and port and the relay functionality will connect to the master server and relay all connected mountpoints. >- server side stream dump this is not in there. >- mp3 streaming

icecast2 is a broadcast server and will broadcast both ogg vorbis and mp3 streams. This assumes that you have a source client which can produce an ogg vorbis and mp3 stream and send it TO an icecast2 server. With mp3 streams, shoutcast mp3 metadata is supported, however you cannot use the shoutcast DSP as a source stream to an icecast2 server. Current clients that we know about that can

I am trying to relay a streamtuner Live365 stream across a ssh tunnel to a remote XP pc, where I would pick it up using winamp. I have a similar setup with a non-live365 stream routed using streamripper to port 9001 and this plays correctly in winamp For my Live365 stream, I have a RealVNC root session that is streaming the Live365 broadcast from streamtuner (using XMMS). I can see XMMS playing

Hi, Just wanted to clarify, can icecast2 not read OR broadcast any mp3, or can it just not broadcast mp3 (but still play from a playlist)? I know the quality would be dropped if it had to reencode them though. And what's up with that POS Winamp3, it doesn't even play gg streams?!? I use xmms, but we have winamp3 on a demo computer, it just sits and keeps prebuffering. I need something

Thanks for the prompt reply Thomas, Well as an amateur, and newbie, I would not know reading logs does not mean anything to me as I have no idea what it means when I can actually find them, this is why I am so confused. Not too sure how to check the logs, maybe obvious to some, but alas I'm not quite acquainted with the walking yet. I have searched for a very long time with issues

Hello, I really don?t know if this question is already been discussed, what I say is that is about 5 days that I can?t find any solution. the problem is that icecast2 works only locally, I am not able to connect remotely. Now I?m going to explain: on ubuntu 12.04, I installed icecast2 with: apt-get install icecast2 it is not the latest version, since I see here there is the 2.4. anyway, I

I can understand wanting to boost the adoption of Xiph codecs, but I think restricting the directory to vorbis streams only will not help this endeavour. I can imagine it will just piss a lot of people, including myself, and give Xiph a bad name. I get very few listeners of my AAC+ stream now since this occured. The restriction is not an insentive to switch to Ogg Vorbis at all. The incentive

I thought the YP code was going to be fixed to use less resources so it could be used with other stream formats. It seems to be taking a long time. As it is now, Icecast2 is not a good solution for those wanting to be on a popular directory. I am forced to recommend using Shoutcast to my clients so they can get onto a popular directory. I would prefer to recommend Icecast2. Ross Levis.

Hello, Is there a way to touch Shoutcast directory with an Icecast server ? Is for a mp3 stream. The server is already serving ogg stream but our foundation got a new member that did not know about ogg, and he needs time to encode his tracks to ogg, and then we should temporarily relay his mp3 stream, but we want to be dired by SC directory ... How to ? :-) -- ASPO Infog?rance