Giter VIP home page Giter VIP logo

rnnoise-wasm's Introduction

rnnoise-wasm

rnnoise noise suppression library as a WASM module.

This repository contains the necessary utilities to build the library using a Docker build environment with Emscripten.

Build

Prerequisites

  • node - tested version v10.16.3
  • npm - tested version v6.9.0
  • docker - tested version 19.03.1

Building the module

Building is straightforward, run:

npm run build

The repository already has a pre-compiled version under the dist folder, running the above command will replace it with the newly compiled binaries and glue wasm .js file respectively.

In order to facilitate the build with docker the following prebuilt image is used trzeci/emscripten/ however, it is slightly altered by installing autotools components necessary for building rnnoise.

In summary the build process consists of two steps:

  1. build:dockerfile - pulls in trzeci/emscripten/ which is then altered and saved. Any suqsequent build is going to check if the images was already installed and use that, so if one wants to make changes to the Dockerfile be sure to first delete the build image from your local docker repo.
  2. build:emscripten - mounts the repo to the docker image from step one and runs build.sh on it. The bash script contains all the steps necessary for building rnnoise as a wasm module.

Usage

Following a build two files are generated under dist, the actual webassembly binary rnnoise.wasm and the generated emscriten .js file named index.js which contains glue code and the necessary libc runtime javascript bindings.

The repo is structured so it can be used as a npm dependency, with the entry point in dist/index.js, be mindful as using index.js automatically implies that rnnoise.wasm needs to be present as well, thus for a normal npm build system one must explicitly copy rnnoise.wasm to the project structure.

rnnoise-wasm's People

Contributors

andrei-gavrilescu avatar saghul avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rnnoise-wasm's Issues

Integration with Debian/Ubuntu packages

I'm not using docker and on the packages from debian repo, after installing, I see rnnoise.wasm on /usr/share/jitsi-meet/libs but can't find the rnnoise-processor js anywhere. I don't hear it enabled either.
Could it be enabled by hand? Do I need to change the config files or will I need to recompile jitsi-meet to include all necessary libs?
If it's not usable, why is the rnnoise.wasm file there to begin with?

feature request: RNNoise for stereo

Hello, happy new year!

I wonder if it would be possible to have RRNoise on a stereo stream?

I'm using a high bitrate (256k) with stereo (in configs) for HD audio.
I send mix an additional stereo stream/track along with the existing one, normally the microphone (like the share audio feature).
I don't need any audio processing in this case but it would be nice to have NS when we only have the mic on.

When I bypass the warning & apply RNNoise on the stereo stream it results in mono to the output having only the left side audible.
(Removing it, unchecking the checkbox will resume the stereo)
I tried as well to apply it on a mono stream (forcing the channelCount of the GUM to 1 in the lib while remaining in stereo), result is the same.

Ideally it would be nice to have more flexibility in general & to be able to renegociate the stereo when we want but it seems too complicated for me.
(Is it for memory usage that you prevent RNNoise on stereo?)

Thank you!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.