Yes it is still alive. We have plans on improving it (hopefully) this quarter. But no dates for that
Yes it is still alive. We have plans on improving it (hopefully) this quarter. But no dates for that yet.
DHey everyone!
I’m trying to set up a live stream using WebRTC WHIP in Go. Got a Go app that shares the screen, and I can connect to Cloudflare—input status shows as connected, and I can see streaming details. But the stream doesn’t actually show up in the playback window, and it just says “stream has not started yet.”
I also tried using the ggarber/whip-go project since it’s in Cloudflare’s docs, but ran into the same issue. Has anyone else faced this or have any idea what could be going wrong?
Appreciate any help!
I’m trying to set up a live stream using WebRTC WHIP in Go. Got a Go app that shares the screen, and I can connect to Cloudflare—input status shows as connected, and I can see streaming details. But the stream doesn’t actually show up in the playback window, and it just says “stream has not started yet.”
I also tried using the ggarber/whip-go project since it’s in Cloudflare’s docs, but ran into the same issue. Has anyone else faced this or have any idea what could be going wrong?
Appreciate any help!
SHey guys!
I'm using Next.js and having some issues generating signed URLs to access a video stored on cloudflare stream. this is my code:
const cloudflareTokenResponse = await fetch(
method: 'POST',
headers: {
'Authorization':
'Content-Type': 'application/json',
},
});
if (!cloudflareTokenResponse.ok) {
return res.status(500).json({ message: 'Failed to generate Cloudflare token' });
}
const cloudflareTokenData = await cloudflareTokenResponse.json();
const signedUrl =
console.log(signedUrl)
return res.status(200).json({ signedUrl });
The URL is generated successfully, I get no errors there, but every time I try to access the generated url, I get an error 401 unauthorized. any idea what may be causing it? I have "Require Signed URLs" checked on the video settings
I'm using Next.js and having some issues generating signed URLs to access a video stored on cloudflare stream. this is my code:
const cloudflareTokenResponse = await fetch(
https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/stream/${VIDEO_UID}/token, {method: 'POST',
headers: {
'Authorization':
Bearer ${CLOUDFLARE_API_TOKEN},'Content-Type': 'application/json',
},
});
if (!cloudflareTokenResponse.ok) {
return res.status(500).json({ message: 'Failed to generate Cloudflare token' });
}
const cloudflareTokenData = await cloudflareTokenResponse.json();
const signedUrl =
https://videodelivery.net/${VIDEO_UID}/manifest/video.m3u8?token=${cloudflareTokenData.result.token};console.log(signedUrl)
return res.status(200).json({ signedUrl });
The URL is generated successfully, I get no errors there, but every time I try to access the generated url, I get an error 401 unauthorized. any idea what may be causing it? I have "Require Signed URLs" checked on the video settings
SAnyone else having problems with direct creator uploads to cloudflare images? The upload url is generated every time, together with the draft. But it seems random if the upload works or just times out..
Kthe token should go in place of ${VIDEO_UID}, and not as a query parameter I believe
SNo, docs specifically state it needs to be a query param
SI figured it out though, I was using videodelivery.net for the final signedUrl and needed to use customer-[id].cloudflarestream.com/
Gwill there be a way to use stream recorded videos as training data without downloading each video?
KOur primary streaming provider is Vimeo still. Because Clouflare still struggling to provide low latency streaming via OBS. It has like 1 to 2 minutes lag which they promised to fix but it has been more than 2 years no progress has been made. Vimeo provides two options via OBS and we use the fast option which has max delay between 6 to 12 seconds.
You may suggest webRTC but it does not support auto upload of the streamed recorded video and in the event of network failure it does not maintain the same session.
I don’t know if cloudflare really serious competing against other players but my account manager convinced me that it is the next best thing, signed me up on an enterprise plan. Thankfully we did not end our contract with Vimeo, saved us from embarrassment.
So far the experience has been a disaster and still feels like we are in beta mode.
If these two issues don’t fix you guys have no chance getting any serious company onboard !
You may suggest webRTC but it does not support auto upload of the streamed recorded video and in the event of network failure it does not maintain the same session.
I don’t know if cloudflare really serious competing against other players but my account manager convinced me that it is the next best thing, signed me up on an enterprise plan. Thankfully we did not end our contract with Vimeo, saved us from embarrassment.
So far the experience has been a disaster and still feels like we are in beta mode.
If these two issues don’t fix you guys have no chance getting any serious company onboard !
1Are you sure this isn't on your end? I can get RTMP latency down to a few seconds (maybe 3-5s off the top of my head) using OBS
1Main setting to be looking at is your keyframe interval, getting it as low as possible without too many buffering hitches. Also turning on LL-HLS support on the live input is a must (even without I feel like latency is always under 15sec)
1For context, I stream 120k - ~1M minutes a month through Stream and have been very happy with the service provided
1I just checked, and the latency is around 10 seconds with the following settings in OBS which took me 30 seconds to decide upon
Edit: changed the preset to P1 and got it down to like 5sec
Edit: changed the preset to P1 and got it down to like 5sec
KThanks I think we tried that but it was never consistent
KI thought that was not possible, would be great to know if it is though. From what I know webrtc can be done only via browser to browser and not rtmp
SAwesome. As beta user I would say having option to record is the most important thing. Clients would not do livestreams without option to downlod them later.
Counter and analytics features can be developed on the client side.
Counter and analytics features can be developed on the client side.
AIs it possible when using Web-rtc to have Creator being streaming and some viewers also Talking back live with the creator?
1#calls would be what you are looking for
AThx, already using it but for my understanding latency with Stream should be much less compared to calls? What am I missing?
1Stream isn't for 2 way calls
KI'm uploading a video of resolution
1280x692is there a way to generate streams in 720p as well?
1Render your video in 720p before upload
Kcan't cf stream do this on its own?
1It wont if the source video is below that res
1Stream isnt a transcoding product
Kyah by default it won't but there should have been some option
1Ive been asking for that for a while lol
Kohh 
.
.1Like it does transcoding in the background, but you cant force it to render weird stuff like that
Kunderstood but they could do something like if its above 680 or something
Kin such cases 720 can be generated
Kor else there's kinda a huge difference
1where is your video coming from? Why the odd resolution
Kthe users are uploading it.
1Not sure who the Stream PM is but can someone more official confirm this?
KI thought you've confirmed it 
1As far as Im aware, but I dont work for CF
Knot much people are active in this channel
Kdid you read it somewhere in docs?
1I can't find a specific reference in the doc
KI'm not sure if they've even mentioned it in docs or not
1But I dont see any reason to waste transcode on upscaling a video very slightly. The pipeline would not be made to do so currently I would imagine
1Why would they? Its a very odd use case
Ki mean they should atleast mention that the streams will only be available in resolution <= resolution of original video
1Common sense would dictate that
Ktrue
1That specific resoluton you mentioned is an odd aspect ratio, how would you want it handled? Cropped to fit in the 720p frame, squeezed to fit, zoomed? Too many variables for what is wasted resources on tiny niche use case
Kokay, but then there should be an option to play the video in the original resolution as it was uploaded
Kapart from the degraded resolutions