Topics

new espeak ng builds

Simon Eigeldinger
 

Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

mattias
 

sapi?

On 2019-11-05 18:36, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


Simon Eigeldinger
 

No.


Am 05.11.2019 um 18:47 schrieb mattias:

sapi?
On 2019-11-05 18:36, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus



Reece H. Dunn
 

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

mattias
 

Reece yes i know that the sapi5 are experimental

But if i want to try i have to compile espeak myself?

If so fine, but there is no free version of Visual studio?

 

Skickades från E-post för Windows 10

 

Från: Reece H. Dunn
Skickat: den 5 november 2019 19:44
Till: espeak-ng@groups.io
Ämne: Re: [espeak-ng] new espeak ng builds

 

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

Hi all,

I have compiled new builds yesterday.
now they also work on all systems.

Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

 

Simon Eigeldinger
 

Hi,

Yes there is.
You can download visual studio community edition.
This is free.
I am using that over here as well.

Greetings,
Simon


Am 05.11.2019 um 19:49 schrieb mattias:

Reece yes i know that the sapi5 are experimental
But if i want to try i have to compile espeak myself?
If so fine, but there is no free version of Visual studio?
Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för
Windows 10
*Från: *Reece H. Dunn <mailto:msclrhd@...>
*Skickat: *den 5 november 2019 19:44
*Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>
*Ämne: *Re: [espeak-ng] new espeak ng builds
On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,
I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).
While they are a pain to manage, they provide features such as the ability to
upgrade, repair, and uninstall. This includes updating the registry and ensuring
that dependencies within the installer are installed based on the features the
user selects. This is done by keeping the GUIDs the same for each item.
I would like to update the MSI to better reflect the current state (e.g. new
voices) before release. I haven't had time to do this yet, but patches are welcome.
Longer term, we can look at better ways to manage the process. Something like
having the GUIDs in the language/voice file with the ability to generate the
voice data part of the installer XML source. This could then be made so that the
tests can check that GUIDs are present and valid, so the regression tests will
fail if any are missing/wrong.
Regarding SAPI support: There is an experimental version commented out for
English. It has a few bugs and is not complete.
Kind regards,
Reece
Greetings,
Simon
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

mattias
 

Simon do you use git for windows to clone the git repo?

 

Skickades från E-post för Windows 10

 

Från: Simon Eigeldinger
Skickat: den 5 november 2019 19:52
Till: espeak-ng@groups.io
Ämne: Re: [espeak-ng] new espeak ng builds

 

Hi,

 

Yes there is.

You can download visual studio community edition.

This is free.

I am using that over here as well.

 

Greetings,

Simon

 

 

Am 05.11.2019 um 19:49 schrieb mattias:

> Reece yes i know that the sapi5 are experimental

>

> But if i want to try i have to compile espeak myself?

>

> If so fine, but there is no free version of Visual studio?

>

> Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för

> Windows 10

>

> *Från: *Reece H. Dunn <mailto:msclrhd@...>

> *Skickat: *den 5 november 2019 19:44

> *Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>

> *Ämne: *Re: [espeak-ng] new espeak ng builds

>

> On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

>

>      Hi all,

>

>      I have compiled new builds yesterday.

>      now they also work on all systems.

>

> Great. Thanks for doing this.

>

>      had to get release mode working.

>      by default visual studio uses debug mode which doesn't let you run the

>      binaries on a non developer pc.

>      Seems we don't get voice variants in the msi installer.

>      We also seem to lack documentation.

>      I ask myself if it is a good idea to continue with msi installers when

>      the creation and keeping them up to date of such ones is pretty complex?

>      What do you think?

>

> MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).

> While they are a pain to manage, they provide features such as the ability to

> upgrade, repair, and uninstall. This includes updating the registry and ensuring

> that dependencies within the installer are installed based on the features the

> user selects. This is done by keeping the GUIDs the same for each item.

>

> I would like to update the MSI to better reflect the current state (e.g. new

> voices) before release. I haven't had time to do this yet, but patches are welcome.

>

> Longer term, we can look at better ways to manage the process. Something like

> having the GUIDs in the language/voice file with the ability to generate the

> voice data part of the installer XML source. This could then be made so that the

> tests can check that GUIDs are present and valid, so the regression tests will

> fail if any are missing/wrong.

>

> Regarding SAPI support: There is an experimental version commented out for

> English. It has a few bugs and is not complete.

>

> Kind regards,

> Reece

>

>      Greetings,

>      Simon

>

>

>      --

>      Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

>      https://www.avast.com/antivirus

>

>

>

 

--

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

https://www.avast.com/antivirus

 

 

 

 

Simon Eigeldinger
 

Hi Reece,

No problem.
We are a small community and whoever is able to help with something (big or small) is a big help factor.

I have also tried to get my hands dirty with the wix xml format but never got my head around it.
So i dropped that experiment. *smile*
Way to many guids, gids and whatever other ids they have.
After that i played with NSIS and Inno Setup and got way better results. *lol*
Or i just went with zip files for simplicity.

Greetings,
Simon





Am 05.11.2019 um 19:44 schrieb Reece H. Dunn:

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:


Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.


had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.
I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.
Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.
Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.
Kind regards,
Reece


Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Simon Eigeldinger
 

yes i did.
https://github.com/git-for-windows/git/

Here's the building howto for espeak ng:
https://github.com/espeak-ng/espeak-ng/blob/master/docs/building.md


Here's my script how i build it.
it builds msi files for 32 and 64 bit.
You might need to replace some directory names.


--- Script begin ---

cd\
c:
cd\
cd src
git clone git://github.com/espeak-ng/espeak-ng.git
cd espeak-ng
cd src
git clone git://github.com/espeak-ng/pcaudiolib.git
cd windows
msbuild /p:Configuration=Release /p:PlatformTarget=x86 /p:Platform=x86 espeak-ng.sln
msbuild /p:Configuration=Release /p:PlatformTarget=x64 /p:Platform=x64 espeak-ng.sln


--- Script end ---


Might also be interesting for the howto.
Though i might rewrite the windows part at some time.


Greetings,
Simon

Am 05.11.2019 um 20:05 schrieb mattias:

Simon do you use git for windows to clone the git repo?
Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för
Windows 10
*Från: *Simon Eigeldinger <mailto:simon.eigeldinger@...>
*Skickat: *den 5 november 2019 19:52
*Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>
*Ämne: *Re: [espeak-ng] new espeak ng builds
Hi,
Yes there is.
You can download visual studio community edition.
This is free.
I am using that over here as well.
Greetings,
Simon
Am 05.11.2019 um 19:49 schrieb mattias:

> Reece yes i know that the sapi5 are experimental

>

> But if i want to try i have to compile espeak myself?

>

> If so fine, but there is no free version of Visual studio?

>

> Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för

> Windows 10

>

> *Från: *Reece H. Dunn <mailto:msclrhd@...>

> *Skickat: *den 5 november 2019 19:44

> *Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>

> *Ämne: *Re: [espeak-ng] new espeak ng builds

>

> On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

>

> Hi all,

>

> I have compiled new builds yesterday.

> now they also work on all systems.

>

> Great. Thanks for doing this.

>

> had to get release mode working.

> by default visual studio uses debug mode which doesn't let you run the

> binaries on a non developer pc.

> Seems we don't get voice variants in the msi installer.

> We also seem to lack documentation.

> I ask myself if it is a good idea to continue with msi installers when

> the creation and keeping them up to date of such ones is pretty complex?

> What do you think?

>

> MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).

> While they are a pain to manage, they provide features such as the ability to

> upgrade, repair, and uninstall. This includes updating the registry and ensuring

> that dependencies within the installer are installed based on the features the

> user selects. This is done by keeping the GUIDs the same for each item.

>

> I would like to update the MSI to better reflect the current state (e.g. new

> voices) before release. I haven't had time to do this yet, but patches are
welcome.

>

> Longer term, we can look at better ways to manage the process. Something like

> having the GUIDs in the language/voice file with the ability to generate the

> voice data part of the installer XML source. This could then be made so that the

> tests can check that GUIDs are present and valid, so the regression tests will

> fail if any are missing/wrong.

>

> Regarding SAPI support: There is an experimental version commented out for

> English. It has a few bugs and is not complete.

>

> Kind regards,

> Reece

>

> Greetings,

> Simon

>

>

> --

> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

> https://www.avast.com/antivirus

>

>

>
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

mattias
 

reece if i will try the sapi how to enable?

i have forgot it

On 2019-11-05 19:44, Reece H. Dunn wrote:
On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus