@sam I think for a locally run language detection container the detection only works with websockets i.e the SDK.
This is mentioned in the FAQ section of the speech containers. Although language detection status and ready API's seem to support REST API calls.
You can test your local container by running antsu language detection client and check if your local endpoint is working. This command should work in this case.
docker run --rm -ti antsu/on-prem-client:latest ./speech-to-text-with-languagedetection-client ./audio/LanguageDetection_en-us.wav --host localhost --lport 5003 --windows
The error with speech to text recognition is because i am not running speech to text container and not passing
sport=5000 in the above command.
@sam As mentioned in the swagger document or demo page the detection endpoint is enabled for web socket only. So, I do not think this will work with direct REST API call via postman.
language detection client antsu is working fine locally but my worry is how to setup this on kubernetes will this client takes dynamic audio files from UI and do we have any other client to check language detection?
antsu client is 3rd party and can be used for verification purpose to test speech containers as mentioned in its documentation. If you are looking to use the speech container and query the endpoint then the recommendation is to use the SDK and point the endpoint to the local endpoint instead of cloud speech service. In this case:
For language detection as per the documentation turn off the following property.
The rest should be similar to using language identification feature from the SDK.
Sign in to comment