A scale is randomly selected at the start and then notes are randomly selected from that scale in the pattern generation, plus the root note number is added to each one.
So if you had the 'Darkness' scale selected and had the root dropdown set to 0, the notes in this scale would be C, C#, D# which is 0, 1, 3 if you count the keys on a keyboard. If you changed the root to 2, then it would become D, D#, F (2, 3, 5).
I've just added a wav export feature. Currently it only exports with the knob positions as they are when the pattern first generates. You can choose how long the exported audio is.
It's a bit of a hack that re-opens the app in an iframe in the background using an offline audio context.
I'll come back to it at some point and make the export pick up the knob positions but I don't have time right now.
Currently, all you can do is save the url which contains all of the initial randomisation settings when a pattern generates. It doesn't update when moving sliders or anything, it's just the intial settings.
Thank you! It's been a few years so I can't remember exactly without reading through the code but it's something like this:
It uses notes from the selected scale and octave (from the dropdowns).
If the pattern is of an even length, say 16, it will split it into 4 chunks of 4, then randomly decide if it should generate new data for the chunk or copy the previous chunk. It uses the repeat slider for the probability on this.
It randomly applies the 303 modifiers (up, down, accent, slide) using probability set with the sliders on the pattern tab.
There's also an 'empty' slider which sets the probablity of an empty note appearing in a chunk.
I've just updated this to make it a little bit easier to use on a phone.
The knobs are now a bit chunkier and should respond better to touch and the instruments sit vertically instead of horizontally.
I created this scheduler library which can be used to play a sequence of notes, create a metronome, drum machine etc.
https://github.com/errozero/beatstepper
Hey, sure I'll try... if you mean usage of the library:
It runs your callback every 16th note, slightly before it is actually due to play, this can vary by a few milliseconds each time but that doesn't matter as the actual audio context start time for the note is passed in to the callback, and you use that to actually schedule the events for that 16th note, eg: osc.start(time).
You can schedule 32nd notes etc too by using the stepLength property that is also passed in, time + (stepLength/2) would be a 32nd note.
Hope that makes sense? I do need to write a better description on the github page of what it actually is.
The inner workings of the library itself are mostly just as described in the article with a few tweaks.
I made a library based on this article which I use as a starting point for all my music app projects. It's useful as the main timing code for things like drum machine and sequencers etc.
https://github.com/errozero/beatstepper
A scale is randomly selected at the start and then notes are randomly selected from that scale in the pattern generation, plus the root note number is added to each one.
So if you had the 'Darkness' scale selected and had the root dropdown set to 0, the notes in this scale would be C, C#, D# which is 0, 1, 3 if you count the keys on a keyboard. If you changed the root to 2, then it would become D, D#, F (2, 3, 5).
Hope that makes sense.