Mok, i fixed. thanks
RHaha i didn't do anything but you're welcome 
SHello everyone I am Devansh from India i am using stream player of cloud flair and i want to know is there any way to open the vidoe in fullscreen by default
Tas far as I know you can use the HTML Fullscreen API to archive almost the same result, but you’ll need this after the first user interaction (e.g. when clicked on a button), you can’t open in fullscreen by just loading the page without any user interaction in most browser (except when opening an installed PWA).
Sis there any documentation for the api?
DHello. Can anybody have look at this issue: https://community.cloudflare.com/t/tus-failed-to-resume-upload-caused-by-object-progressevent/634864
AHello guys! I am George!
I am creating an application where a user uploads a video on my ReactJS frontend, I send the video to backend and then I upload it to Cloudflare Stream service using TUS.
After the upload finishes, I send the video UID as part of the backend response.
So, in my frontend I create a new component when I receive the response:
<Stream controls src={videoUid} responsive={true} />
However, initially, when the Stream component https://www.npmjs.com/package/@cloudflare/stream-react loads, I can see in my browser's network tab that a request to the bellow URL gets a 500 internal server error
https://<customerId>.cloudflarestream.com/<anotherId>/manifest/video.mpd?parentOrigin=http%3A%2F%2Flocalhost%3A4000 --> 500 error
and the video and the player do not load at all.
The strange fact is that if I refresh the page, the player loads the video and everything works fine. Any idea?
(Also I can see a CORS error on the browser's console)
I am creating an application where a user uploads a video on my ReactJS frontend, I send the video to backend and then I upload it to Cloudflare Stream service using TUS.
After the upload finishes, I send the video UID as part of the backend response.
So, in my frontend I create a new component when I receive the response:
<Stream controls src={videoUid} responsive={true} />
However, initially, when the Stream component https://www.npmjs.com/package/@cloudflare/stream-react loads, I can see in my browser's network tab that a request to the bellow URL gets a 500 internal server error
https://<customerId>.cloudflarestream.com/<anotherId>/manifest/video.mpd?parentOrigin=http%3A%2F%2Flocalhost%3A4000 --> 500 error
and the video and the player do not load at all.
The strange fact is that if I refresh the page, the player loads the video and everything works fine. Any idea?
(Also I can see a CORS error on the browser's console)
TAnyone else having issues with WebRTC at around 5pm UTC? It'll be fine for my 4 streams and twice now at 5pm everything starts breaking. I also use the API to check the stream status and it'll return 429 - too many requests
TThanks Rachel. Do you want me to test it and report issues then?
RHello, can we place our own domain name for cloudflare stream?
Tyes
BHello,
With stream, is it possible to setup a feature on our webapp to choose different aspect ratios to download from, for the same video?
With stream, is it possible to setup a feature on our webapp to choose different aspect ratios to download from, for the same video?
Rvery cool live clipping
RThe Cloudflare Blog
With Cloudflare Calls in open beta, you can build real-time, serverless video and audio applications. Cloudflare Stream lets your viewers instantly clip from ongoing streams. Finally, Cloudflare Images now supports automatic face cropping and has an upload widget that lets you easily integrate into your application.
SHello, I have a video that refuses to play on Iphones (works on android and on my mac). What can I do to debug this ?
Rboth HLS and dash links throwin errors?
Sthe dash one prompts me to download the file, it downloads a 8kb file
Bpretty cool feature. I'm definately adding this to my web app
BI just can't find anything on giving users the ability to download different video resolutions, though it wouldn't cost me less in minutes to run the server, it would be great to package it in different pay gates.
AHello, is it possible to use this stream status websocket in my app
TYes. I use it in mine. It's a simple API call
KWould it be possible to make the max preview duration higher, like 30 minutes or so? The live clipping can serve as live playback/rewind, which has been requested by many, but this 5 min restriction prevents this use case (please correct me if I am misunderstanding the duration limit).
Youtube is able to rewind an ongoing live stream to any point in the live stream, it would be super useful to have this as a part of Stream.
Youtube is able to rewind an ongoing live stream to any point in the live stream, it would be super useful to have this as a part of Stream.
AI meant that if it is somewhere in the documentation, I was able to obtain the endpoint but using the browser's dev tools
TOh! That's be cool. Especially because if you call the endpoint too often you start getting 429s
YWill traffic still be charged without using relays?
TThe live clipping feature feels like a joke. You can just cut out one single specific part of the video?! Thanks for nothing. Instead they should make the WebRTC stable for professional use, especially when more than 50 viewers are watching.
TThere are some issues, based on your WHEP implementation example and also recommended OBS settings:
- short stutter/framedrops of about a half of a second till 2 seconds while audio is running fine, occurs randomly every 5 till 30
seconds, this can differ from day to day on the same device - It constantly stopping (hang up) after a while and playback don’t continue automatically, it needs full reload of the player
- when starting playback sometimes it buffers endlessly and doesn’t playback the stream
- sometimes the audio channel won’t play while the video is running and starts after a while (~ 3 minutes), reloading the page don’t fix it, also this occurs randomly between different devices
- our audience needs to reload the video page often to get a stable playback or to continue watching, also it looks like the more viewers are watching (50+) the more issues we have (also on a same device)
KMy two cents: I think changes like live clipping are more essential, and I appreciate the work being done in these directions; I understand webrtc stuff is the future so to speak with its lower latency etc, but I can't help but to feel that this "shinier" tech is drawing resources away from core "stream" features (or perhaps there is just less presence here in the discord, and its not a matter of resources). There are relatively smaller changes, such as fleshing out live clipping/live rewind, or allowing instant mp4 downloads without the processing (which occasionally just errors out), videos stuck in a live-inprogress state for 10 months, etc, that I think would help a larger proportion of actual Stream users. I don't think webrtc users/requesters constitute a significant proportion of Stream users in terms of actual production usage, but perhaps I am mistaken about this.
TThe OBS WHIP output currently only supports AVC and AV1. AV1 is available as of the 30.1.0 release.
TYeah, I honestly haven't been keeping track of which browsers are supporting it. We should probably add HEVC at some point soon
IIf anything HEVC support looks even patchier than AV1, or at least there are a lot more
*caveats on HEVC than AV1.
