Date   

[espeak-ng:master] new issue: Parse into formatted input/output #github

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

[espeak-ng:master] New Issue Created by cmrdt:
#174 Parse into formatted input/output

to help readability (custom ASCII phonetic multi-glyph symbols hard to read) color-coding syntax highlighting to assist readability &debugging

maybe making the RGB color a function

maybe https://en.wikipedia.org/wiki/YUV or https://en.wikipedia.org/wiki/Lab_color_space

maybe also support for IPA input with https://en.wikipedia.org/wiki/International_Phonetic_Alphabet#Diacritics_and_prosodic_notation (more/less round, voiced, central)

maybe interface GUI also similar to formant.tcl demo in (install active-tcl8.4 also) http://www.speech.kth.se/snack/


[espeak-ng:master] new issue: Support for timing output #github

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

[espeak-ng:master] New Issue Created by cmrdt:
#173 Support for timing output

maybe options to output subtitle-subrip (.srt) format files with option to split lines by word or line or phoneme(consonant-vowels) maybe also IPA/phonetic output and syntax coloring/formatting(font,bold)

https://en.wikipedia.org/wiki/SubRip#SubRip_text_file_format https//en.wikipedia.org/wiki/SubStation_Alpha

also, espeak (not NG) ttsapp's synth-"mouth-position" GUI is synced with the speech


Introduction

Christo de Klerk
 

Hello all

I have just joined. My name is Christo de Klerk and I am from South Africa. For the past 10 years I have been maintaining the eSpeak dictionary for the Afrikaans language and I would very much like to continue with that work and make it still more accurate than it already is. Does eSpeak-NG use dictionaries of the same name and format as the old eSpeak? Does one still use eSpeakEdit to compile them? To whom should I send the updated dictionary?

I am really thrilled that this project is continuing. ESpeak's Afrikaans is the only synthesiser for our language and eSpeak's English is by far the best synthesiser, as it is able to pronounce far more characters than any other synthesiser.

Another question: I am using an MBrola voice with old eSpeak. Can the new one also support MBrola? The advantage of this is that one gets a far more natural sounding voice when one uses MBrola.

Excellent work with the continuation of eSpeak.

Kind regards

Christo


Updates to Github #github

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

[espeak-ng:master] New Issue Created by cmrdt:
#179 multi-channel voice-component output for DSPs, mixing or debugging

add command option to split voice into multiple channels?

  • voice-tone
  • voice-tone-roughness
  • consonants voiced
  • consonants unvoiced
  • breath

(time/pitch stretching, noise removal, compression, remastering)

if not, have to manually craft multiple voice variant files to maybe emulate


[espeak-ng:master] New Issue Created by cmrdt:
#174 Parse into formatted input/output

to help readability (custom ASCII phonetic multi-glyph symbols hard to read) color-coding syntax highlighting to assist readability &debugging

maybe making the RGB color a function

maybe https://en.wikipedia.org/wiki/YUV or https://en.wikipedia.org/wiki/Lab_color_space

maybe also support for IPA input with https://en.wikipedia.org/wiki/International_Phonetic_Alphabet#Diacritics_and_prosodic_notation (more/less round, voiced, central)


[espeak-ng:master] New Comment on Issue #175 GUI for real-time custom voice-variant parameter tuning
By cmrdt:

maybe interface GUI also similar to formant.tcl demo in (install active-tcl8.4 also) http://www.speech.kth.se/snack/

clipboard

or

clipboard2


[espeak-ng:master] New Comment on Issue #175 GUI for real-time custom voice-variant parameter tuning
By cmrdt:

maybe interface GUI also similar to formant.tcl demo in (install active-tcl8.4 also) http://www.speech.kth.se/snack/

clipboard

clipboard2


[espeak-ng:master] New Issue Created by cmrdt:
#178 upgrade internal audio quality (sample rate and bit-depth)

also in espeakedit (not ng) the resampling quality seemed to be so-so (maybe not sox's fault, maybe command-line-settings) but resampling from a low-quality source-wav file isn't the same as starting from one of higher quality (lower rates lack higher frequencies)

default currently is 11025×2 Hz 16-bits maybe increase to (18×2)kHz+ and 32-bit-float as compile option; & rather do downsampling from higher quality if need be (update syllables containing high frequencies: s f z ʃ ʒ t k θ ð v d ) aka syllables that people (old or hearing loss) may have trouble distinguishing

and if using sox use best-quality sinc option, max precision


[espeak-ng:master] New Issue Created by cmrdt:
#178 upgrade internal audio quality (sample-rate & bit-depth)

also in espeakedit (not ng) the resampling quality seemed to be so-so (maybe not sox's fault, maybe command-line-settings) but resampling from a low-quality source-wav file isn't the same as starting from one of higher quality (lower rates lack higher frequencies)

default currently is 11025×2 Hz 16-bits maybe increase to (18×2)kHz+ and 32-bit-float as compile option; & rather do downsampling from higher quality if need be (update syllables containing high frequencies: s f z ʃ ʒ t k θ ð v d ) aka syllables that people (old or hearing loss) may have trouble distinguishing

and if using sox use best-quality sinc option, max precision


Re: Introduction

Reece H. Dunn
 

On Thu, Dec 29, 2016 at 01:08 am, Christo de Klerk wrote:

Hello all

I have just joined. My name is Christo de Klerk and I am from South
Africa. For the past 10 years I have been maintaining the eSpeak
dictionary for the Afrikaans language and I would very much like to
continue with that work and make it still more accurate than it already
is. Does eSpeak-NG use dictionaries of the same name and format as the
old eSpeak?

Yes, the dictionary format is the same.

Does one still use eSpeakEdit to compile them?

Currently, espeakedit needs a patch to be able to work with espeak-ng.

If you have built espeak-ng locally, you can run:

    make af

to build the Afrikaans dictionary. Alternatively, you can run:

    espeak-ng --compile=af

A GUI editor to replace espeakedit is planned, but has not been implemented yet.

To whom
should I send the updated dictionary?

You can send the source files to this list. Alternatively, if you add the updates to the git source code, you can point me to your repository or create a pull request on GitHub and I will incorporate your changes.

I am really thrilled that this project is continuing. ESpeak's Afrikaans
is the only synthesiser for our language and eSpeak's English is by far
the best synthesiser, as it is able to pronounce far more characters
than any other synthesiser.

Another question: I am using an MBrola voice with old eSpeak. Can the
new one also support MBrola? The advantage of this is that one gets a
far more natural sounding voice when one uses MBrola.

Yes, espeak-ng supports MBROLA.

Kind regards,

Reece Dunn


Re: Introduction

Christo de Klerk
 

Hi Reece

Many thanks for your quick and helpful response.

I have only worked on the eSpeak dictionary and not on the program source code itself, so my knowledge about git and repositories is just about non-existent. I also don't have a local build of espeak-ng. So, for the time being, until I acquire those skills, I will send updated source code of the Afrikaans dictionary to the list.

I have noticed that, when I have Afrikaans active under espeak-ng and then open the symbols dictionary in NVDA, it still opens the English one. I have an Afrikaans symbols dictionary which works well with old eSpeak's Afrikaans. How do I get espeak-ng Afrikaans and the Afrikaans symbols dictionary to be linked?

Sorry, but I will probably have plenty of questions in time to come.

Kind regards

Christo

On 2016/12/29 11:29 AM, Reece H. Dunn wrote:
On Thu, Dec 29, 2016 at 01:08 am, Christo de Klerk wrote:



Hello all

I have just joined. My name is Christo de Klerk and I am from South
Africa. For the past 10 years I have been maintaining the eSpeak
dictionary for the Afrikaans language and I would very much like to
continue with that work and make it still more accurate than it already
is. Does eSpeak-NG use dictionaries of the same name and format as the
old eSpeak?

Yes, the dictionary format is the same.



Does one still use eSpeakEdit to compile them?

Currently, espeakedit needs a patch to be able to work with espeak-ng.

If you have built espeak-ng locally, you can run:

make af

to build the Afrikaans dictionary. Alternatively, you can run:

espeak-ng --compile=af

A GUI editor to replace espeakedit is planned, but has not been implemented yet.



To whom
should I send the updated dictionary?

You can send the source files to this list. Alternatively, if you add the updates to the git source code, you can point me to your repository or create a pull request on GitHub and I will incorporate your changes.



I am really thrilled that this project is continuing. ESpeak's Afrikaans
is the only synthesiser for our language and eSpeak's English is by far
the best synthesiser, as it is able to pronounce far more characters
than any other synthesiser.

Another question: I am using an MBrola voice with old eSpeak. Can the
new one also support MBrola? The advantage of this is that one gets a
far more natural sounding voice when one uses MBrola.

Yes, espeak-ng supports MBROLA.

Kind regards,

Reece Dunn


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #178 upgrade internal audio quality (sample-rate & bit-depth)
By cmrdt:

also if audio file same quality as device native-sampling rate, it would not have to resample again

also android resamplers use up battery and may be of low quality.. detect native sampling rate maybe by playing a sine wave chirp at various sample-rates and looking at the spectrogram

roughness … Reduces the amplitude of alternate waveform cycles in order to make the voice sound creaky. if's it's artificial & not anti-aliased , if not adequately over-sampled introduces artifacts/distortions into the audio


[espeak-ng:master] New Comment on Issue #178 upgrade internal audio quality (sample-rate & bit-depth)
By cmrdt:

also if audio file same quality as device native-sampling rate, it would not have to resample again

also android resamplers use up battery and may be of low quality.. detect native sampling rate maybe by playing a sine wave chirp at various sample-rates and looking at the spectrogram

roughness … Reduces the amplitude of alternate waveform cycles in order to make the voice sound creaky.

if's it's artificial & not anti-aliased , if not adequately over-sampled introduces artifacts/distortions into the audio


Updates to Github #github

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

5 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
9bb9e98f8476: Don't exclude the test voice directory. This directory is no longer available, so the check is now redundant.

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f37a9a388daa: Move the Armenian languages to the Indo-European language family.

Added: espeak-ng-data/voices/ine/hy
Added: espeak-ng-data/voices/ine/hy-arevmda
Removed: espeak-ng-data/voices/axm/hy
Removed: espeak-ng-data/voices/axm/hy-arevmda
Modified: src/windows/installer/Product.wxs


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
516699bbb2c3: Move the Basque language to the parent directory as it is a language isolate.

Added: espeak-ng-data/voices/eu
Removed: espeak-ng-data/voices/xaq/eu
Modified: src/windows/installer/Product.wxs


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f7ef3808f9ab: Move the Latvian and Lithuanian languages to the bat (Baltic) language family.

Added: espeak-ng-data/voices/bat/lt
Added: espeak-ng-data/voices/bat/lv
Removed: espeak-ng-data/voices/xaq/lt
Removed: espeak-ng-data/voices/xaq/lv
Modified: src/windows/installer/Product.wxs


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
3c33da948c16: Provide a list of the supported languages and accents.

Added: espeak-ng-data/voices/README.md
Modified: README.md


1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
2424cbaedf45: Provide a list of the supported languages and accents.

Added: espeak-ng-data/voices/README.md
Modified: README.md


1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
0991ba8bfc49: Provide a list of the supported languages and accents.

Added: espeak-ng-data/voices/README.md
Modified: README.md


what is the different between espeak ng and the old espeak regarding the installation procedure?

Amir Din <mrdin8877@...>
 

hi, i just installed the old espeak on my windows 64 bit. the old
installation process requires us to enter the voice name + variants
for each voices that we want. for example if i want english, i will
enter, en and followed by the variants for the english voice such as
female, so it will become, en+f1. so do these steps still apply if i
use the espeak ng installer? and additional question, can i use espeak
with narrator? i want to make it as narrator's voice. this is 64 bit,
that is why narrator won't see the old espeak voices. but what about
the new espeak ng?


Re: what is the different between espeak ng and the old espeak regarding the installation procedure?

brandon T <brandongold98@...>
 

Hello,

eSpeak-NG only has experimental support for SAPI, which I don't think
is included in the installer by default. This means that, unless you
change this (which I'm unfortunately not sure how to do, that you
can't use this with Narrator at this point in time.

Hope this helps,

Brandon

On 12/30/16, Amir Din <mrdin8877@...> wrote:
hi, i just installed the old espeak on my windows 64 bit. the old
installation process requires us to enter the voice name + variants
for each voices that we want. for example if i want english, i will
enter, en and followed by the variants for the english voice such as
female, so it will become, en+f1. so do these steps still apply if i
use the espeak ng installer? and additional question, can i use espeak
with narrator? i want to make it as narrator's voice. this is 64 bit,
that is why narrator won't see the old espeak voices. but what about
the new espeak ng?



--
“Be what you are. This is the first step towards becoming better than you are.”
– J. C. Hare & A. W. Hare


eSpeak optimizations for Android 6.0

Matěj Plch <plchterminator@...>
 

Dear users and developers,
I am very happy, that this discussion group was established and the next generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?
I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some engine optimizations, because I register quite often crashes of latest available version 1.48.15 on Android Marshmallow.
I tested it on many devices with this OS and the crashing problem is noticeable especialy during fast typing on Google Keyboard or sometimes, when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not know, if developers catched them.
Does someone else has the same experience here?
I can give the name of for example: Motorola Moto G (3rd gen) and Xiaomi Redmi 3S.
Your comments will be greatly appreciated.
Sincerely,
Matej


Re: eSpeak optimizations for Android 6.0

Reece H. Dunn
 

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers,
I am very happy, that this discussion group was established and the next
generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?

The changes are described in the changelog (https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1.  Clean up the build process.

2.  Simplify porting to other systems (BSD, Mac, Windows).

3.  Clean up the codebase to make it easier to maintain.

4.  Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some
engine optimizations, because I register quite often crashes of latest
available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The focus on security and stability above should help reduce/remove the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem is
noticeable especialy during fast typing on Google Keyboard or sometimes,
when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not
know, if developers catched them.

I can see them, but as I have said, it is difficult to know what the cause of the crash is. The work I have done already should help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so that the android code will be usable from the main releases instead of requiring the android branch to be updated. This should make it easier to perform new Android releases in the future.

Kind regards,

Reece Dunn


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

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

2 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f1bb4a01a982: CHANGELOG: Structure the changelog around the project name.

Modified: CHANGELOG.md


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
391e301a724f: CHANGELOG: Fix a typo.

Modified: CHANGELOG.md


Re: eSpeak optimizations for Android 6.0

Matěj Plch <plchterminator@...>
 

Okay, Reece, thanks for your answer.
I totaly understand.
Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers,
I am very happy, that this discussion group was established and the
next
generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some
engine optimizations, because I register quite often crashes of latest
available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The focus
on security and stability above should help reduce/remove the number of
crashes on Android.

I tested it on many devices with this OS and the crashing problem is
noticeable especialy during fast typing on Google Keyboard or
sometimes,
when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not
know, if developers catched them.

I can see them, but as I have said, it is difficult to know what the
cause of the crash is. The work I have done already should help, but
there is still more to fix and improve.

I am working on merging the android code into the main branch, so that
the android code will be usable from the main releases instead of
requiring the android branch to be updated. This should make it easier
to perform new Android releases in the future.

Kind regards,

Reece Dunn


Re: eSpeak optimizations for Android 6.0

Mario Perčinić <mario.percinic@...>
 

Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS Engine from RedZoc apk. On his page he says that he optimised espeak for android 6 and later.

Mario

On 12/31/2016 1:38 PM, Matěj Plch wrote:
Okay, Reece, thanks for your answer.
I totaly understand.
Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):
On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers,
I am very happy, that this discussion group was established and the
next
generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some
engine optimizations, because I register quite often crashes of latest
available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The focus
on security and stability above should help reduce/remove the number of
crashes on Android.

I tested it on many devices with this OS and the crashing problem is
noticeable especialy during fast typing on Google Keyboard or
sometimes,
when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not
know, if developers catched them.

I can see them, but as I have said, it is difficult to know what the
cause of the crash is. The work I have done already should help, but
there is still more to fix and improve.

I am working on merging the android code into the main branch, so that
the android code will be usable from the main releases instead of
requiring the android branch to be updated. This should make it easier
to perform new Android releases in the future.

Kind regards,

Reece Dunn

--
Mario Percinic
Accessibility consultant
mario.percinic@...
Skype: acousticman
Twitter: @MarioPercinic
GSM: +385922630259


Re: eSpeak optimizations for Android 6.0

Reece H. Dunn
 

On Sat, Dec 31, 2016 at 04:50 am, Mario Perčinić wrote:

Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS Engine
from RedZoc apk. On his page he says that he optimised espeak for
android 6 and later.

They have not released the source code for their version of eSpeak for Android, so it is not clear what changes RedZoc have made and which are from the eSpeak for Android port. It is likely that they have not changed the eSpeak code itself where the crashes are happening, just the Android side.

Kind regards,

Reece H. Dunn


Re: eSpeak optimizations for Android 6.0

Matěj Plch <plchterminator@...>
 

Hi Mario,
I know about this port of eSpeak, but there is some in-app
advertisement, so I do not like this port.
It is established on the existing code and I found the crashes too.
Sincerely,
Matej


Dne 31.12.2016 v 13:49 Mario Perčinić napsal(a):
Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS
Engine from RedZoc apk. On his page he says that he optimised espeak
for android 6 and later.

Mario



On 12/31/2016 1:38 PM, Matěj Plch wrote:
Okay, Reece, thanks for your answer. I totaly understand. Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):
On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers, I am very happy, that this discussion
group was established and the next generation of eSpeak will come
in near future! Can you highlight some important changes, which
we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).


My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make
some engine optimizations, because I register quite often crashes
of latest available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The
focus on security and stability above should help reduce/remove
the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem
is noticeable especialy during fast typing on Google Keyboard or
sometimes, when I want to open several apps quickly. I posted
many crashing reports directly from the devices, but do not know,
if developers catched them.

I can see them, but as I have said, it is difficult to know what
the cause of the crash is. The work I have done already should
help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so
that the android code will be usable from the main releases
instead of requiring the android branch to be updated. This
should make it easier to perform new Android releases in the
future.

Kind regards,

Reece Dunn


Re: eSpeak optimizations for Android 6.0

Mario Perčinić <mario.percinic@...>
 

Hi guys.

Sorry i was just trying to help. Btw i have that version installed on my current phone and i don't see any advertisements which you mentioned over here. Do you know exactly when or in which situations they pop up?

Mario

On 12/31/2016 1:57 PM, Matěj Plch wrote:
Hi Mario,
I know about this port of eSpeak, but there is some in-app
advertisement, so I do not like this port.
It is established on the existing code and I found the crashes too.
Sincerely,
Matej


Dne 31.12.2016 v 13:49 Mario Perčinić napsal(a):
Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS
Engine from RedZoc apk. On his page he says that he optimised espeak
for android 6 and later.

Mario



On 12/31/2016 1:38 PM, Matěj Plch wrote:
Okay, Reece, thanks for your answer. I totaly understand. Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):
On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers, I am very happy, that this discussion
group was established and the next generation of eSpeak will come
in near future! Can you highlight some important changes, which
we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).


My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make
some engine optimizations, because I register quite often crashes
of latest available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The
focus on security and stability above should help reduce/remove
the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem
is noticeable especialy during fast typing on Google Keyboard or
sometimes, when I want to open several apps quickly. I posted
many crashing reports directly from the devices, but do not know,
if developers catched them.

I can see them, but as I have said, it is difficult to know what
the cause of the crash is. The work I have done already should
help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so
that the android code will be usable from the main releases
instead of requiring the android branch to be updated. This
should make it easier to perform new Android releases in the
future.

Kind regards,

Reece Dunn
--
Mario Percinic
Accessibility consultant
mario.percinic@...
Skype: acousticman
Twitter: @MarioPercinic
GSM: +385922630259


Latest dictionary files for Afrikaans attached

Christo de Klerk
 

Hi Reece

I have attached my latest updated dictionary files for Afrikaans: af_list and af_rules. I compiled them and test them locally and there are no errors. I will appreciate it if you could process them for me.

Incidentally, I figured out the issue I had with Afrikaans punctuation not being pronounced correctly. What I had to do, was to copy the two files in the NVDA\locale\af_ZA folder to the nvda\locale\af folder and all is working fine with espeak-ng. Who should arrange for those files to be included in that folder for future builds of NVDA?

Many thanks for the great work you are doing.

Kind regards

Christo


Re: eSpeak optimizations for Android 6.0

Matěj Plch <plchterminator@...>
 

Hi,
I do not have instaled this port now, but when I tried it, they popped up, when the main user interface of the app was opened.
Regards,
Matej

Dne 31.12.2016 v 14:05 Mario Perčinić napsal(a):

Hi guys.

Sorry i was just trying to help. Btw i have that version installed on my
current phone and i don't see any advertisements which you mentioned
over here. Do you know exactly when or in which situations they pop up?

Mario
On 12/31/2016 1:57 PM, Matěj Plch wrote:
Hi Mario,
I know about this port of eSpeak, but there is some in-app
advertisement, so I do not like this port.
It is established on the existing code and I found the crashes too.
Sincerely,
Matej


Dne 31.12.2016 v 13:49 Mario Perčinić napsal(a):
Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS
Engine from RedZoc apk. On his page he says that he optimised espeak
for android 6 and later.

Mario



On 12/31/2016 1:38 PM, Matěj Plch wrote:
Okay, Reece, thanks for your answer. I totaly understand. Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):
On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers, I am very happy, that this discussion
group was established and the next generation of eSpeak will come
in near future! Can you highlight some important changes, which
we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).


My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make
some engine optimizations, because I register quite often crashes
of latest available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The
focus on security and stability above should help reduce/remove
the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem
is noticeable especialy during fast typing on Google Keyboard or
sometimes, when I want to open several apps quickly. I posted
many crashing reports directly from the devices, but do not know,
if developers catched them.

I can see them, but as I have said, it is difficult to know what
the cause of the crash is. The work I have done already should
help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so
that the android code will be usable from the main releases
instead of requiring the android branch to be updated. This
should make it easier to perform new Android releases in the
future.

Kind regards,

Reece Dunn