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

lsdj-wave-cruncher

v0.1.0

Published

Turns a sound clip into a LSDJ wavetable synth.

Downloads

244

Readme

lsdj-wave-cruncher

lsdj-wave-cruncher is a bundle of scripts allowing an LSDJ user to create wavetables instruments in LSDJ (a steel drum, or other instruments with complex waveforms).

WARNING ⚠️ : .snt files only contain the 16-frames long 4-bit waveform data. The synth parameters are not saved.

crunching

Crunching a sample is downsampling and bitcrushing the given sample into a .snt binary file ready to be patched to a LSDJ song.

To crunch a sample, use :

$ node crunch.js [SAMPLE.WAV] [NOTE|FREQUENCY] --normalize --channel=0
  • [SAMPLE.WAV] is the file that'll be crunched.
  • [NOTE|FREQUENCY] is either the note at which the sample is (ex: C4, D4) or its frequency (ex: 440 Hz).
  • --normalize, if present, will normalize the sample.
  • --channel=0 specifies the channel where the sound data will be taken. If not present, it defaults to the 1st channel (0). This parameter is only relevant for stereo sound.

patching

Patching a synth is writing the binary .snt data into a LSDJ song.

To patch a synth, you can use both of these commands :

$ node patch.js [LSDJSAVE.SAV] [SONGNUMBER] [SYNTHFILE.SNT] [SYNTHNUMBER]
$ node patch.js [SONG.LSDSNG|.SRM] [SYNTHFILE.SNT] [SYNTHNUMBER]
  • [LSDJSAVE.SAV] is the save that'll be patched. If you want to patch a .SAV file, you'll have to supply the number of the song [SONGNUMBER] you want to add the synth to.
  • [SONG.LSDSNG|.SRM] is the song file that'll be patched. In that case, you don't have to supply a song number.
  • [SYNTHFILE.SNT] is the synth data that'll be patched.
  • [SYNTHNUMBER] is the ID of the synth where the data will be written.

crunch-patching

Crunch-patching is downsampling and bitcrushing a sample and writing it right away into a LSDJ save file/song.

To crunch-patch a sample, you can use both of these commands :

$ node crunch-patcher.js [SAMPLE.WAV] [NOTE|FREQUENCY] [LSDJSAVE.SAV] [SONGNUMBER] [SYNTHNUMBER]
$ node crunch-patcher.js [SAMPLE.WAV] [NOTE|FREQUENCY] [SONG.SRM|.LSDSNG] [SYNTHNUMBER]
  • [SAMPLE.WAV] is the file that'll be crunched.
  • [NOTE|FREQUENCY] is either the note at which the sample is (ex: C4, D4) or its frequency (ex: 440 Hz).
  • [LSDJSAVE.SAV] is the save that'll be patched. If you want to patch a .SAV file, you'll have to supply the number of the song [SONGNUMBER] you want to add the synth to.
  • [SONG.LSDSNG|.SRM] is the song file that'll be patched. In that case, you don't have to supply a song number.
  • [SYNTHNUMBER] is the ID of the synth where the data will be written.

exporting

Exporting a synth is extracting synth data from an existing LSDJ save or song and exporting it as a .snt file.

To export a synth, you can use both of these commands :

$ node export.js [LSDJSAVE.SAV] [SONGNUMBER] [SYNTHFILE.SNT] [SYNTHNUMBER]
$ node export.js [SONG.LSDSNG|.SRM] [SYNTHFILE.SNT] [SYNTHNUMBER]
  • [LSDJSAVE.SAV] is the save that'll be used as source. If you want to find a synth in a .SAV file, you have to supply the number of the song [SONGNUMBER] you'll want to get the synth from.
  • [SONG.LSDSNG|.SRM] is the song file that'll be used as source. In that case, you don't have to supply a song number.
  • [SYNTHFILE.SNT] is the path of the .snt file that'll be created.
  • [SYNTHNUMBER] is the ID of the synth that'll be exported.