that is the PATCH url you need to use

Oh ok, perfect!

I'll check on it and report the results, thanks ❤️

you can send DELETE request to the Resource URL to stop the stream instantly

it is the Location header from the POST request with SDP

In the RFC spec, the url you send sdp to is the*Endpoint*, not the *Resource URL"

the reason behind it: it is conceivable that one endpoint may be used to start multiple streams, how does the server know which stream you want to stop?

Ok, i think the WHIP example should be updated

Then

Because it's using the wrong url

Hmm which example

The only WHIP example you provide in the documentation, hosted on stackblitz

let me checm

It provide the function to stop the stream but that function when called fails with the error i previously reported

I blame my past self from 2 months ago

Hahahaha relatable

No problem, glad it was that simple to fix

yep that is wrong

I will fix

The example on github should be fixed now

Interestingly the whip spec does not mention the charset part. I think we will make it acceptable to have charset at the end

since we are in the land of UDP, we have to rely on timeout to notice that your peerconnection is gone. whip/whep spec has the DELETE to resource url to expedite the process

It's a known issue that some times a stream will die randomly but the viewer side won't get updated error. We will fix it soon

Thanks! We were also passing the publish url to the deletion. Will test with the resource url.

Anyone knows if TUS deferred length is supported or is in Cloudflare's roadmap?

Thanks! I'll try to do some more logging on the broadcaster side as well to see if I do get something there but I'm just missing it, did find I have at least one reconnect bug on my end just today so there might be something there too :)

Hey all, is it possible to use Cloudflare stream for audio only streams?

@Logicpoints We do not currently support just-audio content. One workaround other customers use is providing an unchanging video as the video portion of the broadcast.

hmm is nvidia's rtx super resolution part of chromium source code or chrome exclusive (since edge gets it too)

https://chromium.googlesource.com/chromium/src/+/a9b4263e45e135d15f428245eecec29f71d0e83d oh it is