What does it say on the Settings > Info page under USB or MIDI?
If you are using a USB-C to USB-C cable (with no adaptors), and you have the MetaModule in “USB Mode: Auto”, then sometimes you have to plug/unplug a few times until it says “MIDI Device mode, connected to a host”. The reason is that some computers can be a Host or Device, and the MetaModule can be a Host or a Device, so they just randomly pick one way each time you plug it in.
If you choose “USB Mode: Device Only” in the MetaModule preferences, then it will force it to be a device. Or another solution is to use a USB-C to USB-A cable (the A side going to the computer, the C side going to the MetaModule), which will force the MetaModule to be a device, even if you have it in “Auto” mode.
There’s an I2C header on the back of the MIDI Expander, which goes to a line driver (which is there to protect the MetaModule and to keep the signal intact even over long daisy-chains). I still plan to implement some I2C commands…
Yes, you can do that now!
2 Likes
I tried it all. No luck. Is the Meta suppose to appear on my desktop ?
Love the update, did a patch yesterday. Physical Marbles into Meta Gate 1 and Gate 2 and In 1 and In 2 and then the two instances of CV - MIDI modules with destinations (Midi channel 1 and 2) to Bitwig and a patch in there, had so much fun, should have filmed but both hands occupied. Nice update Dan!
Is it possible for Meta to become visible as a drive? Like access the sd card with a USB cable, for example drag and drop module updates. Sorry if this question already been asked, kinda low frequent online visits on my part. 
It’s not supposed to show up on your desktop, it’s just supposed to show up as a MIDI device. E.g. in VCV Rack, any MIDI module such as the MIDI->CV module will let you select “MetaModule MIDI” as the MIDI device.
Yes but it’s not intended for normal usage. You cannot access the SD card, though, it’s a separate drive.
There’s “developer mode” which you can enable in preferences, and it creates a USB drive. You can copy an mmplugin file and then eject the drive and it should install the plugin. It’s meant for developers to use for rapidly testing plugins while developing. It’s not meant for installing plugins for normal use because:
- the developer drive uses 16MB of plugin memory
- anything you install is gone forever when you power off
- it’s not guaranteed to work with all OS’s unless you use the console (via a terminal program like minicom or screen)
Edit: Sorry, I should clarify: the Developer Mode is not part of v2.3.0, it’ll be part of the next firmware (v2.3.1).
1 Like