If you have 20K viewers, you should be adequately monetised to support the event. I had a $1K cost for a 3 hour sports with "just" 1-2K viewers. $3K for 20K is good
Which is part of the reason why it costs what it costs. It's not easy doing what they're doing, and I think the pricing model is a good balance and is better than other platforms who charge per GB instead of per min
Im thinking maybe its because you dont have a separate Stream subscription, I am not an expert but thats what comes to mind for me. a sub to Stream is entirely separate to your Pro/Business/Ent. subscription
Minor UI complaint: when browsing the list of live inputs, you should let me open each one in a new tab! Currently I have to open them one by one, when Im trying to get through a dozen at once its frustrating
When generating an MP4 download, are there any particulars around speed, or when generating multiple clips at a time? Would be good to be able to predict load times as I usually have a bulk lot (5-20 3hour videos) to generate more or less at once, get an idea of how the OTE encoder operates im that regard
hey are these limitations for stream webrtc still up to date. specifically, i was wondering if we could WHIP from video source to CF then play with RTMP or WHEP. thanks
Cloudflare Realtime is infrastructure for real-time audio/video/data applications. It allows you to build real-time apps without worrying about scaling or regions. It can act as a selective forwarding unit (WebRTC SFU), as a fanout delivery system for broadcasting (WebRTC CDN) or anything in between.
Are we still quite a ways off from having an input stream and output stream of differing formats? Specifically, I have a use case where I need to stream in with SRT and output to WHEP. Stream seems like the perfect product for this, rather than running a conversion gateway locally to produce a WHIP stream.
Do you have existing accurate analytics to support your view numbers, or just basing off rough numbers? Your math is correct, but its very rare that a viewer will be watching long form content for the entire time. I do many regular 3 hour streams, with hundreds of total views, and average 5-25K minutes viewed per stream. Which means each viewer is only watching a small portion of the total runtime on average
I've asked this before, but with the Browser Rendering API and OTFE platform slowly maturing over time, is there possibility for being able to inject a HTML5 browser instance over the top of a live stream? That and input switching would be the only things I need to entirely transition from AWS
Yeah, this is all theoretical; on behalf of a client I'm doing consulting for. I too, think the numbers are ambitious, but I have to give them a cost based on their figures