Displaying 7 results from an estimated 7 matches for "narrowcasting".
2005 Dec 25
4
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 matching the max. packet size...
2005 Dec 28
0
Use of TCP_CORK instead of TCP_NODELAY
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-bitrat...
2005 Dec 28
2
Use of TCP_CORK instead of TCP_NODELAY
...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 matchi...
2005 Oct 05
3
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 number of mountpoints
below 347. As soon as we
2005 Oct 05
0
icecast2 mountpoints maximum
A small update from my side.. i have updated both icecast and libshout to
the nightly snapshot versions of icecast.org. Also, in the configfile i have
raised the threadpool to 500 and all timeouts to 3000.
This did help a bit. Right now i can get it up to 1020 inputstreams, however
then it just stops accepting new connections.
Is there a theoretical maximum to the number of mountpoints icecast
2005 Dec 22
2
sir please let me know ( Installation problem)
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...
2005 Dec 28
0
Use of TCP_CORK instead of TCP_NODELAY
...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 matchi...