Firmware v2.0.0-dev-12.8

Released v2.0.0-dev-12.8

What’s Changed since dev-12.5

  • Befaco v2.9.0: added new modules
  • Fix crash in PatchSelector
    • After opening 20+ distinct patch files, sometimes it would crash when clicking to open a new patch in the PatchSelector page
    • Also, after entering the PatchSelector page 32 times, it might crash if memory usage was high
  • Fix Wi-Fi sometimes not working when a MIDI device is attached
  • Fix some graphic screens drawing improperly (or being clipped improperly)

Minor changes

  • Hide cable-making notification after 4 seconds
  • Limit Recent patches to 5
  • Fix highlighting in directory/volume side bar
  • Fixed missing rack uiFont loaded at boot time (effected CV Funk Strings module crashing)
2 Likes

Auto-mapping knobs in CVFunk Step wave, hungs the module. Tried 48k 128 and 512.

Ok, I’ll try to reproduce that. Any particular knob?

Just pressing Auto-map knobs in the menu freezes it right away.

I just tried it at 48K 64 and it did not hang.

Mine does. All the other CVfunk modules seem to work fine.

If I load another module first, then it doesn’t freeze.

Hi Dan,
What’s the status of the cv-midi core module? It seems that I can trigger it ( I can see generated midi note information on the panel) by feeding CV and Gate but I can’t get actual Midi Out using v2.0.0-dev-12.8 (or indeed before). Is this a cabling issue at my end or are there still things to be implemented? I’m hoping one day to use the Meta as bespoke midi sequencer, taking full use of the jack inputs and panel controls.

I’m getting some issues with mapping as well, I’m looking into it.

It should be working (just tested it now), but the thing is that the MetaModule is still a MIDI host. So the connected device must be a MIDI Device, and it might not be listening for MIDI messages from the host.
I’ve had the most consistent results by sending a MIDI Clock to the device. E.g. on my Beat Step Pro, I have to set Sync to “USB” and then when I play a sequence, it’ll sync to the MIDI clock tempo that I’m sending from the MM (via the CV->MIDI module by patching a clock into the Clock jack).
Another way of verifying it’s working is that I send MIDI Note messages out of the MM into my MIDI controller, and then have a MIDI->CV module in the same patch. On its screen I see the same MIDI Note messages because my Beat Step Pro is apparently passing on the messages it receives (I don’t know if this is a config option or what).
On my LaunchControl XL, it doesn’t do this message passing (sort of MIDI Thru, I suppose), but it does light up some lights at certain notes (again, I haven’t dove into the controller setup or manual to see why).

1 Like

I found the bug, and have a fix. So… there will be a 12.9 soon!

Also found another issue – with Block size set to 512, when you create a new knob mapping, it will default to knob A instead of the last knob you turned.

Great. Could you also check this.

When modifying previously saved patch in meta module and then duplicating and renaming it, sound immediately or after stopping and starting playback, changes. Sometimes with new patch file detected refreshed, pops up.
Seems like saving resets some settings on the modules.

At least Noise Plethora resets banks, DLD delay time was back to 50%, Dark Energys settings also changed. Djembe pots also reset to zero.

Also Noise Plethora program pot don’t seem to work anymore.

Regarding the CV>Midi - still no joy here using the latest V2dev12.8. I’ve attached the .yml for anyone else to try - it can only be made using the Meta. The display on the CV-MIDI suggests it’s working but nothing is coming through.

It’s a very simple patch and the gate input signal is being trigged from the Clock. I’ve also tried putting something into the Clock Input of the device but it hasn’t helped.

FWIW I’ve got the midi in working, using my usb configuration, so I don’t think the problem is the cabling. I’ve tried feeding this into a Digitone that is listening for midi on its USB port - but nothing registering.

I note that the CV-Midi device midi channel is offset by one. So the CV>MIDI screen displays Midi Channel Zero, while the Options setting for the device reports it’s Midi Channel 1.

Basic_CV_Midi5no1.yml (4.3 KB)

Got it. That might be the same bug as I mentioned above in dev-12.8.
I just ran this on dev-12.9 (just released, but haven’t announced yet) and it runs. I hear the ascending/descending tones and my midi controller responds with lights when it receives certain MIDI Notes.

Good catch, yes that appears to be a mixup of 0-based and 1-based indexing. I’ll sort that out.

1 Like

Oh… yeah I see that, too. That looks like it happened with the Befaco v2.9.0 merge. @hemmer, I think this commit is the one that did it:

Yeah, I think there are a couple things happening here. The pots reset to default position, which is confusing (it also happens if you open a patch before you play it – the pots are in the default position even though the patch specifies different positions). But they jump to the right position when you start playing. It’s just a visual glitch, I can fix that.

As for the sound change, I’m not sure, I’ll look into that.

It’s not only a visual thing, as sound changes noticeably when saving a duplicate, restarting playback don’t fix it. It has happened in every patch this far.

Right, I hear that too, not sure why but I’m looking into it

Yeah sorry about that, I’m a bit confused because I thought those MM specific changes would persist when I merged in (as no other changes to Noise Plethora) but clearly not! I’ll watch out for that next time…

I’ve pushed the reversed commit to v2-mm Befaco branch (aeecdd0615925378edc1cb1e8a137cf5a6306e71), and can open a PR if you want but maybe fastest for you do update submodule directly (even on main) @danngreen?

Cool, no problem I’ll merge it on main