similar to: intended login protocol for icecast2

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

At 12:24 AM 8/18/02 +0200, you wrote: >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

Hi: On Thu, 22 Aug 2002, Moritz Grimm wrote: > P.S.: While installing Icecast2 myself once again today, I noticed that > the current reference icecast.xml lacks the new <icelogin> directive, > which also can be either 0 or 1, and is 0 by default. If you want to use > a source client that doesn't support http basic auth yet, like Oddcast > DSP RC5, you have to add

You can use oddcast DSP (www.oddsock.org) ml On Friday 11 October 2002 06:56 pm, Richard wrote: > Help! > we're trying to set up an online radio station for Columbus day here > in Denver and can't seem to find a good working streamer for a windows > machine! Icecast2 works fine when I use the ices2 streamer on the same > linux box. What do you recommend - winamp plugin

The ice-* headers are the standard protocol for connecting to icecast2, the trouble is making all source clients adhere to the standard. The option is to be very militant about it, and basically deny any source clients that do not connect with the ice-* headers , but we chose the more compatable route...although there is a limit to this compatability....I would strongly urge darkice to use

yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote: > On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3

Hi, I'm trying to adapt darkice to the current state of icecast2. As I see, there is a possibility to stream in various formats, by specifying a Content-type field on the source header. When I try to log in with an mp3 source, I get a seg fault from icecast2. The connection looks something like: SOURCE /mountpoint ICE/1.0 Content-type: audio/mpeg ice-password: password ice-bitrate: 96

i saw that mail from a mailing list. http://article.gmane.org/gmane.comp.audio.icecast.general/748 I have the same problem as that guy . everything seems OK but ODDCast2 cannot connect to Icecast2 via Winamp3 . but where do you put the <icylogin> </icylogin>. I guess i have to turn it to 0 cause i use icecast2 . <p><p><p>--- >8 ---- List archives:

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

Thomas, this was the right tip (Danke!). Thomas B. Ruecker schrieb: > Tillmann A. Basien | ToolBox Solution GmbH schrieb: >> I am using Darkice 0.17.1 and Icecast2 2.3.1 >> >> >> Darkice cannot talk to icecast, and I have no idee about there reason: >> >> Logentry on icecast server side: >> [2009-04-29 16:48:49] EROR connection/_handle_connection

I am using Darkice 0.17.1 and Icecast2 2.3.1 Darkice cannot talk to icecast, and I have no idee about there reason: Logentry on icecast server side: [2009-04-29 16:48:49] EROR connection/_handle_connection HTTP request parsing failed config for Icecast is a standard mount which works with ices. config for darkice is: [icecast-0] bitrateMode = vbr # constant bit rate bitrate

Hi there, I?m a bit stuck, not sure if I should be configuring the icecast.xml, or if I?m doing something wrong in the darkice.cfg. Works perfect streaming from its self, but as soon as I add a shoutcast stream, it breaks ? commenting out the icecast section in darkice.cfg I have tried various combinations of configurations with no luck. I am testing the possibilities in streaming to an on-line

oddsock wrote: > 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

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

A question to icecast2 developers: is there a possibility to have some sort of user feedback in icecast2? I'm thinking of having a client that would send some info back though the same socket it receives the stream. If no such feature currently exist, where should I start to implement it? Thanks, <p>Akos <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast

On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is >

According to what I've read on this mailing list, it should be possible to stream MP3 data to icecast2 using ices-0.2.3, which I assume also should be the case for any other streaming client based on libshout1. So I decided to test this out to see if we really could dispense with icecast1 altogether on the server I help administer. My results were not promising, to say the least. I wiped out

I'm inquiring about some possible features of icecast2, that are important to me: - stream relay - server side stream dump - mp3 streaming alongside Ogg Vorbis which of these are going to be in the upcoming beta? another question: how and what stream metadata can be set when using icecast2? <p>Akos --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project

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

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