From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Alexandre IOOSS <erdnaxe@crans.org>,
galene@lists.galene.org, nounous@crans.org,
Sean DuBois <sean@siobud.com>
Subject: [Galene] congestion control, loss (recovery), whip and obs...
Date: Tue, 11 Jul 2023 10:18:40 -0600 [thread overview]
Message-ID: <CAA93jw5PK3qo=SqypoiaDR=tx79DAtNxvn5eqvxKAZdB3L1e0A@mail.gmail.com> (raw)
In-Reply-To: <87bkgiwowv.wl-jch@irif.fr>
I would dearly like to be capturing more data and pictures of what
videoconferencing traffic looks like, through the CAKE algorithms in
libreqos. I know that sean put google congestion control (GCC) into
pion and I think now, twitch? GCC was recently "dissed" somewhat in
this paper, but I think it was some old versions in there:
https://tma.ifip.org/2023/wp-content/uploads/sites/12/2023/06/tma2023-final37.pdf
Naturally fq_codel shines. The paper also introduces a new means of
measuring videoconference QoE, called BRISQUE.
I know there are some really complicated high stress OBS setups out there.
I am very interested in the difference between vp8 and vp9 in
particular, in bandwidth demands and loss response.
On Tue, Jul 11, 2023 at 7:36 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> > Streaming with OBS Studio (master branch) works fine with Galene "whip2"
> > branch. Here is a recording of the test:
> > https://owncloud.crans.org/s/rkqbv9P9T6Tkhu4
>
> Excellent news, thanks for testing, Alexandre! I have no idea why my test
> failed last night.
>
> Sean, now you need to implement VP9 SVC in OBS :-)
>
> -- Juliusz
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2023-07-11 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 14:29 [Galene] OBS Studio and Galene WHIP Alexandre IOOSS
2023-06-10 16:00 ` [Galene] " Juliusz Chroboczek
2023-07-10 21:35 ` Juliusz Chroboczek
2023-07-10 22:04 ` Sean DuBois
2023-07-10 23:12 ` Juliusz Chroboczek
2023-07-10 23:21 ` Sean DuBois
2023-07-11 0:30 ` Juliusz Chroboczek
2023-07-11 17:39 ` Alexandre IOOSS
2023-07-11 19:22 ` Sean DuBois
2023-07-11 12:05 ` Alexandre IOOSS
2023-07-11 13:36 ` Juliusz Chroboczek
2023-07-11 16:18 ` Dave Taht [this message]
2023-07-11 19:34 ` Sean DuBois
2023-07-11 20:33 ` Juliusz Chroboczek
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='CAA93jw5PK3qo=SqypoiaDR=tx79DAtNxvn5eqvxKAZdB3L1e0A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=erdnaxe@crans.org \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--cc=nounous@crans.org \
--cc=sean@siobud.com \
/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