We’re about to release v2.0-dev-13!
Fingers crossed, this might be the last breaking change before v2.0 is officially released.
We’ll make an official announcement after I tidy up a few things. But before it’s out, it’d be great if all plugin developers re-compiled their plugins with the SDK tagged api-v2.0-dev-13.
I have updated my MM to dev-13.1 firmware. The install seems to be successful. But I cannot then manually load my Chilly Cheese dev-13 module from the Setting → Plugin page. When I select the left-hand “Plugin” option to show the plugin page, then try and turn the encoder to scroll through the list of plugins, the highlighting of the selected element jumps and flickers. This then starts happening in the main left-hand Settings menu also. I have not seen this happen before in previous firmwares.
The “Load patches” menu and list seem OK. It just seems to be affecting the main Settings menu.
From a UX perspective if you are all doing a last recompile, for a shiny v2.0, FYI the parameters and jacks appear to the user as generic e.g. Param1, Param2 or Out1, Out2, if you do not do some sort of naming magic, the detail of which which I do not know. Parameter navigation in a module is another kind of magic. Thank you for you work.
Yeah, that’s a separate issue, those names are there because the plugin does not give a name to the jack or knob. So to fix that, we need to modify the plugin source (vs. firmware and SDK release)
Excellent! I’ll get Unfiltered modules recompiled when I get back from spring break. I got a bug report for one of the delay modules that is MetaModule specific, so I’ll try to roll that in. I have two new HetrickCV modules ready for release as well!
I noticed that trying to delete a module in a patch crashes the system, except if it’s a ClonedInstruments module? There might be some other exceptions since I didn’t go through all the plugins.
Is this a known bug, there’s something in the issues:
What it means is that all plugins can now use graphic screens (not just VCV ports). There’s a set of new CoreProcessor virtual functions that a module class can implement to draw pixels on a screen if it wants to. I added the ThorVG library which I plan to extend out to plugins, but modules can use anything they want to draw.
For VCV ports, the change is just internal. There were some bugs with things like text alignment and positioning, that I fixed. Performance is improved a bit, too.
@etcetc I get a crash when I run the CPU load test on the NOI modules. I haven’t narrowed down which module is at fault yet.
And Nozoid has an issue with the releases: There’s a release for v1.6 firmware (in this one: Release Release: v1.0.0 · Ericxgao/metamodule-nozori · GitHub)
But when I try to run that on v1.6 firmware, it won’t load and says “No init function”. Which is strange, I looked at the code and it looks OK. I can try to compile it locally and see if I can figure it out. But unfortunately our script isn’t too sophisticated and we can’t limit a plugin to just one version, so I have to keep it off v2.0-dev plugins until we figure that out.
The other 6 plugins passed the tests though, so they’re in the v2.0-dev plugin zip!
Update: I went ahead and added NOI too because I can’t get it to crash when making patches by hand. I’ll step through the cpu load test and see if I can pinpoint it.
That one works for dev-13, but the problem is our script looks for a v1.x release for all plugins. It doesn’t find a valid v1.x plugin in that release, so it goes on to scan the next release (which is the link I posted in my previous message). There, it does find a valid 1.x plugin (the file Nozoid-v1.0.0.mmplugin), so it includes it in the official firmware plugins. But, upon loading that file on v1.6 firmware, it gives an error.
The easiest thing would be for you to delete the Nozoid-v1.0.0.mmplugin file from that second release.