similar to: New feature : peercasting / anonymous relay / burst

We found an interesing issue that after a downed publishing point is restored, the fallback relay doesn't stop relaying. We've tried everything, but once /asf2 or /asf3 is envoked for /asf1 fallback reasons, they don't stop relaying their source streams even though the output stream /asf1 has returned to normal. Eventually we end up with /asf2 relaying indefinately with no

Hello, I'd like to setup something similar to dir.xiph.org on a lan. The goal is simply to show users what radios are currently available. The documentation explains how to configure the peercast server for being referenced on yellow pages, but there is nothing about the yellow pages server. So, is the source for dir.xiph.org available for this? Thanks for your help!

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

At 08:24 AM 2/15/2005, you wrote: >Sending again .... is this thing on? sorry, meant to respond, been very busy of late.... >On 11-Feb-05, at 9:20 PM, oddsock wrote: > >>no...at the moment, only "song" is supported. All other stream info >>details (URL, Genre, etc) is not currently update-able via the admin >>interface. The must be supplied by the source

Hello List Having great trouble relaying an icecast2 mp3 stream to a shoutcast server. My client program successfully streams to icecast which is listening on port 7000. I can listen to this stream with mozilla and xmms with no problems. I can also stream my client directly to the shoutcast server but it makes the client unstable (which is why i'm attempting a relay). The shoutcast server is

My listeners connect to a publicly accessible Icecast server with the config below. Between broadcasts it uses a fallback mp3, which loops. During broadcasts it relays from a local Icecast server that I broadcast to (config also below). I am aiming for approx 30-45 seconds buffering, as the connection from public to local icecast server is 'less than ideal'. The set up is working fine

Greetings: I use Icecast 2.4.0 on Windows 8.1. I have a config file which sets up roughly a dozen relays to connect on demand. My typical use is to connect to 1-4 of the streams simultaneously. All connections are either via WinAmp to 127.0.0.1 or via other clients on my LAN. My intent is to leave the connections active for up to 72 hours. When I connect through my relays, eventually the

https://bugzilla.netfilter.org/show_bug.cgi?id=1306 Bug ID: 1306 Summary: burst packets becomes burst bytes Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at netfilter.org

I know this isn't exactly concerning Icecast, but PeerCast shares some similarities nonetheless... Is there anyone who would be willing/capable to code a streamlined Ogg Vorbis decoder for inclusion with the PeerCast client? The only thing preventing Ogg Vorbis from wide use is the many software players that still don't support it (Real, WiMP, MMJB). Since people have to download

Thanks Karl- Setting the burst-size to 0 does indeed disable Burst-on-Connect. FYI: I have verified that disabling Burst-on-Connect allows VLC Player to play Icecast2 streams. I am notifying the VLC developers of this, so hopefully they can support Burst-on-Connect Icecast2 streams. SHOUTcast burst seems to work just fine, so maybe it won't be such a big problem to fix. Any other

I am trying to narrow-down a problem with VLC Player and I would like to temporarily disable burst-on-connect. I have set this to 0, but it doesn't seem to disable. <burst-on-connect>0</burst-on-connect> <burst-size>65535</burst-size> http://stream.orban.com:80/eval Any ideas? Thanks. -greg.

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. I''m using the following filter from lartc "ultimate PPP" example: tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \ 0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1 It works fine, but when I remove the "burst 10k", I receive the following error: "burst" requires "rate". Illegal "police"

Hi. I am running the as.ltraj () function in adehabitat (v 1.4 under R 2.2.1) but can't seem to correctly specify the burst argument. i.e., the ltraj object returned consists of only one component, when in fact my data consist of more than one burst of reloctions per animal. i've set up the data (xy, date, id, burst) in list form following the example given in ?as.ltraj. to simplify,

All: Does anyone know what the burst and cburst parameter do? My understanding so far: * I see a lot of different definitions on the web. It seems like burst is the number of bytes sent before serving other queues/classes. So if burst was 1000 bytes and class rate was 100kibit per second. It would send 1000 bytes each time the scheduler service that queue to a rate of 100 kbit per

My test case must relative with burst traffic such data or real time traffic somebody can advise me how to generate traffic data like ICMP to be burst and about real time traffic too ,.. i don''t have any idea to make burst traffic for test HTB and HFSC which can manage that situation good. Express yourself instantly with MSN Messenger! MSN Messenger Download today it''s FREE!

I am trying to determine exactly what the difference in Burst-on-Connect is between SHOUTcast and Icecast2. There are a number of players that are having difficulty with the Icecast2 Burst-on-Connect feature. To determine where the problem might be, I tried to lower the burst-size to 32768, but doing so will not allow sources to connect to the Icecast2 server. Anyone know what accepted

I am trying to determine exactly what the difference in Burst-on-Connect is between SHOUTcast and Icecast2. There are a number of players that are having difficulty with the Icecast2 Burst-on-Connect feature. To determine where the problem might be, I tried to lower the burst-size to 32768, but doing so will not allow sources to connect to the Icecast2 server. Anyone know what accepted

On Sun, 2005-01-02 at 14:20, Greg J. Ogonowski wrote: > I am trying to narrow-down a problem with VLC Player and I would like to > temporarily disable burst-on-connect. I have set this to 0, but it doesn't > seem to disable. > > <burst-on-connect>0</burst-on-connect> this is just a compatibility option for some pre 2.1 setups, the following option is overriding

some body can advise me about how to create burst traffic two type is 1. ICMP burst traffic (i need to create general and normal data burst traffic but i don''t have any idea to do it) 2. Real time traffic (i think may create by open real-time streaming with a big file from real-time server but i don''t sure it will work!) thank you raku