npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cc-livekit/audio-pipeline-plugin

v1.1.7

Published

A WebAssembly audio pipeline module for RNNoise and DeepFilterNet on web frontends.

Downloads

859

Readme

Audio-Pipeline-Plugin

  • A WebAssembly module implementing fixed-order audio pipeline processing for web frontends.
  • The denoise stage currently supports rnnoise and deepfilternet.

Denoise Stage Modules

  • rnnoise (default)
  • deepfilternet

DeepFilter Build Artifacts

  • DeepFilter wasm source package: DeepFilterNet/libDF/pkg/df.js + df_bg.wasm.
  • Artifact generator: node ./scripts/build-deepfilter-artifacts.mjs.
  • Generated files: src/dist/deepfilter-bindgen.js, src/dist/rnnoise-sync.js, dist/deepfilter.wasm.
  • build:js runs artifact generation first, then bundles worklet + library outputs.

Example

import { AudioPipelineTrackProcessor } from "@cc-livekit/audio-pipeline-plugin"

const processor = new AudioPipelineTrackProcessor({
    workletUrl: "/assets/AudioPipelineWorklet.js",
    stages: {
        denoise: "rnnoise",
    },
    moduleConfigs: {
        rnnoise: {
            vadLogs: true,
            vadLogIntervalMs: 1000,
        },
        deepfilternet: {
            attenLimDb: 100,
            postFilterBeta: 0,
        },
    },
})

await processor.setModuleConfig("rnnoise", { vadLogs: true, vadLogIntervalMs: 800 })
await processor.setModuleConfig("deepfilternet", { attenLimDb: 30, postFilterBeta: 0.02 })
await processor.setStageModule("denoise", "deepfilternet")
await processor.setStageModule("denoise", "rnnoise")

Runtime Behavior

  • Single AudioWorklet runtime.
  • WASM and models are loaded only at init. Both rnnoise and deepfilternet WASM binaries are fetched and both modules are created during init(). No model or WASM is loaded when switching modules or when calling setModuleConfig later.
  • setStageModule("denoise", ...) switches the active denoise module in-place (rnnoise ↔ deepfilternet). Only the already-loaded active module is used; no extra loading.
  • setModuleConfig("deepfilternet", ...) after init only updates parameters (attenLimDb, postFilterBeta). DeepFilter uses the built-in model only (no custom model loading).
  • setModuleConfig("rnnoise", ...) updates rnnoise-only config.
  • vadLogs and vadLogIntervalMs are rnnoise-only configs.
    • They are ignored by deepfilternet.
    • Updating rnnoise config while deepfilter is active is cached and applied when switching back to rnnoise.
  • Input audio must be 48 kHz; the pipeline does not perform sample-rate conversion.