…to false – SPE starts even if initialization of some technology instance fails during SPE initialization server.require_all_configured_technologies = true This setting controls whether all technologies and instances (configured in technologies.xml) must be successfully started during SPE initialization. Starting from SPE 3.51, default value is true, which ensures that SPE initializes exactly as configured; any failed technology instance initialization causes the…
Search: setting.ini
19 results
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…
…is not easy to decode which thread caused which issue. # Set multi-thread technology initialization # When enabled server use multiple thread to speed up initialization of technologies server.technology_multithread_initialization = false # Number of threads for initialization of technologies # Use for automatic detection server.technology_multithread_initialization.n_threads = Authentication This section is important for developers. If sessions are switched on and multiple…
…undesired for running SPE as service, i.e. changing the logging setting might be wise) Changed: Number of workers and RTP input streams limit are set automatically by default Changed: Require initialization of all configured technologies by default Removed: Dropped support for Windows 7 / Windows Server 2008 R2 and older Removed: Removed 4th generation of STT/KWS model for PL_PL Speech…
…│ ├── 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…
…initialization of SPE engine takes too long. Phonexia Browser software treats it as initialization failure and kills the server. You can fix this by doing the following: Increase timeout in Settings > Speech Engine tab > First connection timeout Use fewer instances of technologies, thus letting the Speech Engine to start faster Use smaller models of technologies in FAQ Phonexia…
…(7 cores × 4 streams per core) i.e. the realtime workers setting should be server.n_realtime_workers = 28. The number of initialized STT_STREAM technology instances (configured via phxadmin –configure-tech) should be also set to 28. There is no point to initialize more than that since there won’t be more workers available, i.e. no more than 28 simultaneously running tasks anyway. NOTE:…
…or phxadmin2. The resulting configuration is then stored in technologies.xml configuration file, placed in SPE settings directory. SPE reads this configuration file during startup and initializes the technologies instances according to the information in the file. The file has very simple structure and can be also created or modified using any plaintext edtor, or programmatically. Example The below example shows…
…localhost: giving up and kill the localhost. A: This error may happen if the initialization of SPE engine takes too long. Phonexia Browser software treats it as initialization failure and kills the server. You can fix this by doing the following: Increase timeout in Settings > Speech Engine tab > First connection timeout Use fewer instances of technologies, thus letting…
…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…
…PhxBrowser (on Linux) You should see following the information window. Click OK to start the configuration. (You can later come back to alter the configuration by going to the Settings -> Speech Engine tab) In the Settings dialog, on the Speech Engine tab, Enable all the technologies and hit Apply. Make sure to hit Apply to apply the changes and…
…8 physical cores are used, benchmark test starts to initiate more SID4 processes with a hope that Hyper-Threading may help. This hypothesis unfortunately can’t be confirmed. See Figure 2 which clearly shows that initiating more SID4 processes than the number of available physical cores simply doesn’t provide better performance than reserved physical core count is enabled in virtual machine. With…
…name User configuration file name stt_cs_cz_5_online.bs stt_cs_cz_5_online.bs.usr kws_nl_nl_5.bs kws_nl_nl_5.bs.usr phnrec_pashto.bs phnrec_pashto.bs.usr vpextract4_xl4.bs vpextract4_xl4.bs.usr During technology initialization (e.g. during Speech Engine startup), the initialization routine checks for existence of such user config file. If found, it’s automatically loaded after loading the main configuration file and the settings from user config is automatically applied over the setings from main configuration file. Usage…
…(MySQL) database is the way to go. When SPE is configured to use SQLite database, the database is created and initialized automatically by running phxadmin or phxspe. SQLite database is typically created during first-time SPE setup, when configuring technologies using phxadmin – it’s created silently behind the scenes, using values from phxspe.properties[1] configuration file (location, file name) and default SPE…
…happen if the initialization of SPE engine takes too long. Phonexia Browser software treats it as initialization failure and kills the server. You can fix this by doing the following: Increase timeout in Settings > Speech Engine tab > First connection timeout Use fewer instances of technologies, thus letting the Speech Engine to start faster Use smaller models of technologies…