Search Results for: which file formats are supported

Results 1 - 10 of 89 Page 1 of 9
Results per-page: 10 | 20 | 50 | 100

Supported audio formats

Relevance: 100%      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 (http://www.ffmpeg.org) or SoX (http://sox.sourceforge.net/). Both are multiplatform software tools for MS Windows, Linux and Apple OS X. Example of usage: ffmpeg ffmpeg -i <source_audio_file_name>…

SPE configuration

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

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

Q: How can I tell in which format the .wav file is?

Relevance: 70%      Posted on: 2017-06-27

A: From the utilities in the package, you can find it in "ffprobe <file_name>", it will write out the info about the file. *Utility "ffprobe" is not included in our package(s). It is part of ffmpeg (https://ffmpeg.org/ffprobe.html) and it is neccessary to install it separately.

SPE3 – Releases and Changelogs

Relevance: 54%      Posted on: 2020-10-14

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). This page lists changes in SPE releases. Releases Changelogs Speech Engine 3.35.1 (10/13/2020) - DB v1600, BSAPI 3.35.1 Public release Fixed: Missing input stream task name in log messages Fixed: Missing arguments in "word not found" error messages (when using preferred phrases) Speech Engine 3.35.0 (10/01/2020) - DB v1600, BSAPI 3.35.0 Public release New: LID model L4 was promoted to production (LID BETA_L4 renamed to LID L4) New: Added new language tag…

What is a user configuration file and how to use it

Relevance: 46%      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…

Licensing (technical details)

Relevance: 44%      Posted on: 2018-03-02

This document describes all licensing types for Phonexia product licensing available to our partners and customers. Each partner/customer can choose the licensing variant which best fits the current project or infrastructure. The document does not describe business conditions of Phonexia licensing. What is the License? The License is a formal agreement regarding “The Product Usage Rights” between Phonexia s.r.o. and a user of any Phonexia technology or Phonexia product. Licenses are issued by the Business Department for all speech technologies and products, and may be required in order to use utilities and tools developed by Phonexia or partners. For technical…

Q: Which authentication options are allowed by the server and how does it work?

Relevance: 39%      Posted on: 2017-06-27

A: The following options are supported: HTTP basic authorization - Client asks for session by resource “post /login” with HTTP basic authorization in query header. If server responds with error 405, server doesn't support authorization by sessions and it is necessary to use basic authorization. Authorization by session - Authorization by session is done by adding parameter “X-SessionID“ into HTTP header to each query. Basic Authorization is done by HTTP standard in header of each query for the server. You can set this in ./settings/phxspe.properties