Text Language Identifier
- 13 Feb 2025
- 1 Minute to read
- Contributors
- Print
- PDF
Text Language Identifier
- Updated on 13 Feb 2025
- 1 Minute to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Detects the language of provided text.
Parameters:
name | description | default |
|---|---|---|
| Address | Address of Text Language Identification service that will be used. | |
| IgnoreSslErrors | ignore any certificate errors if Text Language Identifier address contains https | false |
Inputs
Audio:
None.
Events:
| name | description | known nodes that generate this event |
|---|---|---|
Every Event that has Data.Text field. | i.e SR Milestone events. Translation events, Custom events etc. | SR Http, SR WebSocket, Translate |
Outputs
Audio:
One Channel Segmented Audio
Events:
| name | description |
|---|---|
| Language Change | Raised whenever a language change is detected. |
Remarks :
- This node produces events that can trigger changes on other nodes' behavior. eg. SR Http node changes the model accordingly when it receives a language change event.
Project Structure
A simple project utilizing Text Language Identifier can be built like:
This project accepts events from the client. Text Language Identifier is utilized to detect the incoming language, and change the TTS Http node's language accordingly.
Supported flow types: Stream, Batch
Was this article helpful?