Is it the center of a small rack or part of a larger rig? Just trying to get an idea of use cases and best practices.
1 Like
My rack is here: 1. Current rack - Eurorack Modular System from gabrielroth on ModularGrid
Not sure if that’s small or larger, depends on your frame of reference I guess. I recently got an Oxi One which I love and which will replace the two sequencers in there.
I typically start a patch with the Meta as a sound source (Plaits, Rings, or a couple of FM-OPs) and then add various utilities within the Meta as needed while patching.
I’ve only scratched the surface of the Meta’s capabilities but I’m OK with that — it would be very possible to get overwhelmed by the possibilities.
Would love to hear other folks’ answers!
This is my rack. I also have a Volca Drum, a Korg SQ1, and a Behringer Brains in its own case for some extra sonic horsepower.
Using it a lot and love it.
It sits in my main rack and I generally use it for individual or basic combinations of modules rather than full on patches.
In that sense it’s become the most powerful Eurorack Swiss Army knife imaginable 
1 Like
There is an existing thread so it probably pays to search before posting one.
Seems like the kind of topic that will resurface periodically and I don’t think there’s anything wrong with that. It’s not a thing where important information gets lost if we have multiple threads.
1 Like
Sure, I also supposed you do not personally manage community groups operating on online platforms. Now I wonder why this feature was built-in the platform itself.
I did not see that dead thread before I posted. It has not had any activity in months.
are most of you using 1.6.9 or Beta 2.0?
If I make patches on 1.6.9 can I later use them when upgrading?
im using beta dev 2 for sample playback capability. ive been able to load all my old non beta created patches in dev 2 fine. and ive been able to load patches created in dev 2, in 1.6.9. except the patches ive created in dev2 that use plugins that only work in dev2, such as sicko or bidoo. but those patches will still work fine once dev 2.0 becomes the stable release, since the yml format isn’t going to change really between now and then. however i think any beta dev 2 plugins that etcetc are making may have to be updated to work once 2.0 becomes the stable release, but he seems pretty on top of things!
I am using Beta 2 and been using it most of the time since I bought it. How many people still use 1.6.9?
I’m still using v1. I don’t plan on moving up to V2 until it is out of development. I don’t have the time or patience to keep up with all the frequent changes and updates in the dev channel. But as soon as Dan says V2 is ready for prime time, I’ll be there.
1 Like
I tried v2 but downgraded so I could run Elastika.
1 Like
It will be nice when we could get all of the modules available on one platform. I believe that @danngreen said 2 would become the new stable version soon. I hope that happens!
1 Like
BTW, Elastika is in v2 beta. It is under CosineKitty-Sapphire.
Good to know, thanks!
It can be a bit overwhelming keeping track of all the new developments.
3 Likes
This is my current case with the MM in, I’m using it for my live breakcore/Gabber/Hardcore setup, and basically the MM is handling all sample playback duties using a load of modules which I wrote myself. I didn’t originally intend to use it like this, but after having tried every single sampler in Eurorack and found that none of them worked well enough for the way I wanted to do things I finally gave in and wrote my own! It’s also doing a couple of other things like making envelopes from the sample playback (again using my own modules) which I use for sidechaining in the mixer, and a little bit of fx etc… The rest of the rack is really geared towards noise and feedback stuff, which I then shape with the sidechaining, and with other envelopes.
Probably the other module of note in that setup is the DPT, which is also running some code I wrote for a kind of crazy noise oscillator which you can also lock into fixed buffers to get a kind of random wavetable oscillator thing going on, with scanning through the buffer, a super resonant LPF, feedback and a really aggressive wavefolder, so it’s really cool for lots of percussive textures as well as more melodic (but still noisy and unpredictable) sounds.
What you don’t see from modulargrid is that connected to those ES modules is a Raspberry PI, running a load of RNBO code which I wrote as a really complex modular control system, which I use to generate loads of patterns and output a load of phasors which I use for various indexing and timing purposes in the rack. I control that with two Launchcontrol XL’s.
It’s obviously a really complex (and pretty insane) setup, but it’s all geared towards improvising stuff in the moment, and to do that in a compact system you don’t have a lot of choice but to write a lot of custom code IMO. The metamodule really has been a godsend though, because I could never have done the kind of crazy cutup stuff that I’m doing with it without building everything myself and the development cycle from VCV to the MM is really a dream to work with compared to all the other program it yourself modules which are out there (maybe the Percussa SSP is an exception to that, but it’s basically unmaintained and even the examples don’t build so there’s no way I was going to drop the money on that to have to spend a million hours just trying to get it up and running). So yeah, the metamodule rules and I’d not be able to do this without it!
5 Likes
That’s awesome. It’s so cool how the Meta lends itself to such radically different styles and uses.
2 Likes
I have today, started my first Eurorack after having my first MM a few weeks in a small skiff. As a beginner learning, so many exotic modules out there, am I missing anything?
5 Likes
Well for a start I don’t think you have enough MetaModules 
6 Likes