3 ms·

Seems cool! Was getting into WebRTC last year and this would have helped a lot. Is the pricing for this available yet?

verdverm 2y ago
Looks to be $0.05 / realtime GB https://blog.cloudflare.com/whats-next-for-cloudflare-media https://blog.cloudflare.com/whats-next-for-cloudflare-media
- bcjordan 2y ago
  What bandwidth does a typical video call use per hour?
  - leetrout 2y ago
    First TB is free. I would assume at least 1.5 Mbps for HD so ~5.4 Gbph ... ~.7 GBph so 3.5¢ per hour if my math checks out. Unclear if that would multiply by number of callers.
  - Sean-Der 2y ago
    Depends what codec! For 1280x720 with a VMAF score of 90 this is the numbers I use. * H264 - 1.25Mbps * VP8 - 1.00Mbps * VP9 - 700kbps * AV1 - 550kbps
Sean-Der 2y ago
What did you find difficult about WebRTC? What could have been better/easier?
- parhamn 2y ago
  I couldn't tell if this was a joke.
  - Sean-Der 2y ago
    Why do you think this was a joke? I have have been trying my best to make WebRTC more accessible [0] [1]. It's powerful, but the complexity makes it challenging. [0] https://github.com/pion https://github.com/pion [1] https://webrtcforthecurious.com https://webrtcforthecurious.com
    - parhamn 2y ago
      Thanks for your work -- I've used pion before myself. Then you know the answer to that question. I imagine on a thread like this that would only tread the surface of the complexity, the first question will always be "What the hell even is STUN, TURN, ICE, SCTP, DTLS, SRTP?" And thats the beginning of the complexity. But it's also a naturally complex problem. So, I thought it was a joke.
- adhamsalama 2y ago
  To me it was that all tutorials are very outdated, using deprecated browser APIs, and/or using packages and services that abstract away WebRTC (SimpleWebRTC deprecated package and service, PeerJS, etc...), and none of them using TypeScript. So I wrote my own WebRTC app that solves all of those issues [0]. I really liked your book, but there's no code in it at all, and I'm a person that learns more by following examples and applying them. I honestly found it a bit weird that a book about WebRTC has no code at all. [0]: https://github.com/adhamsalama/webrtc https://github.com/adhamsalama/webrtc
- gslaller 2y ago
  Thanks for your contribution and maintaining the pion library(I am a user). The thing is that WebRTC usually isn't a complete solution, many don't want to have p2p but a p2s2p(which usually means distributed computing/SFU) solution, which makes developing an application way too complex.

Looks to be $0.05 / realtime GB https://blog.cloudflare.com/whats-next-for-cloudflare-media https://blog.cloudflare.com/whats-next-for-cloudflare-media

bcjordan 2y ago
What bandwidth does a typical video call use per hour?
- leetrout 2y ago
  First TB is free. I would assume at least 1.5 Mbps for HD so ~5.4 Gbph ... ~.7 GBph so 3.5¢ per hour if my math checks out. Unclear if that would multiply by number of callers.
- Sean-Der 2y ago
  Depends what codec! For 1280x720 with a VMAF score of 90 this is the numbers I use. * H264 - 1.25Mbps * VP8 - 1.00Mbps * VP9 - 700kbps * AV1 - 550kbps

Sean-Der 2y ago

What did you find difficult about WebRTC? What could have been better/easier?

parhamn 2y ago
I couldn't tell if this was a joke.
- Sean-Der 2y ago
  Why do you think this was a joke? I have have been trying my best to make WebRTC more accessible [0] [1]. It's powerful, but the complexity makes it challenging. [0] https://github.com/pion https://github.com/pion [1] https://webrtcforthecurious.com https://webrtcforthecurious.com
  - parhamn 2y ago
    Thanks for your work -- I've used pion before myself. Then you know the answer to that question. I imagine on a thread like this that would only tread the surface of the complexity, the first question will always be "What the hell even is STUN, TURN, ICE, SCTP, DTLS, SRTP?" And thats the beginning of the complexity. But it's also a naturally complex problem. So, I thought it was a joke.
adhamsalama 2y ago
To me it was that all tutorials are very outdated, using deprecated browser APIs, and/or using packages and services that abstract away WebRTC (SimpleWebRTC deprecated package and service, PeerJS, etc...), and none of them using TypeScript. So I wrote my own WebRTC app that solves all of those issues [0]. I really liked your book, but there's no code in it at all, and I'm a person that learns more by following examples and applying them. I honestly found it a bit weird that a book about WebRTC has no code at all. [0]: https://github.com/adhamsalama/webrtc https://github.com/adhamsalama/webrtc
gslaller 2y ago
Thanks for your contribution and maintaining the pion library(I am a user). The thing is that WebRTC usually isn't a complete solution, many don't want to have p2p but a p2s2p(which usually means distributed computing/SFU) solution, which makes developing an application way too complex.