Talk:Speech recognition

message: "Voice Recognition" is analysis of the spectral patterns of one's speech to verify if that voice belongs to a registered individual. Voice recognition is used in authentication systems. "Speech Recognition" is analysis of the speech stream to parse semantic content, frequently used for command and control. Why is even wikipedia conflating these two terms?  —Preceding unsigned comment added by 24.18.198.206 (talk) 13:50, 22 April 2009 (UTC)
replies: text: Probably because Voice Recognition is often mentioned together with Speech recognition in published literature. A second reason would be that VR techniques come from SR. OrenBochman (talk) 14:25, 28 March 2012 (UTC)
replies: text: And laypeople often confuse the terms. --Thnidu (talk) 17:03, 14 October 2018 (UTC)
thread_title: Voice Recognition

message: http://www.cs.colorado.edu/%7Emartin/SLP/Updates/  —Preceding unsigned comment added by 84.135.80.109 (talk) 10:26, 7 September 2007 (UTC)
thread_title:  Textbook Link ? 

message: Content from Speech Recognition, now a redirect here.
My understanding is that the entropics HTK toolkit, while available, is copyright microsoft.  I would suggest looking elsewhere for places to start... probably CMU sphinx, as evil and difficult as it is to use.
NotSoAnonymousCoward 17 Nov, 2005
The phonemes identification is produced when the sound of speech arrives at the computer as analogue wave forms. At the end of the process, these phonemes make up words, which recognise the inputs either they are continuous or discretes. To gather every single word is necessary a hard and long work, which goes on in training samples (known as corpora). There are also some problems when trying this. First of all, the recognition of the kind of speech, depending on a deliberated speech or a continuous one; besides, the difficulty to identify any speaker with the trouble individual speech brings. The pollution in the system produced by outer noises is also another problem. And at the end, to overcome the Grammar mistakes caused by differences in accents, dialects and spoken languages.
Charles Matthews 09:20, 6 May 2004 (UTC)
replies: text: If it's wrong, then correct it. If it's mislabeled, then label it correctly. Don't just delete--that's not we do things here. Nohat 23:08, 18 Apr 2005 (UTC)
replies: text: I restored the above content. It's generally considered bad form to delete content from Talk pages unless it's been archived to an archive page. Nohat 23:56, 18 Apr 2005 (UTC)
thread_title:  Old comments 

message: Possible copyright violation from http://www.wombatnation.com/2004/04/speech-recognition/  Arvindn 08:09, 7 May 2005 (UTC)
thread_title: copyvio

message: I was under the impression that speech recognition differs from voice recognition (which uses voice or voiceprints to identify someone).  If so, I don't think a search for voice recognition should redirect someone here to speech recognition.  
Am I too off target?
Bill
:You're thinking of voice authentication, which as of this writing is an article which does not exist yet. You are correct, voice recognition should be a disambiguation page pointing to speech recognition and voice authentication. Nohat 23:42, 10 April 2006 (UTC)
thread_title:  speech recognition vs voice recognition 

message: Are there any open source speech recognition projects? It would be great to summarize how the best few are doing or note the lack if there are none. — Hippietrail 17:35, 15 April 2006 (UTC)
thread_title:  Open source software 

message: Quoting:
Start-ups are also making an impact in speech recognition, most notably SimonSays Voice Technologies. A Toronto-based company, Simonsays has made several breakthroughs in robust server-based speech recognition. Though SimonSays currently possesses a smaller market share, they are certainly a company to watch.
I would rather like to have some references. This sounds too much like an adverisement. SiriusGrey 17:06, 18 April 2006 (UTC)
thread_title:  SimonSays 

message: In terms of freely available resources, the HTK book (and the accompanying HTK toolkit) is one place to start to both learn about speech recognition and to start experimenting (if you are very brave)
The last bit about being brave seems kinda POV... sentence should be reworded? Ben Tibbetts 23:12, 10 May 2006 (UTC)
thread_title:  non-encyclopedic? 

message: I have clean up some of the descriptions, mathematics in the previous version up to the point of "HMM-based speech recognition".  The previous description was biased towards commercial speech recognition.  So it is easy to mislead readers on some basic facts.  
Things I will point out is that on one hand, dictation engine could have high recognition performance.  However, for individual speaker, the recognition rate could be varied from speaker to speaker.  Notably, when the user speak English with different accents, then the performance will not usually be 98%.  So this is generally more a claim, than a fact.
Another thing I will point out is the mathematical explanation of the basic principle of speech recognition.  The previous authors obviously mistaken the use of noisy channel formulation (The P(W|A) thing if you don't know what I mean) with HMM.   This I will call a mistake, because without the max term appear in finding the best words sequence, it is actually not trivial to remove the term P(A).  The theory of speech recognition is actually quite sophisticated.  The explanation in the old version lacks of certain mathematical vigor. 
This version is still lacking behind a certain standard.  For example, I strongly agreed the comment in non-encyclopedic and simon said.  The former is really POV and the latter is really just an ad. I also disprove of using Bill Gate's quote in speech recognition.   (He is really not a researcher of speech recognition or any speech related research at all.   
We also need more scholarly articles and references to support the content.  Hopefully, we could add that in future.
:This section was added by  at 06:50, 18 May 2006; see . --Thnidu (talk) 17:12, 14 October 2018 (UTC)
thread_title:  some clean ups 

message: This article jumps into the technical issues without giving any context to the history of speech recognition advances over the years.  In the intro there is a very short summary of applications, but there are no dates or names associated with them.  I guess patent filings would give a good history of who did what when in this field. --DeweyQ 15:59, 22 July 2006 (UTC)
replies: text: "One of the most notable domains for the commercial application of speech recognition in the United States ..." another article which reads like ONLY the US have such technologies ... read i.e. the German version, and learn how Philips (from the Netherlands) took leadership on speech recognition. If I had a wish free at christmas: stop US-propaganda in Wikipedia. --77.186.130.110 (talk) 16:31, 3 November 2008 (UTC)
thread_title:  Missing history 

message: Funnily enough, the Speech-to-text article was redirected but the Speech_to_text article wasn't. I have rectified this. rmccue 01:01, 23 July 2006 (UTC)
thread_title:  Redirected from Speech to text 

message: This article focuses heavily on the "nuts and bolts" technical discussion of speech recognition technology, and gives scant coverage to the actual business uses, which are many.  For example, this article could be expanded to include the impact phone-based speech reco systems have had on customer service (positive and negative).  There's also an interesting movement to displace outdated and cumbersome touch-tone IVRs with speech-enabled systems.
Nezzo 15:29, 5 September 2006 (UTC)
thread_title: Broader Implications of Speech Recognition

message: No mention of the programs that one could use to perform speech recognition (i.e., NaturallySpeaking or ViaVoice)? Or how about cell phones and car navigation systems with voice commands? Personally, I thought this was lacking from this article. RobertM525 03:36, 12 October 2006 (UTC)
thread_title:  Software? 

message: Removed a spam link (several times) to a website called ivrdictionary.  This is a thinly veiled attempt to put advertising on Wikipedia.  Links were added by several anonymous users within a tight IP range.  Website purports to list ivr terminology, but in reality it prominently displays an advertisement to Angel dot com, which is a commercial company that sells IVR related products.  The same links were added to other articles that are related to IVR technology.  Calltech 16:56, 17 November 2006 (UTC)
thread_title:  Remove external link 

message: Would anyone like to take a stab at making an overview for the following almost-the-same-thing subjects. I know someone round here is just salivating at the prospect of 4 slightly different articles saying the same things but I personally find the whole thing confusing and unrequired. Please put an overview. 
*Speaker recognition
*Speaker verification
*Speaker identification
*Speech recognition
--I'll bring the food 01:15, 26 November 2006 (UTC)
thread_title: Hello.

message: I find it odd that this article has a section titled 'Books' this section currently conatins a single book on the subject (despite there being many and links to a online bookshop website where the book can be purchased. To me this reads like an advertisement especially as the book presented seems possibly less specialised on the subject of speech recognition than many other books that are out there but of course are not all listed. Canderra 01:41, 18 January 2007 (UTC)
thread_title:  Books Section 

message: I think that VoxForge (www.voxforge.org) should be added as an external link (but I am the VoxForge maintainer, so I cannot add the link myself).  LDC is listed, and it *sells* Speech Corpora.  VoxForge is trying to create a free English speech corpus for use in creating acoustic models for open source speech recognition engines.  We are similar to the BAS – Bavarian Archive for Speech Signals site, which provides  a free database of spoken German, which also has an external link. Kmaclean 18:42, 10 May 2007 (UTC)
thread_title:  Possible external link 

message: Please note the "wes is gay ..." comment here. Look then at the history of changes and look at the other things this AC has changed recently. Vandalism pure and simple.  —Preceding unsigned comment added by 69.44.127.179 (talk) 18:34, 4 October 2007 (UTC)
thread_title:  Vandalism here and else where from 65.175.138.211 

message: I would agree with User: Three-quarter-ten that the task of most ASR is to take an input of human vocal utterances and to deduce from them, by means of phonemes, syllables or word shapes, a series or "words" conforming to an expected syntax or natural lanuage. But the visible (or audible) output is going to be a system design decision, e.g. the output might be - where to route a bag in an airport baggage handling depot, might be a grade on a pupil progress chart, or might be a string of words spoken in a different language i.e. not necessarily "written text" at all. Martinevans123 (talk) 23:12, 15 January 2008 (UTC)
replies: text: Very good point. I revised my edit from "converts spoken words to machine-readable text, that is, to a string of character codes" to "converts spoken words to machine-readable input, for example, to a string of character codes". I guess that the irreducible common denominator, regardless of the system, is that the output of speech recognition is a binary string to be used as some sort of input. With a string of character codes to be input into a Word document being a very archetypical example. Thanks! — ¾-10 00:33, 16 January 2008 (UTC)
replies: text: I see what you mean. From the point of view of the average user, what they "put in" is speech and what they "get out" is a string of character codes, which is to say, "typed" text in their Word document. I'm going to try another revision: "converts spoken words to machine-readable input (for example, to the binary code for a string of character codes)". That's a little dense for the lay reader, but it's more accurate than what I had before. If anybody has any ideas for yet a better phrasing (accurate but lay-friendly), feel free. — ¾-10 01:17, 16 January 2008 (UTC)

text: Solicitations of any kind are not proper for inclusion in Wikipedia artilces. OccamzRazor (talk) 00:49, 11 May 2008 (UTC)
thread_title:  "machine-readable text?" 

message: The article makes no mention of Windows Vista, even though it has one of the most advanced spoken command recognition and speech dictation capability among home and office use affordable environment. 82.131.210.162 (talk) 14:34, 27 May 2008 (UTC)
replies: text: And? Just add it - better than howling around here. By the way, those "capabilities" may work in English, maybe ... maybe ... it is not working in the German Vista version.
--77.186.130.110 (talk) 16:34, 3 November 2008 (UTC)
thread_title:  Shameful anti-Gates bias! 

message: There is no mention of the expected future for speech recognition.  Any studies on the expansion of markets, acceptability of users, rate of increase of robustness to noise, etc?
It has been stated that speech recognition machines may exceed a humans understanding by the year 2012.  Can anyone confer?  —Preceding unsigned comment added by 71.65.21.242 (talk) 05:40, 8 June 2008 (UTC)
thread_title:  Future of 

message: Speech-to-text currently redirects to this article, however Speech-to-Text Reporter is not even mentioned on this article. Speech-to-text reporting is obviously a subset of speech recognition, but as the corresponding article presents no in-text citations and relatively little information anyway, I recommend a merge rather than an inset summary. Neelix (talk) 23:15, 10 November 2008 (UTC)
replies: text: You seem to be simply suggesting that because the computer speech recognition is not optimal in this case, the operator (or a second operator) has to check the output word-by-word before it is saved? But isn't that true for many, if not most, applications which have a visual HMI component? Martinevans123 (talk) 16:12, 7 April 2009 (UTC)
replies: text: But reading Speech-to-Text Reporter I now see that it is, as you say, basically a real-time audio-typing function, albeit with a special keyboard. It thus seems to have nothing to do with computer speech recognition and I have to change my view to "Completely disagree" also. Apologies for missing the point first time here. It may be a "subset of speech recognition", but only insofar as is any natural human speech recognition. Martinevans123 (talk) 17:48, 16 April 2009 (UTC)
thread_title:  Merge with [[Speech-to-Text Reporter]] 

message: Full disclosure: I am employed by LumenVox, which sells a commercial automatic speech recognizer. I make this disclosure in compliance with the WP:SCOIC guidelines. While I am a longtime user of Wikipedia, I have no experience as a contributor and would appreciate any help or guidance from editors.
Essentially I would like to suggest that our product, the LumenVox Speech Engine, be added to the list of "Commercial software/middleware" in this page. A description of the product can be found on our Web site at http://www.lumenvox.com/products/speech_engine/
I am not sure precisely what sorts of third-party references are needed to justify inclusion into this list, but if any editors can supply me with the type of references that would be required to justify notability, I can happily provide references. I don't see any references for the other applications in the list. I do believe the product (and the company) meet the notability guidelines.
Stephen Keller (talk) 19:09, 10 March 2009 (UTC)
replies: text: It looks like someone added this in the mean time. Is it accurate? -- kenb215 talk 20:18, 14 April 2009 (UTC)
replies: text: Yes, it looks good. Stephen Keller (talk) 20:25, 14 April 2009 (UTC)
thread_title:  Proposed addition: LumenVox Speech Engine 

message: Aren't those 2 different things?  Speech-to-text is like Dragon Naturally Speaking whereas Text-to-Speech would be the email readers or the speech reader for the Kindle 2.  Shouldn't that be clarified? Harriska2 (talk)  —Preceding undated comment added 16:39, 16 April 2009 (UTC)
thread_title:  Speech-to-Text vs Text-to-Speech 

message: The caption under the main pic (screensaver) describes it as a Toshiba Laptop; is this accurate?  —Preceding unsigned comment added by 86.157.24.9 (talk) 14:19, 25 April 2009 (UTC)
thread_title:  Laptop? 

message: An individual speaker can make a speech with their voice, but isn't always the owner of the speech that they have just spoken; a speech can be written down on paper in words (or binary), and repeated.
A voice is a completely different thing, a voice is what an individual generates in their mind, and owns, even before it leaves their head (even if it's then recorded, and finally repeated elsewhere afterwards, as a speech / waveform).
A voice might be pre-molecular in origin, it might not be, but might also be beyond any systematic explanation, so what, its still a voice (just like a tree is a tree).
The semantics, the lack of scientific categorisation, and use of terms, or lack of, has completely messed-up this article.
Wiki needs definitive linked definitions to the following:
Voice recognition, as a generic term (with links to the following two types of voice recognition).
Speaker recognition, as a means of voice evaluation / verification, etc..
Speech recognition, as a means of voice convertion to text / command controls, etc..  —Preceding unsigned comment added by 86.159.197.208 (talk) 17:50, 26 April 2009 (UTC)
thread_title:  Conflation Error, Corrected? 

message: I've remove the Commercial software/middleware and Open Source Software/Middleware sections per WP:EL and WP:NOTLINK.  --Ronz (talk) 00:48, 13 July 2009 (UTC)
replies: text: Thanks Ronz. For the benefit of anyone feeling that the lists should be restored, the See Also section has wikilinks to List of speech recognition software and Speech recognition in Linux which cover most of the notable ones without turning the main article into a link farm Kiore (talk) 11:44, 13 July 2009 (UTC)
thread_title: Linkfarms

message: I am an employee of a company that I believe deserves an article on Wikipedia, but I am reluctant to post the article myself due to my obvious conflict of interest (I believe in the past my company had some employees post articles which were then deleted). It was previously suggested to me that I write a version of it in my user space and ask for it to be reviewed and eventually created by other editors. I have written a draft of the article at  and would like feedback on whether it is sufficiently NPOV, researched, and if it meets the notability guidelines. Any help is appreciated. Stephen Keller (talk) 00:04, 6 March 2010 (UTC)
replies: text: This has been done.Stephen Keller (talk) 00:23, 13 March 2010 (UTC)
thread_title:  Request for Review of Potential New Article: LumenVox 

message: Reference 3 is a dead link, isn`t it? (Euro Fighter)
I don't know the original page, but my suggestion is: 
http://www.eurofighter.com/capabilities/technology/voice-throttle-stick/direct-voice-input.html  —Preceding unsigned comment added by 88.134.136.209 (talk) 14:00, 10 May 2010 (UTC)
thread_title:  Update Links (Euro Fighter) 

message: The discussion of current research is controversial, provocative and not supported by citation.  The implication that funding for speech recognition has been reduced since 2001 is factually false.  The DARPA projects EARS and GALE were both very well funded.
It is also misleading to say that performance has plateaued.  Large vocabulary speech recognition has always been a very difficult task.  Most of the performance improvement over the last 35 years has been due to the steady accumulation of small incremental improvements. The published results from the EARS and GALE research continues this trend.  In fact the EARS project was noted for a reduction in error rate on certain tasks of nearly a factor of two, one of the largest single-year improvements in speech recognition performance.
It is true that DARPA has changed focus in that GALE no longer supports recognition of English, but only of Mandarin and Arabic.  However, it has always been DARPA practice in speech recognition funding to continually shift focus to harder tasks as sufficient progress is made on the earlier tasks.  It is sign of success, not of failure. Jay Page (talk) 16:42, 24 July 2010 (UTC)
replies: text: it is true that is not DARPA anymore funding this research. But then other entities should bring on this research. DARPA is always on the forefront of research. According to this article the situation hasn't changed much from 2001 to 2006. http://robertfortner.posterous.com/the-unrecognized-death-of-speech-recognition If there are other results you should write them with the bibliography.  —Preceding unsigned comment added by 188.81.64.228 (talk) 10:54, 4 November 2010 (UTC)
thread_title:  Current Research 

message: There seems to be an error in the first paragraph of the History section, it says the IBM shoebox was first exhibited
in New York's world fair of 1964, even though the article for the IBM shoebox states,just as the official IBM site, that
it was shown to the public in 1962 at the Seattle's World Fair
Excuse me if my way of speaking is confusing, English is not my first language and I haven't practiced it in years.  —Preceding unsigned comment added by 201.172.101.197 (talk) 05:06, 12 October 2010 (UTC)
thread_title:  An error in the History section 

message: I am not happy with the refernces (just 8, 3 of which are irrelevant) or the overall quality of the article. It talks a lot about applications, but doe sot really deal with the technical challenges etc. I would say a 70% rewrite is needed. Not that I can pay attention to it now, but it should be suggested for someone in the field to rewrite. History2007 (talk) 13:32, 7 February 2011 (UTC)
thread_title: Quality & refs

message: Where is the best place for voice monitoring for other measures such as stress, e.g.  and fatigue, e.g. , and ? Thanks. Martinevans123 (talk) 21:26, 27 September 2012 (UTC)
thread_title:  Stress and fatigue voice characteristics 

message: The five paragraphs under the title "Neural Networks" are very misleading.   They imply that the only work done on Neural networks and speech recognition before 2010 was to use only neural networks on their own, that is without integrating with HMMs.   Whilst this was true for a few years in the late '80's, in the early '90's saw the integration of MLPs and RNNs with HMMs (the neural nets replaced the GMMs in HMMs).   This allowed phoneme recognition (see, Deep_learning#Automatic_speech_recognition which starts in 1992) and word recognition (see the section Deep_learning#History which says "Both shallow and deep learning (e.g., recurrent nets) of ANNs have been explored for many years.[42][43][44]").   In my mind this is enough evidence to show what the problem is, but I can find more if needed.
As I did quite a bit of the RNN/HMM work in the '90's I'm well placed to see the problem here and I do know the history so I could fix it.   However, that would be in violation of the Wikipedia:Conflict_of_interest, so if I can help someone else do it please let me know.
DrTonyR (talk) 18:40, 8 December 2018 (UTC)
thread_title:  very misleading section under the title "Neural Networks" 

message: Voice Tag redirects here, but is not explained in the article. -- Beland (talk) 23:52, 1 March 2019 (UTC)
thread_title:  Voice Tag 

message: I'm aware humans are attempting to make software understand their speech. But is there a spoken language specifically designed to be easy to understand by software? I enabled closed captions on a random YouTube video, and Google's software still messes up so much... Surely humans are smart enough to be able to design a spoken language that's easy for both humans (for speech) and AIs (to recognize)? Unless I'm overlooking it, I don't see anything on this in the article. --143.176.30.65 (talk) 15:18, 23 March 2021 (UTC)
replies: text: Human natural languages have developed to optimise "human-human" communication. Are you talking just about artificial grammars and vocabularies that use words from existing languages, but restrict legal utterances? Or are you also looking to include general phonetic restrictions as well to create, for example, a wholly artificial spoken language? I guess there would be a trade-off on how easy that would be for any human to learn. AI-recognisable spoken language used in most applications is quite task-specific? Martinevans123 (talk) 15:27, 23 March 2021 (UTC)
replies: text: Hi Martinevans123. I'm aware of WP:NOTFORUM, so I'll keep it relatively short. Basically, I'm wondering if a 'wholly artificial spoken language' exists with essentially a full vocabulary that's designed to make speech recognition much easier - yet still being easy enough for humans to learn. A universal language that any human, regardless their native language, could learn to easily communicate with AIs. Because lots of effort is put into improving software to understand dozens - if not hundreds - of different languages that are spoken in all kinds of ways. Is there a versatile language with characteristics (words or sounds) that are impossible to mix up for AIs. Is any research going into that direction. --143.176.30.65 (talk) 15:58, 23 March 2021 (UTC)
replies: text: I see. I have never heard of any. I suspect the problems might outweigh the benefits. Martinevans123 (talk) 16:06, 23 March 2021 (UTC)
thread_title:  A spoken language that's easy to understand for AIs? 

message: The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:
* 
Participate in the deletion discussion at the . —Community Tech bot (talk) 20:25, 11 September 2021 (UTC)
thread_title:  A Commons file used on this page or its Wikidata item has been nominated for deletion 

message: Hi everyone 27.109.115.130 (talk) 13:34, 8 March 2022 (UTC)
thread_title:  Everyone 

message: Hallo sayang 36.68.53.51 (talk) 14:52, 31 August 2022 (UTC)
thread_title:  Ada pesan dari siganteng heri 

message: "Speech recognition most important an interdisciplinary subfield of computer science and computational linguistics that develops methodologies and technologies that enable the recognition and translation of spoken language into text by computers with the main benefit of searchability."
Perhaps I'm just having an aneurysm, but this is seems confusing. 72.192.173.145 (talk) 04:24, 27 February 2023 (UTC)
replies: text: I also noticed that and came here to see what was up with it 66.108.250.83 (talk) 07:41, 27 February 2023 (UTC)
thread_title:  First sentence is not a sentence? 

message: — Assignment last updated by Fedfed2 (talk) 00:53, 9 December 2023 (UTC)
thread_title: Wiki Education assignment: Linguistics in the Digital Age

message: I am a first time editor, please let me know if this looks ok? I think it would be good to add in the performance section. 
=== Bias ===
Speech recognition tends to understand certain races and genders better than others. Speech recognition has a worse performance for women and non-white English speakers when looking at accuracy in English. Speech recognition has difficulty with certain accents and dialects. The rate of accuracy depends on the dialect that is spoken. Scottish and Indian accents tended to be misunderstood by speech recognition programs, like YouTube's auto-captioning. 
These biases exist because speech recognition software has had more exposure to certain types of voices, which can lead to the programs getting voices not included in the training mistaken. Companies that use speech recognition are taking steps to try and fix the bias, but the bias exists on many speech recognition platforms today. 
# ^ 
# ^ Jump up to:a b 
* This page was last edited on 13 October 2023, at 23:50.
Pbroskoff (talk) 23:54, 13 October 2023 (UTC)
thread_title:  Bias 

message: Speech recognition tends to understand certain races and genders better than others. Speech recognition has a worse performance for women and non-white English speakers when looking at accuracy in English. Speech recognition has difficulty with certain accents and dialects. The rate of accuracy depends on the dialect that is spoken. Scottish and Indian accents tended to be misunderstood by speech recognition programs, like YouTube's auto-captioning. 
These biases exist because speech recognition software has had more exposure to certain types of voices, which can lead to the programs getting voices not included in the training mistaken. Companies that use speech recognition are taking steps to try and fix the bias, but the bias exists on many speech recognition platforms today. 
# ^ 
# ^ Jump up to:a b 
* This page was last edited on 13 October 2023, at 23:50.
Pbroskoff (talk) 23:54, 13 October 2023 (UTC)
thread_title:  Bias 

message: Crear voz para hablar 152.206.232.240 (talk) 09:11, 26 December 2023 (UTC)
replies: text: Could you make any comment(s) here in English? Thanks. Martinevans123 (talk) 12:29, 26 December 2023 (UTC)
thread_title:  Crear voz para hablar