Sean-Der

16 ms·

1. 241.▲
   by Sean-Der 2y ago

   Peer calls can run in P2P mode or as a SFU. Different topologies are better for different use cases. 1:1 vs group calls in this case!
2. 242.▲
   by Sean-Der 2y ago

   I think people are excited because it’s easy to run yourself and well documented. I find the code base easy to understand since it’s built by one developer. It’s a consistent read and not sprawling/pointless duplication
3. 243.▲
   by Sean-Der 2y ago

   My dream would be if WebRTC Agents would experiment with Port Control Protocol. I don't know if it is the answer, but a world without dependence on STUN servers sounds pretty amazing. I can see why it would feel like kludge, but how co
4. 244.▲
   by Sean-Der 2y ago

   I don't think Chrome or FireFox support passive ICE-TCP Candidates. The assumption is that two clients are in the same LAN they would use UDP anyway. If are in two differents NATs doing traversal with TCP isn't support. I have rea
5. 245.▲
   by Sean-Der 2y ago

   You should build that!
6. 246.▲
   Cloudflare released WebRTC TURN via anycast(blog.cloudflare.com)

   9 points by Sean-Der 2y ago|0 comments
7. 247.▲
   by Sean-Der 2y ago

   Check out the initial commit of https://github.com/awslabs/amazon-kinesis-video-streams-webr... it was Pure C and simple. Early versions of https://github.com/pion/webrtc used lots of cgo its an e
8. 248.▲
   by Sean-Der 2y ago

   I love that WebRTC re-uses existing IETF standards. Makes it easy to plug existing pieces together. I tried to capture that with webrtcforthecurious.com breaking it down by subsystem. I should do a companion piece ‘Build yourself a WebRTC’
9. 249.▲
   by Sean-Der 2y ago

   ONVIF is getting WebRTC [0]! So you will be able to use it in your LAN (or over ) without using proprietary middleware :) [0] https://www.onvif.org/specs/stream/ONVIF-WebRTC-Spec.pdf
10. 250.▲
    by Sean-Der 2y ago

    I’m working on this! A WebRTC implementation for my microcontrollers exist https://github.com/sepfy/libpeer it requires more work to use then most want (but it is the perfect building block for higher pieces) I am tryi
11. 251.▲
    by Sean-Der 2y ago

    My assumption is the amount of people encoding is much smaller then decoding. overlap exist in encode/decode. When working on a Opus codec I did have a fair amount of code distinct to one path still.
12. 252.▲
    by Sean-Der 2y ago

    It’s my passion in life to see WebRTC utilized to its full potential! When I learned about P2P/NAT Traversal I could never go back :) Why do you think it’s had trouble? Poor software, educational materials etc… always looking for new p
13. 253.▲
    Open Source security camera on Raspberry Pi(github.com)

    286 points by Sean-Der 2y ago|52 comments
14. 254.▲
    Microcontrollers getting native WebRTC Support(youtube.com)

    2 points by Sean-Der 2y ago|0 comments
15. 255.▲
    by Sean-Der 2y ago

    What are your encoder settings? Mind joining the discord easier to debug I don’t actively check HN sorry :/
16. 256.▲
    by Sean-Der 2y ago

    mediamtx is a great project! Use w/e works best for your use case. I just encourage people to use. * Free Software * Project is operated/managed by individuals * Use Open Standards/Protocols
17. 257.▲
    by Sean-Der 2y ago

    Google doesn't use any STUN/TURN servers I just went and confirmed. The following is the RTCPeerConfiguration used. ``` https://meet.google.com/***-***-\*\ *, { iceServers: [], iceTransportPolicy: all, bundlePolicy
18. 258.▲
    by Sean-Der 2y ago

    My public instance runs on a world addressable host and doesn't have TURN. I have no problem using it from my phone and it is behind a CG NAT. No TURN/Relay servers are needed. > I've never been able to use any WebRTC-enab
19. 259.▲
    by Sean-Der 2y ago

    I would have your friend stream to Broadcast Box. You can run it on the Raspberry Pi! Then I would pull that source into your OBS. You have two options * Pull Broadcast Box as a browser source * Use my PR that adds WHEP Sources https:&#x2F
20. 260.▲
    by Sean-Der 2y ago

    H265 support is available in Chrome now! Launch with these flags `--enable-features=WebRtcAllowH265Receive --force-fieldtrials=WebRTC-Video-H26xPacketBuffer/Enabled` I haven't used it myself yet.
21. 261.▲
    by Sean-Der 2y ago

    I am excited for you to use it! If you run into bugs or have any cool ideas join the discord and would love to chat https://discord.gg/An5jjhNUE3
22. 262.▲
    by Sean-Der 2y ago

    To build this quickly I would chain Broadcast Box instances. Have it look like a n-ary tree and spin up another broadcast box instance when you need it. `OBS -> Broadcast Box -> Broadcast Box -> Broadcast Box -> Viewer` To start
23. 263.▲
    by Sean-Der 2y ago

    This is all done client side. OBS sends up multiple renditions, the server is just in charge of forwarding the specific layer. I think this is better in a few ways. * Lower latency - The extra decode + encode adds enough latency that you st
24. 264.▲
    by Sean-Der 2y ago

    vdo.ninja is a fantastic project, can’t recommend it enough. It made the dream of ‘co-streaming’ available to home users and not just those with hardware/pro setups.
25. 265.▲
    by Sean-Der 2y ago

    Lots of options! More and more WebRTC SFUs are adding WHIP support. Check out https://galene.org/ it lets you do OBS in and has things like chat. Might be better if you are streaming to family and want chat. I would try and
26. 266.▲
    by Sean-Der 2y ago

    Open Source doesn’t have an instant scalability offering yet. I hope someone takes it on! Quite a few companies offer this a service though. Cloudflare, Twitch’s IVS, Dolby Millicast, Phenix RTS… LiveKit did a write up on how they built the
27. 267.▲
    by Sean-Der 2y ago

    I created Broadcast Box originally as a reference server to test OBS against. It was way easier for people to test my WebRTC/WHIP PRs against. Seeing people use it I am seeing the benefits/excitement more. * low latency means you
28. 268.▲
    by Sean-Der 2y ago

    I agree, if you are in a perfect network! If you have any packet loss, changes in throughput, or roaming it breaks down. RTMP for me is preventing that next generation of use cases.
29. 269.▲
    by Sean-Der 2y ago

    It drives me crazy that we have had the technical ability to do these things, but just not the demand. I believe it is a chicken/egg problem. It is one of those things that you don't get until you try it yourself. I hope if more b
30. 270.▲
    by Sean-Der 2y ago

    The alternative today is ~few seconds. This is from my T420 Thinkpad on Linux. The only significant input I can think is my RTT to the server. ``` Reply from 165.227.221.230: bytes=32 time=37ms TTL=49 Reply from 165.227.221.230: bytes=32 ti