Not sure who the Stream PM is but can someone more official confirm this?
Not sure who the Stream PM is but can someone more official confirm this?
KI thought you've confirmed it 
1As far as Im aware, but I dont work for CF
Knot much people are active in this channel
Kdid you read it somewhere in docs?
1I can't find a specific reference in the doc
KI'm not sure if they've even mentioned it in docs or not
1But I dont see any reason to waste transcode on upscaling a video very slightly. The pipeline would not be made to do so currently I would imagine
1Why would they? Its a very odd use case
Ki mean they should atleast mention that the streams will only be available in resolution <= resolution of original video
1Common sense would dictate that
Ktrue
1That specific resoluton you mentioned is an odd aspect ratio, how would you want it handled? Cropped to fit in the 720p frame, squeezed to fit, zoomed? Too many variables for what is wasted resources on tiny niche use case
Kokay, but then there should be an option to play the video in the original resolution as it was uploaded
Kapart from the degraded resolutions
1Could you link me to an m3u8 of one of your videos?
Kwe are using mpd
1Thats fine just curious what it shows
1PM if you cant share public
KI don't think I'll be able to share it since its not mine personally
Kwhat do you want to know specifically?
1I was going to try uploading my own video at 692P then compare the files
Kit just contains representation tags for 480, 360 and 240p
Kcan you try once as well?
1Will do, I wanted to compare bitrates of the encoded renditions. Lemme just encode something at that res
Kokay
Kbut there is no
Representationnot sure if thats how mpd files work
Ki think they have fixed set of supported resolutions
1videos aways get transcoded on Stream, no access to original as far as Im aware
Kohh
1I also only got a 480p stream max, encoded at 1.5mbps, the original was at 5mbps
1Tell your users to upload proper videos :lul:
K:face_holding_back_tears:
Sthe price for web RTC streaming is the same as stream? in the pricing page is not clear, it says
Delivery is counted by HTTP requests for video segments or parts of the MP4. Therefore:
Client-side preloading and buffering is counted as billable delivery.
Content played from client-side/browser cache is not billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
MP4 Downloads are billed by percentage of the file delivered.
HLS and DASH playback is rounded to the segment length. For uploaded content, HLS and DASH segments are four seconds. Live broadcast segments are determined by the keyframe interval or GOP size.
Delivery is counted by HTTP requests for video segments or parts of the MP4. Therefore:
Client-side preloading and buffering is counted as billable delivery.
Content played from client-side/browser cache is not billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
MP4 Downloads are billed by percentage of the file delivered.
HLS and DASH playback is rounded to the segment length. For uploaded content, HLS and DASH segments are four seconds. Live broadcast segments are determined by the keyframe interval or GOP size.
Sother technicall question, did't found a way to delete the web rtc published URL
Sin the rest API or docs
Scan anyone shrare that doc with me
S?
DAs of right now a stream published via whip doesn't get stored/recorded. Thus there is nothing to delete.
FHello, anyone knows if this kind of transform is possible with cloudflare stream for vertical videos? I mean adding the blud background for vertical videos.
1You would need to do that on the cliend side before sending the stream to CloudFlare
KThanks. I tried the same settings, but they are not consistent.
Here are our findings with Low Latency enabled in Cloudflare:
an average of 35s latency at 1080p
an average of 20s at 720p
We run about 30 live sessions daily, averaging about 140 minutes per live session.
Vimeo's low latency via HLS averages below 10 seconds, the minimum we need for our live classes.
anyways we had no choice but to renew another 2 year contract with Vimeo. our CF account manager sold us some pipe dream. low latency issue never got fixed, it has been 2 years now
Here are our findings with Low Latency enabled in Cloudflare:
an average of 35s latency at 1080p
an average of 20s at 720p
We run about 30 live sessions daily, averaging about 140 minutes per live session.
Vimeo's low latency via HLS averages below 10 seconds, the minimum we need for our live classes.
anyways we had no choice but to renew another 2 year contract with Vimeo. our CF account manager sold us some pipe dream. low latency issue never got fixed, it has been 2 years now
Ddoes the video need to be converted on the client before sending to cloudflare?
JI’m considering Cloudflare Stream for live gameplay streaming but have concerns about achieving low latency. I’ve read mixed feedback on its performance for real-time applications like gaming, where minimal delay is crucial for viewer experience. Has anyone used Cloudflare Stream for live gameplay, and if so, did you encounter any issues with latency or stream quality? Additionally, are there any tips to optimize Cloudflare Stream specifically for low-latency use cases?
1I have been able to get at or under 10 seconds with these settings in OBS, and LL-HLS turned on in Stream. Your mileage may vary. WebRTC streaming is best for low latency, but it currently also needs to be delivered in WebRTC too
JCurious if anyone has recommendations for low cost chat service to go hand in hand with cloudflare stream. I'm surprised by the cost of such services.
FAnyone knows if stream clip api (https://developers.cloudflare.com/api/operations/stream-video-clipping-clip-videos-given-a-start-and-end-time) generates a new video or modifies the original one? If modifies the original one what happens if the video wasn't processed yet? Do I lose quality?
Interact with Cloudflare's products and services via the Cloudflare API
1Generates a new video
1#durable-objects with Hibernatable Websockets would be the way to go. A basic solution can be built in under 100 lines of code, under 500ms latency and cost is super reasonable
J@1984 Ford Laser thanks for the info I’ll check it out
