I highly recommend the Speech @ Microsoft blog for more up-to-date information on Microsoft’s speech technologies.

Also, Rob’s Rhapsody is a good blog maintained by Microsoft’s Rob Chambers.

You can to email the Speech product team at Microsoft as well: listen@microsoft.com for speech recognition questions, and speak@microsoft.com for speech synthesis and Text-to-Speech (TTS) queries.

The best place for developers to get the Speech SDK samples and documentation is the Windows SDK.  Download all or just part of it.  You can email your SAPI related questions to sapitech@microsoft.com.

If you’re interested in contacting me personally, you can email me at chuckop@gmail.com or chuckop@live.com.  Search the internet for Charles Oppermann OR ChuckOp and you’ll generally find me.  I hope to hear from you!

Speech technology is incredibly enabling and is now mainstream and accepted by users.  The technology is easily available to developers, so go forth and add the power of the human voice to your application!

Thank you,
Charles Oppermann
Program Manager, Microsoft Corporation
Microsoft Bob, Windows 95, Internet Explorer 3.0, Active Accessibility, Internet Explorer 4.0/4.01, Windows 98, Windows 2000, Windows 2000 Active Directory Programming (author), Windows Vista, Office Communication Server 2007, Windows Speech Recognition Profile Tool, Windows 7

“A computer on every desk and in everyone home…
…usable by everyone!”

One of the better forums for speech recognition is run by Professor Itamar Even-Zohar of Tel Aviv University, where he teaches Culture Research.  Itamar has been a long time user of speech recognition and vocal in feedback regarding Windows Speech Recognition.  His web site on speech recognition contains useful information on WSR and speech recognition included in Office XP and Office 2003.  In particular, his ms-speech forum is invaluable.

Recently when David Pogue of the New York Times wrote about the newest version of NaturallySpeaking, Itamar was quick to write David and set him straight on a few matters, including a plug about Windows Speech Recognition Macros!

David wrote of Itamar, "Clearly, I’ve unearthed the world’s leading authority on speech-recognition foreign-language versions,"

If you read the links I'm providing, you'll see that Professor Even-Zohar is not enamored of all that we do.  He's critical of several aspects of WSR and while he "gets it" regarding WSR Macros, he's quick to point out flaws and features.

It's users like this that we need more of; people who are highly experienced and unafraid to share their opinions.  The information provided is valuable to me and the rest of the product teams.  On the flip side, we have to be careful regarding users expectations.  Bending our ear doesn't mean you'll get whatever feature you asked for, and within a particular timeframe.

Oftentimes we'll have more features than time or people available.  We have to be very choosy about where to spend our resources.  Even things that are a number #1 priority sometimes have to take a backseat to a lesser feature because it was one that we could do in the time or resources available.

Having the feedback from experienced users though help us make the most of the resources we have.  We can prioritize better and have confidence that what we're doing will have the greatest impact.

To everyone who writes us at listen, speak and sapitech - we thank you and keep the feedback rolling!

We're always looking for feedback on how to improve Windows Speech Recognition.  If you are a frequent user, please take a moment to respond with your experiences.  You can email us, or leave a comment below.

1. What mode of microphone control do you use most often?
   1. I use “start listening” and “stop listening”
   2. I press CTRL+WIN to change listening modes
   3. I use my headset/microphone mute button
2. If you use “start listening” (or have in the past), how reliable is it for your environment?
   1. Very reliable: WSR only listens when I say “start listening”
   2. Somewhat reliable: WSR occasionally wakes up even if I did not say, “start listening”, but it’s not a problem for me.
   3. Not reliable: I cannot use the Sleep mode because “start listening” is recognized too frequently.
3. Were you aware that pressing CTRL+WIN was a possible means of controlling the listening state?
   1. No
   2. Yes
4. When you add words to the speech dictionary, do you also record a pronunciation?
   1. Yes, always
   2. Sometimes
   3. Only if after adding the word WSR still does not recognize it correctly
   4. What’s the speech dictionary?
5. Do you find that while correcting misrecognized phrases, that WSR still misrecognizes the phrase, even after one or more corrections?
   1. Always
   2. Frequently
   3. Enough that I notice
   4. Occasionally
   5. Rarely
6. What is your favorite feature or aspect of Windows Speech Recognition?
   
7. Conversely, what is the one thing you’d like to change?

Thanks for taking the time to share your feedback!  We do value your feedback and use it to help guide future development.

using System;
using System.Collections.Generic;
using System.Speech;
using System.Speech.Synthesis;
using System.Speech.AudioFormat;

namespace SelectVoice
{
  class SelectVoice
  {
    static void Main(string[] args)
    {
      Console.WriteLine("SelectVoice Example");
      SpeechSynthesizer ttsSynth = new SpeechSynthesizer();

      Console.WriteLine("Listing installed speech synthesizer voices...");
      foreach (InstalledVoice ttsVoice in ttsSynth.GetInstalledVoices())
      {
        Console.WriteLine("Name:\t{0}", ttsVoice.VoiceInfo.Name);
        Console.WriteLine("Desc:\t{0}", ttsVoice.VoiceInfo.Description);
        Console.WriteLine("Id:\t{0}", ttsVoice.VoiceInfo.Id);
        Console.WriteLine("Gender:\t{0}", ttsVoice.VoiceInfo.Gender);
        Console.WriteLine("Age:\t{0}", ttsVoice.VoiceInfo.Age);

        Console.WriteLine("Supported Audio Formats:");
        foreach (SpeechAudioFormatInfo audioFormat in ttsVoice.VoiceInfo.SupportedAudioFormats)
        {
          Console.WriteLine("\tEncodingFormat:\t{0}", audioFormat.EncodingFormat);
          Console.WriteLine("\tChannelCount:\t{0}", audioFormat.ChannelCount);
          Console.WriteLine("\tBits/sec:\t{0}", audioFormat.BitsPerSample);
          Console.WriteLine("\tAvg Bytes/sec:\t{0}", audioFormat.AverageBytesPerSecond);
          Console.WriteLine("\tSamples/sec:\t{0}", audioFormat.SamplesPerSecond);
          Console.WriteLine("\tBlockAlign:\t{0}", audioFormat.BlockAlign);
        }

        Console.WriteLine("Additional Information:");
        foreach(KeyValuePair<string, string> kvp in ttsVoice.VoiceInfo.AdditionalInfo)
          Console.WriteLine("\t{0}:  {1}", kvp.Key, kvp.Value);
        Console.WriteLine();
      }
    Console.WriteLine("Finished listing installed voices.");

    ttsSynth.SelectVoice("Microsoft Anna");
    ttsSynth.Speak("Greetings, my name is " + ttsSynth.Voice.Name);
    }
  }
}

Having been part of the Windows 95 team, and then shipped components in Windows 98, Windows 2000 and Windows Vista, I'm used to people complaining that the newest version of Windows is not as good at the previous version.

There are a lot of misconceptions about Windows Vista - that's it's slow, that feature X is not as good as it was in Windows XP, or any number of possible excuses.  Many of the people doing the complaining haven't used Vista, or installed it on hardware that didn't meet have the recommended system requirements.

If you have Windows XP and are concerned that Windows Vista won't work with your hardware of existing applications, check out the very useful "Windows Vista Upgrade Advisor" tool.

What's your favorite Windows Vista feature?  Of course, I'm partial to Speech Recognition and the Microsoft Anna TTS voice, but there are many new features, tell me yours.

Update:  The New York Times collects some reaction.

She recently blogged about some odd requests she's gotten for old software.  One of them was "where can I get the Microsoft Bob SDK?".  I've been feeling nostalgic about Bob recently, as I visited Dan Rose's exhibit on Microsoft Bob, part of Dan's 20th Century Abandonware site.

My first job at Microsoft in 1994 was working on Microsoft Bob which was code-named Utopia.  My contribution to the product was minor, but in my opinion, it never deserved the trashing it got by the industry and pundits at the time and ever since.  Someday I'll write more regarding what went right and what went wrong with Microsoft Bob.

In the meantime, and for a stroll down memory lane, check out Dan's website.

HRESULT SetRuleState(
   LPCWSTR       *pszName,
   void          *pReserved,
   SPRULESTATE   NewState
);

This instead it should be:

HRESULT SetRuleState(
   LPCWSTR       pszName,
   void          *pReserved,
   SPRULESTATE   NewState
);

Note that instead of "*pszName" the parameter should be "pszName".

We'll update MSDN and the Windows SDK documentation, but in the meantime we wanted to publish this errata.

• Updated: SAPI 5.3 documentation
• Updated: System.Speech documentation
• Updated: Sample source code
• 8 C++ projects
• 3 C# projects
• 2 sample engines - TTS and SR
• New: Grammar Compiler (GC.EXE) tool now part of the tool binaries included in the SDK

The Windows SDK completely replaces the older SAPI 5.1 SDK and supports development on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.

Customers can download this SDK as a DVD image (1,330MB ISO file) from this location:
https://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF

Or go through a guided setup process where only the components they need are downloaded.  Speech is part of the base install.
https://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC

 I'm particularly interested in your feedback regarding the Windows SDK as a whole and in particular getting speech information.

However, some applications assume the mouse activitated the functionality and positions the context menu wherever the mouse is.  Since I'm using speech or typing and haven't touched the mouse in a while, the menu appears nowhere near where the cursor or selection is.

A more common variant of this is when the menu appears in the upper-left corner of the edit box when activated by keyboard. 

The article titled Using Menus on MSDN contains sample code that always uses lParam for the X/Y location to display the menu.  The documentation on WM_CONTEXTMENU is clear:

If the context menu is generated from the keyboard—for example, if the user types SHIFT+F10—then the x- and y-coordinates are -1 and the application should display the context menu at the location of the current selection rather than at (xPos, yPos).

That advice is ignored in the Using Menus topic, so I used the "Add Community Content" to add a note, and I'll file a bug on this so that it can be fixed in the future.

Using MSDN's Community Content feature, I added the following to the Using Menus article:

Remember when processing the WM_CONTEXTMENU message, that the X/Y coordinates might be -1/-1 which indicates that the keyboard generated the menu, thus, the menu should be shown at the cursor location or at the location of the selection - NOT at -1/-1 or the mouse pointer location.

The samples currently in this article do not account for this and will attempt to display the menu at -1/-1, which is confusing to the keyboard user.  Pressing the Application Key on Windows keyboards (to the right of the spacebar) generates a VK_APPS virtual scan code which by default generates a WM_CONTEXTMENU.  You can also get this if the user presses SHIFT+F10.

Never handle SHIFT+F10 or VK_APPS to popup a context menu, rely on the WM_CONTEXTMENU message and if the location given is -1/-1, revert to using the text cursor and/or selection information to place the menu.

I'm constantly amazed that people think that putting shortcuts to programs on the desktop makes accessing that program "easier".

For the second time in about a week, I've encountered people asking how to put shortcuts to programs on the desktop. 

The desktop is ill-suited for this. To start with, items located on it are often not visible because other windows are placed in front of the desktop.  Depending on the current window layout, you might have to make one or more mouse or keyboard operations to select the desktop item you want. 

To make matters worse, the location of the items will shift positions as screen resolutions change (because of games, connecting monitors, etc.) and items are added.

While oftentimes commercial software will litter the desktop with shortcuts, the purpose is to increase visibility, not ease of use.

Why not use the Start Menu? If WordPad is a program you use often, just "Pin" it to the Start Menu and it'll always be there, available in less keystrokes than trying to use it off the desktop.

If you really want quick access, pin the item to the Start Menu and then modify the item's properties to have a shortcut key assigned. Only items in the Start Menu can have shortcut keys assigned to them.

Update 9/4/2007: My bad, shortcut keys can be assigned to shortcut file that are located on the desktop.  My initial test of this failed, and since I knew that only certain locations respect shortcut keys, I figured that the desktop was not one of them.  I'll try to find a definitive list, but it appears that any of the Start Menu locations and the Desktop are valid places for a shortcut file to have a shortcut key assigned.  Interestingly, shortcut keys for items in the Quick Launch toolbar location are not respected.