# browser-signal-processing

> Speech signal processing directly in the browser or exploiting relevant web services

Latest version **0.1.7** (published 2017-02-24) · MIT license · 0 weekly downloads

## Install

```sh
npm install browser-signal-processing
pnpm add browser-signal-processing
yarn add browser-signal-processing
bun add browser-signal-processing
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.1.7 |
| Published | 2017-02-24 |
| First published | 2016-08-21 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Maintainers | mjochim |

## Links

- npm: https://www.npmjs.com/package/browser-signal-processing
- Repository: git@gitlab.lrz.de:MJochim/browser-signal-processing
- npm.io page: https://npm.io/package/browser-signal-processing

## Dependencies (2)

- [@types/es6-shim](https://npm.io/package/@types/es6-shim.md) ^0.31.32
- [@types/text-encoding](https://npm.io/package/@types/text-encoding.md) 0.0.30

## Recent versions

- 0.1.7 (latest) — 2017-02-24
- 0.1.6 — 2017-02-24
- 0.1.5 — 2016-10-07
- 0.1.4 — 2016-10-07
- 0.1.3 — 2016-08-21

## README

# Browser Signal Processing

The browser-signal-processing library offers some signal processing functions
designed for speech applications. Some of them are executed directly in the
Javascript engine, while others exploit remote web services.

The functions executed directly in the browser include both simple algorithms
that fit into a few lines, such as RMS, and advanced algorithms such as PSOLA.
The supported web services cover some very complex signal processing such as
automatic phoneme segmentation ([WebMAUS](https://clarin.phonetik.uni-muenchen.de/BASWebServices/)).

The library also includes some helper functions to read and write specific
on-disk formats (such as WAVE or TextGrid) and to simplify the use of such
browser APIs as WebAudio or XMLHttpRequest.

## Usage Hints

The signal processing functions either operate on an array of numbers
(number[]; the most basic form of a Javascript digital signal), or on a
Float32Array, or on an AudioBuffer object. Some functions need to know the
signal's sample rate. It needs to be passed explicitly unless the signal is
passed as an AudioBuffer object, which has the sample rate integrated.

Functions that need to exchange data in terms of some on-disk format (generally
functions that call remote web services) accept these data in two ways. They
can either be already encoded in said format and be passed as ArrayBuffer
objects (which are easily retrieved via XMLHttpRequests), or as Blob objects.
Or they can be in an unencoded form: string for plain text files,
AudioBuffer/Float32Array/number[] for audio files.

Functions that call remote web services either connect to them via WebSockets
or use asynchronous XMLHttpRequests to call RESTful APIs. The results are
made available to the calling Javascript/Typescript code by means of Promises
that resolve to the result values as soon as they are available.

## Usage Examples

@todo add usage examples

## License and Authors

The libary is published under the terms of the MIT license (see file LICENSE).

The main author is Markus Jochim (<markusjochim@phonetik.uni-muenchen.de>).

Some code is re-used from other projects, most notably the [EMU-WebApp](http://ips-lmu.github.io/EMU.html).
Contributors are:

* Raphael Winkelmann
* Georg Raess
* Matt Diamond
* Jam3

---
_Source: https://npm.io/package/browser-signal-processing · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._