workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
âš¡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
HLS playback discussion thread
We're also still having the same issues with (some) HLS streams, I'm afraid.
Thanks for responding la x rc 1203 sorry
Thanks for responding @la.x.rc , sorry I missed it. Should I follow up with a forum thread instead? I am a bit puzzled by the cloudflare player as any company serving short videos has / will have this issue… I could roll out my own customised video.js player but would love to use the CF one if possible
Two use cases if it is allowed
Two use cases if it is allowed:
1. Phishing. This could be used for malicious actors to make users think they're streaming to the correct account when they're really streaming somewhere else. If the only thing that differentiates between which account a stream goes is the stream key then it would be easy to trick users. Example: If live.securemedicalstreams.com is CNAMEd as a Cloudflare Stream domain. A malicous user finds that out via a simple DNS scan. So they add the domain to their account too. They can phish a user giving them the real domain, just with their own stream key. If that's possible both live.securemedicalstreams.com/1111111111 and live.securemedicalstreams.com/2222222 could go to separate stream accounts with one potentially being malicious.
2. Shared vanity domain. A use case for allowing it would be to let multiple users use custom domains. I have ingest.stream and rtmps.stream which make good ingest domains imo. I don't care if others use them....
I’ll check back in in a few days if
I’ll check back in in a few days, if YouTube holds then it’s definitely the Restream. But to be clear, cloudflare’s regular HLS output held perfectly for a week now. Only the restream seems to be an issue.
i m using the cloudflare stream player
i'm using the cloudflare stream player and am trying to pause a video if it is playing when a users clicks on another tab
```javascript
const player = Stream(playerFrame);
if (document.visibilityState === "hidden") {
console.log("pausing");...
👋 Generating mp4 downloads for my
👋 Generating mp4 downloads for my videos used to be snappy, but the one I just kicked off is moving glacially slow. Like it's been 5 minutes and it's done 22% of a 30 second video 😛 Has something changed recently?
Me too Having the stream player be
Me too. Having the stream player be iframed also means we can't use the MediaSession API :/
Abnormal playback through WebRTC
I am testing WebRTC, starting the stream from OBS, and trying the playback on this demo website: https://webrtc.player.eyevinn.technology/
Anything moving around seems like it's running on very slow framerate? I don't know how to describe it, maybe the included video can do better job? And it's not just moving cars, if an individual in the stream waves their hand, it seems choppy....
Is there any way to set
Is there any way to set maxDurationSeconds when uploading from a URL?
https://developers.cloudflare.com/api/operations/stream-videos-upload-videos-from-a-url
It seems the Upload-Metadata header is fully ignored here...
Thanks We need MPEG 4 Part 14 container
Thanks. We need MPEG-4 Part 14 container videocoded as HEVC or H264, progressive scan, closed GOP, 4:2:0 chroma subsampling. Those are requirements to be able to upload a reel in Instagram
WebRTC Beta - still Beta?
Did the Beta end? Not seeing the option appear any-longer in our Console view (paid account)
It s usage based so you d be paying per
It's usage-based so you'd be paying per minute delivered to each viewer
FRC Ontario
Hey Jamie!
- You can have as many ingest endpoints as you need — in Stream these are called "live inputs"
- You can see when ingest started by looking at the
created timestamp of the video UID associated with a given live input (/live_inputs/uid/videos https://developers.cloudflare.com/stream/stream-live/watch-live-stream/#use-the-api) - when you start streaming to a live input, a new video UID is created, and this created timestamp should match when we start receiving video
- Max resolution is 1080p. What's the use case for 4x 1080p streams? Can you describe what purpose this serves today, and why it's important?...API docs inconsistency
https://api.cloudflare.com/#stream-live-inputs-list-live-inputs
https://developers.cloudflare.com/api/operations/stream-live-inputs-list-live-inputs
the
result object is supposed to contain the streams inside a liveInputs object like this:
```json...New: Changelog RSS feed
New: RSS feed for the Cloudflare Stream changelog
Interested in subscribing to updates about new functionality and changes to Cloudflare Stream? Our changelog (https://developers.cloudflare.com/stream/changelog/) now has an RSS feed, at https://github.com/cloudflare/cloudflare-docs/commits/production/content/stream/changelog.md.atom.
Plug it into your RSS reader, or into an RSS-to-email tool like Feedrabbit, Zapier, or IFTT to get email updates about new features and updates to Stream....
h264 WebRTC support
I don't believe there is currently, as Stream's WHIP endpoints do not support h264 yet.