Frequently Asked Questions about the Speechly SLU platform and API.
The SLU rules define the SLU model. The model is configured through sample utterances that are annotated using our custom syntax.
An utterance is something that the end-user says. It can consist of one or more segments. See SLU Examples.
It depends fully on the complexity of the model. If your model is only trained to turn the lights on and off, probably 50 lines of utterances is already a pretty good amount. For any more complex application, the number of sample utterances should rather be in thousands.
An application ID is needed to build an access token for the Speechly API. You can find your application ID in the Speechly Dashboard. The application ID should not be shared publicly, because it allows others to access your model. If you fear your application ID has leaked, you can either delete the application or ask us to revoke access to it.
You can test your model in the Speechly Playground, and share access to it in our Dashboard.
It depends heavily on the number of SLU rules. It shouldn’t take more than 5 minutes with most setups, but if you have thousands of lines of rules, it can take longer. You will get a notification once the training is completed.
You can do this easily in the Playground window by clicking the Share button located on the top right corner. When you share the model, you are asked to set the visibility of your app to public and describe the app’s purpose so that the users know what it’s intended to be used for.
The Speechly API can be called from whatever device or platform. To do this, please review the API Reference to see how to call the API and receive responses. We have also created ready-made libraries / SDKs that help you connect clients on the most popular platforms to the API. You can find documentation for client libraries here.
We will launch our more advanced analytics features shortly, but in the meanwhile, you can test your model in the Speechly Playground.
You can delete all user data from the Admin Dashboard. If you want a verification that all data is deleted, you can contact firstname.lastname@example.org
You can find your API token under Project Settings. Remember that you need to save the token as there’s no way to see it after you’ve created it.
The easiest way to start developing on Speechly is our Quick Start tutorial or the Speechly Web Client library. You can also revisit our simple NodeJS client in GitHub. We offer client libraries for iOS and Android too. Contact us to get access to those libraries.
You can either use our API reference or contact us.
The device ID is a unique identifier for the end-user device. It is used in our API to differentiate between the different devices that use the model. The application ID is used to adapt the speech recognition to the particular acoustic properties of the microphone on the device, the speaker, and the usage context of the application. Keeping this ID persistent and distinct for each user/device will significantly improve the accuracy of the voice user experience.
iOS doesn’t allow asking for microphone permissions on the page load, but rather, after user interaction. While some browsers might support other patterns, this is the best practice on all browsers, because the user should explicitly initiate the action that requires a microphone. If the permissions are asked on the page load, the user might not understand why it is needed, and may simply deny access.
If you are experiencing bad speech recognition results on browser clients (React and browser) it’s probably due to corrupted audio. As Speechly is optimized for low latency and real-time audio, the audio can become corrupted if the main thread is blocked for too long times.
Make sure your application’s main thread is not blocked by moving all resource heavy computation to other threads by using Web Workers.
The Speechly SLU model is based on machine learning. If your intents and entities are not recognized correctly, we recommend you to add more training rules (i.e., example utterances) to the configuration that contain those intents and entities. Then try again.
Please send us an email and we can help you forward.
Once you start the Playground, you’ll have to click on Tap to start and give permissions for your browser to access the microphone. Here’s a short clip that shows the process:
Tap to start
If you have denied access to the microphone and don’t get the dialog for microphone permissions, see these browser-specific instructions:
Last updated by ottomatias on November 24, 2020 at 13:38 +0200
Found an error on our documentation? Please file an issue or make a pull request