From: Juliusz Chroboczek <jch@irif.fr> To: Dave Taht <dave.taht@gmail.com> Cc: galene@lists.galene.org Subject: [Galene] Re: SVC support Date: Wed, 12 May 2021 18:26:43 +0200 [thread overview] Message-ID: <87lf8jor3w.wl-jch@irif.fr> (raw) In-Reply-To: <CAA93jw4uvB0G+nNDY3Gy17nu2E4CQFDzufi30BdivvaUo12Dzw@mail.gmail.com> >> SVC is a technique where a single video stream is "layered": frames are >> labelled with information about whether they can be dropped, and the >> server can reduce the bitrate sent to a client. The advantage of SVC over >> simulcast is that switching layers is a much more lightweight operation: >> switching simulcast streams requires a keyframe, while switching scalable >> layers can happen a few times per packet. > This is a really, really promising sounding technique! Yes, I find it exciting too. You can essentially switch layers every 100ms or so, with no disturbing artifacts, so you can react to fine-grained congestion control feedback. You'll be glad to know that SVC is tightly integrated in AV1. > Currently. As both these are open source they can certainly be > improved. I haven't hacked on firefox in quite some time... I can reach > out to some contacts in the mozilla organization and/or is there a good > mailing list to join? The current situation is a mess: - both Chromium and Firefox tie together simulcast and SVC for VP8; - Chromium does weird things when attempting simulcast VP9; - Debian's Chromium crashes when attempting simulcast VP9; - Firefox uses a non-standard protocol for simulcast. For now, I'm just disabling simulcast/SVC when the sender is Firefox. Jitsi appear to implement Firefox's protocol for simulcast, we should probably do the same in Pion. >> unfortunately, I wasn't able to test the VP9 support, since my version >> of Chromium immediately crashes when you request a VP9 simulcast >> stream. I've found a version of Brave that doesn't crash. However, it doesn't seem to actually send either simulcast or a scalable stream. So it's going to be VP8-only for now. >> Spacial scalability (reducing the resolution) should be doable for VP9, >> but the point is somewhat moot until Chromium fix their bug. > > Have you reported it? I've reported it with Debian, since Brave is based on the same version of Chromium and doesn't crash. I've talked to Lorenzo Miniero (the Janus guy), and he hasn't seen that bug. The crash is immediately reproducible here: https://janus-legacy.conf.meetecho.com/echotest.html?simulcast2=true&vcodec=vp9 With my version of Chromium, clicking "Start" leads to an immediate crash. -- Juliusz
next prev parent reply other threads:[~2021-05-12 16:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-12 15:19 [Galene] " Juliusz Chroboczek 2021-05-12 15:41 ` [Galene] " Dave Taht 2021-05-12 16:26 ` Juliusz Chroboczek [this message] 2021-05-12 16:35 ` 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=87lf8jor3w.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=dave.taht@gmail.com \ --cc=galene@lists.galene.org \ --subject='[Galene] Re: SVC support' \ /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