search

Azure-Samples / Cognitive-Speech-STT-ServiceLibrary

Service SDK - C# Samples, documentation for service to service speech to text
22 stars 26 forks source link

Feature request: UWP support #16

Open ArchieCoder opened 6 years ago

ArchieCoder commented 6 years ago

Hello,

Sorry, if it is not a real issue, but it would be great to see some UWP love with Cognitive Services. I have seen the UWP feedback back in 2017 in UserVoice https://cognitive.uservoice.com/forums/430321-bing-speech-api/suggestions/18440209-support-for-windows-10-uwp-in-bing-speech and it was marked Under Consideration. I believe UWP is something important to support.

Thank you

zhouwangzw commented 6 years ago

We have just published new version of speech SDK with more features. We are currently working on UWP support for the new SDK. Please stay tuned.

ArchieCoder commented 6 years ago

Glad to hear about UWP support.

gMehlmann commented 6 years ago

Hi, also glad to hear about the new API, however, I am slightly confused and have some questions: What are the main differences or improvements of the new SDK version except for simplification of the interface - is it the intergration of STT, TTS, custom speech and translation service under a single SDK? Since I wasn't able to get your SDK running under .Net 3.5, I was using the websocket protocol directly until now. Is it now possible to use your new SDK with the .NET 3.5 framework? Is the actual underlying endpoint STT web service, accessible through the websocket protocol, used by the SDK's the same or are they different? Thank you and best regards!

zhouwangzw commented 6 years ago

The new SDK requires .Net 4.6.1 for now, but we are going to provide .Net core support soon. Would it be helpful for you?

gMehlmann commented 6 years ago

I am unfortunately forced to use .Net 3.5 in the project that I am currently involved in. There I have to integrate STT, TTS, and NLU in an existing software. Nevertheless, supporting .Net Core in the furure would certainly be great! I dont't mind implementing the Azure services' websocket- or REST-based protocols myself - provided that I have access to the same features and functionalities as if I were using your SDK.

Best regards Gregor