Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

wrong websocket address #64

Open
manuliner opened this issue Jan 5, 2018 · 8 comments
Open

wrong websocket address #64

manuliner opened this issue Jan 5, 2018 · 8 comments

Comments

@manuliner
Copy link

manuliner commented Jan 5, 2018

to make this work i needed to change the websocket address in this line

return Storage.Local.GetOrAdd("Host", "wss://speech.platform.bing.com");

to

return Storage.Local.GetOrAdd("Host", "wss://{your Deployment ID}.api.cris.ai");

i also changed this in my gulped JS file under node_modules/microsoft-speech-browser-sdk/distrib/src/sdk/speech.browser/SpeechConnectionFactory.js

you should change this in your sample, as it is not working at the moment

@zhouwangzw
Copy link

The sample is for using Speech Recognition API(using general-purpose model without customization), so the endpoint "wss://speech.platform.bing.com" is correct.
If you want to use Custom Speech service with your own customized model, you need to use the endpoint with your own deployment.

Thanks,

@manuliner
Copy link
Author

manuliner commented Jan 8, 2018

hello @zhouwangzw,
Custom Speech Service DOCs tells me to use these samples.

Subsection OPUS
https://docs.microsoft.com/de-de/azure/cognitive-services/speech/api-reference-rest/websocketprotocol

@zhouwangzw
Copy link

zhouwangzw commented Jan 8, 2018

On the Custom Speech Service Doc, "Send requests by using the Speech Protocol" asks you to replace the endpoint in the sample with your own deployment endpoint:

Currently, the only official client implementation is for JavaScript. If you want to start with the sample provided there, make the following changes to the code and build the sample again:
In src\sdk\speech.browser\SpeechConnectionFactory.ts, replace the host name "wss://speech.platform.bing.com" with the host name shown on the details page of your deployment. Do not insert the full URI here but just the wss protocol scheme and the host name.

The OPUS section you mentioned is for the general-purpose speech recognition API (instead of custom speech API), so it uses the "wss://speech.platform.bing.com" endpoint.

@manuliner
Copy link
Author

manuliner commented Jan 8, 2018

maybe u can help me on my next issue:

my 15 seconds test file is working, but when i change to my 3 minutes testfile, cutsom speech service is not recognizing the whole file(stops after 15 sec). Any idea what i can change?

i tried recognitionmode dictation and conversation
implemention as in the sample

@zhouwangzw
Copy link

For custom speech issues, please contact the custom speech service team. We do not own their service.

@manuliner
Copy link
Author

how to contact?
all contact possiblities forward to this git repo

@solidcloudio
Copy link

Our services aren't available right now

We're working to restore all services as soon as possible. Please check back soon.

Ref A: E46EE7F8DE28480E89BA1F908D77D2DC Ref B: PHX01EDGE0217 Ref C: 2018-03-29T15:44:18Z

@mikebranstein
Copy link

See pull request #82 that addresses this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants