Will that stop buffering as well? I was thinking I might do it on a timeout as well, yeah, similar to how YouTube asks "are you still there" after a while.

The player doesn’t buffer infinitely (most real players don’t - waste of bandwidth on both sides) - so pausing will stop the player from needing to read more into the playback buffer.

Oh, cool. Thanks

You can validate with the

buffered

property, which conforms to a https://developer.mozilla.org/en-US/docs/Web/API/TimeRanges

Does the Cloudinary Stream player optimize the video for the size requested? I.e. if I request the video in an 800x400 iframe will I receive less MB's than when I request the video in a 1600x800 iframe?

is there a full example of the webhook request body somewhere? https://developers.cloudflare.com/stream/uploading-videos/using-webhooks/#example-post-request-body-sent-in-response-to-successful-encoding

Yes, because the Stream player uses HLS.

HLS delivers the video, not only in different levels of visual quality, but also different resolutions depending on the viewer's device size.

@Isaac McFadyen | YYZ01 That's dope! I'm not too good on video knowledge. Would this be a good fit for instance for background videos on web marketing sites?

Hmm... it depends on what you need.

Looking at VOD of course not live streams

The issue with that is that if a user clicks away, Stream doesn't stop the player automatically so it keeps billing.

There is a possible solution however.

I asked it up here actually but basically, as long as the video is only a background video that you don't care if it pauses, you can pause the video via Javascript when it detects the "blur" event (click-away event)

yeah that popped into my mind initially as well

Basically what I want is something like the image transformations to safe myself bandwidth and the user bandwidth, I noticed Cloudinary has video transformations pretty much the same as image transformations, but I'd rather keep all my stuff in Cloudflare

So I was wondering if this is a valid use case 😄

I'll test it out sometime soon, thanks for the response

(Solved) So with the stream API. Linked to an old post below and am currently having the same issue. Getting a 500 response that says error code 10000, "Authentication error". However, like the forum post I linked to I'm 100% sure my token is valid (I test it in a preceding request using the tokens/verify endpoint) and the token has permissions for read + edit Stream (along with the read template). The poster did seem to get it to work with the legacy global API, but I've had no such luck. (Also, since the doc examples use Authorization it should work) Considered it being a permissions issues and added all the ones I think could possible be related to it but still nothing. ✅ Fixed: Thank you @Zaid (Cloudflare) for your help! The API requires you to use the Account ID. I was mistakenly using the User ID instead. You can find the accounts available to a user by using this endpoint: https://api.cloudflare.com/#accounts-list-accounts and then using the ID associated with the account. https://community.cloudflare.com/t/cloudflare-stream-10000-authentication-error/149227

Thanks, and @tt2468 on your low latency comments - super helpful Where would I go to find out more about low latency HLS support? I'm building a "real-time-as-possible" broadcast video streaming system. I'd prefer to use an off the shelf video player, so 30s HLS latency in the worst case I guess

You should also look into WebRTC depending on your use-case. https://www.wowza.com/blog/low-latency-hls-vs-webrtc

thanks, was wondering about that too. Downside is it'd need a custom CDN (eg Wowza), which I don't think cloudflare would be able to replace? Or maybe with Spectrum...

mmm generally with WebRTC you wouldn't be using of a CDN

just because unlike HLS which effectively partitions the video into segments

WebRTC is realtime with no realy easy way of having a cache buffer that could easily be connected to from clients

got it

Well caching is only required anyway because HLS is stateless for the client.

Trying out TUS upload and I'm getting a

Non-256KiB chunk size multiple

error. I've got my chunk size set to

52_428_800

but my file is smaller than that, could that be the reason?

Never mind! Just some very confusing documentation. The

Upload-Length

says it should be the "video length" when it actually should be the video size in bytes.

Making a docs PR now.