Thanks for the bug report. I filed it as an issue on the github source. Yes, the earliest OSX supported is 10.13. I’ll see if I can come up with a fix for that to support older versions.
1 Like
Do we need a new library tag (meta ?) to indicate modules that are compatible?
3 Likes
@4ms - Have the OrangeLine modules been ported to the 4ms meta? Your Github suggests that they might but its not clear.
that’s great news. thanks for confirming. Am I right in thinking this is the only pitch quantiser currently available for the 4ms meta?
Possibly - there is loads of Count Modular modules so might be one there too?
VCV has a quantiser
Surprisingly no pitch quantisers in Count Modular or Bog Audio for that matter.
That would be great but as I understand it, VCV modules aren’t available for the 4ms Meta (would be amazing if they were)
?
2 Likes
There’s around 30 VCV modules available in MM, which was a nice surprise as I wasn’t aware of that either.
Looks like you’re in luck with the Quantiser too…
2 Likes
I have ordered one and am putting some patches together so I can hit the ground running when it arrives (probably Wednesday here as we have a bank holiday on Monday).
In the absence of a manual, could I just check with you that I am not wasting my time:
-
A Meta patch, as I understand it, is made and updated with the ‘Save’ button on the Meta template?
-
A Meta patch consists in one Meta module, any modules any knobs are mapped to, and any modules patched to that Meta module?
-
Any name I give a knob will be visible on the physical module?
-
There is no way of intelligently cutting and pasting mappings and knob namings to create, for instance, multi oscillator polyphony, i.e. all the laborious naming etc has to be carried out for each module in a patch?
-
There are no samplers? (Not sure why you didn’t include the STS @4ms ?).
Awesome! Curious to know how it goes!
See upthread:
2 Likes
Sure, and this is based on using the module over the past few days…
- Meta patch, as I understand it, is made and updated with the ‘Save’ button on the Meta template?
Yes, build the patch as normal and then use the red ‘Save’ button on the MM. The resulting file can be loaded into the MM and boom - there it is! Bear in mind you need to make sure any VCV plugins you are using not automatically on the module are loaded though.
- A Meta patch consists in one Meta module, any modules any knobs are mapped to, and any modules patched to that Meta module?
Correct, although obviously the MM module from VCV doesn’t show up as that would be a bit…meta 
- Any name I give a knob will be visible on the physical module?
You can name knob sets but the parameters are name the same as they are on VCV modules as far as I can tell.
Update: You can use ‘alias’ on VCV to rename them, nice!
- There is no way of intelligently cutting and pasting mappings and knob namings to create, for instance, multi oscillator polyphony, i.e. all the laborious naming etc has to be carried out for each module in a patch?
You can duplicate the cable connections to the MM module, as per usual in VCV but not the knob mapping as far as I can tell. Honestly though, it takes no time at all to assign them
- There are no samplers? (Not sure why you didn’t include the STS @4ms ?).
Looks like STS is in development from 4ms, the rest are down to the plugin developers.
Hope that helps, the MM comes with a decent manual that explains all of this.
3 Likes
Thanks for explaining the 4ms workflow. Now it starts to make sense. Really good to know the VCV quantiser is there - I use it all the time. Re. samplers Mahlen Morris has stated here that he’s considering porting some of the Stochastic Telegraph modules over which would be amazing:
Re samplers - StochasticTelegraphMahlen Morris 9d
Thank you, so would I. I haven’t quite knuckled down and figured out the process to make that happen yet.
2 Likes
Thank you for the info.
It’s useful that the Meta patches are discrete, as I can keep many of them in a single VCV patch.
2 Likes
Thanks.
I will certainly report back here on my experiences with it. The first module I ever bought was an ES-9, but the whole VCV over ES-9 did not work for me at all. Too much latency. I gave up trying to fight it. I still sometimes use a patch that is all scopes & analysers with it, if I need to figure out more than I can do with my Data. I will be interested to see what the latency is like with the Meta but it will certainly be far less than with the ES-9.
I’m looking forward to using Meta, stoked to use the EnOsc, Braids, Elements, Fm-Op, and polyphonically too, in my rack. The whole legendary 4ms clock suite of modules is there too. Ratcheting heaven.
I’m also particularly interested in running sequencers out of it (the knobs and buttons expanders are going to help a great deal here). One of the most basic things I look forward to using it for is the 8FO.
In many ways, I feel this module will be everything that the Disting Ex promises but makes so painful to use in practice.
Expectations are high!
2 Likes
If you can I would encourage you to start a topic in here (“Nik’s meta diary”), where you share what works and doesn’t work, as you use the module - what you find it’s particularly good for and what we should forget about, the pitfalls you run into and the practical solutions that are good to know. Would be interesting to lots of folks I’m sure…
5 Likes
Good suggestion. Will do!
6 Likes
Yeah - the Distings are great but too fiddly for me as a creative tool. Whereas with the MM I can build something in and have it working as part of my Eurorack setup in just minutes.
Trying out external MIDI control this morning using the USB port on the MM.
1 Like