@Kyle_Cloudflare explodiated live input

As a heads up we're currently investigating a Stream-impacting incident https://www.cloudflarestatus.com/incidents/rk5zbj8z94nc

Impact is resolved, we're monitoring

Hey how can I talk w Stream acct mgr? DM me thanks

any plans to support 4k on stream playback at present? 👀

Anyone here using WebRTC stream in production? Any input on reliability of streams that are 1-2hr in length? What about overall quality of streams when you’re publishing say 100s or 1000s of WebRTC streams daily?

I'm getting a few of these on my videos: it's weird to, I'm testing on a video link that I know worked before, so maybe there's something I'm doing that interrupts encoding?

I personally am running a YouTube live re-broadcast (lofi girl) as a test stream (24x7), using gstreamer to encode H264 into VP9. So far it is pretty good.

the only interruption is when the live manifest from youtube expires and it needs to restart the encoder

as for the quality of the stream., that depends on the publisher network condition

also if the viewer has a good network condition as well

you are doing webrtc to youtube???

That’s just a standard stream though right? Not WebRTC? A related question is if say I am creating a few thousand upstream connections out of a single datacenter, would you see that creating an issue w CF being able to handle that many 2-3mbps streams from one network connection to the CF edge location closest to my datacenter? I will only have a handful of datacenters across the US and each may be streaming a few 1000 streams.

WebRTC is even more so for requiring good network connection, because the transport is over UDP. If the publisher network starts dropping packets, ALL viewers will have dropped frames.

That's the tradeoff you are making for extremely low latency

The other way around, YouTube live to Stream (WebRTC)

The publisher network will be excellent and reliable in my case. I’m just more curious if CF sees any issues w that many streams originating from a single network origin / datacenter?

Hi all, I have a project design for a CDN-type system which leverages IPFS under the hood to make the distribution of immutable data blobs (videos, images, binaries, etc.) more manageable and less stressful on the network. Personally, I don't have much experience with CDN technology, nor do I know what pain points or challenges those systems face, but Matthew Jacob recommended me to message this channel about it, since CF Stream is geared towards video distribution. I've written a rough outline for what the system would consist of, and how a CDN could be built around it. Would someone from Stream be willing to give it a look and tell me if it could be useful at all, the input would be hugely appreciated? Link is here: https://github.com/ipfs-cluster/ipfs-operator/discussions/100

It is in open beta. Try it out and see how it works. Beware, there be dragons for beta software.

Oh.

Any idea when a production version will ship…. Not sure this is right fit if it’s in beta.

Hi there 👋 I have been wanting to explore Stream as an alternative to hosting product demo videos on YouTube (because privacy), but one of my biggest questions was about using an HTML5 video element instead of the Cloudflare Player iframe. It seems this just works ™️ if you check the option to "Enable MP4 Downloads" on the video and just point the

<video><source>

element at the resulting mp4 URL. Is this an antipattern (am I doing it wrong)? What are the drawbacks of this approach vs the embedded player? Is this going to be cost prohibitive? The docs don't provide a lot of information on this approach, so I'm hoping y'all will know. Thanks in advance for your help! 😊

normally you'd use something like hls.js (https://github.com/video-dev/hls.js) or https://videojs.com/ for this

you could upload the videos to #940663374377783388 too though

Do you mind if I ask why not use our player (such as ) or even third-party player? While you can use the download link for video source, do keep in mind about: 1. Billing may be counted not in your favor, as now it is billed per bytes, converted into minutes as a ratio of the total file size. Depending on the format and length, you may be billed for extra; 2. Download link video is not seekable; 3. No ABR with download link. Our official recommendation for the use of download link is when you are: 1. Building short-video style apps (such as tiktok); 2. Downloading for client-side offline viewing (such as Plex); 3. Showcasing with background splash video.

I’m not familiar with the term “Showcasing with background splash video” - could you explain what this means?

You see some websites with a video playing in the background of the banner? Maybe half translucent? I call that background splash video, but people may call it differently

Gotcha! Are there any specific downsides with using streaming for these?

It really depends on what you are doing, the biggest downside is no ABR, but for tiktoks and background video, they don't matter as much as they are likely played to completion or loop