Search Results for: spe configuration

Results 1 - 10 of 28 Page 1 of 3
Results per-page: 10 | 20 | 50 | 100

What is a user configuration file and how to use it

Relevance: 100%      Posted on: 2020-03-28

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…

SPE configuration

Relevance: 100%      Posted on: 2018-02-02

Basic explanation of configuration directives for SPE with hints & tips. Overview of phxspe.properties for beginners.

Keyword Spotting results explained

Relevance: 9%      Posted on: 2019-06-12

This article aims on giving more details about Keyword Spotting outputs and hints on how to tailor Keyword Spotting to suit best your needs. Scoring Keyword Spotting works by calculating likelihoods that at a given spot occurs a keyword or just any other speech, and comparing those two likelihoods. The following scheme shows Background model for anything before the keyword (1), the Keyword model (2) and a Background model of any speech parallel with the keyword model (3). Models 2 and 3 produce two likelihoods – Lkw and Lbg (any speech = background). Raw score is calculated as log likelihood…

Phonexia Speech Engine

Relevance: 9%      Posted on: 2017-05-18

About Phonexia Speech Engine v3 (SPE3) is a main executive part of the Phonexia Speech Platform. It is a server application with REST API interface through which you can access all available speech technologies. Both, Linux 64bit and Windows 64bit operating systems are supported. Phonexia Speech Engine (SPE3) is adjustable server component which houses all speech technologies. SPE3 provides RESTfull application programming interface to access various technologies. Aside from technologies themselves the SPE has implemented other various functionality supporting work with speech technologies, recordings and streams, and others. Features Main purpose of SPE is to work as processing unit for…

Browser3 – Releases and Changelogs

Relevance: 9%      Posted on: 2020-07-08

Phonexia Browser v3 (Browser3) is developed as client on top of Phonexia Speech Engine v3. Phonexia Browser is a successor of Phonexia Speech Intelligence Resolver v1 (SIR1). This page lists changes in Browser releases. Releases Changelogs Phonexia Browser v3.31.1, BSAPI 3.31.0 - Jul 08 2020 Non-public Feature Preview release New: Browser now requires CentOS 7 or other Linux based OS with glibc >= 2.17 Version 3.31.0 was skipped Phonexia Browser v3.30.8, BSAPI 3.30.8 - Jun 29 2020 Public release Fixed: SID Evaluator - folder selection dialog does not allow to select existing folder Fixed: SID Evaluator - button "Display chart" can…

Workflow – Releases and Changelogs

Relevance: 9%      Posted on: 2019-10-07

Phonexia Workflow is a set of tools complementing Phonexia Speech Engine (SPE), which allow users to chain speech technologies into scenarios and process audio recordings automatically using these scenarios. This page lists changes in Workflow releases. Changelogs == Phonexia Workflow v1 == Phonexia Workflow 1.4.1 (10/07/2019) - SPE 3.16 - 3.17 Support for IPv4 only (since SPE does not support IPv6) Configurable application webhook address in both Workflow Runner and Data Discovery Tool This address is auto-detected when no value is supplied - default In some cases like network specific configuration it might be necessary to configure it manually Rapid…

Speech Intelligence Resolver v1

Relevance: 9%      Posted on: 2017-05-18

About Phonexia Speech Intelligence Resolver v1 (SIR1) combines the power of speech technologies within a single application. The application automatically performs visualization of the record as well as filtering the speech metadata uncovered from your records effectively. Speech technologies implemented: Phonexia Speaker Identification (SID2) Phonexia Language Identification (LID2) Phonexia Gender identification (GID) Phonexia Voice Activity Detection (VAD) Phonexia Speaker Diarization (DIAR) Phonexia Keyword Spotting (KWS) Phonexia Speech Quality Estimator (SQE) Phonexia Speech Transcription (STT) SIR is a client application cooperating with REST servers. It can be used as a standalone application due to the integrated local REST server. It was…

SPE3 – Administration and Backup

Relevance: 9%      Posted on: 2018-04-15

Each Partner has its own administration and back up policy. Here, we highlight the most important SPE3 components to be administrated and backed up. Administration It is strongly recommended to describe your own administration approach with the following components SPE users (accounts) - Partner should maintain list of SPE users (accounts). There should be only few persons with “admin” role. All other should be with “user” role (do not see content of other “user”) and/or “vbs” role (dis/enables using of VoiceBiometry plugin) the SPE database and/or VBSplugin database administration – where the (temporary) results are stored user.home - where the…

How to configure Speech Engine workers

Relevance: 9%      Posted on: 2020-03-28

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. The default workers configuration in settings/phxspe.properties is as shown below – 8 workers for files processing and 8 workers for realtime streams processing. These numbers mean the maximum number of simultaneously running tasks. # Multithread settings server.n_workers = 8 server.n_realtime_workers = 8 Requests for additional file processing tasks are put in a queue and processed according their order and priorities. Requests for…