…of Phonexia Browser. Installation of new language or technology model can be done in the following steps: Unzip installation package with new models to a temporary directory. Each installation package will contain phxadmin (Linux) or phxadmin.exe (Windows) binary. When Phonexia Browser is stopped, move the new models from the bsapi directory to the bsapi directory in your SPE installation. In…
Search: installation%20guide
34 results
Some packages are distributed with only a limited set of speech technologies and languages or without speech technologies. First installation Our software is distributed as a ZIP file. Installation procedure is as simple as: unzip the archive paste additional KWS, STT… models paste the license.dat file to the root directory where you have BROWSER folder and run_browser(.exe) script run the…
…on which technologies are included in the particular SPE installation. For testing and first-time evaluation we usually include the full set of technologies, other installations may contain only limited subset. Location of bsapi directory can be modified using bsapi.path option in SPE configuration file. This might be useful in complex network infrastructure, for sharing technologies between multiple SPEs, and similar…
In this post, we break down the complexities of the initial installation process of Phonexia Speech Engine (SPE), as a standalone installation. This means the SPE has to be started separately from the Phonexia Browser GUI (unlike in the embedded SPE mode, where Browser starts SPE as its background subprocess). By the end of the guide, you will be able…
In this post, we break down the complexities of the initial installation process. By the end of the guide, you will be able to start processing your recordings with Phonexia Speech Technologies. 1. Download Evaluation package Download the Phonexia Evaluation package from https://partner.phonexia.com/kb/sp/speech-platform/evaluation-package/ Create a new directory and unzip the package into it in your desired location, for ex. C:/Phonexia/…
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…
…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…
…Different post offices may provide different (sets of) services – smaller offices may provide only small set of services, while big ones can have multiple floors with wide service portfolio. Different Speech Engine installations may provide different (sets of) technologies – smaller installations can have like only single technology configured, while big ones can have wide set of various technologies…
…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…
…SPE as embedded component and set inside the file this directive: server.enable_authentication_token = false In that case you can still use SPE with Basic HTTP authentication, as described in documentation, section “Basic authentication“ If you 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…
…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….
…installation and additional space for data storage. recommended – CPU: Intel® Core™ i7 or better, RAM: 8 GB, Required HDD space: 0.5 GB for software installation and additional space for data storage. Step #2 – First start Ensure you have obtained a license (license.dat). To obtain an evaluation license, contact your Phonexia sales manager, or ask at [email protected]). Unzip the…
…storage – user-specific data Since SPE comes with pre-configured user “admin”, the default SPE installation contains admin subdirectory inside home: home └── admin ├── storage └── data Storage The user’s storage directory is where SPE stores files and directories uploaded or created via REST API, i.e. every action made using the /audiofile or /directory endpoints is reflected here – e.g….
…files in [SPE]/doc in standard software package and installation. You can also find REST API reference (Speech Engine) documentation online. You might be interested in reading the following information in manual: REST API reference Structure of API queries Asynchronous request Task prioritization Authentication Audio requirements RTP/HTTP streams Error responses API Commands Usage examples API Requirements Installation guide And much more…
Partners and customers are encouraged to see the Browser3 software End User Manual available in [BROWSER]/ PhxBrowser_manual.pdf in a standard software package and installation. You might be interested in getting familiar with the following information in the manual: Typical Use Cases Technical Requirements Installation (the First Start) Update Using the Application – Features Using the Application – Typical Workflows…