On the mobile have you tried different browser or internet connection?
On the mobile have you tried different browser or internet connection?
TNo but im gettin this popup from safari ios
T
TSo on page load it would show the stream video first frame like it loaded correctly, everything is muted and autoplay is off
Tthen iOS Safari error pops up at the top
Tand then stream goes black and i'll get an error message
TIts strange because when i first implemented cloudflare and their embed a few weeks ago, everything was working fine. Now this occurs.
Ive tried on different phones yes
Ive tried on different phones yes
TRegular playback, youtube embeds, and everything else work fine in this modal I created. It specifically is an issue with cloudflare embed
1Not iphone?
Tyes iphone
TEverything works besides iphone
1right
1try different player maybe
1I swear theres an issue with Safari playback or something? Someone chime in
Taight - it seems to be a common issue according to all these misc. cloudflare help requests
Thavent found solutions
1Copy the HLS manifest link from your stream and see if it works here on your device: https://hlsjs.video-dev.org/
TI did test using the HLS manifest URL - that one worked on mobile, but then it didnt work on desktop. I used the manifest URL in the cloudflare iframe however, it seems the examples show to use it in a video element with JS event determining if hls playback eligible or not
Tooo nice lemme try it on this site
1the manifest URL won't work in the iframe, you will need to use it with a separate player like hls.js, video.js etc
Tgot it
Tnice - ok this is a step in the right direction 
Manifest works fine on this site, im gonna try it with hls player, thank you
Manifest works fine on this site, im gonna try it with hls player, thank you
TUsing vidstack js for the stream works now
T@1984 Ford Laser appreciate the help!
BHey everyone,
I'm trying to embed a Cloudflare Stream iframe into my mobile app, but I'm running into an issue. I added my app’s origin, but it says the origin is not allowed. It works fine when I allow all origins, so I’m guessing Cloudflare Stream only supports standard web protocols (HTTP/HTTPS).
Has anyone successfully embedded the iframe in a mobile app with the "Allowed Origins" feature enabled?
Thank you~
I'm trying to embed a Cloudflare Stream iframe into my mobile app, but I'm running into an issue. I added my app’s origin, but it says the origin is not allowed. It works fine when I allow all origins, so I’m guessing Cloudflare Stream only supports standard web protocols (HTTP/HTTPS).
Has anyone successfully embedded the iframe in a mobile app with the "Allowed Origins" feature enabled?
Thank you~
SIs https://developers.cloudflare.com/stream/webrtc-beta/ dead or its normal to take this long to make an official release?
Cloudflare Docs
Sub-second latency live streaming (using WHIP) and playback (using WHEP) to unlimited concurrent viewers.
1Huh? Alpha comes before beta not after. Plenty of people have been using WebRTC fine
SI mean official release. Sorry.
SIts in beta for like 2 years
XHi, i noticed that when I update the caption on the video, refreshing the page still uses the captions cached on the client side. is there any way to bust the cache to fetch new captions?
1How long after changing did you test? I wonder if captions rely on KV for metadata, which have an up-to 60sec global propagation period
1Also did you do a hard refresh with Ctrl+F5 or similar?
OWas trying to create Stream fro cloudflare dashboard and having this error
Authorization Failure: The authentication credentials are not authorized to perform the request. Verify the credentials and try again.Xyep. after hard reload, it still uses the cached version:
i tested just shortly after adding the captions. (accessing the video via incognito works since there's no local cached version)
i'm trying to figure out how to ignore this local cache.
i'm using an iframe to render the video, and within the iframe the request to fetch captions is made with a url like
is there any way to change the Cache-Control response headers for this request? its currently set to
200 OK (from disk cache)i tested just shortly after adding the captions. (accessing the video via incognito works since there's no local cached version)
i'm trying to figure out how to ignore this local cache.
i'm using an iframe to render the video, and within the iframe the request to fetch captions is made with a url like
https://cloudflarestream.com/{video_id}/text/en.vttis there any way to change the Cache-Control response headers for this request? its currently set to
max-age=1800
ODisregard didn't realise you have to enable it and pay separately here https://developers.cloudflare.com/stream
Cloudflare Docs
Cloudflare Stream lets you or your end users upload, store, encode, and deliver live and on-demand video with one API, without configuring or maintaining infrastructure.
SThe main blocker is the lack of recording. Unlikely someone would do live stream without option to record it.
1I mean they have said it's being worked on. Recently the WebRTC on Stream was recently moved over to the Calls backend, so it does receive updates. I'm personally hoping we can get some compositing options for the stream channels
1Nothing for Stream during dev week? 
Ghi, how do I enable "Low-Latency HLS Support" on a live-input by default?
GI see hlsUrl has
protocol=llhls but we need to enable it for the iframe's live-input by default.Gfound it!
preferLowLatency: true1Cannot wait for the Containers open beta so then I can finally use ffmpeg within CF directly 
KWhat do you use ffmpeg for?
Athere should a stream option without any fancy realtime transcoding options, but a much lower price
Aits kinda expensive to use atm
1encoding video
1Its actually really well priced as far as video streaming goes
ACome on, streaming an hour event is like 3000$ for 20k viewers
Not expensive but for cdn word with bw guage its kinda is
Not expensive but for cdn word with bw guage its kinda is
Ai understand that transconding is expensive, but sockets and bw should be CF flex territory
1Well do the transcode yourself offplatform and serve it from R2 or something. See how that stacks up
