This is mainly a visual update to improve the look of the modules, hope you like it.
But there is also a tiny addition to WAVULIKE to show the exact frequency in the context menu as this can be useful for things such as Jakub Ciupiński’s aliasing trick
pretty nice. a small tip: on your tooltips they “jump around” a lot as they go to different numbers of decimal places. It looks a little nicer if pick how many places you want to show and do that consistently, possibly adding zeros if necessary. Of course the C runtime makes this very easy.
This one is a bit special because the TMNT module has some feature upgrades; it now has CV trigger inputs for the manual step buttons, and it has a button and CV trigger input to randomise the steps.
Fixed all currently known bugs for V2, so ready to go for release unless new bugs are found.
Hopefully this means I can either add some new features to the modules, or maybe even finish off some of the experimental modules I’ve been working on for the official release.
You shouldn’t need to extract it, it should download as the vcvplugin format, you just put it in your plugins directory and start VCV Rack 2 and it will extract it for you
thats exactly what I did,
and I get the message when I want to run v2 from my mingw64
with the “make run” command,
then I get the “Unrecognized archive format” message in mingw64
I’m not really sure how I can help out, it seems that the issue stems from the building of Rack currently.
How are you downloading the file from github? Maybe there is something going on there.
Maybe you could try opening the archive directly, ie: reversing this part of the makefile tar -c $(SLUG) | zstd -$(ZSTD_COMPRESSION_LEVEL) -o "$(SLUG)"-"$(VERSION)"-$(ARCH_OS_NAME).vcvplugin
I just did a new build of Rack version 2.git.042a9ce0
Did you also download the new 2.git.042a9ce0 version of the SDK?
My understanding is that both the app and the plugin need to be built against the same version
Ok good to hear you got it working, yes it sounds like a github thing, when i click on the link it shows me the file in the repo, and then there is a download button. If anyone knows of a better way to link to a repo file in markdown i’ll happily change it.
Well maybe for a repo where you build the code, but this is just my manual site and a single preview page with links to files that I have added to the repo, does a release make sense in that context?