Talk:eSpeak

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing: Software

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Disability

ESpeak is within the scope of WikiProject Disability. For more information, visit the project page, where you can join the project and/or contribute to the discussion.DisabilityWikipedia:WikiProject DisabilityTemplate:WikiProject DisabilityDisability articles

Google Translate

For languages not listed in the updated voices, Google Translate still uses eSpeak. For example, Afrikaans and Armenian are still using eSpeak, while Hungarian and Danish are using the updated (non-eSpeak) TTS voices. Rhdunn (talk) 09:35, 2 January 2017 (UTC)[reply]

Unexplained {{COI}} template

@Chrissymad: I don't see any mention of a conflict on interest on this talk page. Is there any specific reason for the cleanup tag that you added to this article? Jarble (talk) 07:49, 13 January 2017 (UTC)[reply]

@Jarble 180.241.28.65 (talk) 03:28, 1 September 2024 (UTC)[reply]

Focus on eSpeak, not eSpeakNG

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: Moved. Please update the article accordingly — Martin (MSGJ · talk) 20:41, 23 May 2019 (UTC)[reply]

ESpeakNG → ESpeak – Several independent sources seem to establish the notability of eSpeak, but the only links referencing eSpeakNG seem to be from its developers. Languorrises (talk) 22:39, 14 May 2019 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

It seems to me that there has only ever been one project, with several changes in maintainers, homepage, names, etc., without significant phases of parallel development of separate projects with different paths: eSpeakNG seems to be the one and only continuation of Speak/eSpeak, approved by the original author.--Reseletti (talk) 12:12, 30 January 2021 (UTC)[reply]

Quality comparison

Generally, I expect the best Free Software programs to be of similar quality to good proprietary programs. But when I tried espeak-ng, I was disagreeably surprised by the poor quality of generated English speech. I remember hearing output from a Digital Equipment Corporation product in the mid-1980s that produced better-quality English speech (more natural-sounding) than espeak-ng produces in 2022 (on a vastly more powerful computer). I think some comment about this needs to be made in the article, maybe to the effect that this espeak-ng is not meant to be a production program. I'm unfamiliar with how Wikipedia deals with this, so leave it to others to consider. Insulation2 (talk) 18:22, 4 February 2022 (UTC)[reply]

It’s difficult to say without more information about what the code is supposed to do and what’s happening when it’s executed. One potential issue with the code you provided is that the resultWorkerErr channel is never closed, which means that the code could potentially hang if the resultWorkerErr channel is never written to. This could happen if b.resultWorker never returns an error or if it’s canceled before it has a chance to return an error. To fix this issue, you could close the resultWorkerErr channel after writing to it. For example, you could add the following line of code after the line that sends the error on the channel: 106.219.184.135 (talk) 18:02, 30 July 2024 (UTC)[reply]