From: Juliusz Chroboczek <jch@irif.fr> To: err404@free.fr Cc: galene@lists.galene.org Subject: [Galene] Re: poor screen sharing quality on galene (vp9) when the cpu is not strong enough. Date: Wed, 29 Dec 2021 19:18:56 +0100 [thread overview] Message-ID: <87ee5vl1f3.wl-jch@irif.fr> (raw) In-Reply-To: <250d8537-8742-1e65-ce54-66ffead13256@free.fr> > the video stream quality was good but when I tried to share my screen, > the screen sharing quality was uggly, really... even on a not moving > screen (displaying static text). [...] > I tried the same on another computer (better cpu, better graphic card), > the quality was better on screen sharing > it is appear that every second (or two), the quality drop again to > ugly. (seem the stream was lost and restarted) Interesting. The periodic drop in quality indicates that somebody is requesting a new keyframe every two seconds. This may happen if either the browser or the server believes that the stream is broken. I'll see if I can reproduce the issue. Was that over WiFi? Did the statistics interface indicate large numbers of lost packets? What happens when you disable simulcast on the sender side? What happens if you set the sender's video quality to "low"? What happens if you set the sender's video quality to "unlimited"? > I though that sharing a static screen was easier than streaming a 720p > webcam :p The reolution of the webcam is chosen by the browser, it's most probably lower than 720p (probably 640x400). You may manually toggle the resolution by doing /set resolution [1024,768] then restarting the video stream. (This is deliberately undocumented, until I find a good UI. Unfortunately, the JavaScript API does not allow me to find out the webcams native resolution, so it's tricky.) -- Juliusz
prev parent reply other threads:[~2021-12-29 18:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-29 12:09 [Galene] " err404 2021-12-29 18:18 ` 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=87ee5vl1f3.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=err404@free.fr \ --cc=galene@lists.galene.org \ --subject='[Galene] Re: poor screen sharing quality on galene (vp9) when the cpu is not strong enough.' \ /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