Voice Command Managed Wrapper

  • Thread starter Thread starter Joel
  • Start date Start date
The problem has always been a licensing issue rather than a technical one.
There have been no further announcements of an API for Voice Command. It's
been technically possible to automate Voice Command since it was first
released (I wrote a proof of concept and showed it to some Microsoft people)
but the speech engine is licensed by Microsoft from a third-party and the
license only allows it to be used for the Voice Command functionality, not
to provide any programmatic access to the engine.

Peter
 
Thanks for the explanation. I was really beginning to think that MSFT forgot
about it. I can see how opening third party access could cut the technology
owner out of potential income.

Joel
 
Back
Top