V2.0 SDK is released!

Plugin Development
1

To all plugin developers: the SDK has been tagged with api-v2.0.0.

Please re-compile your plugins with this SDK and test on firmware v2.0.0-rc1

Since this is no longer a dev firmware, remove the -dev-13 tag from the plugin file name.
Also, we have relaxed the requirements for the -fw-X.Y tag. Instead, you should bump up the plugin version. So if you previously had released:
Myplugin-v1.0.4-dev-13.mmplugin

then this v2.0 SDK release should be called:
Myplugin-v1.0.5.mmplugin

…or feel free to name it with any version you wish, as long as it’s newer than the latest -dev-13 release.

What will happen next is that we’ll manually test all plugins on v2.0 firmware and verify there’s nothing needed to be changed in the SDK. If it’s all good, then we’ll change the website to host the v2.0 plugins and v2.0 firmware

18 Likes
2

Congratulations Dan! This has been a ton of work and represents a huge step forward for the Meta Module.

3 Likes
3

Congrats! Thanks for all of your efforts to make this happen!

1 Like
4

Everything seems to work fine with kocmoc plugin, compiles and runs

Note that this is a prerelease testing version of the plugin and it includes a new module that’s not yet in the VCV Rack library

I had to add the new tag in the Github Action:

5

The Chilly Cheese module seems to work fine on an api-v2.0.0 build and running on the v2.0.0-rc1 firmware.

6

@janne808: a new diode filter, cool! The only thing is that the plugin-mm.json format has been updated. The MetaModuleIncludedModules field now needs to be a dictionary:

I’ll finish the transition from our examples repo to your repo with this release.

7

Looks good, thanks for that!

8

I totally missed this but it should be fixed now on v2.0.10:

Sounds good.

1 Like
9

@danngreen

I’ve tagged and kicked off v2.0 releases for all of my ports. Let me know if I missed any. I am also out of town so cannot test them, I just upped the tag version and re-ran the workflow for a new release.

1 Like
10

Our parser is reporting syntax errors with the trailing commas after the name field. I think that’s it though

11

Most are good, but we are getting json errors for four plugins:

Fehlerfabrik: extra [ and ] in MetaModuleIncludedModules:

Mockba: trailing comma on line 166:

SanguineMonsters: same error as Mockba (trailing comma after last module)

RPJ: same thing again (trailing comma)

12

Fixed it:

Maybe there should be a simple sanity check in the Github Action script? Something like

jq . -e plugin-mm.json >/dev/null || exit 1
13

Good idea! I’ll put that in the example workflow.

I tried using cmake’s native JSON string support to validate, but it lets through too many mangled cases.

I’ll add a validation check to the plugin-sdk as well so you can catch errors before pushing, but it’ll just issue a non-fatal warning if it can’t find the jq executable.

14

Thanks - rebuilt those four as v2.0.1

15

Perfect! Everything checks out!