Moved my music collection from iTunes Match to Navidrome a few months ago. So now I can analyze every track and cluster them.
a demo of embedding the graph in another app. the drum machine UI just uses the it as a module with a shared state.
also i named it nido because `webaudio-canvas` wasn't cutting it anymore.
nido-drum-test.exp.descend.o…
also already have webmidi nodes so it can just send signals to other apps. ez
using AVL drumkits here, partially because they are easy to run on linux
x42-plugins.com/x42/x42-avld…
a small ux thing with node graphs. create a node from a new edge, connect to the best available port based on type.
following the touchdesigner pattern here. if you drag a node out to nothing, it disappears. if you drag one out and open the palette, it attaches to the new node automatically for you.
if i've sent you a 30 rock reaction gif in the past, i apologize that it will happen again in the future
websocket node for sending signals/events. screen recording audio is kinda peaky on my linux machine but whatever.
was playing with a particle thing inspired by @zachlieberman’s recent sketches here.
clock -> sample and hold -> quantize gives these sorts of stepped scales, with configurable bpm and per-measure trigger.
also made the modules more blender geonodes-like with names imports/exports and a couple other things.
building this in browser but with the goal of the graphs being headless so they can be run in node, rust, or embedded in other apps.
revisiting my web audio graph project and adding nodes to approximate the audio in my last post. not there yet but quantizer goes a long way towards it.
next adding a better clock and then script node.





