Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Sean DuBois <sean@pion.ly>
To: Dave Taht <dave.taht@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: Future plans: Pion v4 and TWCC
Date: Wed, 1 Jan 2025 20:16:28 -0500	[thread overview]
Message-ID: <6F18A9C1-ED2E-4080-8B4F-11CF94F16347@pion.ly> (raw)
In-Reply-To: <CAA93jw6+Q+rVHYtuqj=e-i13OYxqUwhpefw8xoa+0A0y6EXcfg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]

It does [0]

It can use improvements though. I have been distracted by broadcasting/robotics recently, but I would
love to come back to this.

[0] https://github.com/pion/interceptor/blob/master/pkg/gcc/delay_based_bwe.go#L50


> On Jan 1, 2025, at 5:27 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> On Wed, Jan 1, 2025 at 12:45 PM Juliusz Chroboczek <jch@irif.fr <mailto:jch@irif.fr>> wrote:
>> 
>> Hi,
>> 
>> The reason I've released 0.96 is that it looks like a rock solid version,
>> and I'm planning to break things.  More specifically, I've just finished
>> doing a straightforward port to Pion WebRTC v4, and I'm planning to make
>> the following changes to Galene's protocol:
>> 
>>  - use a separate RTX track for retransmissions;
>>  - use TWCC instead of REMB for GCC congestion control.
>> 
>> The RTX track will allow browsers to do more precise accounting of packet
>> loss, which should improve behaviour under packet loss.  Replacing our
>> home-grown implementation of REMB with Pion's implementation of TWCC will
>> hopefully improve behaviour on congested links (it will no longer be
>> necessary to manually switch to "Send: low" when on a slow link), but more
>> experimentation is needed.
>> 
>> This work is going on in the "pion-v4" branch, which I'll merge into master
>> when I'm satisfied it doesn't break anything.
> 
> Did delay and not just loss make it into pion?
>> -- Juliusz
>> _______________________________________________
>> Galene mailing list -- galene@lists.galene.org <mailto:galene@lists.galene.org>
>> To unsubscribe send an email to galene-leave@lists.galene.org <mailto:galene-leave@lists.galene.org>
> 
> 
> 
> -- 
> Dave Täht CSO, LibreQos
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org <mailto:galene@lists.galene.org>
> To unsubscribe send an email to galene-leave@lists.galene.org <mailto:galene-leave@lists.galene.org>

[-- Attachment #2: Type: text/html, Size: 10501 bytes --]

  reply	other threads:[~2025-01-02  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 20:45 [Galene] " Juliusz Chroboczek
2025-01-01 22:27 ` [Galene] " Dave Taht
2025-01-02  1:16   ` Sean DuBois [this message]
2025-01-02 17:57     ` Dave Taht
2025-01-02 19:15       ` Tim Panton
2025-01-02  1:49   ` Juliusz Chroboczek
2025-01-02 17:58     ` 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=6F18A9C1-ED2E-4080-8B4F-11CF94F16347@pion.ly \
    --to=sean@pion.ly \
    --cc=dave.taht@gmail.com \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox