Date   

[espeak-ng:master] new issue: modifying sapi5 espeak from sourceforge #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by joshknnd1982:
#963 modifying sapi5 espeak from sourceforge

I found it easiest and since I ultimately think a good stable sapi5 espeak is best so I chose to try and modify the speech player in espeak found at: http://grossgang.com/tts/speechPlayer%20in%20espeak/ It's been awhile since I played with intonations file so can you please refresh my memory? Can I add extra tunes such as tune s2, c2, e2, q2? And also when I add tunes statements to a voice variant is only one tune allowed? Or can I do something like:

tunes c2 e2 s2 q2 Or is that the wrong format and I need a comma? I want to try to make a variant that will make speech player in espeak so it will talk like the humanware keynote gold, doubleTalk, decTalk, or eloquence. The espeak from sourceforge seems to have the most stable sapi5 implementation that I have found so far. Unless there is an equivalent espeak ng sapi5 setup package and easy way to edit intonations and klatt voices that I am unaware of?


Github push to espeak-ng:espeak-ng #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

4 New Commits:

[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
b51353499537: fi: remove the english pronunciation of some loan words

Modified: dictsource/fi_list


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
67086dc1da57: fi: add exceptions to doubling with -sti

Modified: dictsource/fi_list


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
92b797a0e100: fi: changes to abbreviations

Modified: dictsource/fi_list


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
16f30f652247: fi: small changes

Modified: dictsource/fi_list


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #849 Stuttering since latest libpcaudio0 update on Raspberry Pi
By riban-bw:

Damn! I was moving to ng because I wanted to direct output with the -d option but am suffering this issue when using Raspberry Pi built-in audio. I do not suffer the audio breakup if I use a soundcard, e.g. Hifiberry hat.


[espeak-ng:master] New Comment on Issue #849 Stuttering since latest libpcaudio0 update on Raspberry Pi
By riban-bw:

Damn! I was moving to ng because I wanted to direct output with the -d option but am suffering this issue when using Raspberry Pi built-in audio. I do not suffer the audio breakup if I use a soundcard, e.g. Hifiberry hat. I am compiling latest source to see if it happens and also maybe diganose issue. I wondered if it related to samplerate / word length.


[espeak-ng:master] reported: voices with different intonation or tunes definitions #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #962 voices with different intonation or tunes definitions
By joshknnd1982:

Is ESpeakEdit available for windows10? That is what I use.

Sent from Mail for Windows 10

From: Valdis Vitolins Sent: Friday, June 4, 2021 12:42 To: espeak-ng/espeak-ng Cc: joshknnd1982; Author Subject: Re: [espeak-ng/espeak-ng] voices with different intonation or tunesdefinitions (#962)

eSpeak Edit is available as espeakedit package on Debian-based Linux distributions, for example, Ubuntu. You install it with graphical installer for particular distribution or running sudo apt-get install espeakedit in command line. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #962 voices with different intonation or tunes definitions
By valdisvi:

eSpeak Edit is available as espeakedit package on Debian-based Linux distributions, for example, Ubuntu. You install it with graphical installer for particular distribution or running sudo apt-get install espeakedit in command line.


[espeak-ng:master] New Comment on Issue #962 voices with different intonation or tunes definitions
By hozosch:

Well but what about Windows?


[espeak-ng:master] new issue: voices with different intonation or tunes definitions #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by joshknnd1982:
#962 voices with different intonation or tunes definitions

a number of years ago with normal Espeak, the old version, I was able to modify its tunes definitions files by first downloading and installing Espeakedit. By doing this you could do anything from making ESpeak sound like Keynote gold, or give it a singing novelty voice. I would like to ask someone to make new voices or variants with different intonation or tunes definitions so ESpeak will emulate the pitch and inflection and speaking style of Keynote gold, DoubleTalk, etcetera. Maybe add some novelty voices such as voices that sound like they are singing, etcetera. thanks. Tunes or intonations definitions files as i remember correctly are, or were, very powerful and by changing them you could greatly expand how Espeak would talk, and even sing, and someone on twitter named Gillam years ago gave me an intonations files and voice and when I applied it, ESpeak sounded like the keynote gold tts from humanware.


[espeak-ng:master] closed: Espeak takes too long to phonemize on colab#github

espeak-ng@groups.io Integration <espeak-ng@...>
 


[espeak-ng:master] new issue: improvement for the arabic espeak #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by king-dahmanus:
#961 improvement for the arabic espeak

Hello devs! I really wish that the arabic espeak gets improved, and these are my suggestions for it. 1, the letter ain (ع) isn't being pronounced correctly and i get it, but you can use the mbrola version by piching it down to match espeak ng's standards. 2, the letter raa (ر) is being pronounced like an english r, which doesn't exist in arabic. 3, the letters daad and saad: (ض & ص) are sometimes pronounced relatively good, and at most times, they aren't, a discord or a communication sort of way can maybe let me give you an example. 4: the numbers aren't so well pronounced, and there's an intonation issue in general. These are the problems that i remember now. for interested devs, please contact me at ilyesidriss2015@..., or at discord at the-blind-dragonoid#3765. Thanks and regards!


Pull Request Opened #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by alex19EP:

#960 separate the android project from the make system.

WIP

I want to make the build of android application independent of make and autoconf.

this will simplefy building the application on non-linux platforms and improve project usability with android-studio.


Pull Request Opened #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by alex19EP:

#959 add cmn and yue to the .gitignore


[espeak-ng:master] reported: espeak has not been pronounced properly with other languages #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #951 espeak has not been pronounced properly with other languages
By NVCDevelopmentTeam:

I will write the full alphabet so you can learn: a, ă, â, b, c, d, đ, e, ê, f, g, h, i, j, k, l, m, n, o, ô, ơ, p, q, r, s, t, u, ư, v, w, x, y, z.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #954 Espeak takes too long to phonemize on colab
By Jaskaran170599:

I think version is the issue it does work fine on the 1.50 version but I need ubuntu 20.4 version for that and i want to run it on colab , I'll try installing the 1.50 version on colab by the installing instructions. these are the commands:

!sudo apt install espeak-ng #1.48.03 04.Mar.14 Data at: /usr/lib/x86_64-linux-gnu/espeak-data !pip install phonemizer

import phonemizer text=phonemizer.phonemize(txt, language=lang, backend='espeak', strip=True, preserve_punctuation=True, with_stress=False, njobs=1, punctuation_marks=';:,.!?¡¿—…"«»“”()', language_switch='remove-flags')


[espeak-ng:master] New Comment on Issue #954 Espeak takes too long to phonemize on colab
By Jaskaran170599:

I think version is the issue it does work fine on the 1.50 version but I need ubuntu 20.4 version for that and i want to run it on colab , I'll try installing the 1.50 version on colab by the installing instructions. these are the commands:

!sudo apt install espeak-ng #1.48.03 04.Mar.14 Data at: /usr/lib/x86_64-linux-gnu/espeak-data !pip install phonemizer

import phonemizer text=phonemizer.phonemize(txt, language=lang, backend='espeak', strip=True, preserve_punctuation=True, with_stress=False, njobs=1, punctuation_marks=';:,.!?¡¿—…"«»“”()', language_switch='remove-flags')


[espeak-ng:master] New Comment on Issue #954 Espeak takes too long to phonemize on colab
By Jaskaran170599:

I think version is the issue it does work fine on the 1.50 version but I need ubuntu 20.4 version for that and i want to run it on colab , I'll try installing the 1.50 version on colab by the installing instructions. these are the commands:

!sudo apt install espeak-ng # 1.48.03 04.Mar.14 Data at: /usr/lib/x86_64-linux-gnu/espeak-data !pip install phonemizer

import phonemizer text=phonemizer.phonemize(txt, language=lang, backend='espeak', strip=True, preserve_punctuation=True, with_stress=False, njobs=1, punctuation_marks=';:,.!?¡¿—…"«»“”()', language_switch='remove-flags')


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #951 espeak has not been pronounced properly with other languages
By NVCDevelopmentTeam:

â, ă, ô, ơ, u, ư, ê, đ, d. Those are the words that need to be corrected in pronunciation. You have to know Vietnamese then when I speak you can understand the standard pronunciation, but if I speak vocabulary, then in essence, if I speak English, it will be different from the Vietnamese I told my friends.


[espeak-ng:master] New Comment on Issue #951 espeak has not been pronounced properly with other languages
By NVCDevelopmentTeam:

â, ă, ô, ơ, ư, ê, đ, d. Those are the words that need to be corrected in pronunciation. You have to know Vietnamese then when I speak you can understand the standard pronunciation, but if I speak vocabulary, then in essence, if I speak English, it will be different from the Vietnamese I told my friends.


Pull Request Opened #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by pvagner:

#958 Android: add all missing voice variants to the variant selection

Throughout the years many voice variant files were collected from various sources. I've updated the android app voice selection to include al of them. This is a follow up PR after #957 as speechplayer based voice variants are included too.


Pull Request Opened #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by pvagner:

#957 Android: Add speechplayer to ndk-build configuration

When building android app also include speechplayer code.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request updated by jbowler:

#955 Issue 945

This is the "dynamic allocation" fix. Note that that bug isn't in the phoneme_list handling, it is in ph_list2 handling. The circular buffer fix might have worked but lacked attraction given the number of globals. This is a step to removing all the globals are therefore allowing creation of an MT capable libespeak.


[espeak-ng/espeak-ng] Pull request closed by jbowler:

#955 Issue 945

This is the "dynamic allocation" fix. Note that that bug isn't in the phoneme_list handling, it is in ph_list2 handling. The circular buffer fix might have worked but lacked attraction given the number of globals. This is a step to removing all the globals are therefore allowing creation of an MT capable libespeak.


[espeak-ng:master] reported: Issue 945 #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By rhdunn:

I've pushed fixes for the various warnings, including the -Wint-conversion warning. -- That's the kind of thing I'm looking for, where each commit does one thing (constify variables, isolate phoneme list table/list sizes, fix a type of warning, etc.).

Note: You can use make CFLAGS="-Wall" to pass additional flags to the build outside of the autoconf/automake process. For example:

make CFLAGS="-Werror -Wall -Wextra -Wno-format-overflow -Wno-format-truncation -Wno-format -Wno-sign-compare -Wno-implicit-fallthrough"

It is generally cleaner commit-wise to rebase and edit the commits. It may also be easier (especially for reviewers) to split this into smaller PRs, possibly around the different commits you have.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request updated by jbowler:

#955 Issue 945

This is the "dynamic allocation" fix. Note that that bug isn't in the phoneme_list handling, it is in ph_list2 handling. The circular buffer fix might have worked but lacked attraction given the number of globals. This is a step to removing all the globals are therefore allowing creation of an MT capable libespeak.


6 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
5791bf28de91: Fix -Wunused-parameter warnings.

Modified: src/libespeak-ng/speech.c
Modified: tests/ssml-fuzzer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
ed6e096b5b5b: Fix -Wunused-function warnings.

Modified: src/libespeak-ng/sPlayer.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
53283a910aa5: Fix -Wunused-but-set-variable warnings.

Modified: src/libespeak-ng/wavegen.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
720405c5c602: Fix -Wreturn-type warnings.

Modified: src/libespeak-ng/wavegen.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f581436deb2d: Fix -Wmissing-prototypes warnings.

Modified: src/libespeak-ng/sPlayer.h


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
a13f9bb62a45: Fix -Wint-conversion warnings.

Modified: configure.ac
Modified: src/libespeak-ng/synthesize.c


[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By jbowler:

That should have removed all the space borkage. There are a lot of [^^I]^I sequences in there - a lot of cases where tabs are used within comments, but those aren't ones that I added which is probably why when I tried to re-indent translate.c and phonemelist.c things got changed.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By jbowler:

I'm having a hard time understanding the last commit, as it is making a lot of changes and I cannot wrap my head around what has changed from looking at the diff only. Having that broken up into separate commits would make it more manageable to review. Also, each commit is doing multiple things, which makes it harder for someone looking at the code (especially if a git bisect identifies one of these commits as breaking something) to verify that it is correct and if not what is wrong with it.

By "last commit" you mean 2d3cc580b8f837aabad369665f677846490ccdbd, right?

This has to be a single commit; it makes all the allocations after the ReadClause call up to but not including the MakePhonemeList call in TranslateClause dynamic. It wouldn't even compile if it were split up let alone pass "make check".

Because of the prior commits it ends up being a highly localized change - just translate.c. Similar changes are possible in readclause.c (for source[N_TR_SOURCE], as was) and makephonemelist.c (for phoneme_list, ph_list3) though the latter may not be necessary as the length of ph_list2 is already known.

One major problem is that much of the language handling is encoded in the C code including code in dictionary.c that is used for parsing. So language developers will change code that itself has to be changed significantly for dynamic allocation. My feeling is that forking a new major version will effectively disconnect that version from language improvements.


[espeak-ng/espeak-ng] Pull request updated by jbowler:

#955 Issue 945

This is the "dynamic allocation" fix. Note that that bug isn't in the phoneme_list handling, it is in ph_list2 handling. The circular buffer fix might have worked but lacked attraction given the number of globals. This is a step to removing all the globals are therefore allowing creation of an MT capable libespeak.


Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By jbowler:

By "last commit" you mean 2d3cc580b8f837aabad369665f677846490ccdbd, right?

This has to be a single commit; it makes all the allocations after the ReadClause call up to but not including the MakePhonemeList call in TranslateClause dynamic. It wouldn't even compile if it were split up let alone pass "make check".

I don't care at all about the comments; they were just to help me because I couldn't readily see which pointer arguments were input, output or in-out. The "const" on the global phoneme_tab is part of the "constify" commit 13f5039491a6380c9e90febff5ffb90e0b0868a1; it seems useful to me but it doesn't matter to me. Removing the array sizes is part of isolating N_PHONEME_LIST, but that's part of the next change (to allocate phoneme_list and ph_list3 dynamically).

I've noticed -- especially in 2d3cc58 -- that there are a lot of extraneous whitespace changes, changing spaces to tabs in comments. The general rule in the espeak-ng codebase is "tabs to indent, spaces to align" so tabs should only appear at the start of lines and not in comments.

My default vi configuration is space indent, which is why this started happening. I changed to this:

:set noexpandtab :set copyindent :set preserveindent :set softtabstop=0 :set shiftwidth=4 :set tabstop=4

Is that correct? It comes from this URL: https://vim.fandom.com/wiki/Indent_with_tabs,_align_with_spaces

When I discovered what was going on I tried to re-indent everything correctly, but it looks like the above is allow tab indentation after the first non-tab too... It would be good to work out the correct settings and create an _vimrc in the project (the directories with source files) to keep it right. I'll do a re-indent commit when I've fully verified all the non-space changes.


[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By jbowler:

I've noticed -- especially in 2d3cc58 -- that there are a lot of extraneous whitespace changes, changing spaces to tabs in comments. The general rule in the espeak-ng codebase is "tabs to indent, spaces to align" so tabs should only appear at the start of lines and not in comments.

My default vi configuration is space indent, which is why this started happening. I changed to this:

:set noexpandtab :set copyindent :set preserveindent :set softtabstop=0 :set shiftwidth=4 :set tabstop=4

Is that correct? It comes from this URL: https://vim.fandom.com/wiki/Indent_with_tabs,_align_with_spaces

When I discovered what was going on I tried to re-indent everything correctly, but it looks like the above is allow tab indentation after the first non-tab too... It would be good to work out the correct settings and create an _vimrc in the project (the directories with source files) to keep it right. I'll do a re-indent commit when I've fully verified all the non-space changes.


[espeak-ng:master] New Comment on Pull Request #955 Issue 945
By jbowler:

I've noticed -- especially in 2d3cc58 -- that there are a lot of extraneous whitespace changes, changing spaces to tabs in comments. The general rule in the espeak-ng codebase is "tabs to indent, spaces to align" so tabs should only appear at the start of lines and not in comments.

My default vi configuration is space indent, which is why this started happening. I changed to this:

:set noexpandtab :set copyindent :set preserveindent :set softtabstop=0 :set shiftwidth=4 :set tabstop=4

Is that correct? It comes from this URL: https://vim.fandom.com/wiki/Indent_with_tabs,_align_with_spaces

When I discovered what was going on I tried to re-indent everything correctly, but it looks like the above allows tab indentation after the first non-tab too; I didn't think about that... It would be good to work out the correct settings and create an _vimrc in the project (the directories with source files) to keep it right. I'll do a re-indent commit when I've fully verified all the non-space changes.

421 - 440 of 4679