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

parse-midi

v2.0.2

Published

A small parser for MIDI messages.

Downloads

53

Readme

parse-midi

Netlify Status

A small parser for MIDI messages.

The parser follows midi.org's MIDI 1.0 specification, meaning it:

  • Identifies the channel and message type ("noteon", "noteoff", "controlchange"...) of a MIDI message
  • Provides human-readable strings corresponding to the default mapping for every control change message ("volume", "pan", "effect1"...)
  • Provides human-readable strings for each channel mode message ("allnotesoff", "resetallcontrollers", "polymodeon"...)

Installation

npm install parse-midi

Usage

Basic usage

import parseMidi from 'parse-midi';

parseMidi([144, 60, 62]);
// { messageType: 'noteon', key: 60, velocity: 62, channel: 1, messageCode: 144 }

Responding to MIDI messages in the browser

In browsers that support MIDIAccess, the parser can be used on event data:

navigator.requestMIDIAccess().then(access => {
    Array.from(access.inputs.values()).forEach(input => {
        input.addEventListener('midimessage', (event) => {
            const midiMessage = parseMidi(event.data);
            console.log(midiMessage);
        });
    });
});

See the demo for a working example.

Return values

The parseMidi function returns an object which always has at least these properties:

{
    messageCode: 0-240,
    channel: 1-16,
}

In addition, specific properties exist for each messageType:

{
    messageType: 'noteoff',
    key: 0-127,
    velocity: 0-127,
}

{
    messageType: 'noteon',
    key: 0-127,
    velocity: 1-127,
}

{
    messageType: 'keypressure',
    key: 0-127,
    pressure: 0-127,
}

{
    messageType: 'controlchange',
    controlFunction: string, // e.g. 'volume'
    controlNumber: 0-127,
    controlValue: 0-127,
}

{
    messageType: 'channelmodechange',
    channelModeMessage: string, // e.g. 'allnotesoff'
    controlNumber: 0-127,
    controlValue: 0-127,
}

{
    messageType: 'programchange',
    program: 0-127,
}

{
    messageType: 'channelpressure',
    pressure: 0-127,
}

{
    messageType: 'pitchbendchange',
    pitchBend: 0-16383,
    pitchBendMultiplier: -1 - 1,
}

{
    messageType: 'unknown',
    data1: 0-127,
    data2: 0-127,
}

TypeScript

With TypeScript, type safety and intellisense can be achieved by refining the type of the return object:

const midiMessage = parseMidi([144, 60, 62]);

// Bad - won't compile
console.log(midiMessage.key);

// Good
if (midiMessage.messageType === 'noteon') {
    console.log(midiMessage.key);
}