Firmware v2.0.0-dev-12.2

Dev Firmware Discussion
1

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

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.
4 Likes
2

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.

3

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

4

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

5

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

6

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.

7

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

8

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.

9

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.

10

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?

11

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

12

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

13

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