I meant that if it is somewhere in the documentation, I was able to obtain the endpoint but using th
I meant that if it is somewhere in the documentation, I was able to obtain the endpoint but using the browser's dev tools
TOh! That's be cool. Especially because if you call the endpoint too often you start getting 429s
YWill traffic still be charged without using relays?
TThe live clipping feature feels like a joke. You can just cut out one single specific part of the video?! Thanks for nothing. Instead they should make the WebRTC stable for professional use, especially when more than 50 viewers are watching.
TThere are some issues, based on your WHEP implementation example and also recommended OBS settings:
- short stutter/framedrops of about a half of a second till 2 seconds while audio is running fine, occurs randomly every 5 till 30
seconds, this can differ from day to day on the same device - It constantly stopping (hang up) after a while and playback don’t continue automatically, it needs full reload of the player
- when starting playback sometimes it buffers endlessly and doesn’t playback the stream
- sometimes the audio channel won’t play while the video is running and starts after a while (~ 3 minutes), reloading the page don’t fix it, also this occurs randomly between different devices
- our audience needs to reload the video page often to get a stable playback or to continue watching, also it looks like the more viewers are watching (50+) the more issues we have (also on a same device)
KMy two cents: I think changes like live clipping are more essential, and I appreciate the work being done in these directions; I understand webrtc stuff is the future so to speak with its lower latency etc, but I can't help but to feel that this "shinier" tech is drawing resources away from core "stream" features (or perhaps there is just less presence here in the discord, and its not a matter of resources). There are relatively smaller changes, such as fleshing out live clipping/live rewind, or allowing instant mp4 downloads without the processing (which occasionally just errors out), videos stuck in a live-inprogress state for 10 months, etc, that I think would help a larger proportion of actual Stream users. I don't think webrtc users/requesters constitute a significant proportion of Stream users in terms of actual production usage, but perhaps I am mistaken about this.
TThe OBS WHIP output currently only supports AVC and AV1. AV1 is available as of the 30.1.0 release.
TYeah, I honestly haven't been keeping track of which browsers are supporting it. We should probably add HEVC at some point soon
IIf anything HEVC support looks even patchier than AV1, or at least there are a lot more
*caveat
TDidn’t know of the licensing issues, so thanks for this information. Although h265 would be the better codec in terms of compression and quality.
TVP9 isn’t fully supported by iOS, VP8 can’t be used for WHIP (just for local recording). I’ve tested this on OBS and Streamlabs. AV1 is also not supported and crash the software when start streaming. The only option is H264 Software and NVIDIA H264. Since we have round about 30 streamer making live streaming we need some robust solution any of them can use out of the box. Actually the missing audio track when starting the video is very frustrating, this issue wasn’t there before a week. The WHEP/WHIP just doesn’t feel stable actually.
TAudio and Video looks good, no issues. The missing audio occurs randomly, not every start of the stream. Also we got more issues when more viewers are watching. When I tested myself everything is fine.
TOur audience is coming from Germany only, no VPN used.
TUsing the latest/current OBS release
THEVC hardware decode is at this point available on most platforms, so it's really a pretty good stop-gap solution until AV1 decoders catch up, especially on mobile devices
TI can reproduce 3 issues from my list when playing your test stream:
- short framedrops of about 1 second every 30 seconds till 2 Minutes (roundabout)
- the stream hangs up after a while of playing, especially when tab was inactive or run in background before refocus again
- stream was starting with no audio
DHello - I'm seeing random buffering in our CloudFlare livestreams. Streaming from OBS to Restream to YouTube and CloudFlare. YouTube stream has no buffering. Recording has no issues. But livestream in Cloudflare has buffering with 3 dots on the center of the frame at random intervals. Any suggestions for how to improve this?
DI'm seeing this error in the Console Log: [warn][hlsjs: non-fatal error occurred]
{evt: 'hlsError', data: {…}}
data
:
{type: 'mediaError', details: 'bufferStalledError', fatal: false, buffer: 0.08654699999999593}
evt
:
"hlsError"
{evt: 'hlsError', data: {…}}
data
:
{type: 'mediaError', details: 'bufferStalledError', fatal: false, buffer: 0.08654699999999593}
evt
:
"hlsError"
DI don't - is this what you're looking for? https://help.tanium.com/bundle/HARfile-Create-Read/page/KA/HARfile-Create-Read/HARfile-Create-Read.htm
T1 would be great to get improvements, my CPU usage is around 0.5% when streaming so 99.5% are available (using CPU Encoder)
2 probably the player implementation, unfortunately it isn’t that easy to get same stable behaviour like the iframe integrated CF player. biggest issue is to continue playing when stopped without needing to fully reload/re-instantiate the player
3 the audio recovers after 1 till 3 minutes, this issue wasn’t there before a week roundabout, since then it randomly happens, reproducable, along different devices, also your teststream
2 probably the player implementation, unfortunately it isn’t that easy to get same stable behaviour like the iframe integrated CF player. biggest issue is to continue playing when stopped without needing to fully reload/re-instantiate the player
3 the audio recovers after 1 till 3 minutes, this issue wasn’t there before a week roundabout, since then it randomly happens, reproducable, along different devices, also your teststream
Jhello. I am currently working as a backend developer at a startup in Korea. I'm trying to use Cloudflare as a stream service, but I have a few questions.
- I heard that there is a problem with the Korean regional CDN regarding network usage fees. Will there be any problems using the Korean CDN with Cloudflare stream now?
- Are there additional charges to use Korean CDN with Stream Service?
2.1 If additional fees are required to use the Korean CDN, how are those fees charged?
2.2 What is the structure of the additional fees required to use the Korean CDN, and is there a way to minimize the additional costs?
NHi,
anyone using Cloudflare Stream for live streaming? I tried to stream with OBS Studio to it, but I always had the Error „the RTMP Server sent a invalid SSL Certificate“ - do you have a idea how I could fix this problem?
anyone using Cloudflare Stream for live streaming? I tried to stream with OBS Studio to it, but I always had the Error „the RTMP Server sent a invalid SSL Certificate“ - do you have a idea how I could fix this problem?
TUpdate Windows
TYour CA cert repository is outdated
NIt’s a fresh install of Windows 10 
I also updated the CA cert repo
I also updated the CA cert repo