similar to: ICECast in Flash / IEWin

I'd like to resurrect this orphaned thread: http://lists.xiph.org/pipermail/icecast/2003-December/006139.html We're using the embedded flash player for listeners of pulverradio.com and can't use 2.2 for relaying from our encoders. Apparently we can use Icecast v1.3 Although this is clearly a problem caused by ActiveX and Microsoft boneheads that is a mountain that may prove

Alternatively you can just script the window media player control, and bind it to your stream, that should work just fine, assuming you have my directshow filters installed. Zen. ----- Original Message ----- From: "Michael Smith" <msmith@xiph.org> To: "Ian Andrew Bell" <hello@ianbell.com>; "icecast" <icecast@xiph.org> Sent: Monday, October 18,

I also tried installing Icecast 1.31 ... the config file claims its relaying capabilities aren't very well tested and I can verify this. But now I'm concerned that even 2.0 won't work for me in relaying. I'm trying to relay multiple streams from a cluster these hardware encoding devices: http://www.audioactive.com/products/realtime_enc/rte_ovw.html ...to do so you

I've been working with AudioActive the last couple of days to fix their behaviour... looks like they're going to update their firmware EPROMs. What are the chances that Michael's fix below could be incorporated into a future version, so that all those boxes without the Firmware upgrade will work? -Ian. <p>On 10-May-04, at 7:20 PM, Michael Smith wrote: > On Tuesday 11

Now that 2.2.0 is out, we can update metadata on-the-fly. At pulverradio.com we are working on an injector that takes the song info from our broadcast automation software and dumps it in (thanks guys for the help). I realize that we can inject the song info like so: http://server.ip:port/admin/metadata?mount=/ mountpoint&mode=updinfo&song=ACDC+Back+In+Black .... but are there

Doesn't work so well on Mozilla or anything other than IEWin... and I'm worried about using lots of extra software. Thanks for the suggestion tho. -Ian. On 18-Oct-04, at 6:46 AM, illiminable wrote: > Alternatively you can just script the window media player control, and > bind it to your stream, that should work just fine, assuming you have > my directshow filters

On Sunday 17 October 2004 07:16, Ian Andrew Bell wrote: > I'd like to resurrect this orphaned thread: > > http://lists.xiph.org/pipermail/icecast/2003-December/006139.html > > We're using the embedded flash player for listeners of pulverradio.com > and can't use 2.2 for relaying from our encoders. Apparently we can > use Icecast v1.3 > > Although this is

Hello, I'm using a flash player. First It didn't work with icecast 2. The blocking difference between icecast 1 and icecast 2 is that icecast 2 don't send the Content-Length header. So, I made a small PHP proxy and now Flash works very well with icecast 2. Other solution is to add this header in the icecast 2 source code and compile it, but I don't have time to test. My

As a follow-up to this thread: http://lists.xiph.org/pipermail/icecast/2004-May/007171.html ... I am still attempting to relay effectively from two separate Audioactive encoders via an icecast server. Since we last discussed this Audioactive have updated their firmware to comply to the standards for MP3 streaming more explicitly. And according to Michael Icecast was patched to be more

Hello, Michael Smith <msmith@xiph.org>: > > We don't sent a content-length header because there's no way to know the > content length in advance - it's a stream, after all! I kown this, after more than 1 hour the flash player stop to play. But during 1 hour It's possible to listen music, better than hearing nothing. > > So, I made a small PHP proxy and

On Tuesday 02 November 2004 03:13, Ika OSCAOS wrote: > Hello, > > I'm using a flash player. First It didn't work with icecast 2. The blocking > difference between icecast 1 and icecast 2 is that icecast 2 don't send the > Content-Length header. > We don't sent a content-length header because there's no way to know the content length in advance - it's a

I have a situation where I'd like to be able to have icecast reach out to another icecast server as a client. Is this possible with relaying? From what I read relaying and master relaying both have the server reach out to another server. The reason is this. I have a hardware encoder (Telos audioactive) sitting on a cablemodem. I have a remote provider (streamcheap or something) set to

Like any other major radio station we output our music from automation software via analog audio through a mix board in a studio, where we insert other stuff like live DeeJays, etc. only to have that stream re-encoded by hardware MP3 encoders for distribution to our network of IceCast servers. The chain of song information gets broken as soon as we output from the Automation software,

Just wanted to let everyone know that we are prepping for a 2.2.0 release of icecast. Just as before, we are doing Release candidates first, and if no bugs are reported, these will become the official release. We ask that anyone that can, please test the RC and send any issues or bug-reports to the mailing list or http://trac.xiph.org/ until the mirrors get updated, please download the release

On Fri, Dec 17, 2004 at 10:00:19PM -0300, Mr Dihelson Mendonca wrote: > The problem with Icecast OGG system is that common > people doesn't want to download any other software in > order to listen to a radio station, even a plugin... Of course. But that's not the whole story. Microsoft only supports MP3 because so many people listen to mp3 radio stations and files. And before

This is killing me... I've tried everything I can think of, but Icecast still crashes if I define more than 10 listen-socket ports. Is there a limit that's not documented or is this a bug? I'm using the latest Windows build that OddSock compiled. Thanks for any help/ideas Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Tuesday, July 19, 2005

the interleaved metadata is only sent by clients requesting it (icy-metadata: 1 in the request header) and by default is not sent...if you are receieving metadata in a stream that you don't expect to, you'll most likely just hear blips in the stream.. oddsock At 05:33 PM 12/1/2003 +0000, you wrote: >On Mon, Dec 01, 2003 at 03:56:09PM +0100, Macsym wrote: > > > Serving a

Sending again .... is this thing on? On 11-Feb-05, at 9:20 PM, oddsock wrote: > At 10:21 PM 2/11/2005, you wrote: >> Now that 2.2.0 is out, we can update metadata on-the-fly. At >> pulverradio.com we are working on an injector that takes the song info >> from our broadcast automation software and dumps it in (thanks guys >> for >> the help). I realize that we

yep, they simply forward the bitstream to icecast. And in general, bitrate changes are handled by most listening clients, although very few I have found (if any) can handle samplerate changes appropriately. oddsock At 10:03 AM 9/14/2004, you wrote: >You mentioned these programs and their "no-reencoding" mode. Can they >handle collections of MP3s of different bitrate? >

At 10:21 AM 12/20/2004, you wrote: >Great Job ! ;) >Are you planning to : >- correct the metadata problem when you're relaying an icecast v1 server ? >(our radio totaly depend on icecast v1...) we don't support icecast 1.x. The question is, why are you dependent on it ? >- add an option to enable backup streams only when the primary one is done >? I mean that if a