Search Results for: Audio Source Profile

Results 1 - 10 of 65 Page 1 of 7
Results per-page: 10 | 20 | 50 | 100

Speaker Identification: Results Enhancement

Relevance: 100%      Posted on: 2019-05-29

Speaker Identification (SID) Results Enhancement is a process that adjusts the score threshold for detecting/rejecting speakers by removing the effect of speech length and audio quality. This is achieved by use of Audio Source Profiles, that represent as closely as possible the source of the speech recording (device, acoustic channel, distance from microphone, language, gender, etc.). Although the out-of-the-box system is robust in such factors, several result enhancement procedures can provide even better results and stronger evidence. Audio Source Profile An Audio Source Profile is a representation of the speech source, e.g., device, acoustic channel, distance from microphone, language, gender,…

SPE configuration file explained

Relevance: 44%      Posted on: 2021-05-03

In this article we explain details of the Speech Engine configuration file, 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, a default configuration is created in the settings directory. The file is loaded during SPE startup, i.e. you need to restart SPE to apply any changes made in the file. If Speech Engine is used together with Phonexia Browser in so-called "embedded" mode (see details about "embedded SPE" mode in Browser…

Error 1007: Unsupported audio format

Relevance: 42%      Posted on: 2018-12-10

Phonexia Browser application may return error "1007: Unsupported audio format" during uploading audio file. Please consider if your audio files are in . But if you need use as input audio recordings in other formats, you can configure SPE for audio automated conversion. As prerequisite install external tool for audio conversion. Recommend is ffmpeg utility, powerful and well documented. Please find your distribution package at Then continue as described below: Using Phonexia Browser with embed SPE Open the Browser configuration dialog by click on button "Settings" located in tool ribbon. Select tab "Speech Engine" and configure SPE as described…

SPE3 – Releases and Changelogs

Relevance: 37%      Posted on: 2021-06-11

Speech Engine (SPE) is developed as RESTfull API on top of Phonexia BSAPI. SPE was formerly known as BSAPI-rest (up to v2.x) or as Phonexia Server (up to v3.2.x). Releases Changelogs Speech Engine 3.40.5, DB v1700, BSAPI 3.40.4 (2021-05-09) Public release Fixed: When trying to register webhook over existing webhook for any stream technology, SPE returns HTTP 400 (1069) error instead of HTTP 500 Fixed: Invalid SQL syntax when overwriting voiceprint in a database Speech Engine 3.35.7, DB v1601, BSAPI 3.35.5 (2021-05-09) Public release Fixed: Invalid SQL syntax when overwriting voiceprint in a database Speech Engine 3.40.4, DB v1700, BSAPI…

Supported audio formats

Relevance: 35%      Posted on: 2018-12-10

Supported audio format are: WAVE (*.wav) container including any of: unsigned 8-bit PCM (u8) unsigned 16-bit PCM (u16le) IEEE float 32-bit (f32le) A-law (alaw) µ-law (mulaw) ADPCM FLAC codec inside FLAC (*.flac) container OPUS codec inside OGG (*.opus) container   Other audio formats must be converted using external tools. SPE server can be configured to support automated conversion on background, see SPE configuration hints. Great tools for converting other than supported formats to supported are ffmpeg ( or SoX ( Both are multiplatform software tools for MS Windows, Linux and Apple OS X. Example of usage: ffmpeg ffmpeg -i <source_audio_file_name>…

Understanding SPE database

Relevance: 34%      Posted on: 2021-06-05

SPE database serves multiple purposes: stores SPE internal data stores various information about SPE entities created by SPE user audio files metadata speaker models and their voiceprints speaker groups and their voiceprints calibration sets keyword lists language packs audio source profiles stores cached processing results (optional, can be set in SPE configuration file) stores SPE log data (optional and MySQL only, can be set in SPE configuration file) To cache or not to cache? Well, that's a question... ;-) It depends on the particular use case AND on the design of your application, whether using the built-in results caching would be…

Open Source Acknowledgement

Relevance: 29%      Posted on: 2018-04-06

This page collect information about Open Source code and licenses. You might be interested to ask your Phonexia contact what part of the page is relevant to your project. Phonexia Voice Verify dependencies Name  Version  License  Django  2.1.11  BSD Jinja2  2.11.2  BSD-3-Clause  MarkupSafe  1.1.1  BSD-3-Clause  Pygments  2.6.1  BSD License beautifulsoup4  4.9.1  MIT  behave  1.2.6  BSD behave-django  1.4.0  MIT  certifi  2020.6.20  MPL-2.0  chardet  3.0.4  LGPL  coreapi  2.3.3  BSD coreschema  0.0.4  BSD  defusedxml  0.6.0  PSFL  django-allauth  0.39.1  MIT  django-constance  2.7.0  BSD  django-cors-headers  3.4.0  MIT License  django-environ  0.4.5  MIT  django-extra-fields  2.0.5  Apache-2.0  django-picklefield  3.0.1  MIT  django-rest-auth  0.9.3  MIT  djangorestframework  3.9.1  BSD  docker  4.2.2 …

LID adaptation

Relevance: 26%      Posted on: 2021-03-02

This article describes various ways of Language Identification adaptation. Basic terminology Languageprint (*.lp file) – numeric representation of the audio, extracted from audio file for language identification purpose of (similar to “voiceprint”, but representing the spoken language, not the speaking person) Languageprint archive (*.lpa file) – multiple languageprints combined into single archive Creation of languageprint archives is not supported by SPE, these are supported as input only.   Language model – digital characteristics of a specific language Language model can be trained from languageprints (*.lp), language prints archives (*.lpa), or from combination of both. LID language model should not be…