I ported Nozori modules

Plugins
1

Per request of @Nvgtr

All of the Nozori module line. They’re quite nice and CPU light but I didn’t test a ton of them. Let me know how you find them!

Download here: Nozori - MetaModule - Google Drive

Github:

VCV Rack:

7 Likes
2

Whoa…so fast. I’ll check these out! Amazing!!

1 Like
3

hadn’t really played with these ones before!! seems like a really big great set of modules, ty much for porting!!

1 Like
4

thank you a bunch will be playing with these today

5

It’s an interesting set of modules, all based on a hardware module that can run various firmware similar to the concept behind the Noise Engineering Versio/Legio platforms. Essentially it is a hardware module that runs software that has been adapted run as a software plug-in in VCV that has been now been ported to run on the MM hardware (…something like that).

6

Hi - trying these out, thanks very much. I’m into phase modulation VCOs at the moment, so dived straight into the Sin-PM module, great, and low CPU too (15% 48KHz, 256 block).

1 Like
7

I should have learned by now to read the manual. It turns out that some (all?) of these modules are designed to run at 96KHz (the same as the original hardware), and actually print a pink warning message at the bottom of the module if the sample rate is not 96KHz, which can be seen on the MM screen too. Not a problem for me, just wanted to point this out here in case this might affect your choice whether to load and run this plugin on the MM. It seems the modules still work at 48KHz etc but the behaviour may not be the same as the originals…

1 Like
8

I noticed this too. I didn’t hear anything out of the ordinary or unusable from my basic tests but I didn’t go through them all

@phommed
I can try to remove the warning test if it’s annoying. I just went through a few modules, they seem to be working fine at 48 khz, frequency range unimpacted etc. I’m sure you would be able to find a nuance with the original Nozori ones but we can consider these a charming variant if so :slight_smile:

1 Like
9

Also updated here @danngreen

I removed the warning UI from showing up - while it’s valid it’s complaining about 96khz I’ve not heard any issues with it, and it’s impossible to change on MM anyways

1 Like
10

BTW the release is for firmware 1.6, not sure if you meant that? The .mmplugin file in the metamodule-plugins/ dir in the repo is for dev-2.0

11

Not intentional, trying to do this again.

@danngreen - Do I have to make a new tag? Triggering another workflow on the same tag still pulls from dev12 firmware

12

Hmm… I think that actually is compiled with -dev-13. Looking at the workflow file, I hard-coded the “-dev-12” suffix to any plugin built with the v2.0-dev branch. Ooops…

So, you can just change that line to -dev-13. Or, github lets you edit the filename of a release file.
When v2.0-dev becomes main then we’ll need to edit that file again. I’ll update the template example in the sdk docs.

Just to be sure, I tried it and it runs on dev-13. Only tried the VCF_MOD but sounds good and all knobs and the switch work.

13

Ok, I updated the example script in the docs. I just took out the line about FW_VERSION and again where it appears in the mmplugin filename.

Now it’s a more sustainable approach: you just put the dev-13 or whatever you want in the tag:

git tag -a v1.0-dev-13 -m "First release for firmware dev-13, yay!"
git push origin v1.0-dev-13

That way as we upgrade, versions you don’t need to change the script.

1 Like