search for: ici

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

hi list this is as probably more of networking problem than an icecast problem but it is related - hope people don't mind. I've been running tests for a project that starts 20 August. I'm sending stream from my audio software to a local icecast server, then relaying this to a commercial shoutcast service. Initially i was using 7000 for the relay port. Worked fine. Then one morning

THAT was it! Both ones work, so I think I'll stick to the last one. Now the KiSS will connect to the IceCast2, and I have enabled the metadata again without problem. Thank you very much! Henrik ?stergaard Henrik Ostergaard Madsen wrote: > It did unfortunately not change anything.. Except that the track titles > disappears in WinAmp (as expected). > > As the player was able

Scott, > Thats what i do.. just relay. Exactly how are you doing it, and what software are you using (shoutcast version / icecast 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

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

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

...deo TS. > > To play this requires specific support, and it also needs to know about > the embedded metadata, which once again, contrary to popular belief, ICY > metadata IS NOT ID3vX. > > ICY MP3 streaming is similar, although becoming less and less relevant > because of low efficiency MP3. > > > > There are a number of Flash Players that can play ICY/FLV formatted > streams within browsers, including metadata, but with Flash being the > security nightmare that it has become, this is another problem for ICY > compatibility. > > > > /greg. >...

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:

Hi - I'm using Icecast to stream some audio that I embed in an <audio> tag on a webpage. This is working great for desktop browsers and on iOS, but it doesn't work on Android. It looks like Chrome mobile sends the header "Range: bytes=0-1" and then doesn't try to load any more data when Icecast responds with a 0 byte "HTTP/1.0 200 OK" response. From my

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 >

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:

> Thanks for the network dumps. As you say, it's weird because Flash, even > when embedded, can access the stream of Icecast2. I already noticed it by > analyzing Icecast2's logs as I wrote in the first message of this topic. > There is something I couldn't see in the network dumps: is the embedded > flash DOWNLOADING the stream even if it doesn't play it (with

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

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 >

Hello, I have a request for an additional header. This header is needed to inform the client of the burst it is going to receive. Why ? This header could be very usefull for the streaming-client to have an idea of it's delay, 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

Hi all: I'm looking at some of the features in SVN Icecast, particularly 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

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 index

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>

Im running in a chroot'd environment: RH 9.0 lame-3.93.1 icecast-2.0.0 LiveIcePatched-1.0.0 xmms-1.2.7 I was able to get icecast running on port 8000, I was able to get liveice compiled and can see the .so file within xmms. Im pretty sure I have xmms configured to match my icecast config(passwords and mount points for source match). When I start up xmms I get the following error in my