Judging by a few videos, this thing is super fun and musical. Would love if something like this existed in VCV Rack. I guess it’s kind of a sampler (record length 2 sec.) with means of recombining audio bits in different sizes and ways and order to create useful musical rhythms and little textures from recorded material. Seems like they have really done a great job with it. Was a pedal and is now in Eurorack. It randomizes, as they say, so you never get the same results twice.
As often when something pops up interesting, it’s sold out and £225 + tariffs. Granular, with stereo spreading, and who knows what delay/filter/reverb resampling algorithms behind the randomization. I’m curious why a big knob if it’s really always selecting a different randomization as described – a button would serve. I guess it lets you have those pretty settings indicators.
Hoping the big knobs varies it in certain ways depending on where it is on the dial. But you are probably right! I’d love to know what is happening in there. Google search turns up this:
Here is how it works:
New Loop Generation: Every time you move the big knob, the internal parameters are randomized, and a new, unique loop or texture is generated based on the captured two-second sample.
Position as a Seed/Parameter: The position of the knob determines the specific set of random parameters applied to the audio playback engine. It is not just an on/off for randomness; the physical position (or incoming CV) shapes the character of the generated sound.
No Undo: The core philosophy of the module is about commitment and chance; there is no way to “go back” to a previous loop, emphasizing that the knob’s position creates an irreversible, new sonic moment.
The module offers a switch to select between Texture and Rhythm modes, which changes the type of randomization, but within either mode, the knob position determines the specific randomized outcome. The knob can also be controlled via a dedicated CV input for generative modulation.
Website: Weaver Modular – Fieldtone
More overpriced lo-fi hipster nonsense….
I would start with Simpliciter, and to replicate the knob that produces random settings, hook up some of these to change a few parameters, and some sort of button to trigger randomisation:
It’s quite distorted, so maybe some wave shapers and patch in a tiny bit of noise. Also try randomising this:
Also, try this:
I wanted to put it up to hipster nonsense, but a friend has one and it grabs the room sound pretty well, the mic has a decent pattern, makes cool sounds with that.
I really like this little thing here:
Actually I found another one. I have absolutely no idea what this does but it’s great fun! I’ve been playing guitar through it, and patched Chronoblob into the send/return so I can capture random bits and loop it. The output then goes through a low-pass filter with the cutoff modulated.
It\s a crazy random loop generator:
Simpliciter can randomize itself pretty well. In the “Grid” portion of the UI, turn on all three buttons: On, Peak, and Rnd. Set the playhead to loop. Send the eoc from Simpliciter to backward-and-forward on the tape control expander module. Maybe send a slow clock to Simpliciter’s record button
It will do wild and unpredictable things all by itself.
Yeah I’ve been using Simpliciter for years but it’s buggy, and the other module I linked apparently has better features like eight layers with polyphonic output, built in EQ and parameter morphing.
However, there is no manual and I can’t see how to get more than one layer working. I think the library could do with some quality control, it’s great that anyone can make their own module and get it published but really frustrating as user when things seem to be half finished and completely undocumented.
There’s a manual in the source code repository (source link from the VCV library page), though it doesn’t seem to explain very much, and seems to talk about random things from the source code that aren’t relevant to the end user. It’s also not very easy to access, you have to download the HTML file and open it in a browser.
For what it’s worth, that collection seems to be vibecoded- or at least the majority of the coding is done by AI, so I assume that’s part of the reason for the poor documentation.
As for having better quality control in the library, I’m not sure we’d have the wealth of modules we do now if developers weren’t allowed to make some mistakes when starting out.
I believe I’ve also seen a couple of other developers mention they wouldn’t make modules if they were forced to write manual pages for them.