no not realy because for comparion I had to convert minutes to bandwith and bandwith to minutes 1000 minutes on cloudflare cost 1 dollar .... 50 dollar for 82.000 minutes on vimeo pro

vimeo pro is 50 dollar for max 2 TB of bandwith .. now how many minutes if 2 TB of bandwith in HD .. its 82.000 minutes

What is your conversion from TB to minutes based on? Does Vimeo specify the video bitrate?

I calculated it was 3.4 megabit per sec streaming in hd h264 thats about 0.4 megabyte per sec streaming .. but if vimeo does even better compresseion then that then the number of minutes is even higher ..

I was 100% sure before doing the math that cloudflare stream would be way more affordable ... but if I am not missing something here its the oposite

for this use case

3-4 mbits seems to be a good basis for a HD stream. That's what I would assume too.

I am a little blown away by this because I was expected cloudflare stream to be more affordable on every level but it seems to be the complete opposite for this use case ...

now cloudflare has a creator bundle that gives you for 50 dollar 50.000 minutes of stream and 10.000 minutes of storage ... but on vimeo bis you get 82.000 minutes of stream and 208.000 minutes of storage for hd video

now if cloudflare stream minute price would include 4k then the math would be way different and cloudflare stream would be more affordable ... anyway I would be happy if I could get some additional stuf that I could tell the client to go with cloudflare stream that vimeo dont have that would make it better to go with cloudflare stream ... and would motivate the higher price of cloudflare stream

On another topic: Is the Websocket connection for a live input (Bitrate, FPS, etc.) documented in any way? I see that it takes the format of

wss://live-status.videodelivery.net/websocket/source/{INPUT_KEY}/status

. I'd like to present this information to clients but I don't know if I can depend on the endpoint to stay where it is.

Keep in mind that there's a lot you're not taking into consideration here.

1. multiple bitrates for different connection qualities

2. storing and delivering different formats for different devices (i.e. safari doesn't support webm)

3. the cost of compute for encoding

if there’s ever a “everyone supports X except Y” you can trust it to be Safari

Or is that Images that's working on the pricing model? 🤔

Images are working on the pricing model

Currently it’s not feasible for high quantity, low quality

I think Stream is similar - since it’s per minute, you want to deliver the most data possible per minute

Or you’re losing value in that minute, whereas bandwidth doesn’t have that issue

👋 This change is now live: https://discord.com/channels/595317990191398933/1003711335923724410/1003711337370751086

considered this, but wouldn't the webhooks fail whenever I'm not running the reverse proxy? it would be nice if there was an officially supported way of doing local development with CF Stream, like having Wrangler set up the subscription/forwarding

What would be your use case that it matters if Webhook calls fail, when the dev tunnel is down? I mean, you seem to be not working on it when you don‘t use the tunnel 😅

Is there any way to end a ongoing live input via API? I'm asking because I want to have way to close/block an ongoing live event if a customer reaches paid delivered minutes or violates terms (copyright, etc.)

Will deleting a Live input also cut an ongoing transmission?

And more important: Is there any API endpoint to fetch current usage (by creator)? Data shown like in the dashboard would be sufficient.

Are there plans to allow users to create project folders for Stream videos? I've submitted a feature request for this, but wanted to see if anyone knew offhand. As the number of videos grow, it can be really hard to locate a video when everything is in a single folder and you can't tag anything (at least in the dashboard).

There's an endpoint to drop the publisher, but it doesn't block them from reconnecting. You could possibly rig it to a webhook to auto-drop them after a few seconds.

Can you point me in the right direction to where I can find documentation about this endpoint? I don't see anything related in the API v4 documentation