5 comments

  • Sean-Der 9 hours ago

    This is something I have been working on for years and am sssooo excited to see merged. This starts a new generation of broadcasting (I hope)

    * Cheaper servers. More competition and I want to see people running their own servers.

    * Better video quality. Encoding from source is going to be better then transcoding.

    * No more bad servers. Send video to your audience and server isn't able to do modification/surveillance with E2E Encryption via WebRTC.

    * Better Latency. No more time lost transcoding. I love low latency streaming where people are connected to community. Not just blasting one-way video.

    ----

    Please please test it out! I want to catch any bugs/make improvements before branch cut.

      nihiven 8 hours ago

      This all sounds great, how does this merge enable these things? I'm not very familiar with streaming or how this would work.

      Edit: I see there is some info at: https://obsproject.com/kb/whip-streaming-guide

        Sean-Der 8 hours ago

        Yea it shows up in the UI. Sorry I am so wrapped up in it I don’t know how to explain it well.

        What part did I do a bad job at explaining? The what it does, why it’s exciting or just the enabling it?

          nihiven 8 hours ago

          I don't understand how adding WebRTC/Whip enables the bullet points you listed. Is the idea that we'll transcode locally and because of that, we can set up a cheap host? How does this impact the level of hardware we'll need locally?

          Thanks for taking the time to answer.

            Sean-Der 7 hours ago

            Pretty much! You are doing multiple encodes lately.

            Yes you will use more bandwidth/compute locally. In the future I hope to support SVC so you have zero bandwidth overage.