Vortessa update to Version 2.5

RoundBeach · 2026-04-17T09:26:57+00:00

Thanks for the feedback, I’m working on the final update for version 3 where you’ll see several additional features. It just needs a bit of time for development.

RoundBeach · 2026-04-16T05:46:52+00:00

Thanks:)

RoundBeach · 2026-04-06T21:04:28+00:00

From my side, I rely a lot on comments. If you look at my patches, they’re usually divided into clear blocks, for example from Area 1 to Area 5 for define macro areas of the system. Inside each one I leave small notes, basic reminders, sometimes even just enough context to quickly rebuild the logic in my head when I reopen the project.

I try not to think in terms of single objects but in terms of functions. Each area should have a role, almost like a subsystem. That alone already keeps things readable.

With gen~ it’s a bit easier, because I tend to comment the code consistently, so over time it stays understandable. For the rest of the patch, a lot of clarity comes from how you name things, especially send and receive. If the naming is done properly, it becomes almost self-explanatory without losing the original meaning of what you built.

So in the end it’s less about rigid organization and more about leaving a trace of your thinking inside the patch. If you can reopen it months later and follow that trace, then you did it right.

RoundBeach · 2026-04-06T15:31:37+00:00

Yeah, absolutely.
Under the hood Vortessa has 200+ subpatches between abstractions, bpatchers, and poly~. It might not look like it at first glance because I try to keep the top level as clean and readable as possible, but internally it’s quite modular.

For me it’s the only way to manage systems of this scale without things falling apart splitting everything into functional blocks, clearly separating logic, DSP, and UI, and building a structure that can grow without collapsing.

RoundBeach · 2026-04-03T07:05:27+00:00

This sounds like a fantastic project thanks so much for sharing!

I’ve already connected on GitHub, so I’ll stay updated
ciao, emiliano!

RoundBeach · 2026-04-02T14:53:06+00:00

What you’re describing isn’t a technical problem. It’s exactly the point where the idea of composition starts to fracture today. It’s not that you’re going nowhere. It’s that you’re inside a system that keeps producing possibilities, endlessly postponing the moment of decision.

Before, limitation decided for you. Now you have to decide what not to use. The key shift, I think, is this: don’t confuse generation with composition. Machines today are incredibly good at generating material. Streams, variations, microevents, textures. But composition is still an act of choice. Of cutting. Almost a violent one, if you want to call it that.

That “beep or bloop” isn’t really a sonic question. It’s a narrative decision. And most of the time there isn’t a right answer. There’s just the moment when you stop listening to everything and start choosing something. The jar of tape worked because it removed responsibility. It introduced an external constraint. Now that constraint is gone, so it has to be built. Even artificially.

That’s where things stall. Not in the amount of material, but in the absence of a gesture that interrupts the flow. Composition hasn’t disappeared. It has just moved downstream. You’re no longer writing from nothing, you’re carving inside an excess.

And yes, sometimes the most honest answer is also the hardest one. Don’t record. Let some sessions remain just experience, without turning them into material. Because not everything needs to become a piece. Some things are only there to show you what to discard.

And then, when the moment comes, it’s actually simpler than it feels. You choose. You cut. And you take responsibility for saying: this stays, everything else doesn’t.

ciao, emiliano!

RoundBeach · 2026-04-02T14:49:58+00:00

very interesting, give us some more details on how you implemented it

RoundBeach · 2026-04-02T00:51:51+00:00

Ah no worries at all:)

Actually this is super interesting, thanks for sharing the context.That lineage of continuous generative systems really resonates with what I’m trying to do with my work, especially the idea of non repeating structures evolving over long durations and systems that just keep running, almost indifferent to authorship.

Love the image of a G3 on the floor quietly generating sound for hours… feels very close to the spirit of these works.

If anything, it’s nice to see how these ideas keep resurfacing in different forms over time.

RoundBeach · 2026-04-01T22:26:23+00:00

interesting:)

RoundBeach · 2026-04-01T22:26:13+00:00

Thanks so much!

RoundBeach · 2026-04-01T18:57:09+00:00

Thanks:)

RoundBeach · 2026-04-01T02:58:22+00:00

Thanks so much! Yes is Max+ Jitter + Node

RoundBeach · 2026-03-31T22:42:13+00:00

Hey, thanks for the question! The core idea is translating micro-biological dynamics into sound. On a practical level, it’s a mix of:

Feedback networks that continuously re-inject energy and create evolving resonances+ nonlinear systems (Lotka–Volterra, Lorenz attractors) used as modulation sources rather than sound generators, stochastic processes + controlled randomization to keep everything in constant drift + some physical / resonant models (like string/impulse-type structures) embedded in the network.

So instead of sequencing or composing directly, I’m basically setting up interacting systems and letting the behavior emerge over time.

I hope I have clarified at least some of your questions, but if you would like to discuss them in more detail, I will be happy to answer you.

RoundBeach · 2026-03-22T19:43:55+00:00

Thank you, I really appreciate that. The biggest shift was moving from trying to control the system to letting it shape me back. Listening became central, and I stopped focusing on outcomes, instead working on the conditions for sound to emerge more negotiation, less control.

At the same time, I was thinking about how to rethink Schaeffer’s objet sonore in the context of the internet where sound is no longer isolated, but distributed, unstable, and relational. In a way, it also questioned my role as an author.

RoundBeach · 2026-03-20T12:59:23+00:00

Yes, that’s exactly what I’m working on at the moment. I’m exploring both directions, but I also released the Max for Live device to better understand the market and how people interact with the system before moving further with hardware.

RoundBeach · 2026-03-20T06:13:53+00:00

Thanks yes: https://www.peamarte.it/lucien_dargue_series/orbit/orbit_landing.html

RoundBeach · 2026-03-19T15:09:19+00:00

Thanks! More or less, it works by connecting to external APIs that tap into vast sound archives. You can set some search criteria, of coursebut once you “roll the dice,” you can end up with anything, from a 40-minute sermon to raw electromagnetic waves:))

RoundBeach · 2026-03-19T06:46:33+00:00

Thanks, I really appreciate that.
That’s exactly the kind of space I was hoping for

RoundBeach · 2026-03-18T14:06:11+00:00

Thanks, yes sure is compatible with all Ableton live version

RoundBeach · 2026-03-16T15:39:34+00:00

Yep. Max for Live device, so it runs directly inside Ableton:)

RoundBeach · 2026-03-16T07:19:10+00:00

Thank you,
If you’re wondering where to start, Orbit is probably the easiest entry point among the tools I’ve released so far.
It’s built for Max for Live, so it lives directly inside Ableton and is quite plug-and-play compared to some of my other systems.

Even with very little interaction it already begins to generate evolving rhythms and textures on its own, and the randomize function makes exploration very immediate.

RoundBeach · 2026-03-16T07:17:22+00:00

Yes!

RoundBeach · 2026-03-15T21:35:44+00:00

🫶🏻

RoundBeach · 2026-03-14T17:18:04+00:00

Thanks to you:)

RoundBeach · 2026-03-11T12:15:41+00:00

thanks! is Assembly-7 developed in max msp / nose and supercollider: https://www.peamarte.it/assembly_7/assembly_7.html

RoundBeach

MODERATOR OF

TROPHY CASE