Skip to content Skip to main navigation Skip to footer

Search: directory structure

14 results

Understand SPE directory structure

…hold (customized) technology models shared by all SPE users. Historically, customizations are registered for particular SPE user only (e.g. when registering LID language pack using phxadmin –add-language-pack). Putting the customized technology model in shared directory makes it available for all users. The shared directory should contain bsapi subdirectory with the same structure as the main directory in root of SPE…

Understand SPE configuration file

…For additional details about home directory, see Understand SPE home directory article. bsapi.path # Set path to bsapi directory # bsapi.path = ${application.dir}bsapi Path to a directory where data of individual Phonexia speech technologies are stored in per-technology subdirectories. Defaults to bsapi* subdirectory of SPE application directory. For multi-instance SPE deployments, this can be set to a shared location to…

Understand SPE database scripts

…… To allow updating from any DB version to any DB version, the update directory contains scripts which “describe” the changes in DB structure between two consecutive versions. E.g. script v1500-v1600.sql “describes” difference between DB version 1500 and 1600. Executing that script would update DB with version 1500 structure to a DB with version 1600 structure. The intended usage when…

STT: Language Model Customization tutorial

…model in Speech Engine using phxadmin 1) Placing the customized STT model in correct location In order to be recognized by Speech Engine, the customized STT model must be placed in a correct location. The best location in SPE 3.41 or newer is <SPE_directory>/shared/bsapi/stt (see Understand SPE directory structure article). In older versions it’s <SPE_directory>/bsapi/stt. The data and settings directories…

Understand SPE benchmark

…SPE by replacing the content of default directory with your own audio files creating a directory with name according the name-matching rule (see above) and putting audio files in corresponding language in the directory For example: directory named es would be matched for es_6 and es_es_5 models, but not the old spanish_american model directory named cs_cz_fin would be matched only…

Phonexia Speech Engine

…first steps with Speech Engine, after obtaining a license file from Phonexia and downloading the Speech Engine package using a link provided by Phonexia. https://www.youtube.com/watch?v=4qrB-GfFdWY In short, these are the steps as described in the tutorial: Unzip the package to a directory Copy license file into the same directory Run phxadmin –configure-tech in console to configure technologies Edit settings/phxspe.properties configuration…

Understand SPE configuration

…text-based, well commented and human readable. Read carefully these comments as there are some useful tips and tricks hidden inside. Let’s begin; pay attention to the comment about variables notation format mentioned in the configuration preamble: # This is the default properties file for Phonexia Speech Engine # # Variables: # ${application.dir} path to application directory # ${system.env.<NAME>} system environment…

Understand SPE database

…list of internal directory types rest_file_shadow list of information about files registered in SPE – path, creation and modification timestamps, owner (SPE user), directory rest_log SPE log data, see above rest_resource_type list of internal resource types – file, SID speaker model, SID speaker group, SID calibration set, SID audio source profile, KWS keyword list, LID language pack rest_resource_lock list of…

Speech Engine update

…performance and using it the right way. That knowledge can be gained by taking the Phonexia training, eventually by deep studying of the documentation and articles on this site. In short, the procedure is make a backup of your SPE directory first compare the content of your SPE directory and the content of the new version distribution ZIP, including content…

Understand SPE connectors for external TTS

…(taking longer time to synthesize). Connector naming, location, configuration TTS connectors should be placed in {SPE_installation_directory}/external/technologies/tts directory, each connector in a separate subdirectory. To enable a connector, include its subdirectory name to the external.technologies.tts_connectors setting in SPE configuration file. Connector executable file must be named connector (i.e. without file extension). Connector configuration – like TTS service address, access credentials, API…

Understand SPE technologies configuration file

…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…

Understand SPE metafiles

…can store whichever type of data would help your application. The files are physically stored in the SPE user’s “home”, in data subdirectory (see Understanding SPE home directory article for details). Maximum size of single metafile can be set using server.max_metadata_size setting in SPE cofiguration file. Example As an example, the picture below shows how Phonexia Browser uses SPE metafiles…

Licensing (technical details)

…locally installable licensing server, providing flexibility of the NET license, but not requiring online connection to Phonexia server. See below for more details about each license type. How to use license file The default and simplest way is to place the license file to the same directory as the product executable. The product will find the license file automatically during…

Releases and Changelogs (VIN)

…distribution allows 1:1 comparison Fixed: Various bug fixes Improved: Reworked dialog for population set management Changed: Population sets structure changed Removed: Speaker Identification models S2, L2, L3, XL3 are no longer supported Voice Inspector 3.2 Voice Inspector v3.2.2, BSAPI 3.15.0 (2018-06-05) Fixed possible application crashes on Windows Added phoneme type ‘affricate’ and fixed phoneme types: phoneme ‘C’ changed from ‘fricative’…