From: Juliusz Chroboczek <jch@irif.fr>
To: Sean DuBois <sean@siobud.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Keeping the developer honest: why native clients are important
Date: Wed, 18 Sep 2024 21:07:18 +0200 [thread overview]
Message-ID: <87cyl0232x.wl-jch@irif.fr> (raw)
In-Reply-To: <jnrdnarifhlo7ki2zhizzlbrg3hb32qsbry4qnsqyl5m663j6z@vshmto47ognu>
> I would like to extend WHIP/WHEP to cover a few more use cases. I am not
> sure where to start though.
>
> * Conference Calling. I have one WHIP session to upload, then one
> (or many) WHEP sessions to download. Maybe some sort of 'pseudo WHEP'
> resource that I can listen for SSE events on? That would announce the
> streams as they join/leave?
Another problem is that people really want to have a chat when
videoconferencing, and there's no standard, simple chat protocol. (Don't
get me started on XMPP.)
> * Autoconf. I want to push video into OBS. Or send video OBS<->OBS into
> the same network. Remove dependence on proprietary software to do
> video mixing in the LAN.
How do you push video into OBS? Can OBS act as a WHIP endpoint?
-- Juliusz
prev parent reply other threads:[~2024-09-18 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 13:55 [Galene] " Juliusz Chroboczek
2024-09-18 15:10 ` [Galene] " Sean DuBois
2024-09-18 19:07 ` 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=87cyl0232x.wl-jch@irif.fr \
--to=jch@irif.fr \
--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