This patch was going to be Nostromo-like ambience, with oodles of metallic reverb, but the MM CPU ran out of steam, even at 24 kHz. So, Plateau et al. got jettisoned out of the interstellar cruiser and we landed on the LV-426 planetoid, which is a chirpy kinda place. CPU usage: 80% (24 kHz sample rate, 64 block size). There’s something chewing up CPU cycles and I suspect it’s the MIX8. Maybe Dan can advise. The patch is on auto-pilot.
LV-426 v2.vcv (3.8 KB)
LV-426 v2.yml (12.2 KB)
Thats pretty cool man and funny as Ive also created a patch with the same name
LV246 .yml (11.2 KB)
similar concept
Great minds think alike.
Great patch - thanks for posting - really sets out what the 4ms Meta is all about - extending my modest hardware rack into different sonic territories.
Thanks. One of the great things about MM is that it obliges you to find workarounds given the CPU limitations. And, once you’ve achieved what you want, you don’t feel as if you’ve been limited.
Absolutely. I’m guessing over time, we will get some ultra optimised bread and butter (lfos, mixers, clocks etc) modules for the 4msMM.
im really hoping for this a well! a set of utility modules that are possibly ‘stepped down’ inside, running at event rates. or even something like the prototype module from vcv ported to mm so we could load javascript or puredata files which would, i believe, allow for far more complex tricks without a lot of cpu use
