# Firmware v2.0.0-dev-12.2

**URL:** <https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123>\
**Category:** Dev Firmware Discussion\
**Created:** [February 22, 2025, 4:58am UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123 "2025-02-22T04:58:42Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**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:** [February 22, 2025, 4:58am UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/1 "2025-02-22T04:58:42Z")

</div>

Pleased to release v2.0.0-dev-12.2, which adds MIDI Output support and a few other things:

> **[Release Firmware Version: firmware-v2.0.0-dev-12.2 · 4ms/metamodule](https://github.com/4ms/metamodule/releases/tag/firmware-v2.0.0-dev-12.2)**
>
> What's Changed
> 
> Midi output and CV-\>MIDI module by @danngreen in #464
> Fix jack being marked unpatched if panel jack is unplugged but internal cable remains
> Fix GUI slowdown when lots of mapped knob...

## Features:

- Midi output via Rack interface
- Ported CV-\>MIDI module to “RackCore” brand

## Fixes

- Fix jack being marked unpatched if panel jack is unplugged but internal cable remains
- Fix GUI slowdown when lots of mapped knobs are on the screen
- Fix AsyncThreads missing symbols (refactor API)

## Minor improvements

- Add `AsyncThread::run_once()` and `AsyncThread::stop()` to the API
- Auto loader will attempt to load plugins that don’t have a version in their name. Example: If ‘Plugin’ is supposed to be auto-loaded then if it finds “Plugin.mmplugin” it’ll try to load that file. If this fails then it will NOT keep searching.

---

<div class="post-metadata">

**Author:** ![tony10000](https://forum.4ms.info/user_avatar/forum.4ms.info/tony10000/32/704_2.png) [@tony10000](https://forum.4ms.info/u/tony10000)\
**Post date:** [February 22, 2025, 4:01pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/2 "2025-02-22T16:01:23Z")

</div>

Make sure you also download the new plugin library for 12.2. I found out the hard way when it started throwing header errors and would not load plugins.

---

<div class="post-metadata">

**Author:** ![Midibrat](https://forum.4ms.info/letter_avatar_proxy/v4/letter/m/848f3c/32.png) [@Midibrat](https://forum.4ms.info/u/Midibrat)\
**Post date:** [February 22, 2025, 4:36pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/3 "2025-02-22T16:36:53Z")

</div>

I’m super interested in MIDI out. Especially being able to send continuous controller information. What is this rack interface that midi out works with? When I search online all I see is the Wi-Fi expander am I searching for the wrong term?

I’m really enjoying my meta module. I can’t wait till I can use it to send midi information on specific channels

---

<div class="post-metadata">

**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:** [February 22, 2025, 4:49pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/4 "2025-02-22T16:49:58Z")

</div>

> [@tony10000](#):
>
> Make sure you also download the new plugin library for 12.2

Right! Sorry I didn’t mention that. There are new plugins as well

---

<div class="post-metadata">

**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:** [February 22, 2025, 4:52pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/5 "2025-02-22T16:52:26Z")

</div>

> [@Midibrat](#):
>
> I’m super interested in MIDI out. Especially being able to send continuous controller information. What is this rack interface that midi out works with?

There’s no module in VCV yet – so far the only way to add MIDI out is to add it from within the MetaModule (add a new module, select RackCore brand, select CV-MIDI module)

Eventually I’ll add support from within VCV – making a patch with the VCV builtin “CV-\>MIDI” module will automatically show up in the MetaModule

---

<div class="post-metadata">

**Author:** ![Midibrat](https://forum.4ms.info/letter_avatar_proxy/v4/letter/m/848f3c/32.png) [@Midibrat](https://forum.4ms.info/u/Midibrat)\
**Post date:** [February 22, 2025, 5:55pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/6 "2025-02-22T17:55:02Z")

</div>

I think I would like to try the dev firmware you just released is there a guide to installing it I’m having a little trouble finding that part. I have downloaded the latest firmware and the latest plugins for version 2.0. I’m just fuzzy on how to transfer it to the hardware. Thank you for your patience Thank you for your patience

Edit: Never mind. I found the instructions.

---

<div class="post-metadata">

**Author:** ![Midibrat](https://forum.4ms.info/letter_avatar_proxy/v4/letter/m/848f3c/32.png) [@Midibrat](https://forum.4ms.info/u/Midibrat)\
**Post date:** [February 22, 2025, 7:03pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/7 "2025-02-22T19:03:39Z")

</div>

I just finished the update. I’m very excited thank you. As a bonus I didn’t realize the scope was in there. Super excited. Thanks again

---

<div class="post-metadata">

**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:** [February 22, 2025, 8:06pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/8 "2025-02-22T20:06:44Z")

</div>

Great! Keep in mind that the “v2.0-dev” firmware are in-progress, developmental versions. So some features are incomplete, buggy, etc. It takes a little extra work to stay on top of these bleeding-edge releases (keeping plugins updated, not always good documentation, dealing with bugs and general weirdness…), but you get to use new features earlier.

---

<div class="post-metadata">

**Author:** ![Okami](https://forum.4ms.info/user_avatar/forum.4ms.info/okami/32/2251_2.png) [@Okami](https://forum.4ms.info/u/Okami)\
**Post date:** [February 23, 2025, 4:08pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/9 "2025-02-23T16:08:38Z")

</div>

I have tried version 12.2. The mdi mapping now works wonderfully. But I would say that my current patch now requires 1-2% more cpu.

---

<div class="post-metadata">

**Author:** ![etcetc](https://forum.4ms.info/letter_avatar_proxy/v4/letter/e/b38774/32.png) [@etcetc](https://forum.4ms.info/u/etcetc)\
**Post date:** [March 7, 2025, 9:31pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/10 "2025-03-07T21:31:44Z")

</div>

Out of curiosity - does this mean that my Roto control can now receive MIDI events to match the state of the loaded patch when I change the controls?

---

<div class="post-metadata">

**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:** [March 7, 2025, 9:42pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/11 "2025-03-07T21:42:32Z")

</div>

No MIDI is being sent unless you patch a CV-\>MIDI module or some other module that sends MIDI.

---

<div class="post-metadata">

**Author:** ![etcetc](https://forum.4ms.info/letter_avatar_proxy/v4/letter/e/b38774/32.png) [@etcetc](https://forum.4ms.info/u/etcetc)\
**Post date:** [March 7, 2025, 9:53pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/12 "2025-03-07T21:53:27Z")

</div>

I see - so I could send midi out from a CV parameters, but not necessarily the current value of a knob then? Unless I map the knob to a fixed voltage source and then sent that out haha

---

<div class="post-metadata">

**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:** [March 7, 2025, 11:03pm UTC](https://forum.4ms.info/t/firmware-v2-0-0-dev-12-2/1123/13 "2025-03-07T23:03:58Z")

</div>

Right. I just implemented MIDI Output from modules. I didn’t implement the automatic MIDI reporting thing.
