From: Juliusz Chroboczek <jch@irif.fr>
To: Sean DuBois <sean@siobud.com>
Cc: Alexandre IOOSS <erdnaxe@crans.org>, galene@lists.galene.org
Subject: [Galene] Re: OBS Studio and Galene WHIP
Date: Tue, 11 Jul 2023 22:33:31 +0200 [thread overview]
Message-ID: <87fs5uur1g.wl-jch@irif.fr> (raw)
In-Reply-To: <ZK2u0hjo2jofN6lU@SeanLaptop>
(Removed nounous from CC.)
> How much better is SVC then Simulcast? I can bring it up with OBS devs,
> but Simulcast is already pretty tough to convince people it is worth it.
It's simpler to implement, and it allows much more fine-grained control:
you don't need a keyframe in order to switch layers, and you don't need to
consult NTP timestamps (which might not be available) to ensure that time
doesn't flow backwards when you switch.
In the specific case of Galene, SVC is rock solid, while there are
occasional visual glitches when switching simulcast streams. And the
simulcast switching code can be used to frighten little children, while
the SVC code way simpler and more elegant.
-- Juliusz
prev parent reply other threads:[~2023-07-11 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 14:29 [Galene] " 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 ` [Galene] congestion control, loss (recovery), whip and obs Dave Taht
2023-07-11 19:34 ` [Galene] Re: OBS Studio and Galene WHIP Sean DuBois
2023-07-11 20:33 ` Juliusz Chroboczek [this message]
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=87fs5uur1g.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=erdnaxe@crans.org \
--cc=galene@lists.galene.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