This issue occurs since version for meta button… At least since 2.1.3.
Here and there, knobsets frees when I’m navigating between them, whatever the method I use for navigating between knobsets. It did also one time while changing parameters for a knob.
This is very annoying, since I wasted a lot of time in patching progression since I don’t save my work every 5 minutes… And what if it occurs in a live performance? Ahhh!
When freezing knobs of the last active knobset still work, but I can’t do anything with the back button and the encoder.
I’m I the only one in that situation?
Here’s the patch used on the video. 4 FM OP befaco (sax).yml (29.9 KB)
I did a video, but it seems that we cannot upload videos here.
I have the exact same issue! Running on v2.1.4 with the IO and Wifi expander. I started with 2.1.3 when I bought the MetaModule 4 weeks ago.
I tested it out with several patches, both out-of-the-box and self created, stored on the SD card or on the module itself, and found that the screen freezes typically after 60 page switches (pushing the Rotary knob on the next page, indicated by “>>”). This is after a power-off/on of the module and loading a patch.
I also tested with switching between several patches (card & internal) and found that the sum of all page switches before a freeze is very consistent at 60.
Ok, excellent, that patch led me right to it!
There’s a bug when changing Knob Sets that have multiple parameters mapped to a single button on the expander. I should be able to post a fix tomorrow once I can attach a debugger while it fails. But for now I’m able to make the patch work if I remove the multiple mappings from buttons (HH mute and bongo mute).
Great!
I’m glad you found the cause.
But what is strange is that it happens also on all the other patches even if nothing is mapped on the expander… Could be it possible that the reason is because the expander is connected to the metamodule?
Thanks.
I missed this message earlier today, but this is very helpful information. I just tried it, and confirm it indeed crashes after the 60th click of the >>. Very strange!
I traced it, and the bug is in the GUI library we use (actually an add-on to LVGL). Re-writing that part of the library to make it more simple and direct fixes it.
I’m going to re-write other portions of the firmware that use this library feature as well to make sure it’s not causing some other bugs.