…4th generation models, typically marked with a number 1, 2, 3 or 4 in the model name. Other technology models (SID, LID, GID, DIAR, AGE, SQE, VAD, DENOISE) Tech. models supported (generation specified by number in “Tech. model name”). Technology Tech. model name Released End of support Maintenance SID4 XL5 2022-09 6th gen. SID 5th gen. SID XL4 2020-03…
Search: models
43 results
…generation STT models New: Added changelogs for STT models (located in bsapi/stt/data/models_<model> directory) Improved: Updated language models of 6th generation STT RU_RU_6 (version 6.1.0) RU_RU_A_6 (version 6.1.0) Fixed: *.bs.usr configuration files are ignored by phxadmin and phxadmin2 Fixed: ❗❗❗ Unable to open audio files with non-ASCII/Unicode characters in the name or path on Windows Speech Engine 3.58 (Public release) Speech…
…FA_IR4), leading to more precise search results in audio content. New Decoder and VAD Configuration in STT Technology Models Thanks to a new decoder and VAD components added to our STT, the transcription accuracy (WAcc) has improved on average by 2 percentage points (compared absolutely to our original 6th generation models). The update was applied to all technology models (languages)…
…you audio files using GET /technologies/languageid/extractlp endpoint Create new (yet empty) language model using POST /technologies/languageid/languagemodels/{name} endpoint Upload languageprint- or languageprint archive file to the language model using POST /technologies/languageid/languagemodels/{name}/file endpoint repeat this upload for all necessary files – e.g. when creating completely new language model from your own audio files, this would be hundreds or thousands of files (see…
…with data for XL3 and L4 models – STT with data for 5th generation English language and 6th generation Czech language gid stt lid ├── data ├── data ├── data │ ├── l4 │ ├── models_cs_cz_6 │ ├── l4 │ └── xl3 │ └── models_en_us_5 │ └── xl3 ├── example ├── example ├── example │ ├── l4 │ ├── cs_cz_6…
…by SPE users: rest_model_sid list of SID speaker models – name, owner (SPE user), modification timestamp rest_model_sid_sources list of files used as sources for SID speaker models creation rest_model_sid_metafiles list of files used as SID speaker models metafiles rest_group_sid list of SID speaker groups – name, owner (SPE user) rest_group_sid_models associations between SID speaker groups and speaker models rest_voiceprint SID…
…editor now distinguish KWS/Diar technology models (it is possible to open results for more models at once) [#4979] SID models status indication [#4979] User can prepare SID model/group by context menu [#4980] Show speech length for speaker models [#5041] Fixed processing a lot of files in SID evaluation cause application crash Phonexia Browser v3.8.2, BSAPI 3.12.0 – Jun 29 2017…
…Installation packages with new language models are custom created and provided to you by your assigned Phonexia contact. As the language models are version dependent, we need to know the exact version of the Speech Engine you have. Version of installation package must match the version of your SPE. How to check SPE version In the Phonexia Browser right click…
…As an example for English the following acoustic models can be trained: US English – to be used with US speakers British English – to be used with UK speakers Language models Language model consists of a list of words. This is limitation for a technology, as only the words from this list can go to the transcription. Together with…
…value is ‘${application.dir}shared’ server.shared.path = ${application.dir}shared Path to a directory intended to hold (customized) technology models shared by all SPE users. Defaults to shared subdirectory of SPE application directory and exists only in SPE 3.41 or newer. For additional details about shared models directory, see Understanding SPE directory structure article. NOTE: If you change the server.shared.path, you might also want…
General Lifecycle of Phonexia products is driven by Phonexia Product Support and Lifecycle Policy (valid from Q3/2019). Content of our support and software versioning approach is defined as well in this document. Specific versions of our products and languages are supported and maintained according to following tables. Phonexia Speech Engine Version Release Date End of Support Maintained Until Release type…
…SID4C (SID4 extractor and SID4 comparator) with both L4 and XL4 models, depending on actual availability of the technologies/models in that SPE installation. Due to the “…single character” pattern definition, the list won’t include SID4E_STREAM, SID4C_STREAM and SID4CALIB technologies. phxadmin2: example 3 ./phxadmin2 technology enable sid?_stream:*l?=3 sid4?_stream:*l?=1 enable 3 instances of technologies with names matching “sid followed by single character,…
…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 />…
…technology models configuration usually introduces new features or major fixes, which may change communication between server and client, or other changes which may affect customer processes can also include new technology models; with such update you can add only the new technology, without SPE installation Upgrade changes the first version number (e.g. x.y.z to x+1) and is a major change…
…0022 Data storage and multithread settings The home directory of SPE contains all user data including audio recordings and metadata files from speech processing (speaker models, description etc.). This is another good example of using environment variables if your topology design requires multiple instances of SPE processing the same payload. This is great for sharing raw data between multiple physical…