How are you using the meta module?

its been out for a couple of weeks now, have you found ‘your way’ with it yet?

what role have you been using it for?

(a synth voice? a utility module? an fx modules?)

how many modules do your typical patches have?

how do you create patches?

do you develop patches exclusively/mainly in vcv then transfer?
do you most create patches on the meta module?

generally, Im wondering how do you play to the strengths of the meta module within its constraints


notes:

( * ) I think strengths/weakness are somewhat subjective/personal… hence the focus on what works for you.

( ** ) I don’t mean specific patch/module examples, we have plenty of examples posted that we can use for inspiration - no need to repeat here.

for me, Im stilling finding my way… hence the post I guess…

Ive been doing a bit of mixture of patching on module and in vcv.
on module, it tends to be simple patches using one or two modules…
almost like using a dist-ing, just grabbing something I need.

in vcv, im being a bit more ambitious, but haven’t yet really found a role for it.

that said, I only yesterday really started to dig into all the modules available,
so this might open new avenues.
( before I focused on ones I already know pretty well)

also, its in my ‘development rack’… and I think I might move it into my main rack.
Im getting the feeling it would be better used as compliment to my other modules… esp. as I lack FX in my main rack.
not sure though… as its handy being close to computer for vcv desktop.

but, as I said, I very much still finding my way… deciding what role it might have in my setup.

I have built a few patches in VCV that are essentially fully-mapped (the way I want them) single modules such as Braids, Elements and the EnOsc. One of the really nice things here is that you can stick attenuverters in front of modules that have ports, that lack them.

I tend to fill all the spare outputs with various Sloths, because I use slow chaotic modulation more than any other modulation source, and I never have enough of it. I’ve also built banks of different modulation sources.

On the fly, I simply add utility modules and modulation sources as I need them for a patch. I never patch more than three modules together in the module itself; most of the time, the modules are running discretely and are not patched together at all, but are patched to other modules.

I didn’t buy this module because I want to run complex VCV patches on it (though I doubtlessly will in time), but because I want access to some modules with little hardware equivalent, and because its final destination is my 7U focus case, where I never have enough modulation or utilities.

It can also free up the Versio, which is often in that case, running Campestria, which is a 3rd party Plateau port, and give me a DLD when I want it in that case (I have a physical one in my main case).

All that may seem a rather tame use, but after over 3 years with them, I have had enough of battling with my Distings, which suck all pleasure out of patching.

Thus far, the module has done everything I have asked of it without hitting the CPU limit so I couldn’t be happier with it.

1 Like

I am using it a lot, already have a new track where it’s handled both the core synth parts and as an FX processor using a wild, envelope follower controlled version of Plateau on a drum part from Logic.

I tend to build stuff on VCV in my laptop and then transfer via the cloud into my studio. That workflow works for me as ideas often come better away from the confines of the studio.

Need that WiFi expander soon tho!

1 Like

for now, i am using 2 mm’s and building 99% of the time in vcv strictly for live performances. beyond the back forth usb swap mm<>laptop dance of getting everything to work 100% on the mm (V tricky since some modules, especially bog, are still buggy on the mm, atm), it’s also been a little challenge staying organized with 2 sets of patch files between 2 mms. ive finally got a quickish flow now of just using 1 mm for testing patches until they work well, then transferring as needed, to the 2nd mm.

the 1st setup ive tried w the 2mm’s that works ok for my experimental ambient texture drones: 1mm as the voice (typically using midi keyboard) or sending contact mics/guitar into the inputs with some fx patches, and the 2nd mm as the stereo fx > distortion > loopers > reverb unit. the voice mm will be patch-switched heavily during performance to give more sonic variety over time, and the 2nd will probably just use the fx/looper patch the whole time.

i want to try a 2nd setup where both mm’s are voices or mic fxs (& samplers whenever that is added to mm) and i can fade back forth between the two mm’s, swapping the patch on one mm when it’s volume is off. this method will take a lot more time to build up a proper arsenal of patches in order to be able to create ‘patch playlist’ that will compose a proper live set flow.

eventually i want to try a 3rd performance setup where both mm’s act as sequencers/cv control for external synths/ios (whenever midi out is added to mm), then maybe run the synth/ios app audio back into the mm’s for further effects. maybe not patch switching on the mm’s so much.

this is my first skiff/foray into modular. it is small, portable, quite boring with just 2 mms + 4x stereo mix module, but the idea was “easy travel (my back is bad)” + lots of exploration and sonic firepower in a small space. so far so good!

2 Likes

Been using it solely as a standalone module → going to audio outs. It feels good to be able to focus on one thing exclusively, then learn it well.

  1. Educational tool - discover new modules and experiment more
  2. Motivational tool - get off my slack to finally learn some VCV
  3. Budgeting tool - convince myself not to keep getting the latest & greatest
  4. Entertainment tool - have a blast porting VCV patches to play on hardware
2 Likes

Hi there,
I have quite a huge system (800hp) so I use it to add things like utility and I want to test new modules before buying.
I´m working on pre-patches for small combinations of attenuverters and single-function modules such as complex envelopes, LFOs, dynamic sequencing, etc.

1 Like

I like small racks… esp, with this kind of module…
its nice to be able to move it between desk (for pc) and couch, or to move it close to other hardware (synths/modular).
also, at my age, getting a bit closer to the smaller screens is useful :wink:

Ive had a really productive afternoon with this setup…

manage to learn a lot about the modules we have available, and starting to get an idea what I want to use MM for…

just had a beautiful patch running,
Marbles/LFO/Envs running on the MM feeding into the eagan matrix.
all then going into the XMX running clouds w/ some modulation from seq/lfo.
I then record the resulting audio…
change the sequence up in marbles on the MM.
then layer that new audio w/ previous layer(s)

all from a 84hp case, whilst sitting on the couch, listening thru headphones, drinking some tea…

… now tear down the patch, and do it all again :wink:

4 Likes

ok that looks like a super fun portable rack! i was actually looking at the ssp around when metamodule was announced (which swayed me from getting the ssp). instead i opted for 2 mm’s as 1. cost less than ssp, and 2 probably more versatile sonically especially once sample playback and recording are added.

im curious what you feel about the xmx compared to the mm? i might still end up getting one to experiment as $500 seems reasonable and at 28hp i could still fit it in this meager 60hp case w an additional 2hp unity mixer (4hp for the polyend power). i need to do more reaearch on xmx though

they are quite different beasts, each have their pros/cons.

I may well do a video discussing them at some point.
but I want to make sure I understand them both really well before I do that.

it was fun today, actively patching and using both at the same time,
really did highlight the differences in approach, functionality.
some things on the XMX in particular, I knew it had, but I guess I almost take for granted.

but yeah, very different, each has its advantages :slight_smile:

1 Like

Some serious horsepower there. Please do make a video about the three modules; there can’t be many who have that combo so people will be fascinated.

2 Likes

My idea was to use it as single or a couple of modules e.g. Osc and filter. I’ve however been mainly patching in VCV rack and being too ambitious and creating larger patches. Problem here is it’s easy to hit the CPU limit in the MetaModule so I’m getting the 99% patch load message.

1 Like

i also would love to see a video with some thoughts on how the mxm mm compliment each other :]

the story of all our lives these days lol. would be hilarious to have a tshirt with that error message on it

1 Like

Hi folks,

Personnally I’ve still not really found my way. For now, I spend the little time I have to try things that pop up in my mind. The mistake I often do is thinking I have a mini rack in my hardware rack… my patches are often too ambitious … and they overload the module.
The main idea when I planned to buy the MM was clearly to use it as a multi swiss knife tool to extand my case.And my first experiences with this beast confirm that it is the right way to use it.
Cheers

I have the same problem with being too ambitious.
The problem is if your use VCV rack you only limitation is your computer power so you can create large complex patches with any problems.
I’m not sure the Metamodule was created so you could have mega constructions within an eurorack system but where you can expand your Eurorack system with modules you may not want or have physically within your system. I’m finally cutting my VCV creations down and using my existing physical eurorack modules to create things.

1 Like

Yes, that’s a good way to put it. The Meta Module is not “VCV Rack with knobs,” it’s “add a couple of virtual modules to your hardware system.” Which, honestly, is pretty great. I have a small system and the MM makes it much more flexible and interesting.

1 Like

So far really enjoying the 4msMM. The Scanner Darkly module only uses 20% and I can lose a couple of hours just playing with that. Can’t wait to start building my own sequencing rigs. I think some of slight ambivalence that I’ve picked up is probably from people expecting 20U of free modules in a small box. If you approach with a more reasonable set of expectations the thing is really fantastic. It seems Dan is committed to refining things moving forward. I found working with the patching/dial settings to be fast and intuitive. Clearly a lot of care has been taken with the interface design. My key request would be a built in midi out so that we can drive the rest of our gear. 9.5 out 10 from me!

4 Likes

I’m using the 24 kHz sample rate option, which makes a huge difference to the complexity of patches that can be loaded. I can’t hear much above 12 kHz anyway :smile:

1 Like

honestly for certain kinds of music it definitely could make sense to go with 24khz. like watery generative drones or tonal ambient music that doesn’t rely too much on complex high end timbres (like hihats or snares). im using a few patches in 24khz during a live upcoming drone set im positive that once the sounds go through the pa, travel across the room, and into the audiences’ ears, that the differences between 24 and 48 aren’t going to be noticed. i don’t know yet if i’d want to ever do final release recordings at 24 w mm… guess those patches could just be rendered in 48 or 96 via laptop

Hey there,

new to this forum. Got my meta module a couple of weeks ago but haven’t really had the time yet to play around with it. I intend to use it as the centre piece of a little vocal effects box for live which I’m building (yes I do love weird vocals). Not the easiest thing to find suitable plugins from what I can tell right now, but I’m sure I’ll get there, eventually. I’m currently looking for bread and butter stuff like EQ, compression, different reverbs and delays which I intend to stretch to the max :wink:

2 Likes