In this article we explain details of the Speech Engine configuration file phxspe.properties, located in settings subdirectory in SPE installation location. Settings in this configuration file affect the Speech Engine behavior and performance. The configuration file is usually created after SPE installation – on first use of phxadmin, default configuration file phxspe.properties is created in the settings directory. The file…
Search: sett
41 results
…in REST settings Phonexia Browser v3.1.0, BSAPI 3.5.0 – Feb 25 2016 Support for REST 3.1.x Removed clear results from context menu in test table Removed export results from context menu in test table Removed settings for gender score sharpness and gender balance Removed result database Technologies has configurable technology models New configuration tab in settings dialog for configuring REST…
…│ ├── l4 │ └── xl3 │ └── en_us_5 │ └── xl3 └── settings └── settings ├── lprints │ ├── l4 │ └── xl3 ├── models │ ├── l4 │ └── xl3 └── settings data data directory contains various SPE operational data – default SPE configuration file, example init.d script, example systemd service unit file, built-in benchmark audio files and…
Basic configuration SPE configuration by default is defined in the file {spe_root}/settings/phxspe.properties. This file is automatically created after running the phxadmin utility for the first time, usually used for initial configuration of the system. Otherwise it can be found in {spe_root}/data/phxspe.properties.template from which the actual configuration file may be populated and renamed manually. The format of the configuration file is…
…phxadmin2 –version output format (3.45.0, 6118, 2021-10-07) Changed: phxadmin2 technology show now uses colon to separate technology and model (consistent with “technology enable”) Removed: user setting for maximum number of pending requests (the setting was ignored anyway) Speech Engine 3.45 (Public release) Speech Engine 3.45.7, DB v1701, BSAPI 3.45.8 (2022-05-06) Fixed: Processing slowdown and high CPU usage on Windows platform…
…directory created languageprints get stored to /path/to/my/languageprints, each language to its own separate subdirectory we use the “L4” model, hence the _l4 configuration file suffix ./phxcmd lpextract -v -c /path/to/lid/settings/lpextract_l4.bs -d /path/to/my/audio/MyLanguage -e wav -D /path/to/my/languageprints/MyLanguage ./phxcmd lpextract -v -c /path/to/lid/settings/lpextract_l4.bs -d /other/path/to/audio/MyOtherLanguage -e wav -D /path/to/my/languageprints/MyOtherLanguage etc. for more languages… where: -v parameter tells the tool to provide verbose…
…now displayed by default and gets focused when SPE is started in the background by Browser (since 3.59.0) More detailed debug output is now configurable in Settings dialog and is enabled by default (since 3.59.0) This should help users with tracking down the causes of various issues. The Enable all and Disable all icons in technologies configuration section of Settings…
…are two differences against the XML example: the STT_STREAM technology is missing – Phonexia Browser does not support stream processing, i.e. does not allow configuration of stream technologies the config_file setting is also missing – Phonexia Browser does not support this special expert-level feature, i.e. does not store the setting { “technology_subsystem_settings”: { “technologies”: [ { “name”: “STT”, “models”: […
…current settings/phxspe.properties settings file and update your current settings file if needed (e.g. if new version introduces some new settings options, etc.) If you use MySQL database, manual update of DB may be needed (SQLite DB is updated automatically when needed): Run scripts in {SPE}/data/database/MySQL/update/ NOTE: it is necessary to go version by version. If your current schema is e.g….
Worker is a working thread performing the actual files- or realtime streams processing in Speech Engine. This article helps to understand the Speech Engine workers and provides information how to configure workers for optimal performance and server utilization. Starting from SPE 3.51, new defaults in settings/phxspe.properties make SPE to configure workers automatically according to local conditions (physical CPU cores, configured…
This part requires higher (and non-anonymous) access level.
How to solve this situation:
- Log in here if you are not logged in.
- Register here. It takes just a few clicks and it’s free.
…play with “pure” daemon installation, then phxspe.properties file should exist in ./settings subdirectory. File phxspe.properties is created by phxadmin utility or can be created from ./data/phxspe.properties.default template file. Copy template file to ./settings directory Rename it to phxspe.properties Check for server.enable_authentication_token directive and setup it as needed. Restart phxspe Basic installation steps are described in ./doc/INSTALL.html document. in FAQ Phonexia…
…would like to play with “pure” daemon installation, then phxspe.properties file should exist in ./settings subdirectory. File phxspe.properties is created by phxadmin utility or can be created from ./data/phxspe.properties.default template file. Copy template file to ./settings directory Rename it to phxspe.properties Check for server.enable_authentication_token directive and setup it as needed. Restart phxspe Basic installation steps are described in ./doc/INSTALL.html document….
This article explains details about SPE asynchronous requests processing queue, the processing task lifecycle and its handling states. When SPE receives an asynchronous API request, a task is created and put in a queue. Size of the queue is defined by server.n_task_limit setting in SPE configuration file, default value is 1000 tasks. Tasks in queue are then handled according to…
The server.technology_multithread_initialization setting in SPE configuration allows SPE to initialize instances of technologies during startup using multiple parallel threads. Default setting is OFF, i.e. instances of technologies are initialized using single thread, one-by-one. This allows easier tracking of eventual issues during SPE startup and better readability of technologies initialization log messages (only single initialization happens at a time). The downside…