From: Tim Panton <tim@pi.pe>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Heads up: default video codec is now VP9
Date: Mon, 10 Jul 2023 11:54:38 +0100 [thread overview]
Message-ID: <28EB58F8-F362-4D15-97AC-7D8326A93A9F@pi.pe> (raw)
In-Reply-To: <87fs5wxhmh.wl-jch@irif.fr>
> On 10 Jul 2023, at 10:04, Juliusz Chroboczek <jch@irif.fr> wrote:
>
>> From our experience the deal with autoplay on safari is that you can
>> only successfully call play from a click.
>
> Galene creates videos asynchronously, as people join and leave the group.
> We cannot require a click everytime somebody joins
You don’t need that - I think - if you have at least one <audio> or <video> tag playing already.
The problem crops up when that drops to zero.
> .
>
> There's an (undocumented?) hack in Safari, which allows autoplay if a page
> holds a reference to a microphone or webcam stream. So what we do is that
> we keep a reference to a microphone stream throughout a session. That
> seems to work on iPad, so I'm surprised it doesn't work on desktop.
I’m not surprised - the iOS implementation is much closer to the hardware, it allocates actual hardware resources on demand.
whereas the Mac one seems to have a multiplexing layer over the hardware which isolates things somewhat.
>
> (Thankfully, we don't need to do that on other browsers, since users like
> the ability to follow a lecture on Galene without being required to grant
> microphone access. Thanks to Safari's "security" features, videoconferencing
> software can spy on you.)
I think you can achieve the same thing by playing silent audio or ‘hold music' into a media tag. (Keeping the playing tags > zero)
What you are seeing is that creating an echo cancelling mic session also allocates a playable output channel and so satisfies the criteria.
You still need a user click on chrome to activate play - but only for the first few sessions - which is a nightmare to test.
T.
>
> -- Juliusz
>
prev parent reply other threads:[~2023-07-10 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 14:31 [Galene] " Juliusz Chroboczek
2023-07-09 15:04 ` [Galene] " Dave Taht
2023-07-09 15:16 ` Dave Taht
2023-07-09 15:22 ` eric_G
2023-07-09 16:32 ` Juliusz Chroboczek
2023-07-09 16:45 ` eric_G
2023-07-09 16:55 ` Juliusz Chroboczek
2023-07-10 8:02 ` Tim Panton
2023-07-10 9:04 ` Juliusz Chroboczek
2023-07-10 10:54 ` Tim Panton [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=28EB58F8-F362-4D15-97AC-7D8326A93A9F@pi.pe \
--to=tim@pi.pe \
--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