From: Eliot Mack <eliot@lightcrafttech.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Dave Taht <dave.taht@gmail.com>, galene@lists.galene.org
Subject: [Galene] Re: four other oft-requested features
Date: Tue, 27 Jul 2021 15:03:40 -0700 [thread overview]
Message-ID: <CAA4ndqCV+o0kbVxxUQtsizCnkV0cTAPnZ-KjmSEGbV6F7DOPpQ@mail.gmail.com> (raw)
In-Reply-To: <87im1amq50.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
Hi all,
I read through the plan to record all streams separately as independent
files, and then recombine them.
However, since h264 is not supported as a recording format, any stream that
comes in with this format would be lost.
Are there any plans to be able to convert h264 streams into a different
format for recording?
-Eliot
On Fri, Jul 16, 2021 at 4:53 AM Juliusz Chroboczek <jch@irif.fr> wrote:
> > 1) Better video logging and combination of speakers video and audio.
>
> Yes, it's an important missing feature.
>
> I would reformulate it as better export of recordings -- storing
> recordings as multiple independent files is good design, but there should
> be a way to export a recording as a single file.
>
> This could probably be done in Javascript on the user device.
>
> > 2) speech to text and text to speech. Notably feeding the chat -
> > somehow - into a speech synth - for those of us that are increasingly
> > deaf.
>
> Do any free software browsers support the Speech Synthesis API? Dave,
> what does your browser say if you type
>
> window.speechSynthesis.getVoices();
>
> in the Javascript console? For me, it returns an empty list.
>
> > 3) Roundtable mode - where each speaker is given a limited time to
> > speak, with a visible clock, other speakers can grant the existing
> > speaker some time from their pool, and a moderator (automated) that
> > silences that speaker and then queues the next speaker
>
> The server only allows you to mute a user remotely, not to unmute them.
> That's an important property, and one that I'd be unwilling to break.
>
> -- Juliusz
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org
>
--
Eliot Mack
CEO
Lightcraft Technology
(310) 821-3888
<(805)%20338-7199>
[-- Attachment #2: Type: text/html, Size: 3102 bytes --]
next prev parent reply other threads:[~2021-07-27 22:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 1:41 [Galene] " Dave Taht
2021-07-16 11:53 ` [Galene] " Juliusz Chroboczek
2021-07-16 13:07 ` [Galene] Re: four other oft-requested features / forwarding control ibu ☉ radempa
2021-07-16 14:14 ` Juliusz Chroboczek
2021-07-27 22:03 ` Eliot Mack [this message]
2021-07-27 22:12 ` [Galene] Recording H.264 [was: four other oft-requested features] Juliusz Chroboczek
2021-07-27 23:26 ` [Galene] " Eliot Mack
2021-07-28 12:03 ` Juliusz Chroboczek
2021-07-16 12:16 ` [Galene] Re: four other oft-requested features Antonin Décimo
2021-07-16 12:57 ` Jeroen van Veen
2021-07-16 13:08 ` T H Panton
2021-07-16 18:32 ` Juliusz Chroboczek
2021-07-17 23:35 ` Dave Taht
2021-07-18 22:17 ` Juliusz Chroboczek
2021-07-18 22:44 ` Dave Taht
2021-07-30 19:44 ` Frank Carmickle
2021-07-31 0:36 ` Juliusz Chroboczek
2021-07-31 16:39 ` [Galene] Speech [was: four other oft-requested features] 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=CAA4ndqCV+o0kbVxxUQtsizCnkV0cTAPnZ-KjmSEGbV6F7DOPpQ@mail.gmail.com \
--to=eliot@lightcrafttech.com \
--cc=dave.taht@gmail.com \
--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