r/algorithmicmusic • u/SnooDoggos101 • Jun 11 '26
Early Grid Seq jam
I'm still working out the visual design, and how everything works internally. I have list here of the triangular playheads that I can mute and solo as it plays back.
r/algorithmicmusic • u/SnooDoggos101 • Jun 11 '26
I'm still working out the visual design, and how everything works internally. I have list here of the triangular playheads that I can mute and solo as it plays back.
r/algorithmicmusic • u/Interesting-Bed-4355 • Jun 21 '24
r/algorithmicmusic • u/simonholliday • Mar 01 '26
Hi all,
I've been working on writing an algorithmic, generative MIDI sequencer over the last year or so, and in the past month I've pulled together all the ideas into a new open-source GitHub repo and published it: https://github.com/simonholliday/subsequence
I initially started writing it because I couldn't do what I wanted in other software, standard DAW sequencers feeling too limiting for generative ideas, but environments like SuperCollider felt too dense when I just wanted to sequence my existing synths (and not generate the audio itself).
The main features and strengths of Subsequence are:
- Stateful Generative Patterns: Unlike stateless live-coding that just loops forever, patterns in Subsequence are rebuilt on every cycle. They can look back at the previous bar, know exactly what section of the song they are in, and make musical decisions based on history and context to generate complex, evolving pieces.
- Dial in some chaos: It can be used as a simple non-generative, fully deterministic composition tool, or you can allow in as much randomness, external data, and algorithmic freedom as you like. Since randomness uses a set seed, every generative decision is completely repeatable.
- Built-in algorithmic helpers: It comes with a bunch of utilities to make algorithmic sequencing easier, including Euclidean and Bresenham rhythm generators, groove templates, Markov-chain options, and probability gates.
- Pull in external data: Because it's pure Python, you can easily pull in external data to modulate your compositions. You can literally route live ISS telemetry or local weather data into your patterns to drive any part of the composition. There is an example using ISS data in the repo.
- Cognitive harmony engine: It uses weighted transition graphs for chord progressions (with adjustable "gravity" so you don't drift too far out of key) and Narmour-based melodic inertia.
- Super-efficient & accurate: The core engine is highly optimized, with sub-microsecond clock accuracy and zero long-term drift. It's so efficient you can run it perfectly headlessly on a Raspberry Pi.
- Pure MIDI, zero audio engine: It doesn't make sound. It generates pure MIDI to control your hardware synths, drum machines, Eurorack gear, or software VSTs.
You might find it a useful tool if you're a musician/producers who loves experimental or generative music, is comfortable writing a little bit of Python code, and want a sophisticated algorithmic "brain" to drive existing MIDI gear or DAW setup.
I'm aware that this project has a bit of a learning curve, and the example scripts available in the repo right now are still quite limited. I'm actively looking to expand them, so if anyone creates an interesting example script using the library, I'd love to see it!
The README.md in the repo gives a lot more detail, and there is full API documentation here: https://simonholliday.github.io/subsequence/subsequence.html
I'm pretty happy with the current state of the codebase, and it's time to invite some more people to give it a go. If you do, I'd love to know what you think. I've set up GitHub Discussions on the repo specifically for questions, sharing ideas, and showcasing what you make: https://github.com/simonholliday/subsequence/discussions
Thanks!
Si.
r/algorithmicmusic • u/goodinamohawk • Aug 30 '26
Been working on this for the last few months and finally finished it.
Most of the music isn’t sequenced in the usual way. I built a bunch of rules around probability, timing and different states, then let the system move through them on its own. The visuals and lighting are tied into the same processes rather than being added afterwards.
It ended up somewhere between composition and just setting up the conditions for things to happen.
Would be interested to know how people here think about that line between composing something and designing a system that composes itself.
r/algorithmicmusic • u/SnooDoggos101 • Jun 08 '26
I'm making it compatible as a plug-in to another container program I'm making, but I'm also thinking of making various audio plug-in formats as well. Would you use it?
r/algorithmicmusic • u/BeatShaper • Sep 20 '23
r/algorithmicmusic • u/finneganegan • Jul 05 '23
r/algorithmicmusic • u/BeatShaper • Aug 12 '25
We’re a small team building Beat Shaper, a generative/algorithmic tool for electronic music production. We’ve trained our own custom text-to-MIDI model that creates editable drum loops and bass lines in real time, with House and Techno as the first supported genres with more genres and instruments planned in the future. We’re still training and refining the model to better understand what users want, so any input you can give us at this stage would be extremely helpful.
r/algorithmicmusic • u/simonholliday • Sep 30 '26
Hi folks,
Back in March I posted here about Subsequence, the algorithmic MIDI sequencer I've been writing in Python. A lot has changed since, so here's an update, along with a much better place to start: it now has proper documentation, including a full guide, at https://subsystem.co/subsequence
What it does
Subsequence plays algorithmic compositions that keep evolving: parts that develop over time, answer each other and move through the sections of a piece, over chord progressions it can choose as it goes. It drives your synths, drum machines, Eurorack or DAW over MIDI.
Evolving, algorithmic music. Parts remember what they've played, know the chord and the section they're in, and can respond to each other, so the music develops rather than loops. Harmony can be included from weighted chord graphs in twelve styles, from functional major to chromatic mediants and whole-tone, and melodies can follow Narmour's implication-realisation model, where big leaps tend to turn back and small steps carry on.
Live coding, at the terminal and in files. Change a piece while it plays, from a Python prompt connected to it, or by saving its file, which is heard from the next bar without the music stopping. Keys on your keyboard can fire fills and jump between sections as you perform.
An abundance of algorithms. Nineteen algorithmic generators and more than fifty sequence utilities: Euclidean and Bresenham rhythms, Markov chains, L-systems, one- and two-dimensional cellular automata, the Lorenz attractor, Gray-Scott reaction-diffusion, Perlin and pink noise, logistic-map chaos, Recamán, Thue-Morse, de Bruijn, Fibonacci and golden-ratio rhythms, self-avoiding walks and Xenakis sieves, plus swing, grooves, ratchets and other transforms to reshape what they place.
Connected to my other apps. Subsample, a sampler that turns a microphone or any recording into a playable instrument, and Substation, a radio scanner, can each tell a running composition what they've just heard, and Superconductor (in very early stages) puts a composition's controls on a touchscreen. More on those below.
Under the hood, a composition is plain Python: one function per part, which Subsequence runs again before every cycle, handing it the chord that's sounding, the section it's in, how many times it has played and anything the other parts have shared. Give a piece a seed and every random choice in it repeats exactly, so anything that surprises you can be played again. It makes no sound of its own: it's pure MIDI.
What's new since March
More algorithms. L-systems, the Lorenz attractor, reaction-diffusion, Recamán, Thue-Morse and de Bruijn sequences, Fibonacci and golden-ratio rhythms, self-avoiding walks, 2D cellular automata and Xenakis sieves are all new, along with Toussaint's evenness, off-beatness and syncopation measures, so one part can respond to how syncopated another is playing.
Musical structure. Motifs written in scale degrees, which can be varied and developed, phrases including the classical sentence and period (question, then answer), cadences, Roman-numeral progressions and harmonic rhythm. An energy dial arranges a piece section by section, and fills and mutes can mark the boundaries automatically.
Microtonal tuning. Any equal temperament, a list of ratios or cents, or a Scala .scl file, played through per-note pitch bend, so no MPE is needed.
Live coding by saving the file, and one-shots triggered live that land on the next beat or bar.
More ways to connect. Ableton Link, a knob and a held chord from a MIDI keyboard feeding a part, one part played on several instruments at once, and MIDI files that keep each device on its own track, from a render or a live take.
Tighter timing. Pulse jitter is typically about 1 µs on Linux, no pulse lands more than 0.1 ms out at any tempo from 60 to 200 BPM, and there's no long-term drift.
The documentation
The old API page has gone. In its place, https://subsystem.co/subsequence has:
A guide that teaches Subsequence by building one piece of music: from a first drum beat, through ghost notes, a Euclidean snare, swing, a bass line, chords that move, a melody that remembers, motifs, form, parts that listen to each other, and filter sweeps and slides, to a lead line driven by a day of London weather. Then microtonal tuning, performing, live coding, playing with other gear, and capturing a take as a MIDI file. Every example in it is run against the current release whenever the site is built.
An API reference and a cheat sheet, both generated from the code, so they can't drift away from it.
The apps around it
Subsequence is one of a small family of tools I've been building, all documented at https://subsystem.co:
Subsample cuts separate sounds out of a live input or a recording, sorts them by how they sound, and plays them as an instrument from MIDI. Subsequence can play it, the two can share one file of sound names, and with OSC switched on, Subsample can tell a composition what it has just captured.
Substation is an SDR band scanner that detects, demodulates and records radio transmissions. It can tell a composition over OSC what it has just heard, and Subsample can import its recordings as sounds to play.
Superconductor is a new control surface for Subsequence: a page in the browser that draws a composition's controls (step grids, note grids, stacks of generators and transforms) so you can change it by touch, or with a mouse, while it plays. It's at a very early stage, so expect rough edges and plenty of change.
Who it's for
Musicians who like generative and algorithmic music, don't mind writing a little Python, and want to drive the gear they already have. The guide starts from installing it and hearing a first note, on macOS, Windows or Linux. It's open source (AGPL-3.0): pip install subsequence, on Python 3.10 or later.
I'd love to hear what you make of it (and with it), and what's missing.
Documentation and guide: https://subsystem.co/subsequence
Thanks :)
Si.
r/algorithmicmusic • u/sincopeiro • Mar 28 '23
Hey guys, I'm a frontend developer and would like to start into generative music. I'm also a "musician", so already have some knowledge about music theory stuffs. My plan is to create some small projects for web, like web interfaces where the users can generate some music of a specific genre according to his inputs.
I have seen some discussions about learning Markov Chains, experimenting with Web Audio API, and using libraries like Tone.js. However, I am finding it challenging to create my first "beats" from scratch. I think that the my main question for me is related to the algorithm used to create the music. It is still not clear for me how to develop it and deal with things like tempo, instruments, chords etc.
If any one is interested in learning together, I would love to create some group :)
r/algorithmicmusic • u/BeatShaper • Jan 26 '26
Hey everyone, I've posted here before about Beat Shaper, a generative/algorithmic tool for electronic music production. We’ve trained our own custom text-to-MIDI model that creates editable drum loops and bass lines. You can even route the generated MIDI to control external software and hardware in real-time.
Since I last posted here we'd added support for more genres (techno, house, trance, drum & bass, hip-hop, and trap). Now we've also added a direct-to-Ableton export, that configures an Ableton Live project with loops you generate in the app so you can use them as a starting point for your own tracks.
The app is entirely free and you can try it out here: app.beatshaper.ai
As before, we'd appreciate any feedback that helps us improve the app.
r/algorithmicmusic • u/sir_cartier- • Aug 21 '26
song i made today with my very hands!
r/algorithmicmusic • u/musescore1983 • Jul 25 '26
Hi everyone,
I’ve been experimenting with a method for generating new musical structures from a single notation-based MIDI file.
The basic idea is:
Split a MIDI file into temporally connected musical components.
Describe those components using pitch, rhythm, velocity, register, density, and timing features.
Build a similarity kernel and embed the components into a lower-dimensional space.
Connect the embedded components with a Bézier path.
Use a normalized sequence in the range [0,1] to choose positions on that path.
Map each selected point back to a complete MIDI component.
The sequence does not directly choose a note or chord. It chooses a position on the Bézier trajectory, and the nearest musical component is reconstructed from there.
I tested several control sequences:
cosine
Weierstrass
ruler function — OEIS A001511
paperfolding sequence — OEIS A014577
countdown fractal — OEIS A122196
Kimberling/Wythoff fractal — OEIS A003603
Kimberling signature sequence — OEIS A022328
Kimberling insertion sequence — OEIS A194959
I also added a flexible kernel parameter that controls the number of connected components. Fewer components preserve longer recognizable phrases, while more components create more fragmented and experimental results.
The reconstruction preserves complete note groups rather than generating isolated notes. It can also preserve local tempo changes from the source MIDI.
The repository contains:
Python implementation
command-line tools
LilyPond examples
notation-based MIDI examples
mathematical documentation
an English technical PDF
tests and configuration examples
notes intended to help both humans and AI systems reimplement the method
Repository:
https://github.com/githubuser1983/algorithmic_music_starter_kit
I’m especially interested in feedback from people working with algorithmic composition, MIDI processing, generative music, sonification, kernel methods, or interactive installations.
Possible applications I’m exploring include:
structural MIDI remixing
adaptive game music
data sonification
interactive installations controlled by phones or sensors
educational tools for musical form
generating reproducible training variations for music-AI systems
This is still experimental. It is better at reorganizing the musical vocabulary of an existing piece than at inventing completely new themes.
I’d be very interested to hear:
Does the mathematical model make sense?
Are the component and reconstruction choices musically reasonable?
Which other deterministic or fractal sequences would be worth testing?
What would make the repository easier to reproduce or extend?
r/algorithmicmusic • u/SnooDoggos101 • Jun 08 '26
r/algorithmicmusic • u/BeatShaper • Feb 25 '25
r/algorithmicmusic • u/kubzoey95 • May 08 '21
r/algorithmicmusic • u/Earhacker • Jan 23 '19
r/algorithmicmusic • u/jeremyfromearth • Mar 27 '26
Hi r/algorithmicmusic, I would like to share Sonic Fauna, a desktop app for composing experimental and algorithmic music that I've been working on in my spare time for the past couple of years.
Sonic Fauna provides tools for creating melodies, rhythms and textures with a balance of control and unpredictability through pseudo-random processes.
Here is a quick start tutorial demonstrating the features of the latest version:
https://youtu.be/NKIt1aDpEIo?si=93rzewpfyxxCfh71
This is still a relatively new project, in that it's only recently that I've been posting about it and growing the user base.
I’ve had the good fortune to work with Dr. Chris Warren at San Diego State University on the development of the Spaces module, which uses impulse responses from his EchoThief project in a textural reverb module.
There are still several new algorithmic devices that I am planning to develop in the coming months. Specifically, I have plans for a variety of new sequencers and mutating parameters that will provide a layer of automation.
Sonic Fauna around the web:
Website: https://sonicfauna.com
Discord: https://discord.gg/C97FgegWhZ
BlueSky: https://bsky.app/profile/sonicfauna.bsky.social
YouTube: https://www.youtube.com/@sonic-fauna-app
SoundCloud: https://soundcloud.com/sonic-fauna
If you're interested in testing the app, feel free to DM here or in the Sonic Fauna Discord.
r/algorithmicmusic • u/modal-sx • Dec 27 '25
I just finished a project that turns any set of audio samples into evolving, generative soundscapes.
It’s like a live generative musician jamming in your computer, turning a static samples folder into a constantly evolving performance.
It supports live playing and parameterisation for BPM, pitch, spectral chopping, several effects, and layer weights. These can be adjusted in real-time, move on their own, so the sound is always evolving, but you can override them manually anytime.
I’d love to hear your feedback, feature suggestions, or thoughts on the sound!
r/algorithmicmusic • u/stevehiehn • Aug 16 '22
r/algorithmicmusic • u/dyltur • Feb 09 '22
r/algorithmicmusic • u/wouter-hisschemoller • Aug 11 '20
r/algorithmicmusic • u/Vetii • Mar 02 '16
r/algorithmicmusic • u/Appropriate-Tax-9585 • Aug 01 '26
CARD/OS is a launcher that has built in apps and a lightweight SDK so you can built your own cards in javascript and lua.
In this demo its showing off musical apps. Wait for it
The launcher has a dock which enabled widgets, we have a tempo widget and a mixer accessible from any app.
Running here are jusg a few of the musical apps - which all sync together.
SYNTH
Pocket Studio (similar to a pocket operator)
LOOM (programatic control over synths, drums, randomness, effects etc)
All apps can be used on their own or synced with other built in apps.
The launcher isnt yet released but it also contains a pico8 cart player, ebook/pdf reader, iptv, radio and more.