frudas24

3 ms·

1. 1.▲
   by frudas24 9mo ago

   fixed :)
2. 2.▲
   by frudas24 9mo ago

   Thanks, that’s a great suggestion :) You’re right that re-timestamping is the proper way to avoid renegotiation, and the swap-tracks example is exactly the direction to take. In our case, monitor/crop changes usually required restartin
3. 3.▲
   by frudas24 9mo ago

   The WebRTC complexity came from our pipeline being ffmpeg → H.264 RTP over UDP → pion/webrtc TrackLocalStaticRTP (instead of a “normal” WebRTC source). Any time we changed monitor/crop or restarted the capture, the RTP stream effe
4. 4.▲
   Show HN: DeskSlice – controlling a VS Code agent from my phone(github.com)

   3 points by frudas24 9mo ago|5 comments