ok re-checked SRT vanilla obs - 05e8bcf74a1663fc240f6dff1dee1d34 My friend on vanilla chrome, described the same issues My chrome in virtual machine was experiencing same issues (spinning wheel) after a long time it began to playback stream, but it was very delayed, refreshing the page made it have loading issues again Is there a change the issue is with chrome?

I will have to investigate further tomorrow

We were able to repro the freezing/stalling issue and applied a fix yesterday and today, but it seems that it is not working in your setup

cc @Schachte @Mickie Betz

Thank you!

Good day, May i know if its possible to use webrtc from rtmp input to reduce latency OBS --(input)-> RTMP ---> WEBRTC (for player)

Can you clarify what you mean by "when process starts"? At the moment there are webhooks for when live input connects and disconnects, and another for when the recorded video is playable - happy to relay how to subscribe if this is what you're looking for

^ intended for @DemosJarco question on webhooks above

ah, I see yall continued conversation - I have a suspicion some of the confusion is because there are two separate webhooks and to get the "ready to play" one, you need to also follow these steps (which are different form the live input connect/disconnect webhook instructions): https://developers.cloudflare.com/stream/manage-video-library/using-webhooks/

There's the ready to play event. But if a started processing event could also be triggered. Like the moment cloudflare has received enough to start processing/working on the video

Like I'm storing an array (of the UID) of every video generated by a stream in the meta of the stream itself. That way when a stream is over, I already have the UID and can immediately swap the player to to vod of the stream or do api stuff related to the video (which i need the UID for) like copy over all the other stream meta fields to the video meta fields

But for both of those examples, since I'm not manually uploading the video, I'm left out of the loop until the video is done. So i need the video id as soon as it's available before the video is ready to be played. And for looping every video in the account for details is a bad idea

I see, ok that use case wasn't on our radar before - I can discuss with team

Ok, I'm getting weird webhook behavior. I get 4 identical (same exact webhook content body) webhook posts for a video id

Would you mind providing the video ID? I can try to see what we see on our end

Yea because on first trigger, my worker (the destination of the webhook) deletes the vod. But the subsequent webhook triggers makes by worker error out because the vod has already been deleted

On our end it looks like it received a 500 for the request to the URL, so it retried a few times. I'll DM you the response body we see from the request

Kinda related, my worker exception was because on

GET

accounts/.../stream/live_inputs/...

does not return a

Content-Length

header. But

DELETE

accounts/.../stream/...

does. My worker was using that header to decide on whether to parse the body or not.

Hello, can I ask about webrtc I followed the document and use my obs as a camera just wondering how can i protect my stream to be copied by other people can i block it by token or domain thank you : )

Hello, after the webRTC whip stream is terminated, the connection state on the whep side is changed after 7-8 seconds. Is there a way to detect disconnection on client side more faster?

Did you terminate by sending a DELETE to the resource URL? Or terminate by just closing the application/browser tab?

hi! Yes, you can enable signed URLs for your live input. It is currently undocumented as an option for live streaming, so thanks for raising- we are going to add to documentation soon. In the meantime, the way to do it is like so:

curl -X POST \
-H "Authorization: Bearer <API_TOKEN>" \
-D '{"meta": {"name":"test stream"},"recording": { "mode": "automatic", "requireSignedURLs": true }}' \
https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/stream/live_inputs

Specifically- it's the

requireSignedURLs

bit that you want to enable. An option to toggle through the dashboard is currently on it's way to production. Here's the documentation around signed URLs and how to restrict access for certain options (ip, geo location, etc): https://developers.cloudflare.com/stream/viewing-videos/securing-your-stream/

good callout, we could do better with consistency on returned headers across our responses. Made a note to make this consistent across our API

looks like both have the same result. Even i tried here: https://wish.chens.link/live with end livestream have same result.

Anyone else having problems with SRT Playback? 1) I can't receive sound 2) if send more than 1MB/s the video is freezing.

Thanks 🙂

Hello! I have a problem with RTMP streaming. I use custom video streamer based on FFMPEG. When I create a live input with disabled playback and recording, it works successfully, status indicator lights up green and says "connected". Once I enable live playback and recording, my streamer fails to connect and the dashboard displays video recordings with error: The video uses codec features incompatible with Stream. Is there a way to debug, which features cause the problem?

What are your codec parameters?

Can you try again with a new input? Does it happen only recently?