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 🙏

© 2024 – Pkg Stats / Ryan Hefner

wavesurfer.js-async

v1.0.7

Published

WaveSurfer computing peeks asynchronously

Downloads

4

Readme

npm i wavesurfer.js-async

Motivation

This piece of code is a plugin for wavesurfer.js which prevent blocking main browser thread during analyzing audio file. This problem occurs during analyzing long audio files or high resolution analyzing eg. minPxPerSec = 400 what's means that each second of file produce an array of 800 items for each channel. During analyzing 9 min audio this producing arrays of ~~ 432 000 elements. Computing so long arrays at once in browser environment blocking main tread for hundreds of second.

WARNING Implement only for WebAudio backend. (default)

Modifications

  • modification - wavesurfer.drawBuffer- to using getPeeksAsync
  • adding - wavesurfer.Backend.prototype.getPeeksAsync

How it works

During analysis audio data for each channel data of audio buffer is return promise. This promise run setTimeout with function iterating through whole buffer. If iterating take more that yieldIteration (16 ms by default) then stops loop and resolve promise with value of index to which peeks are computed. If is not whole buffer then function is run again but starting from point on which previous call was ended. In such way iteration of audio buffer is split to 16 ms chunks what's allow keeping 60 frames per second.

Usage

import WaveSurfer from "wavesurfer.js"
import WaveSurferAsync from "wavesurfer.js-async"


const config = {
    container: document.getElementyById("container"),
    minPxPerSec : 300, // the benefits are visible in big zooms 
    plugins: [WaveSurferAsync.create()]
}

const ws = WaveSurfer.create(config);

You can adjust time after witch loop will be break and computes will be moved to next call/iteration

plugins: [
    WaveSurferAsync.create({
        yieldIteration: 16 // optional break point time - default 16 ms
    })
]