Posted by m_kos 4 days ago
There are a lot of Euclidean sequencing tools out there already, in both software and hardware. The premium offerings in the latter category are Elektron sequencers/ samplers/ synthesizers and the Oxi One, a pure MIDI sequencer. but there are many others. Euclidean sequencing is generally combined with things like conditional triggering (playing a note based on probability or a specific iteration of a loop or doing some sort of logic operation on another note in the sequence) and parameter locking (anchoring other parameters like velocity or control data to specific notes). I have the impression taht the authors of this project aren't very familiar with the electronic music marketplace, given that Euclidean sequencing is found even on budget gear now because it's so easy to implement and intuitive for musicians to exploit.
Incidentally, on Vivaldi (built on Chrome) this renders as black text on dark grey, making it nearly unreadable - probably because it's following system defaults, but I think a lot of people have system colors set dark by default.
Thanks for checking out my blog - yes it's heavily written by claude, and contains AI slop ;-)
I'm a lover of petri-nets this was my most interesting experiment so far.
I do have another version of this post that shows a a vis each instrument as a petri-net.
https://blog.stackdump.com/posts/beats-launch-jambox - the 'stage' view shows a better viz.
NOTE: As you all have mentioned - this doesn't work well on phones - I would try this again with another non-browser framework, but the browser is a fun place to iterate w/ claude: Open to suggestions here
also : this project is open source https://github.com/stackdump/beats-bitwrap-io
I can answer any questions - this is almost 100% vibe coded app using claude code, and I do make use of a separate render farm using a headless chrome if I want reproducible builds.
I also created a schema.org compatible protocol for the file format for each generated tack
- the demo on the page makes no sound and is visibly off (triggers happen when the token is at the wrong location, or not at all)
- the demo video is boring
- it doesn't even _do the thing_? it's just a 1d piano roll in a circle? there's no fun petri net dynamics?
(who is upvoting this?)Horizontal (left-to-right) sequencer displays like a piano roll or step sequencer are far more compact to display and easier to read. For drums parts, it's one dimensional until you add a second layer, and then the parts stack vertically, nicely on top of each other.
It's all to say that I don't really see much advantage in this petri nets paradigm. Even the trigger conditions and probabilities have already been incorporated into a large number of DAWs and hardware sequencers. This feels a little like someone who has discovered fire independently from the rest of civilization, but in this day and age I don't think that counts for much when all they had to do was observe the design paradigms that already exist.
In the end, the proof is in the pudding: How good is the music made with the tool? Does the technique allow us to more easily do something that was previously difficult or tedious? In this case, I'm not yet seeing it.
hating on OP for being AI slop is fully legit imo (sorry OP) but don't judge the concept on this example. the rotary sequencer model's actually quite effective. there's lots of niche software and Eurorack modules which implement it, e.g., Moskwa (and Moskwa II) from Xaoc Devices.
here's a YouTube video which shows Moskwa II in action:
https://www.youtube.com/watch?v=C-6n_E9WIfQ
btw the first rotary sequencer was probably Raymond Scott's Circle Machine from 1958:
https://web.archive.org/web/20110927232227/http://raymondsco...
One of those levels could be context-related microtiming - the context being position in the bar, or the actual shape of the phrase, the position in the phrase, and so on.
This isn't sequencing in the classical sense, it's generative composition.
It's not popular because it's much more abstract and harder to work with than "Play this pattern."
There's a lot of unexplored potential in deterministic systems that work with music at these more abstract levels.
The "petri net" or "rhythm necklace" can compact this into a single layer of information. I think something similar can be achieved by using compound meter -- 12/8 instead of "4/4 with swung 1/8th notes" in standard notation, or using something other than the standard 16 steps on a drum machine.
My brain has always struggled with compound meter, somehow I just see a fraction should just be reduced. Much easier for me to imagine a grid that needs different levels of resolution in order to describe certain patterns.
Trying to learn independently, I've found much more difficulty in articulating why a given rhythm is so good, compared to the wealth of theory for understanding great melodies and harmonies.
So it's great to see others building tools and ideas around rhythm, it's a very deep and fun topic to explore.
The demo video has sound though, and sounds pretty cool.
Also - is it just me, or is delivery weirdly off-beat sometimes? Like, isolating to just the kick drums in a standard 4-on-the-floor techno song, it has almost a disorienting amount of delay on some of the beats.
I played with it for a while and implementation is perhaps not the strongest aspect of this project.
Is just browser jank I think, with JS in browsers it is infamously hard to get the timing right and consistent, sequencing make this painfully obvious.
Everyone else does this on the server and then sends you the results.
If my computer is going to do all the work, then I want all the knobs and sliders too.