[Icecast] Configure Ubuntu Server 16.04 for icecast2

Sat Nov 3 00:59:22 UTC 2018

You have confused megabits for kilobits.  The number of listeners depends on the bitrate of the stream.  Assuming a 64kb/s stream, 282.95 Mb/s will support 4400 listeners, but more likely 4000.

Ross.

From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Robert Jeffares
Sent: Saturday, 3 November 2018 11:33 a.m.
To: icecast at xiph.org
Subject: Re: [Icecast] Configure Ubuntu Server 16.04 for icecast2

Bonjour,

Upload: 282.95 Mbit/s

is going to choke at about 5 listeners 

You need a streaming server provider.

https://shoutca.st/

is an example but there are many.

Don't buy 5k listeners buy 100 and see how it goes.

regards

Robert

On 22/10/18 12:03 AM, Abdelkader BKF wrote:

Hi,

Thank you so much for your reply,

I've a dedicated server in OVH, where I have done speed test for the server :

bkf at xxxxx ~> speedtest-cli 
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from OVH SAS (x.x.x.x)...
Selecting best server based on latency...
Hosted by fdcservers.net (Paris) [1.88 km]: 6.488 ms
Testing download speed........................................
Download: 900.46 Mbit/s
Testing upload speed..................................................
Upload: 282.95 Mbit/s

Is it enough for up 5k listeners ? Could you please give me best Providers for streaming ? 

Thanks.

Regards

On Sun, Oct 21, 2018 at 12:53 AM Robert Jeffares <jeffares.robert at gmail.com> wrote:

Hi BKF,

you can configure icecast to serve thousands of listeners but it's not going to happen on anything less then an industrial strength internet connection.

If you have ADSL you can probably handle 5 listeners maybe 10 on an average service.

If you have VDSL increase that to 15 maybe.

If you have fibre it might do 25.

It all depends on the service provided by your ISP and the condition of the cabling between the local switch and your location. 

They control how much data you can send and recieve even on " unlomited "

Then it depends  on the modem router, and your in house network, although these are less likely problem areas.

If you want 5000 listeners you have to send audio to a Streaming Service Provider who has a BIG internet upload capability which costs money.

There are some that charge rather low rates for 200-1000 connections because they know that while you pay for capability very few stations have more then one or two listeners on line at any time. 

I support one that has up to 200 listeners and we may be at 40 or so except when there is some critical news breaking which takes us over the 100.

We have a feed for an app and a feed for tunein and a feed for the website. The app has the highest usage  

On 21/10/18 12:17 AM, Abdelkader BKF wrote:

Hi all,

First of all, thank you for supporting us.

I've installed Libretime (https://github.com/LibreTime/libretime) which user Icecast2 on Ubuntu Server 16.04.

I've also developed a mobile application to listen to stream myhost:8000/mount.

My problem is when the number of listeners increases up 500 (On live streaming with butt), the application blockes, and I hardly get info from myhost:8000/status-json.xsl.

My question is : How shoud I configure my Ubuntu / Icecast / Liquidsoup to allow more than 5000 listeners to listen music without any issue.

Thanks.

Regards.

BKF-Dev

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-- 

BOUKHELF Abdelkader
Analyst / Developer Software Engineer - (Information System)
Skype : akaderb
Mobile : (+213) 556 45 38 71.

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20181103/f8134942/attachment.htm>