Search: Language models

…of XL4 model <?xml version=”1.0″?> <technology_subsystem_settings> <technologies> <item> <name>STT</name> <models> <item> <name>SK_SK_5</name> <n_instances>8</n_instances> <config_file /> </item> </models> </item> <item> <name>STT_STREAM</name> <models> <item> <name>CS_CZ_6</name> <n_instances>2</n_instances> <config_file /> </item> </models> </item> <item> <name>SID4E</name> <models> <item> <name>L4</name> <n_instances>2</n_instances> <config_file /> </item> <item> <name>XL4</name> <n_instances>3</n_instances> <config_file /> </item> </models> </item> <item> <name>SID4C</name> <models> <item> <name>L4</name> <n_instances>2</n_instances> <config_file /> </item> <item> <name>XL4</name> <n_instances>3</n_instances> <config_file />…

…if such directory is found, audio files from that directory are used (expecting that the audio contains speech in that corresponding language). If not found, it falls back to default directory. The reason for language-specific data is that processing audio in different language than the language for which the model was trained negatively affects the processing speed (basically, the processing…

…not visible by SPE and by the account. Similar trickery can be done with the data directory, allowing to share LID language models and language packs, or SID speaker models, etc. between accounts. User accounts management SPE user accounts can be managed using REST API (see Administration section of the API documentation), or using command line administration utilities phxadmin or…

…separate files. Another example would be the information about content of created LID language pack – if LID language pack is successfully created, SPE creates a metafile named report, which contains detailed information about the source files used for the language pack creation. See the LID language pack creation REST endpoint documentation for more details about the report metafile content….