Owncast Self Hosted Live Streaming

299 readers
1 users here now

Owncast is a free and open source live video and web chat server for use with existing popular broadcasting software.

Owncast is your own Self-Hosted live streaming service with seamless #Fediverse integration.

Owncast

Quickstart

Docs

Releases

Troubleshooting

Livestream Directory

Owncast's Mastodon

Gabek's Mastodon

Owncast Firefox Extension

Owncast Chrome Extension

Unofficial #Owncast community.

Feel free to post your #livestream or your favorite live #stream here.

NSFW is allowed, but please mark it as NSFW appropriately.

Do NOT spam.

Everyone be kind, compassionate, and understanding to each other. If we can't get along then you'll be removed.

founded 1 year ago
MODERATORS
1
 
 

So I was wondering the bandwidth usage of Owncast and started crunching some numbers. Then I happened to find that @gabek@social.gabekangas.com had already done the work. Article linked, but here's one of the examples:

Example Scenario#

You’ve configured your broadcasting source (such as OBS) to stream to your Owncast instance at 5000kbps. You have 25 viewers. 5 of them are on slow or mobile networks, 17 of them have fast, stable internet, and 3 of them have fast internet most of the time but the speed fluctuates. All 25 viewers watched an entire stream that lasts two hours. You have a hosting provider that gives you 4TB of bandwidth per month.

Offer a high and low quality option

You decide to offer both a high and low quality option, and you set the high quality option to 5000kbps and the low quality option to 1500kbps.

How much bandwidth is used on your server for this stream?

Bitrate Duration Viewers Total
0.000625 Gigabytes per second (5000kbps) 7200 seconds 19 85 Gigabytes
0.0001875 Gigabytes per second (1500kbps) 7200 seconds 6 8.1 Gigabytes
Total: 93.1 Gigabytes

How much CPU?

Quality CPU Usage
5000kbps Some (It matches the input)
1500kbps More (CPU needs to be used to compress the video)

How is the viewer experience?

Quality Viewers Experience
5000kbps 20 Good
1500kbps 5 Good

Result: You’ve provided both a high and low quality option for your viewers so those with a slow network have an option, and those with a fast network that might periodically slow down can dip down into the low quality when needed. Additionally, in this case you saved almost 20G of bandwidth traffic due to offering a lower quality. You’re using more CPU for a much better experience. You would be able to stream 43 times in a month before you hit your bandwidth limit.

2
3
4
5
6
 
 

turns out that ety has edited VODs

7
 
 

felt cute might delete later

8
 
 

live stream at https://stream.logal.dev/

9
 
 

owncast is now live

10
11
12
 
 

Forgot to post this here long ago. Don't like self promoting, but haven't seen other videos.

Here's a video I did where I'm running a Hetzner VPS for only $8/month and I've simulated 70+ open connections without any kind of issue.

Lots of folks think that the more people watching, the more CPU power. That's not true. Number of quality of streams is what constitutes CPU required. So if I have 2 qualities, you want at least 3 CPUs. If you have 8 qualities, you probably want something like 10.

Your mileage may vary, but the most people watching, just equates to more bandwidth. And the Linux kernel is very good at opening connections and managing them, so it's VERY low CPU usage.

If bandwidth does become an issue, you could always use a CDN or S3 bucket in front of your Owncast.

13
14
15
16
17
18
19
20
21
22
23
24
25
view more: next ›