Skip to content Skip to main navigation Skip to footer

What is User configuration file and how to use it

Advanced users with appropriate knowledge (gained e.g. by taking the Phonexia Academy Advanced Training) may want to finetune behavior of the technologies to adapt to the nature of their audio data.
Modifying original BSAPI configuration files directly can be dangerous – inappropriate changes may cause unpredicatble behavior and without having a backup of the unmodified file it’s difficult to restore working state.
User configuration files provide a way to override processing parameters without modifying original BSAPI configuration files.

WARNING: Inappropriate configuration changes may cause serious issues!
Make sure you really know what you are doing.

User configuration file is a plain text file with the same name as main configuration file, with additional extension .usr. For example:

Main configuration file name User configuration file name

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 example:

When using Czech STT on realtime streams, the results show that system outputs end of segment too often, i.e. longer pauses between words made by the speakers are misidentified as end of sentence, while in fact the speakers actually continue to speak. So it is desired to finetune the system to accept longer delay between words without ending a sentence.

So, following the How to configure STT realtime stream word detection parameters article, we create a text file along the original configuration file in <SPE directory>/bsapi/stt/settings directory and put the following lines in it (changing the forward extension parameter from default 750 to 1500):


Then after restarting SPE – and optionally checking in SPE log that user configuration file was really loaded (this information is available at the ‘trace’ logging level only) – the STT results should show end of segment less frequently.

Related Articles