search for: icy

At 04:30 PM 7/8/2003 -0400, you wrote: >On Tue, Jul 08, 2003 at 03:10:25PM -0500, oddsock wrote: > >Already checked that. this is the HTTP header for the stream: > >Content-Type: audio/mpeg >icy-bitrate:16 >icy-description:SF Indymedia >icy-genre:Talk >icy-name:Enemy Combatant Radio >icy-public:1 >icy-url:http://sf.indymedia.org/ >Server: Icecast 2.0-alpha2/cvs what source client is generating that ? The icy-* header that icecast is looking for is icy-pub, not icy-public...

.../10/05@22:31:41> [source] creating relay socket <08/10/05@22:31:41> [source] resolving relay host <08/10/05@22:31:42> [source] relay host gave success (HTTP/1.0 200 OK) <08/10/05@22:31:42> [source] relay from beijing.zhongshuo.org established. <08/10/05@22:31:42> [source] icy-name:Zhong Shuo: Stories From China On Change ; icy-genre:Talk World Asian Chinese <08/10/05@22:31:42> [source] icy-pub:1 ; icy-br:32 ; icy-url:http://www.reverberant.com/cw <08/10/05@22:31:42> [source] icy-irc:N/A ; icy-icq:N/A ; icy-aim:N/A <08/10/05@22:31:44> [dest: 205.188.234...

...be worth looking at > the differences in communication between the two cases. I include the latest > not-working IceCast dump (no metadata) and the working Shoutcast dump. it could be the OK header that it's not liking, the icecast headers are HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br:128 ice-audio-info: bitrate=128 icy-description:Mixed files of all kinds icy-genre:All icy-name:Radio Ostergaard icy-pub:0 icy-url:http://radio.home.ostergaard.net/index.php Server: Icecast 2.3.1 the shoutcast ones are ICY 200 OK icy-notice1:<BR>This stream requires <a href="htt...

...st version / what streaming software are you using)? I'm running icecast 1.3.10, shoutcast 1.8.0, and irpd 0.16 to stream. When I try to relay from shoutcast to my main icecast server, I get the following: <03/15/01@22:38:06> [main] dns thread starting <03/15/01@22:38:06> [source] icy-name:AniAniAniAni ; icy-genre:Alternative <03/15/01@22:38:06> [source] icy-pub:1 ; icy-br:0 ; icy-url:http://hourfollowshour.org <03/15/01@22:38:06> [source] icy-irc:N/A ; icy-icq:N/A ; icy-aim:N/A <03/15/01@22:38:07> [yp_add] yp.shoutcast.com gave error (nak) <03/15/01@22:38:0...

At 03:58 PM 7/8/2003 -0400, you wrote: >That isnt the only bug. One one of our icecast servers the third >stream, sf-lofi.mp3, is not being announced to YP servers at all. On my >local diagnostics (logs all connections to the liveradio.indymedia.org >YP server) I see that icecast isnt even trying to add it. The other YP >servers are not showing this stream either. It doesnt

Hello - ICI Real Estate Agents, Brokers, Landlords, Commercial/Industrial Tenants, and Investors. - Add Listings to our Industrial Commercial (ICI) database - NO COST! - We will register your home page with 244 search engines - NO COST! - Need a home page? We'll create & host one for you - NO COST! The ICI EXCHANGE (http://www.torontoici.com) is a world class online interactive

On Friday 21 November 2003 13:17, Dave St John wrote: > Anyone know of the correct header that are sent to the icecast2 server? > > example the ones sent to a shoutcast server are > icy-name:whatever station > icy-genre:Industrial, EBM, Electronic > icy-pub:1 > icy-br:256 > icy-url:http://www.mediacast1.com > icy-reset:1 > > just need to know what the equivelant is for icecast2. The same. ice-* or icy-* headers from the source are forwarded as-is to the list...

...s concerning non-standard request headers which is required in order to get the embedded metadata. A patch for ice cast to allow this however is quite possible, perhaps a config directive that tells icecast not to wait for the specific request header and send the embedded metadata regardless of the icy-metadata header will be a nice option. In JavaScript it should be quite possible though. Also, as for “not all browsers support the icy http streaming protocol.” Never had any troubles playing icecast streams in any browser, it really depend on the browsers audio encoding support rather then the “p...

I've attached a small patch against icecast 2 which converts ice- headers to icy- headers for clients that include icy- headers in their request. This allows a few clients (notably xmms) to pick up stream info they otherwise miss. -b -------------- next part -------------- Index: src/format.c =================================================================== RCS file: /usr/lo...

...Encoding: gzip, deflate, sdch Accept-Language: en-US,en;q=0.8 Range: bytes=0-1 Response: HTTP/1.0 200 OK Server: Icecast 2.4.2 Date: Thu, 10 Dec 2015 01:23:11 GMT Content-Type: audio/mpeg Cache-Control: no-cache Expires: Mon, 26 Jul 1997 05:00:00 GMT Pragma: no-cache Access-Control-Allow-Origin: * icy-br: 32 ice-audio-info: bitrate=32;channels=1;samplerate=44100 icy-description: Description icy-genre: None icy-name: mount icy-pub: 0 icy-url: https://host/ Is there a quick patch to disable range support, or a place you can point me to in the code that might be causing this behavior? ______ Andre...

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add > <relay-shoutcast-metadata>1</relay-shoutcast-metadata&...

Hi again. I just compiled icecast 2. It seemed ok but at the end I got this: /usr/bin/ld: warning: libcom_err.so.2, needed by /usr/lib/libcurl.so, may conflict with libcom_err.so.3 Is this anything I have to take care of? Can you explain what it means? Thanx, Luke <p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

...of the failure. I'll try installing mozilla and downloading the plug-in. --------------- SUCCESSFUL 2.0 stand alone ---------------------- GET /live HTTP/1.1 Referer: http://192.168.0.242:8000/live User-Agent: Shockwave Flash Host: 192.168.0.242:8000 HTTP/1.0 200 OK Content-Type: audio/mpeg icy-bitrate:0 icy-description:publicvoice.fm online radio icy-name:Streaming with MuSE icy-public:1 icy-url:http://publicvoice.fm Server: Icecast 2.0-alpha2/cvs ------------------------------------------------------------------ --------------- UNSUCCESSFUL 2.0 embedded ------------------------ GET /li...

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 detail...

...ay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is > unlikely, though - that code hasn't been changed lately AFAIK) Or connect via telnet and see what's really going on ;-) HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br: 64 icy-genre: Talk icy-metaint: 8192 icy-name: Enemy Combatant Radio icy-notice1: <BR>This stream requires Winamp<BR> icy-notice2: SHOUTcast Distributed Network Audio Server/FreeBSD4 v1.9.2<BR> icy-pub: 1 icy-url: http://sf.indymedia.org/ Server: Icecast 2.0-alpha2/cvs Yes, i...

...and (much more important) to be able to do early-on streaming. The question is not on how to implement this in code (probably send the header in the "format_prepare_headers" routine). The question is how this header should be formatted ? Should it be (most likely) something like: "icy-burst-size:262144" (for a burst buffer of 256kB) or something like: "icy-burst:20000" (for a burst of 20 seconds) - This looks somewhat like Microsoft-WMA servers notifies it's clients for bursts. If you do not wish to implement this feature, could you be so kind to define the...

...articularly the ability to reclaim fallbacks. This feature would be very useful for a project I work with, and could see us switching to icecast from Shoutcast compatible technology. One problem arises, however. Some of our broadcasters use the legacy Shoutcast DSP plugin, which can only perform ICY-style connects. My problem arises from the fact that icecast will automatically create a new mount point for every concurrent ICY connection received. This has two side effects. Firstly, it means that an ICY source is always allowed to conect, unlike those using the icecast 2 standard who obviou...

As proposed in #2272, this renames the mount specific mp3-metadata-interval to icy-metadata-interval to prevent confusion about what it does (setting the icy metadata interval) and to make clear it's not mp3 specific but ICY specific. --- src/cfgfile.c | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/src/cfgfile.c b/src/cfgfile.c ind...

Hi does anyone have any luck playing radio streams using internet explorer Only our station plays no problem using firefox crome and edge but will not play in IE www.tafn.org.uk/listen we are broadcasting using aac Mark. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20171015/abe14432/attachment.html>

...t Got command (listmounts.xsl) [2004-02-14 09:40:23] DBUG admin/command_list_mounts List mounts request [2004-02-14 09:40:23] DBUG admin/admin_send_response Sending XSLT (/share/icecast/admin/listmounts.xsl) My access.log contains 192.168.1.21 - - [14/Feb/2004:09:26:57 +0000] "SOURCE / ICY/666" 401 115 "-" "-" 0 192.168.1.21 - - [14/Feb/2004:09:31:06 +0000] "GET /admin.cgi HTTP/1.0" 404 109 "-" "liveice-xmms" 0 192.168.1.21 - - [14/Feb/2004:09:31:06 +0000] "SOURCE / ICY/666" 401 115 "-" "-" 0 192.168...