# Multichannel Midi not working \[FIXED in v2.0-dev firmware\] **URL:** \ **Category:** Feature Requests\ **Created:** [September 6, 2024, 9:49am UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208 "2024-09-06T09:49:52Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![joeman](https://forum.4ms.info/letter_avatar_proxy/v4/letter/j/6f9a4e/32.png) [@joeman](https://forum.4ms.info/u/joeman)\ **Post date:** [October 27, 2024, 11:33pm UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/21 "2024-10-27T23:33:12Z")
I think it is _essential_ that every MIDI mapping learned on the MM (to control knobs/buttons or jacks or anything) should be MIDI channel specific (option 3). It is very limiting otherwise and I was quite surprised when I discovered this (so quickly after trying to integrate the MM into my performance rig which depends on MIDI channels to achieve what I need). Option 1 as a temporary stand in will indeed very much help (I’ve a gig in a couple of weeks where I require the ability to specify MIDI channel on the MM for mappings… \*fingers crossed for asap solution!) ---
**Author:** ![ersatzplanet](https://forum.4ms.info/user_avatar/forum.4ms.info/ersatzplanet/32/1511_2.png) [@ersatzplanet](https://forum.4ms.info/u/ersatzplanet)\ **Post date:** [November 3, 2024, 5:57pm UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/22 "2024-11-03T17:57:23Z")
The most awesome way, for me, to do this is to use a “MIDI learn” feature, that when you highlight a control, jack or whatever on the MM, then provide a MIDI signal, that signal’s MIDI Channel (and CC# if it was a MIDI CC) would get mapped to the target. No matter what channel it was on. Then these mappings would get saved with the patch. ---
**Author:** ![perkowitz](https://forum.4ms.info/user_avatar/forum.4ms.info/perkowitz/32/422_2.png) [@perkowitz](https://forum.4ms.info/u/perkowitz)\ **Post date:** [November 3, 2024, 10:53pm UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/23 "2024-11-03T22:53:51Z")
Any progress on at least getting the Meta out of omni mode so I can add it to my setup? That would be a great first step! ---
**Author:** ![danngreen](https://forum.4ms.info/user_avatar/forum.4ms.info/danngreen/32/14_2.png) [@danngreen](https://forum.4ms.info/u/danngreen)\ **Post date:** [November 5, 2024, 12:27am UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/24 "2024-11-05T00:27:36Z")
Yes, v2.0 has a port of the VCV Free MIDI-\>CV module, which handles selecting a channel. v2.0.0-dev-3 has the channel selection. The UI is still a little rough, but it’s there. I have not written code to have the MM hub on VCV automatically translate patches made with the Rack MIDI-\>CV module into a MM patch using this new module. The only way it works in this dev version is for you to add the MIDI-\>CV module to your patch from within MetaModule hardware (not using VCV). And then patch it up! Update: Here’s the post announcing v2.0.0-dev-3 (warning: firmware has some glitches, experimental!) > [@Development firmware v2.0-dev-1](https://forum.4ms.info/t/development-firmware-v2-0-dev-1/683/15): > > Here’s dev-3: [https://github.com/4ms/metamodule/releases/download/firmware-v2.0.0-dev-3/metamodule-firmware-v2.0.0-dev-3-firmware-assets.zip](https://github.com/4ms/metamodule/releases/download/firmware-v2.0.0-dev-3/metamodule-firmware-v2.0.0-dev-3-firmware-assets.zip) This changes: Fixes all of the 4ms modules whose knobs don’t display as moving. (Airwindows is still TODO) The manual “Adjust” pop-up for params now uses Rack’s display method (units, log/exp base, offset, mult, as well as min/max) Adds MIDI channel selection to MIDI-\>CV module Makes MIDI event log prettier in MIDI-\>CV module Cleans up some Cloned Instr… ---
**Author:** ![gabrielroth](https://forum.4ms.info/user_avatar/forum.4ms.info/gabrielroth/32/17_2.png) [@gabrielroth](https://forum.4ms.info/u/gabrielroth)\ **Post date:** [January 22, 2025, 8:34pm UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/25 "2025-01-22T20:34:32Z")
This thread went quiet so I just wanted to resurface it to say: This now works great in the dev firmware with my Oxi One. All four sequencers are controlling separate voices on the Meta! It’s extremely cool. Here’s how to make this work, in case anyone is wondering: - Make sure you’ve got the latest [v2.0-dev firmware](https://forum.4ms.info/t/development-firmware-v2-0-dev-1/683) installed, along with the plugins for that version. - On the Meta, create a MIDI-\>CV module from the RackCore plugin. (You can’t do this in VCV Rack at this point.) - On that module, go to the Options menu and select a channel. - Map V/Oct, Gate, Velocity, etc. from that module to the devices in your patch. To use a different channel, create another MIDI-\>CV module. ---
**Author:** ![perkowitz](https://forum.4ms.info/user_avatar/forum.4ms.info/perkowitz/32/422_2.png) [@perkowitz](https://forum.4ms.info/u/perkowitz)\ **Post date:** [February 12, 2025, 7:15am UTC](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208/26 "2025-02-12T07:15:05Z")
I finally had some time to get back to the Meta module and this is working great! I’m running two simple synths based around a Mutable Braids on two midi channels and it sounds great. Of course, I look forward to being able to make the midi connections in VCV rack – at the moment I have to lay out the patch in VCV and then add the midi on the Meta. It would also be great to be in a mode where the encoder just pages back and forth through knob sets without pushing buttons – now that I’m running more complex patches, I’m really needing 2-3 pages of knobs and want to go back and forth quickly. [Previous page](https://forum.4ms.info/t/multichannel-midi-not-working-fixed-in-v2-0-dev-firmware/208.md?page=1)