From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: "Christian Thäter" <ct@pipapo.org>
Cc: <emacs-orgmode@gnu.org>
Subject: Re: Suggestions for Text-To-Speech (TTS) from Org sources?
Date: Mon, 11 Sep 2023 10:33:53 +0200 [thread overview]
Message-ID: <87r0n5kt1q.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <20230910220853.64e8a557@wolke.pipapo.org> ("Christian Thäter"'s message of "Sun, 10 Sep 2023 22:08:53 +0200")
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
On 2023-09-10, Christian Thäter wrote:
> On Sun, 10 Sep 2023 16:39:26 +0200
> Jens Lechtenboerger <lechten@wi.uni-muenster.de> wrote:
>
>> On 2023-09-10, Ihor Radchenko wrote:
>>
>> > Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
>> >
>> >> does someone here produce audio via Text-To-Speech (TTS) from Org
>> >> sources? I plan to do that in the context of emacs-reveal to
>> >> generate voice-over for reveal.js presentations, with open
>> >> questions [1] concerning my initial, experimental approach.
>> >
>> > Emacspeak is a mature Emacs solution for TTS. However, it aims blind
>> > users, not presentations. Still,
>> > http://tvraman.github.io/emacspeak/manual/Quick-Installation.html
>> > might be a good starting point for TTS options.
>>
>> Thank you for the suggestion. With espeak this indeed pronounces
>> numbers and abbreviations but its audio quality it not good enough
>> for my purposes. I am looking for (near-) human voices...
>
> using mbrola is probably as good as possible with free software:
> https://en.wikipedia.org/wiki/MBROLA
>
> still not perfect, but much better than the builtin voices of espeak or
> festival (YYMV).
This sounds promising. I’ll check it out.
Many thanks
Jens
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6187 bytes --]
next prev parent reply other threads:[~2023-09-11 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 18:05 Suggestions for Text-To-Speech (TTS) from Org sources? Jens Lechtenboerger
2023-09-09 21:20 ` briangpowell
2023-09-10 14:35 ` Jens Lechtenboerger
2023-09-10 10:43 ` Ihor Radchenko
2023-09-10 14:39 ` Jens Lechtenboerger
2023-09-10 20:08 ` Christian Thäter
2023-09-11 8:33 ` Jens Lechtenboerger [this message]
2023-09-11 9:14 ` briangpowell
2023-09-11 12:06 ` Jude DaShiell
2023-09-11 12:27 ` tomas
2023-09-11 13:52 ` Jude DaShiell
2023-09-11 16:30 ` tomas
2023-09-11 17:21 ` Jude DaShiell
2023-09-11 14:48 ` Jude DaShiell
2023-09-11 12:07 ` Jude DaShiell
2023-09-11 12:31 ` Jens Lechtenboerger
2023-09-28 13:11 ` Jens Lechtenboerger
2023-09-28 14:16 ` Jude DaShiell
2023-09-29 7:56 ` Jens Lechtenboerger
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0n5kt1q.fsf@wi.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=ct@pipapo.org \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).