Differences of 3 libraries in voice programming ?
-
I searched online for 3 speech pronunciation libraries: "System.Speech.dll, Microsoft.Speech.dll and Interop.SpeechLib.dll". I want to know their time and origin, in which 3 libraries easy to use to write code ? Which library supports many countries' voices ? Which library is the most popular with programmers ? In the future, which 3 of the libraries will drop out ? et... ?
-
I searched online for 3 speech pronunciation libraries: "System.Speech.dll, Microsoft.Speech.dll and Interop.SpeechLib.dll". I want to know their time and origin, in which 3 libraries easy to use to write code ? Which library supports many countries' voices ? Which library is the most popular with programmers ? In the future, which 3 of the libraries will drop out ? et... ?
-
Look at the documentation for each library to decide which one will be the best fit for your application.
"But I want you to do all that research for me! It sounds like a lot of work and I'm busy with FaceBook today!"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
"But I want you to do all that research for me! It sounds like a lot of work and I'm busy with FaceBook today!"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
"But I want you to do all that research for me! It sounds like a lot of work and I'm busy with FaceBook today!"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
In the future, which 3 of the libraries will drop out ?
But we have a gift of foresight which he doesn't...
"Five fruits and vegetables a day? What a joke! Personally, after the third watermelon, I'm full."
I found a speech pronunciation example that uses these libraries, I haven't found the source materials and the documentation for them, if someone who has programmed on this issue will answer it quickly, every time I don't know, thanks to you answers, I would say google search so what was the forum set up for ?
-
Look at the documentation for each library to decide which one will be the best fit for your application.
Well, if you don't know, you dont have to answer either! ;P
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Well, if you don't know, you dont have to answer either! ;P
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
I found a speech pronunciation example that uses these libraries, I haven't found the source materials and the documentation for them, if someone who has programmed on this issue will answer it quickly, every time I don't know, thanks to you answers, I would say google search so what was the forum set up for ?
Member 2458467 wrote:
so what was the forum set up for ?
It was set up to answer specific technical questions; see How to get an answer to your question - C# Discussion Boards[^]. You are asking us to tell you which library of three is the best, which supports multiple languages, which may disappear in the future, etc. Apply the same question to any consumer product you care to think of and see why it is impossible to provide a definitive answer.
-
:laugh: :laugh: :rolleyes: :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
:laugh: :laugh: :rolleyes: :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
I have found out. SpeechLib is interop com version of Microsoft Speech The short answer is that Microsoft.Speech.Recognition uses the Server version of SAPI, while System.Speech.Recognition uses the Desktop version of SAPI. The APIs are mostly the same, but the underlying engines are different. Typically, the Server engine is designed to accept telephone-quality audio for command & control applications; the Desktop engine is designed to accept higher-quality audio for both command & control and dictation applications.You can use System.Speech.Recognition on a server OS, but it's not designed to scale nearly as well as Microsoft.Speech.Recognition.The differences are that the Server engine won't need training, and will work with lower-quality audio, but will have a lower recognition quality than the Desktop engine
