a command-line sequencer
______ ______ ______ ______
/\ ___\ /\ __ \ /\ ___\ /\ == \
\ \___ \ \ \ \/\_\ \ \ \____ \ \ __<
\/\_____\ \ \___\_\ \ \_____\ \ \_\ \_\
\/_____/ \/___/_/ \/_____/ \/_/ /_/
npm install -g sqcr
sqcr buffers_path/
A buffer is a plain JS file to be evaluated in the browser in the sqcr context. This context has a few helper functions outlined in the Browser API section below.
You can use buffers to define loops. Loops can play sounds or draw things in the browser or whatever you want synchronized to a clock.
You can even receive OSC events and respond to them accordingly.
Usage:
$ scqr <buffers-path>
Options:
--buffers, -bf specify location of buffer.js files
--port, -p specify port number
--bpm, -b initial BPM
--path, -d specify root path of server
--init, -i specify init file name
A few libraries are already included in the browser context:
OSC.js - For interacting with OSC events.
WebMidi - For Interacting with MIDI
Tonal - For music/note transformation tasks
Define loops to
loop(name: string, callback: (ctx: Loop) => void)
Example:
// watchable_loops_dir/something.js
loop('quarterNotes', async (ctx) => {
playNote(440);
ctx.sleep(T);
});
COMING SOON...
To run examples, clone this repo to your file system and run:
# MIDI example
./sqcr-cli.js examples/midi
# WebAudio example
./sqcr-cli.js examples/webaudio
- Add more browser-utility methods
- Add better web-audio support
- Improve timing precision (it's about ~3-5 ms margin of error on each beat as of now)
- Configurable browser libraries
- TypeScript