https://discord.cloudflare.com logo
Join Discord
Powered by
# stream
  • i
  • d
    Thanks for the contribution, Isaac! Just hit merge on that for ya 😀
  • i
    Awesome, thanks! No problem... glad I could help contribute, got me stuck for a good hour since the errors didn't explain what I was doing wrong 🙂
  • m
    it's unfortunate that support doesn't seem to understand Stream Live, every ticket about ingest issues is responded to with asking about Ray IDs and such 😕
  • p
    should the 
    Upload-Creator
    -header also be in base64? https://developers.cloudflare.com/stream/uploading-videos/creator-id/#tus
  • p
    is it 
    'Upload-Creator': creatorId
    or is it 
    'Upload-Creator': btoa(creatorId)
    ?
  • p
    the docs says "For more information, refer to **Using tus.**", but 
    Upload-Creator
    isn't mentioned here: https://developers.cloudflare.com/stream/uploading-videos/direct-creator-uploads/#using-tus-recommended-for-videos-over-200mb
  • t
    Hey there! 👋 We'll see what we can do to fix that! Thank you for mentioning it here. In the meantime, we've got a form you can submit issues with Stream Live to that will come directly to the Stream team. https://docs.google.com/forms/d/e/1FAIpQLScPNYLzhslGtQ4SUmjGobthg3YqRYF9xVj5j5bAm0UwsQW97g/viewform
  • d
    90 fps?! 👀
  • o
    Copy code
    Access to XMLHttpRequest at 'https://cloudflarestream.com/*****/manifest/video.m3u8' from origin 'https://localhost:8000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
    The issue I am having is when I am trying to load a hls or m3u8 into my local system, it's blocking cause of CORS
  • o
    I haven't been able to figure out where I would be setting the policy for CORS within cloudflare
  • k
    Copy code
    HTTP/2 200 
date: Wed, 15 Jun 2022 11:38:31 GMT
content-type: application/x-mpegURL
access-control-allow-origin: *
  • k
    Seems like it returns it fine for me
  • e
  • d
    question for the stream team. would it be possible to have the option to change/choose the SRT AES encryption key length? i'm using a cheap HDMI encoder that is unfortunately only capable of AES-128 at the moment. i'd just like to rule that option in or out before i dive into custom firmware 😅 cheers
  • p
  • s
    Hey Stream community 👋 . The Cloudflare Stream team is piloting some videos to walk through some of our core features! We're open to feedback and requests for things you'd like to learn or see.

    https://www.youtube.com/watch?v=AkaaKRGXyAI▾

    https://www.youtube.com/watch?v=1z66mnkAJ9A▾

  • k
  • k
    You can do 
    /cfrole
    to get the Cloudflare role here FYI
  • p
    good stuff! 🙂 a quick question, as I'm pretty new to these things: at 6:25 you have this header
    Copy code
    js
'Upload-Metadata': request.headers.get('Upload-Metadata')
    is this to allow the client full control over what is allowed to be uploaded? in my own implementation, I add my own metadata server-side, like 
    maxDurationSeconds
    - am I missing out on something by doing this, and not using what the client sends?
  • s
    Great question. For client uploads from a browser, there might be some things you want to avoid hardcoding on the server, such as the filename, etc. If you want to restrict some fields to be immutable, such as the maxDurationSeconds, you can leave that on the server side, otherwise the client could override these values. Other values, such as watermark, could be pulled from the client if you give the user an option to add a custom watermark, for example. Upload constraints: https://developers.cloudflare.com/stream/uploading-videos/direct-creator-uploads/#upload-constraints Supported options in upload metadata: https://developers.cloudflare.com/stream/uploading-videos/upload-video-file/#supported-options-in-upload-metadata
  • p
    thank you for the detailed answer! I definitely see how it can make sense to let the user directly control some of the metadata. probably would've whitelisted the input though, but that's easy to do 🙂
  • m
    Is there anything to we can do to limit the bandwidth used by stream when serving videos? specifically we're using stream to serve videos in ads, and sometimes the bigger videos hit chrome's Heavy Ad Intervention and get disabled.
  • e
    Would your goal be to cap the resolution / bandwidth consumption (at the cost of visual quality) here?
  • p
    that's how I read it. basically the opposite of what 
    clientBandwidthHint
    does
  • p
  • e
    With a third-party/your own player, you could forcibly set the client bandwidth or limit the max res instead of parsing the manifest (which is more fragile)
  • m
    @elithrar yes, the dream would be "playing this video can use at most X bandwidth"
  • m
    we are doing some integration with our own player so that could have potential
  • p
    totally agree with this, was imagining a case where you didn't have full control over the player.
1...262728...105Latest