I'd recommend something like hls.js, it's lower overhead than the stream player.
I'd recommend something like hls.js, it's lower overhead than the stream player.
JYep. I'm playing with some alternatives. I'd really love for CF to fix thes though.
NMe too. Having the stream player be iframed also means we can't use the MediaSession API :/
MHello everyone, I'm streaming via OBS to a webpage that uses a Cloudflare player. Currently, I'm experiencing about 30 seconds of latency. Could you please help me to minimize this latency as much as possible?
On twitch i have latency like 3-4 seconds from same setup, can we make close to it? Maybe using llhls or dash.
On twitch i have latency like 3-4 seconds from same setup, can we make close to it? Maybe using llhls or dash.
MAs I understand it no solution can be thought of at the moment?
EThe Cloudflare Blog
Cloudflare Stream’s LL-HLS support enters open beta today. You can deliver video to your audience faster, reducing the latency a viewer may experience on their player to as little as 3 seconds
E@Stream 
MThank you guys, looks amazing
Rthats awsome Kyle, i tried it however and i could not see any EXT-X-PROGRAM-DATE-TIME in the live manifest (i enabled Low Latency HLS Support when i created the stream via the GUI).
Is there some flag i need to pass to the API or something to enable it or am i missing something else?
Is there some flag i need to pass to the API or something to enable it or am i missing something else?
Rit worked when i added the protocol parameter! awsome! 
RWill do. While I have your attention, I saw that when i ended the stream and it turned into a video/vod, that the EXT-X-PROGRAM-DATE-TIME are not present in those manifests. Any plans on keeping those (optionally perhaps)?
Our usecase is possibly that we will have some large streams that we want to cut in with start/stop times that are UTC timestamps
Our usecase is possibly that we will have some large streams that we want to cut in with start/stop times that are UTC timestamps
Ralso, is vod manifests only created on live stream ending, or is a vod manifest being written in parallel at all? (guess that would make it DVR then :), which i heard is only through dash at the moment as a workaround)
Ryeah i realize that these manifests would become very large, in our usecase we wouldnt use it to load it into a frontend videoplayer, it would more serve as a source for our own tools to create clips from. But this takes us a long way, i will see what are future looks like, thank for your time
THey everyone, im having issues connecting via RTMPS via OBS Studios, just tells me that it fails to connect to the streaming server and to check internet connection, and it's definietly not my internet connection. It's like it either can't find the server or the server is actively refusing the connection. Anyone have any advise or is there something im missing?
AHi, has anyone managed to get vertical (9:16) videos to encode and stream at full resolution (1080x1920) ? This doesn't seem possible with Stream at the moment. Have posted and searched the community, contacted Cloudflare support but can't seem to get an answer? Mux.com supports it but would much rather use Cloudflare for our platform.
LIdk if you meant to reply to me as I asked about RTMP dropping the restreams to YouTube, but we have a generating movie running on Unreal Engine (sort of an art project), streaming 40 seconds unique clips for 6 months. Some customers want to display this in public places using smart tvs, that's why we need the restream to YouTube to be continuous for this long. We've had the restream fail twice in 4 days, and flicking the output switch on and off helps restart the stream.
AHi, I'm trying to set the name as "Hello" So I have encoded text to base64 but the response is still using the filename. What am I doing wrong here?
MThe problem has been around for many months. Are there any plans to solve the problem one day?
MAm I the only one who gets lags on the site when viewing in llhls? Streaming is unstable, frequent freezes. Is there any way to fix it? Everything works fine on twitch and youtube. I use cloudflare's iFrame.
JWe stream to rather large audiences and always have some users that complain about our livestream freezing, requiring a page refresh to resume. I've even experienced it myself occasionally. We're pushing 200k+ minutes/month, so having a way to fix it is really important. Is this just a problem with the cloudflare player? Or is there something else that's commonly regarded as a better way to fix. Pushing 3500kbps at 1080p 29.97 over RTMP to Cloudflare.
BIs there any way to hide the 'live viewer count' from the clouflare video player?
VCould I get some help understanding the pricing for Cloudflare.
The pricing says:
Is that for the livestream or streaming videos from the storage, or both? Is it based on per user or the amount of minutes I send?
For example, if I send 1'000 minutes of videos that is watched a total of 100'000 minutes by users. Is the price $1 or $100?
It also states:
Imho the latter (minutes per user) would be the equivalent as charging for bandwidth, no?
The pricing says:
Streaming costs at a rate of $1 per 1,000 minutes delivered.
Is that for the livestream or streaming videos from the storage, or both? Is it based on per user or the amount of minutes I send?
For example, if I send 1'000 minutes of videos that is watched a total of 100'000 minutes by users. Is the price $1 or $100?
It also states:
"No charges for encoding or bandwidth"
Imho the latter (minutes per user) would be the equivalent as charging for bandwidth, no?
VOr to calculate a typical video from us:
- First we stream the video (once):
- Video length: 480 minutes
- Total view time: 35 000
- Then the video is stored:
- Video length: 480 minutes (the actual same video)
- Total view time: 3000
Aso for your initial stream of the video, you would be paying $35, followed by another $0.48 to stream it to Cloudflare
and after that you'd be paying another $3, all in all you'd be paying $38.48 for that one video, and $1 for every 1000 minutes of viewership after that.
as for your initial example suggestion, the price would be $105, since it is 1000 minutes of video stored (at $5/1000 minutes prepaid), and 100,000 minutes of video streamed (at $1/1000 minutes postpaid), so that theoretical piece of content would cost you $105/month for that month
hope this helps! (and please correct me if I'm wrong and someone knows better)
and after that you'd be paying another $3, all in all you'd be paying $38.48 for that one video, and $1 for every 1000 minutes of viewership after that.
as for your initial example suggestion, the price would be $105, since it is 1000 minutes of video stored (at $5/1000 minutes prepaid), and 100,000 minutes of video streamed (at $1/1000 minutes postpaid), so that theoretical piece of content would cost you $105/month for that month
hope this helps! (and please correct me if I'm wrong and someone knows better)
VThank you. If I store a video that will be charged every month, right? It's not a one time fee? It makes sense per month but just want to double check.
Ayes, that is correct
Athats what the subscription tiers are for, the "usage fees" part is for the streaming, so you get billed to store the video monthly, and pay based on usages for viewership afterwards 
VThe subscription tier for Creator Bundle has:
- Store up to 10,000 minutes of video content.
- Deliver up to 50,000 minutes of video content each month.
V
VAlso, the part with "Store up to 10,000 minutes of video content.", that's the total of minutes I can store, right? It's not an additional 10,000 minutes each month that's keeps reseting?
Ayes, that would be correct, you have 10,000 minutes of storage to use per month, but it is reset to 0 at the end of the billing cycle and re-calculated from whats in your account when the billing cycle begins again
so if you have 9,000 minutes at the end of cycle A, you will have automatically used 9,000 minutes at the start of cycle B
so if you have 9,000 minutes at the end of cycle A, you will have automatically used 9,000 minutes at the start of cycle B
A"Deliver up to" just says that you have pre-paid for 72,000 minutes of streaming, and 1,200 minutes of storage, but what it actually means is that you have $78 worth of credit for the platform applied to your account, and it is divvied up according to your usages
Aso if you had 10,000 minutes of video, you would only be billed $78, so long as your viewed minutes doesnt exceed 28,000 (I think, maybe someone who works on Stream could check my logic there?)
Asince my own platform doesnt have a use case currently for Stream, I am using R2 backed video playback, so my experience with Stream and it's billing methods are not the best, but I think that is how it works
VOK, thanks. I think I got it now.
So if I stream a 100 minute long video, which is watched 1000 minutes the total cost would be:
Stream: $1 (as 1000 minutes costs $1)
Storage: $0,5 (as 1000 minutes costs $5)
Simple as that?
So if I stream a 100 minute long video, which is watched 1000 minutes the total cost would be:
Stream: $1 (as 1000 minutes costs $1)
Storage: $0,5 (as 1000 minutes costs $5)
Simple as that?
AI think that is roughly correct, though dont quote me on it since im not sure if storage is possible to do in a postpaid method