From: Shevek <shevek@anarres.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org, Dave Taht <dave.taht@gmail.com>
Subject: [Galene] Re: feature: two cameras for galene
Date: Tue, 10 May 2022 17:09:49 -0700 [thread overview]
Message-ID: <fe3bce97-9a70-7892-9baa-48fda16db096@anarres.org> (raw)
In-Reply-To: <87v8udj9jh.wl-jch@irif.fr>
Thank you for following up.
In UI terms, I would expect:
Present/Share My ...
--> Window / Tab / Desktop / _Camera_
----> Select the appropriate window/desktop/camera as usual.
where Camera is a new option allowing me to select a v4l2 source instead
of using screen capture. The presentation source comes in via something
which (in hardware terms) looks like a camera, but usually isn't, in
fact, an optical element. In practice, I use an ATEM to composite the
"presentation" image from various SDI sources, and render it down to a
single stream entirely in hardware, which then presents as a v4l2 device.
If I'm streaming to an RTMP/RTSP reflector (Youtube, Twitch, Brightcove,
Vimeo, etc), then I don't need Galene/Zoom/OBS/GVC at all, as the
hardware has RT*P support. But if I'm hosting a meeting on a particular
bidirectional video conference system, then the ability to treat a
secondary UVC device as a presentation source is an absolute blocker
(unless I want to render the presenter as a PiP, which detracts from one
corner of the presentation, and does not give the viewer choice of focus).
Does that help? I can probably make screenshots...
S.
On 5/10/22 15:40, Juliusz Chroboczek wrote:
>>> They're thinking that presentation cannot be a camera feed,
>
> Having two cameras is not unusual. At seminars, we sometimes have one
> camera focused on the speaker and one that films
>
>>> Logging in from two browser tabs in order to speak to an audience and
>>> present slides would be very odd and somewhat backwards.
>
> We've never encountered this issue, since in our setup the two cameras are
> connected to two distinct computers. We've also been hoping that
> interfacing with OBS would solve this kind of setup issues, but OBS has
> been slow in doing their WebRTC support, and RTMP doesn't have the right
> features.
>
> Shevek, what should the UI for that look like? Open the side menu, click
> « Add secondary camera », a second Present/Unpresent button appears?
>
> If we develop such a feature, would you be willing to do some testing for us?
>
> -- Juliusz
>
next prev parent reply other threads:[~2022-05-11 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw6qDGPa75Wfj1uj+G8yv6cYs8kWP7TqjzMBq5b6_LYo+A@mail.gmail.com>
[not found] ` <4008de81-3f67-2b9e-c83f-62bad76d72e0@anarres.org>
2022-05-10 21:58 ` [Galene] " Dave Taht
2022-05-10 22:40 ` [Galene] " Juliusz Chroboczek
2022-05-11 0:09 ` Shevek [this message]
2022-05-11 2:13 ` Juliusz Chroboczek
2022-05-11 5:21 ` Shevek
2022-05-11 11:16 ` Juliusz Chroboczek
2022-05-11 11:22 ` Toke Høiland-Jørgensen
2022-05-11 5:57 ` Gabriel Kerneis
2022-05-11 6:06 ` Dave Taht
2022-05-11 8:09 ` T H Panton
2022-05-11 8:19 ` Fabrice Rouillier
2022-05-11 11:26 ` [Galene] Re: whipi [was: two cameras for galene] 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=fe3bce97-9a70-7892-9baa-48fda16db096@anarres.org \
--to=shevek@anarres.org \
--cc=dave.taht@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--subject='[Galene] Re: feature: two cameras for galene' \
/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