similar to: icecast2 <relay> issue

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>

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

Hello again: Though you suggested in subsequent reply email that the problem may sit with the SAM2 Broadcaster application I done some additional testing and wanted to run the results by you. I am able to reproduce the problem and see what I would consider odd activities on the Icecast2 windows application. Here goes: 1) Connect and start one stream from SAM2 --> Icecast2 2) Connect

Darrel, Thanks for the help. I'm presuming then that I've misunderstood what is meant by "pull" vs. "push". I understood, I guess erroneously, that the context of 'push' relaying was from the perspective of the icecast2 receiving a 'pushed' stream. I believe now that I have this backwards, and that the context is from the part of icecast2 not being

Good morning, On Thu, 2015-11-19 at 12:54 +0200, Theodotos Andreou wrote: > Hello to all, > > I am a newbie to Icecat2. I already know how to use darkice as a source > but I can't find any information on how to relay a udp multicast stream > like "udp://239.192.0.145:5000 for" example. Can icecast2 stream this > directly or do I need to use some source client?

Greetings, Ok, success. I understand now that what I thought was a relaying server was actually a source client. This was not really clear and caused me a great deal of confusion. My fault.... <must remember to remove head from posterior prior to project commencement> However, I found something interesting that needs to be documented. I was using a password of radi0 with the source

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 guys, There's a transcoding example using liquidsoap in our cookbook here: http://liquidsoap.fm/doc-1.3.2/cookbook.html Hope that helps! Romain 2017-09-05 10:30 GMT-05:00 Jordan Erickson <jordan at coolmic.net>: > Hi Robert, > > Icecast itself doesn't do any resampling of audio streams it receives. > One would likely craft a solution that listens to the original

Hello to all, I am a newbie to Icecat2. I already know how to use darkice as a source but I can't find any information on how to relay a udp multicast stream like "udp://239.192.0.145:5000 for" example. Can icecast2 stream this directly or do I need to use some source client?

Hi Robert, Icecast itself doesn't do any resampling of audio streams it receives. One would likely craft a solution that listens to the original stream and re-encodes on the fly, providing those alternate bitrate streams back to Icecast. I've heard people doing this with liquidsoap and other source clients, and a bit of server-side magic. Some quick Googling provided me with this link

Geoff you are a genius! I have been at this for soooo long today and you are spot on with the solution. I had a feeling it would be something simple! thanks a lot :) Andy ----- Original Message ----- From: "Geoff Shang" <geoff@hitsandpieces.net> To: <icecast@xiph.org> Sent: Tuesday, April 05, 2005 1:53 AM Subject: Re: [Icecast] Using alias to relay Icecast2 to shoutcast

Dan, Thanks for responding. On Mar 23, 2005, at 11:28 AM, Dan Stowell wrote: > On Thu, 24 Mar 2005 01:26:59 +1000, Geoff Shang > <geoff@hitsandpieces.net> wrote: >> Chuck Tellechea wrote: >> >>> What I'm thinking of doing now, is to running an instance of either >>> icecast1 >>> or shoutcast, on the datacenter server, to receive the

On Thu, 24 Mar 2005 01:26:59 +1000, Geoff Shang <geoff@hitsandpieces.net> wrote: > Chuck Tellechea wrote: > > > What I'm thinking of doing now, is to running an instance of either icecast1 > > or shoutcast, on the datacenter server, to receive the 'pushed' broadcast > > from the Nicecast running on the G5 at my customer's office/studio. > >

i don't think anyone has really answered his question yet, so i'll give it a shot. from what you have said i think you are misunderstanding something. the customer that is running nicecast does not need any kind of server on his machine, all he would have to do is tell nicecast to stream to your server as for the archived content, all thet would be required is to run ices on the server

I understand there are two types of relays in icecast2. The master relay which relays everything from a source and a point relay which relays a specific mount point from a source. I have a server which has 3 streams. I want to relay 2 of them. How can I do this? Can I define two relays and two mountpoints within the xml config file? Do i do this in the same relay tag: <relay>

On Wed, 23 Mar 2005 16:46:57 -0500, Chuck Tellechea <chuckt@tellechea.org> wrote: > Greetings, > > Ok, success. I understand now that what I thought was a relaying server > was actually a source client. This was not really clear and caused me a > great deal of confusion. My fault.... <must remember to remove head > from posterior prior to project commencement> >

I'm relaying an icecast1 mp3 stream with icecast2. This works fine, and the song title is displayed correctly no matter if I use <relay-shoutcast-metadata>1</> or not on the relay. But, the stream name and other metadata provided by ices0 on the icecast1 server is not displayed in the listening client. Icecast1 source: [Id: 1] [Sock: 11] [Time of connect: 09/Aug/2004:10:01:24]

> What machine are you running (namely what OS)? Debian. > I dont understand your approach. > Why running a 'streamer' behind a nat? > Not enough 'resources' to rent/ rent to buy a ded. Server? > Mean, can't expect to satisfy a lot of listeners this way. :-) I am listening the Muazkhan indications XD: > > Hi Muaz Khan, >> We are adtlantida.tv and

El mi?, 30-07-2014 a las 21:41 +0200, Simone Dal Maso escribi?: > Hello, > first of all thank you for your patience and having answered you. > I tried to change port from 8000 to 8001 but nothing happened. I am > using a vps server so I don?t need to open port from router. > I paste here all my icecast.xml configuration file. > can you please give a llok and tell me if all seems

Hi there, I have a Debian sarge 512 MB RAM machine with icecast2 and ices2 that I installed via aptitude. I have a 3MBit/s download and 800KBit/s upload link. I would like to configure icecast2 and ices2 properly. Here is my situation: 1)I have a dtdns address omac.darktech.org 2)icecast2 and ices2 on port 8000 would be fine. 3)I simply want to broadcast my 6 year old niece's voice which