Date   

[espeak-ng:master] reported: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

The ssml problem is #947. My clangs only run back to clang-10 and gccs to gcc-6.5.0 (which, for some reason, is masked by Gentoo). I do have 8.4.0 - that's actually the earliest unmasked version I have. Anyway, my current reduced test string is "0.8", which captures the first occurence of the a -> a# phoneme change. The phonemes reported for the translation are as in the test_phon call:

Found: '_.' [t'otS;ka]
Found: '_0' [n'ojl;]
Found: '_8' [v'os;E2m]
n'ojl t'otS;ka# v'os;E2m

That's from under gdb so I'll look at where the transmutation is coming from.


[espeak-ng:master] reported: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By rhdunn:

Can you run the test through -X to see what rules it is considering/using to get the pronunciation you are seeing? From that, we could run and compare the output.

Note: It is common to add tests for issues, fix them, then close the issues. That way, you don't get any regressions of that bug in the future when making changes to the code. That is why #824 is closed as that is about a crash, not a difference in the output.


[espeak-ng:master] reported: tests/ssml.test:test_ssml_audio <prosody>: wrong test fails #github

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

[espeak-ng:master] New Comment on Issue #947 tests/ssml.test:test_ssml_audio : wrong test fails
By rhdunn:

I also see:

testing <prosody>
1c1
< fcb28f00670959980038171ceda3c6bdec61b884
---
> 5ea0dcd3dc9682adacebcaf3d2fa6c8d6fa6e4aa

on my setup -- gcc 8.3.0-6 on Debian buster. The test in #945 passes for me, and all the tests pass on Travis, so I'm not sure what is happening here.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #947 tests/ssml.test:test_ssml_audio : wrong test fails
By jbowler:

  • gcc (Gentoo 11.1.0 p1) 11.1.0
  • Linux hippopopus 5.12.5-gentoo #1 SMP Thu May 20 09:29:16 PDT 2021 x86_64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz GenuineIntel GNU/Linux
  • The OS is Gentoo running the KDE Plasma 17.1 desktop profile: /usr/portage/profiles/default/linux/amd64/17.1/desktop/plasma
  • The audio is: AUDIO_USE="jack pulseaudio openal"

In what way is the test failing? I.e. what has gone wrong?

Note that this seems related to #945; in both cases an incorrectly formatted piece of text results from spurious (#945) or missing (#947) sentence terminators.


[espeak-ng:master] New Comment on Issue #947 tests/ssml.test:test_ssml_audio : wrong test fails
By jbowler:

Could you add the phoneme output for the first test case? I.e. the phonemes that you would get from espeak-ng -xq?


[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By rhdunn:

Travis (https://travis-ci.org/github/espeak-ng/espeak-ng) builds with the gcc (5.4.0-6ubuntu1~16.04.12) and clang (7.0.0) compilers -- the setup there is for amd64 on Xenial Ubuntu. As you can see those test runs are green, e.g. https://travis-ci.org/github/espeak-ng/espeak-ng/jobs/771993713#L2412. Note: I'm planning on migrating to GitHub actions, but haven't had the time to do that yet.

I've also built and run that test successfully on Debian with gcc 8.3.0-6 (although I'm getting a difference in the hash for the prodofy test in ssml.test, which I haven't investigated).

It is more likely that a buffer overflow, out of bounds read, or something similar is causing the issue you are seeing.


[espeak-ng:master] reported: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

Please give me an example of a compiler which, with the current HEAD, produces an espeak-ng that does not treat the periods as end-of-sentence (i.e where make tests/translate.check passes). E.g. what do you use, what does @rhdunn use...


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #947 tests/ssml.test:test_ssml_audio : wrong test fails
By jaacoppi:

I don't know why the first test fails.

I've explained the second test poorly. We're all hoping it would fail. It checks for a known bug #410 which has not yet been fixed. When the bug is fixed, the test will fail and needs to be changed.

What compiler and OS are you using?


[espeak-ng:master] New Comment on Issue #933 Unable to compile zhy dictionay on Windows
By jaacoppi:

@feerrenrut: Can this be closed?


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@...>:
f16b27b8409b: code cleanup: remove unnecessary new_translator in LoadVoice()

It looks like this was used in situations where both "language" and
"translator" voice options were found. Since bda8b6f76a "translator"
hasn't been supported.

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
7c32085dcd78: code cleanup: use translator instead of langopts in LoadVoice()

Since new_translator isn't used anymore langopts will always point to
translator anyway.

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
fb233a7b0c87: code cleanup: move stressLength, stressAdd and stressAmp handling in LoadVoice()

From now on, stressLength must be set before stressAdd because
stressLength will overwrite any previous value. Usually stressLength is
set in a language file and stressAdd in a voice file.

Previously the order of the two commands didn't matter.

Modified: CHANGELOG.md
Modified: docs/voices.md
Modified: src/libespeak-ng/voices.c


[espeak-ng:master] By Juho Hiltunen <jaacoppi@...>:
ac5eeb865e60: code cleanup: new function CheckTranslator()

When a language or voice file in espeak-ng-data is loaded the keyword
"translator" must be set so that other language options can modify the
values in struct Translator.

CheckTranslator() provides standardized error for all switch cases that
modify a value in struct Translator.

Modified: src/libespeak-ng/voices.c


[espeak-ng:master] reported: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jaacoppi:

I think you are trying to fix the wrong problem.

The test case for #824 is to prevent espeak-ng from crashing with long strings. It is not specific to Russian, it also happens with other languages. Whether or not the pronunciation is correct is not important.

I think fixing the test for certain compilers requires identifying which compilers fail and figuring out what has changed in the compiler. The ynthesizer should not produce different results with different compilers.

See: https://github.com/espeak-ng/espeak-ng/issues/824 https://github.com/espeak-ng/espeak-ng/pull/867


[espeak-ng:master] reported: autogen.sh succeeds only on second try #github

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

[espeak-ng:master] New Comment on Issue #941 autogen.sh succeeds only on second try
By jasonhemann:

@rhdunn , no it did not, actually. Although that change moves the problematic line to line num 2438.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

Hang on. The test string isn't Russian; the numbers in it aren't in Russian. The "correct" phoneme output string in tests/translate.test continually drops into English. Here's an example of a Russian number:

**$** espeak-ng -xq -v ru "1,2"
_ojd;'in _:'i_: dv'A_d;Is;'AtYx_

Translating the phonemes back using dictsource/ru_list shows that this is correct:

_1      ojd;'in
_dpt    _:'i_:        // start of decimal fraction
_2      dv'A
_dpt2   _d;Is;'atYx   // end of decimal fraction

That's with the current build that demonstrates the behavior that is supposed to be wrong. The "," character does not occur a single time in the test string, but %2C does and so does the period character ".", which is Russian for "end of sentence" (according to reliable sources), just as in English, and, just as in English should be followed by whitespace. So here is an example fragment from the test string:

**$** espeak-ng -xq -v ru "%200.36817%2C-0.2019%20"
_p@-rats'Ent dv;'es;t;I t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; p@-rats'Ent dv'A (en)s'i:(ru) n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt; p@-rats'Ent dv'AttsVt;_

Since there aren't any spaces in the test string either it seems reasonable to assume that these are mean to be %HH characters, %20 is space and %2C is comma:

**$** espeak-ng -xq -v ru " 0.36817,-0.2019 "
_n'ojl t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt;_

In both cases the "." is a sentence terminator. I don't know if Russian uses the % or %% notation but it probably does (it's a notation used in science and engineering and is internationally acceptable). So the first case is literally speaking the %20 and %2C (hence all the p@-rats) and, putting the missing spaces in:

% 200. 36817 % 2C - 0. 2019% 20

I think the "a#" here is correct - not the original a without the # because the phoneme is followed by a sentence terminator. The second case is:

0. 36817, -0.2. 2019

Both of these are totally messed up. It looks like the test string has been hacked from a longer string using %xx notation for characters (as in a URI). The string starts with "C0.87569253%20" but "C" doesn't occur elsewhere in the string except in the context "%2C". The numbers seem to be English format, not Russian, but given the mix of periods and %2C's it is difficult to tell.

I think this test string should be replaced by something that is correctly formatted Russian that actually makes sense.


[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

Hang on. The test string isn't Russian; the numbers in it aren't in Russian. The "correct" phoneme output string in tests/translate.test continually drops into English. Here's an example of a Russian number:

**$** espeak-ng -xq -v ru "1,2"
_ojd;'in _:'i_: dv'A_d;Is;'AtYx_

Translating the phonemes back using dictsource/ru_list shows that this is correct:

_1      ojd;'in
_dpt    _:'i_:        // start of decimal fraction
_2      dv'A
_dpt2   _d;Is;'atYx   // end of decimal fraction

That's with the current build that demonstrates the behavior that is supposed to be wrong. The "," character does not occur a single time in the test string, but %2C does and so does the period character ".", which is Russian for "end of sentence" (according to reliable sources), just as in English, and, just as in English should be followed by whitespace. So here is an example fragment from the test string:

$ espeak-ng -xq -v ru "%200.36817%2C-0.2019%20"
p@-rats'Ent dv;'es;t;I t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; p@-rats'Ent dv'A (en)s'i:(ru) n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt; p@-rats'Ent dv'AttsVt;

Since there aren't any spaces in the test string either it seems reasonable to assume that these are mean to be %HH characters, %20 is space and %2C is comma:

$ espeak-ng -xq -v ru " 0.36817,-0.2019 "
n'ojl t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt;

In both cases the "." is a sentence terminator. I don't know if Russian uses the % or %% notation but it probably does (it's a notation used in science and engineering and is internationally acceptable). So the first case is literally speaking the %20 and %2C (hence all the p@-rats) and, putting the missing spaces in:

% 200. 36817 % 2C - 0. 2019% 20

I think the "a#" here is correct - not the original a without the # because the phoneme is followed by a sentence terminator. The second case is:

0. 36817, -0.2. 2019

Both of these are totally messed up. It looks like the test string has been hacked from a longer string using %xx notation for characters (as in a URI). The string starts with "C0.87569253%20" but "C" doesn't occur elsewhere in the string except in the context "%2C". The numbers seem to be English format, not Russian, but given the mix of periods and %2C's it is difficult to tell.

I think this test string should be replaced by something that is correctly formatted Russian that actually makes sense.


[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

Hang on. The test string isn't Russian; the numbers in it aren't in Russian. The "correct" phoneme output string in tests/translate.test continually drops into English. Here's an example of a Russian number:

$ espeak-ng -xq -v ru "1,2"
ojd;'in _:'i_: dv'A_d;Is;'AtYx

Translating the phonemes back using dictsource/ru_list shows that this is correct:

_1      ojd;'in
_dpt    _:'i_:        // start of decimal fraction
_2      dv'A
_dpt2   _d;Is;'atYx   // end of decimal fraction

That's with the current build that demonstrates the behavior that is supposed to be wrong. The "," character does not occur a single time in the test string, but %2C does and so does the period character ".", which is Russian for "end of sentence" (according to reliable sources), just as in English, and, just as in English should be followed by whitespace. So here is an example fragment from the test string:

$ espeak-ng -xq -v ru "%200.36817%2C-0.2019%20"
p@-rats'Ent dv;'es;t;I t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; p@-rats'Ent dv'A (en)s'i:(ru) n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt; p@-rats'Ent dv'AttsVt;

Since there aren't any spaces in the test string either it seems reasonable to assume that these are mean to be %HH characters, %20 is space and %2C is comma:

$ espeak-ng -xq -v ru " 0.36817,-0.2019 "
n'ojl t'otS;ka# t@-r;'ittsat;S'Es;t; t'ys;VtS;_! vOs;Ims'ot s;Imn'AttsVt; n'ojl t'otS;ka# dv;'e t'ys;VdZ; d;E2v;Itn'AttsVt;

In both cases the "." is a sentence terminator. I don't know if Russian uses the % or %% notation but it probably does (it's a notation used in science and engineering and is internationally acceptable). So the first case is literally speaking the %20 and %2C (hence all the p@-rats) and, putting the missing spaces in:

% 200. 36817 % 2C - 0. 2019% 20

I think the "a#" here is correct - not the original a without the # because the phoneme is followed by a sentence terminator. The second case is:

0. 36817, -0.2. 2019

Both of these are totally messed up. It looks like the test string has been hacked from a longer string using %xx notation for characters (as in a URI). The string starts with "C0.87569253%20" but "C" doesn't occur elsewhere in the string except in the context "%2C". The numbers seem to be English format, not Russian, but given the mix of periods and %2C's it is difficult to tell.

I think this test string should be replaced by something that is correctly formatted Russian that actually makes sense.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #938 Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict
By BaijinBullet:

I read this dll found in VS Code 2019 Visual tools and indeed was found after installation of it. Now I receive an error:

Error processing file '/usr/share/espeak-ng-data\phontab': No such file or directory.

C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe (process 3872) exited with code 1.
To automatically close the console when debugging stops, enable Tools->Options->Debugging->Automatically close the console when debugging stops.
Press any key to close this window . . .

And:

'espeak-ng.exe' (Win32): Loaded 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe'. Symbols loaded.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\libespeak-ng.dll'. Symbols loaded.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_8.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Unloaded 'C:\Windows\System32\XAudio2_8.dll'
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcp140d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140_1d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_8.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_9.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\MMDevAPI.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\SHCore.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\avrt.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\devobj.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Cannot find or open the PDB file.
The thread 0x2940 has exited with code 0 (0x0).
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Cannot find or open the PDB file.
The thread 0x1614 has exited with code 1 (0x1).
The thread 0x2a78 has exited with code 1 (0x1).
The program '[3872] espeak-ng.exe' has exited with code 1 (0x1).

Correct debug runtime? Before this, I have not used Visual Studio; could you advise me? I installed Visual Studio 2017 with - Desktop Development with C++ -- Visual C++ Core Desktop Features -- Just-In-Time Debugging -- VC++ 2017 version 15.9 v14.16 latest v141 tools -- C++ profiling tools -- Windows 10 SDK (10.0.17763.0) -- Visual C++ tools for CMake -- Visual C++ ATL for x86 and x64 -- Test Adapter for Boost.Test -- Test Adapter for Google Test -- Windows 8.1 SDK and UCRT SDK

-- Visual C++ MFC for x86 and x64 -- C++/CLI support

  • WiX Toolset Visual Studio 2017 Extension
  • WiX Toolset v3 Schemas for Visual Studio
  • WiX Toolset v4 Schemas for Visual Studio
  • NuGet package manager

Visual Studio 2019 - MSVC v142 - VS 2019 C++ x64/x86 build tools

Which other components are necessary? And are any of the components unnecessary and may be removed? Storage is limited. Thank you!


[espeak-ng:master] New Comment on Issue #938 Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict
By BaijinBullet:

I read this dll found in VS Code 2019 Visual tools and indeed was found after installation of it. Now I receive an error:

Error processing file '/usr/share/espeak-ng-data\phontab': No such file or directory.

C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe (process 3872) exited with code 1.
To automatically close the console when debugging stops, enable Tools->Options->Debugging->Automatically close the console when debugging stops.
Press any key to close this window . . .

And:

'espeak-ng.exe' (Win32): Loaded 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\espeak-ng.exe'. Symbols loaded.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Users\moqi\eSpeakNG\espeak-ng\src\windows\x64\Debug\libespeak-ng.dll'. Symbols loaded.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_8.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Unloaded 'C:\Windows\System32\XAudio2_8.dll'
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\msvcp140d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140_1d.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_8.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\XAudio2_9.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\MMDevAPI.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\SHCore.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\avrt.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\devobj.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'. Cannot find or open the PDB file.
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Cannot find or open the PDB file.
The thread 0x2940 has exited with code 0 (0x0).
'espeak-ng.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Cannot find or open the PDB file.
The thread 0x1614 has exited with code 1 (0x1).
The thread 0x2a78 has exited with code 1 (0x1).
The program '[3872] espeak-ng.exe' has exited with code 1 (0x1).

Correct debug runtime? Before this, I have not used Visual Studio; could you advise me? I installed Visual Studio 2017 with - Desktop Development with C++ -- Visual C++ Core Desktop Features -- Just-In-Time Debugging -- VC++ 2017 version 15.9 v14.16 latest v141 tools -- C++ profiling tools -- Windows 10 SDK (10.0.17763.0) -- Visual C++ tools for CMake -- Visual C++ ATL for x86 and x64 -- Test Adapter for Boost.Test -- Test Adapter for Google Test -- Windows 8.1 SDK and UCRT SDK -- Visual C++ MFC for x86 and x64 -- C++/CLI support - WiX Toolset Visual Studio 2017 Extension - WiX Toolset v3 Schemas for Visual Studio - WiX Toolset v4 Schemas for Visual Studio - NuGet package manager

Visual Studio 2019 - MSVC v142 - VS 2019 C++ x64/x86 build tools

Which other components are necessary? And are any of the components unnecessary and may be removed? Storage is limited. Thank you!


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #941 autogen.sh succeeds only on second try
By rhdunn:

In configure.ac, does adding AC_CONFIG_AUX_DIR([.]) before AC_CONFIG_MACRO_DIR([m4]) fix the issue you are having?


[espeak-ng:master] New Comment on Issue #938 Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict
By rhdunn:

The vcruntime140_1d.dll file is the debug version. Have you installed the correct debug runtime? Does building in release work (as it looks like you have the release DLLs installed)?


[espeak-ng:master] reported: Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict #github

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

[espeak-ng:master] New Comment on Issue #938 Windows 10 Build Failed - Cannot Find espeak-ng-data\*_dict
By BaijinBullet:

It seems to be vcruntime140_1d.dll missing. Can I replace with different version? I could not find where it has been included. I have vcruntime140.dll vcruntime140d.dll vcruntime140_1.dll Thank you for the assistance.


[espeak-ng:master] reported: autogen.sh succeeds only on second try #github

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

[espeak-ng:master] New Comment on Issue #941 autogen.sh succeeds only on second try
By jasonhemann:

I do have the required autotools programs.

bash-4.2$ which make
/usr/bin/make
bash-4.2$ which autoconf
/usr/bin/autoconf
bash-4.2$ which automake
/usr/bin/automake
bash-4.2$ which libtool
/usr/bin/libtool
bash-4.2$ which pkg-config
/usr/bin/pkg-config
bash-4.2$ which gcc
/opt/rh/devtoolset-8/root/usr/bin/gcc
bash-4.2$ libtoolize -i -f
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: linking file `m4/libtool.m4'
libtoolize: linking file `m4/ltoptions.m4'
libtoolize: linking file `m4/ltsugar.m4'
libtoolize: linking file `m4/ltversion.m4'
libtoolize: linking file `m4/lt~obsolete.m4'
bash-4.2$ ./autogen.sh
configure.ac:4: installing './config.guess'
configure.ac:4: installing './config.sub'
configure.ac:3: installing './install-sh'
configure.ac:4: error: required file './ltmain.sh' not found
configure.ac:3: installing './missing'
Makefile.am:436: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:447: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:450: warning: '%'-style pattern rules are a GNU make extension
Makefile.am: installing './INSTALL'
Makefile.am:209: warning: compiling 'src/espeak-ng.c' in subdir requires 'AM_PROG_CC_C_O' in 'configure.ac'
Makefile.am: installing './depcomp'
bash-4.2$ ./autogen.sh
libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
Makefile.am:436: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:447: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:450: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:209: warning: compiling 'src/espeak-ng.c' in subdir requires 'AM_PROG_CC_C_O' in 'configure.ac'

I don't have Kramdown, but that doesn't seem like it should affect ltmain.


Updates to Github #github

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

[espeak-ng:master] New Issue Created by jbowler:
#947 tests/ssml.test:test_ssml_audio : wrong test fails

When I run "make check" the first check fails, the second, which the comments say "should fail" succeeds. This is the output with a slightly modified test_ssml_audio which accepts a fourth "IGNORE" argument:

testing IGNORE 1c1

< fcb28f00670959980038171ceda3c6bdec61b884

5ea0dcd3dc9682adacebcaf3d2fa6c8d6fa6e4aa test_ssml_audio: WARNING: ignored testing bug #410 testing

Reproed using 88c4a452fe40413a146d21e31856fcfa9e7e4eea (current pull request, necessary for me to get to these tests, HEAD-1 is f6d092a9c13d864ede78c493f64a7d32cde41f09) and I added the attached 'ssml.test.patch' (.txt is just to make this dialog accept the file), then:

git clean -dfx ./autogen.sh ./configure make check

With the patch 'make check' will complete, but it has ignored the error in the first test_ssml_audio (log fragment posted above). Without the patch of course it fails before executing the second test_ssml_audio.

I added a "tee audio.out" to see what is actually getting output. Kwave reports it as corrupted, but it is a RIFF so who knows:

audio.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 22050 Hz

Groove Music on Windows opens it just fine and it seems to have the correct speech for the input (with the correct prosody). I've attached the output file as a gzip (this dialog does not support any audio files, but it does allow arbitrary gzip'ed files!)

audio.wav.gz ssml.test.patch.txt


[espeak-ng:master] New Issue Created by jbowler:
#947 tests/ssml.test:test_ssml_audio : wrong test fails

When I run "make check" the first check fails, the second, which the comments say "should fail" succeeds. This is the output with a slightly modified test_ssml_audio which accepts a fourth "IGNORE" argument:

testing <prosody> IGNORE
1c1
< fcb28f00670959980038171ceda3c6bdec61b884
---
> 5ea0dcd3dc9682adacebcaf3d2fa6c8d6fa6e4aa
test_ssml_audio: WARNING: ignored
testing <prosody> bug #410 
testing <audio> 

Reproed using 88c4a452fe40413a146d21e31856fcfa9e7e4eea (current pull request, necessary for me to get to these tests, HEAD-1 is f6d092a9c13d864ede78c493f64a7d32cde41f09) and I added the attached 'ssml.test.patch' (.txt is just to make this dialog accept the file), then:

git clean -dfx
./autogen.sh
./configure
make check

With the patch 'make check' will complete, but it has ignored the error in the first test_ssml_audio (log fragment posted above). Without the patch of course it fails before executing the second test_ssml_audio.

I added a "tee audio.out" to see what is actually getting output. Kwave reports it as corrupted, but it is a RIFF so who knows:

audio.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 22050 Hz

Groove Music on Windows opens it just fine and it seems to have the correct speech for the input (with the correct prosody). I've attached the output file as a gzip (this dialog does not support any audio files, but it does allow arbitrary gzip'ed files!)

audio.wav.gz ssml.test.patch.txt


[espeak-ng:master] reported: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Comment on Issue #945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds
By jbowler:

I double checked --with-extdict-ru; the output (on my system) still contains the "a# " strings.


Pull Request Opened #github

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

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

#946 Workround for #945; check for 'ru sum strings'

The change made to 'tests/translate.test' to detect bug #824 also demonstrates what has been described to me as a compiler dependency in the output; on my system every occurence of "a " in the phoneme output is actually output as "a# ".

This is reported in issue #945 (I could find no prior report) however the issue does not seem to be fixed anytime soon; it has been around since the test was added in 30214437fc0bb0d067bb60cd550e192edcd2a626 on Dec. 20, 2020.

The test terminates 'make check' in the case in question and therefore obscures any following errors and makes it very difficult to debug unrelated changes to any part of espeak-ng or the build system.

This change adds support for tests/common:test_phon for a MESSAGE argument "ru sum strings" which was added to the test_phon call by 17e6bd0672421467554dcca95f04c2a63b70c510 on the 16th inst. (although that change doesn't seem to do anything).

If "ru sum strings" is passed every occurence of "a# " in the output received from espeak-ng is changed to "a ". Since "a# " does not occur in the correct output this makes no difference to the original check.

Obviously I've only tested this on my system, I know the issue is known but since there did not seem to be a bug report until I entered #945 I don't know what output other systems generate (other than the correct output). The change is intended to allow "make check" to skip this known error and therefore detect other issues.

Signed-off-by: John Bowler jbowler@...


[espeak-ng:master] new issue: The change to tests/translate.test to detect #824 causes unexplained failures on some builds #github

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

[espeak-ng:master] New Issue Created by jbowler:
#945 The change to tests/translate.test to detect #824 causes unexplained failures on some builds

The change in question added:

bug: https://github.com/espeak-ng/espeak-ng/issues/824

test_phoneme ru ...

to tests/translate.test. Apparently this is to detect the crash documented in #824 and cannot be removed (despite the fact that #824 is closed). Unfortunately this test also demonstrates some variability in the phoneme output which apparently depends on compiler version. I see these changes:

ka v'os; --> ka# v'os; ka vOs; --> ka# vOs; ka t@-r; --> ka# t@-r; ka S,E#s; --> ka# S,E#s;t; 'ista d; --> 'ista# d; E2sta d; --> E2sta# d; ka n'ojldv'A! tR; --> ka# n'ojldv'A! tR; 'ista d; --> 'ista# d;

I.e. every "a " in the correct phoneme output becomes "a# ". I checked translate.test and the byte sequence "a# " does not occur in any of the tests.

The repro sequence, starting from a totally clean git clone (git clean -dfx) is:

./autogen.sh ./configure make check

So all the configure options are the default. I didn't check what happens with the "extra" ru support, --with-extdict-ru (russian extended dictionary).


[espeak-ng:master] reported: Procedure not clear on how to remove/disable a language #github

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

[espeak-ng:master] New Comment on Issue #922 Procedure not clear on how to remove/disable a language
By jbowler:

Yes but it prevents all the other tests running; for example by marking the #824 test "broken" I get to see a whole run of errors in tests/ssml.test (which I haven't tracked down yet). I could supply a patch to add MESSAGE "soft" to test_phon and if espeak-ng does not crash the test succeeds even if the output is 'wrong'.

Anyway, the error is really weird - somehow the incorrect version is adding a # character in certain very particular places:

ka v'os; --> ka# v'os; ka vOs; --> ka# vOs; ka t@-r; --> ka# t@-r; ka S,E#s; --> ka# S,E#s;t; 'ista d; --> 'ista# d; E2sta d; --> E2sta# d; ka n'ojldv'A! tR; --> ka# n'ojldv'A! tR; 'ista d; --> 'ista# d;

I.e. somehow the "broken compiler" case is outputing "a " as "a# " - there are not instances of "a# " in the correct output. I'll file a bug with a patch to sed the output of this one test.


[espeak-ng:master] new issue: autogen.sh succeeds only on second try #github

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

[espeak-ng:master] New Issue Created by jasonhemann:
#941 autogen.sh succeeds only on second try

On my system, building from source, executing autogen.sh fails the first time due to a missing file ltmain.sh. Running autogen twice seems to succeed. I don't yet have a running executable, so it might be this has just masked the problem, however.

Logs:

-bash-4.2$ ./autogen.sh
configure.ac:4: installing './config.guess'
configure.ac:4: installing './config.sub'
configure.ac:3: installing './install-sh'
configure.ac:4: error: required file './ltmain.sh' not found
configure.ac:3: installing './missing'
Makefile.am:436: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:447: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:450: warning: '%'-style pattern rules are a GNU make extension
Makefile.am: installing './INSTALL'
Makefile.am:209: warning: compiling 'src/espeak-ng.c' in subdir requires 'AM_PROG_CC_C_O' in 'configure.ac'
Makefile.am: installing './depcomp'
-bash-4.2$ ./autogen.sh
libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
Makefile.am:436: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:447: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:450: warning: '%'-style pattern rules are a GNU make extension
Makefile.am:209: warning: compiling 'src/espeak-ng.c' in subdir requires 'AM_PROG_CC_C_O' in 'configure.ac'

481 - 500 of 4643