search for: narrowcast

We're abusing icecast in a true narrowcasting setup (personalized stream per mountpoint). The streams itself are created in a piece of proprietory (spelling?, i'm dutch) software, icecast merely relays them. However, the intended endpoint is an embedded device. This device has trouble with tcp/ip packets not matching the max. packet si...

Hi Henri and others, Very interesting post about TCP_CORK. I would be very interested in having it applied in the next version of Icecast. I'm using Icecast in a somewhat narrowcasting setup with large numbers of sources (> 100) and between 5 and 50 listeners per source. All streaming is done at low bitrates (16 - 24 kbit/sec) and listeners use embedded devices connected by 56k modems. It is therefore very important to have efficient use of available bandwidth. For low-bit...

...lijk bericht----- > Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens Henri > Zikken > Verzonden: zondag 25 december 2005 15:05 > Aan: icecast@xiph.org > Onderwerp: [Icecast] Use of TCP_CORK instead of TCP_NODELAY > > > We're abusing icecast in a true narrowcasting setup (personalized stream per > mountpoint). The streams itself are created in a piece of proprietory > (spelling?, i'm dutch) software, icecast merely relays them. > > However, the intended endpoint is an embedded device. This device has > trouble with tcp/ip packets not mat...

We are using icecast as stream-relay for a true narrowcast solution we've developed. The idea behind the system is that each individual client gets it's own mountpoint. Basically we have an application that creates streams. Its written in c++ and uses libshout to handle connecting to icecast. Everything works fine, as long as we keep the numbe...

...cast can handle? -----Oorspronkelijk bericht----- Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org] Namens Henri Zikken Verzonden: woensdag 5 oktober 2005 17:02 Aan: icecast@xiph.org Onderwerp: [Icecast] icecast2 mountpoints maximum We are using icecast as stream-relay for a true narrowcast solution we've developed. The idea behind the system is that each individual client gets it's own mountpoint. Basically we have an application that creates streams. Its written in c++ and uses libshout to handle connecting to icecast. Everything works fine, as long as we keep the numbe...

sir , I Have the following error , please let me know. with kind regards ds checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output...

...lijk bericht----- > Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens Henri > Zikken > Verzonden: zondag 25 december 2005 15:05 > Aan: icecast@xiph.org > Onderwerp: [Icecast] Use of TCP_CORK instead of TCP_NODELAY > > > We're abusing icecast in a true narrowcasting setup (personalized stream per > mountpoint). The streams itself are created in a piece of proprietory > (spelling?, i'm dutch) software, icecast merely relays them. > > However, the intended endpoint is an embedded device. This device has > trouble with tcp/ip packets not mat...