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

normalize-sfx

v1.0.2

Published

Normalize WAV file loudness to EBU R128 standards using FFmpeg

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

edutherapyedutherapy

Keywords

audioffmpegloudnessnormalizewavebu-r128

Readme

normalize-sfx

Batch-normalize .wav sound effects using FFmpeg's two-pass loudnorm filter.

NPM Version

GitLab Last Commit

Requirements

Install

npm install -g normalize-sfx

Usage

normalize-sfx [directory] [options]

If no directory is given, the current working directory (.) is used. Scans for .wav files in the given directory (non-recursive — subdirectories are not visited).

Options

| Flag | Short | Default | Description | |---|---|---|---| | --lufs <n> | -l | -16 | Target integrated loudness (LUFS) | | --tp <n> | -t | -1 | Target true peak (dBTP) | | --lra <n> | -r | 11 | Target loudness range (LU) | | --concurrency <n> | -c | 3 | Max parallel FFmpeg processes | | --output <path> | -o | (none — written alongside originals) | Output directory for normalized files | | --dry-run | -d | off | List files, skip processing |

Output naming

  • Without --output: Files are written alongside the originals with a _norm.wav suffix (e.g. boom_norm.wav). Originals are never overwritten.
  • With --output: Files are written to the specified directory with their original names preserved. A warning is shown if an output file already exists.
  • With --dry-run: Files are listed with their output paths — either alongside the originals (no --output) or inside the custom directory (with --output). No processing occurs.

Examples

# Default targets, current directory
normalize-sfx

# Custom LUFS, specific folder
normalize-sfx ./assets/sfx --lufs -18

# Custom output directory
normalize-sfx ./sounds -o ./normalized

# Preview without processing
normalize-sfx ./sounds -d

# Aggressive concurrency
normalize-sfx ./sounds -c 8

How It Works

Pass 1 — Analysis: FFmpeg runs loudnorm in measurement mode (print_format=json), outputting the file's current loudness stats to stderr. These values (input_i, input_tp, input_lra, input_thresh) are parsed.

Pass 2 — Normalization: FFmpeg runs again with the measured values injected via measured_* parameters, applying linear=true:offset=0.0. When --output is specified the file is written there; otherwise it is written alongside the original.

Safety

  • FFmpeg check: The tool verifies FFmpeg is available on $PATH before processing.
  • Filesystem confinement: All file paths are confined to the working directory — symlinks are skipped and path escape attempts are rejected.
  • Error isolation: A failure processing one file does not stop the rest. A non-zero exit code is returned if any file fails.
  • Per-pass timeout: Each FFmpeg pass times out after 300 seconds.

About EduTherapy

This tool is developed by EduTherapy (a brand of Talim Shifa Studio), specializing in digital transformation for education and healthcare sectors through Progressive Web Apps.

License

MIT