From: Guillaume Denis <gdenispro@gmail.com> To: galene@lists.galene.org Subject: [Galene] about packet pacers Date: Fri, 6 Aug 2021 14:11:01 +0200 [thread overview] Message-ID: <CAB0ELa-TRP7md2=9xZip7QwJMyTJfHT0rjOQXLqymPMM_2LqiQ@mail.gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1491 bytes --] Hello Galène, hello Toke (I might have a question for you below!) For a bit of context I am working on a project [1] that uses pion, in a different fashion than Galène since we transform audio/video streams and add effects to them, implying that we decode and reencode them server side (with GStreamer). My initial question was about how to adapt encoder settings (bitrate) to network conditions, for instance not to send a 200KB/s video to a 100KB/s capable network. Juliusz pointed Google Congestion Control Algorithm [2] and Galène's implementation out to me: thanks to RTCP receiver and REMB reports, and thanks to the GCC algorithm, I can compute a desirable bitrate. Now this bitrate can be used to monitor encoder settings. This article https://www.aitrans.online/static/paper/Gcc-analysis.pdf also mentions that pacers and padders should be adapted. Toke, would you have some input regarding this: - do you think that in this use case monitoring a pacer with the target bitrate would have real added value? - I guess the pacer must act before the RTP packetizer so that timing information present in RTP headers are correct/not modified by the pacer. Is this correct? - are you aware of any reusable pacer implementation? I am also wondering if it would make more sense to be part of GStreamer processing or in pion Thanks, Guillaume [1] https://github.com/creamlab/ducksoup [2] https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-gcc-02 [-- Attachment #2: Type: text/html, Size: 1903 bytes --]
next reply other threads:[~2021-08-06 12:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-06 12:11 Guillaume Denis [this message] 2021-08-06 13:42 ` [Galene] " Juliusz Chroboczek 2021-08-06 20:34 ` Toke Høiland-Jørgensen 2021-08-06 23:01 ` Juliusz Chroboczek 2021-08-10 8:10 ` Guillaume Denis 2021-08-18 18:43 ` Juliusz Chroboczek 2021-08-18 21:32 ` Juliusz Chroboczek 2021-08-19 9:25 ` Guillaume Denis 2021-08-19 11:10 ` Juliusz Chroboczek 2021-09-28 20:51 ` Dave Taht
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAB0ELa-TRP7md2=9xZip7QwJMyTJfHT0rjOQXLqymPMM_2LqiQ@mail.gmail.com' \ --to=gdenispro@gmail.com \ --cc=galene@lists.galene.org \ --subject='Re: [Galene] about packet pacers' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox