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

@ludovicm67/webm-tools

v0.4.0

Published

WebM tools

Downloads

270

Readme

WebM tools

Install this library

npm install @ludovicm67/webm-tools

The following is exposed:

  • Buffer: Buffer that works on both Node.js and browsers
  • utils.blobToArrayBuffer: a function to convert a Blob to an ArrayBuffer
  • ebmlSchema: the EBML schema
  • decode: decode an EBML element
  • displayDecodedElements: display the decoded elements using console.log
  • fix: the function to use to fix a chunk by using the previous one

How the chunks are fixed

WebM is a media format which has become the standard today. However, there's an issue while doing audio chunks because they lack crucial metadata. This essential metadata is stored in the first chunk, so we need to replicate it in the other chunks. The challenge here is that we can't simply extract the header bytes and append them to all other chunks, as each chunk is not an independent "block". They are interconnected, which can confuse the audio player.

Since WebM is based on Matroska, we can use Matroska tools, available at this link, to examine the chunks and ensure they are structured correctly. Specifically, the mkvinfo tool is employed to inspect these chunks.

Matroska employs the EBML (Extensible Binary Meta Language) format, which is a binary format consisting of elements. To address the issue, we must parse the EBML format to identify the specific elements that need to be transferred from the first chunk to the subsequent ones. These elements include the header, which contains essential metadata such as the codec, sampling frequency, and track type. Additionally, we need to transfer the last block of the first chunk, even if it's incomplete, as we will get the end of the block in the next chunk.

The proposed solution is to concatenate the header and the last block of the first chunk with the next chunk. This operation ensures that the structural integrity of the audio file is maintained, making it playable without causing confusion for the audio player.

Command line tool

The cli folder contains a command line tool that can be used to fix or merge chunks.

Have a look at the README of the CLI for more information.