@Balwyn Oh you need to setup special receive objects to create plugin parameters:

https://wasted-audio.github.io/hvcc/getting-started/patching/
https://wasted-audio.github.io/hvcc/generators/dpf/

@Balwyn Eh?

Probably because we don't sign binaries on Windows.

Also: who still uses McAfee? o.O

I could also export it with the heavy compiler, but the effect is really silly

@Orangery You have to install plugdata and open the pd patch from there.

@Orangery oh so it only supports VST2?

Yeah plugdata only comes as VST3, LV2 and CLAP versions.

If you use compiled mode in plugdata (which uses the Heavy Compiler, as I said earlier) you can export VST2 plugins as well, but you have to make sure you use compatible objects.

@Orangery plugdata already runs as a VST3 plugin. So you can just open the script/patch inside of that.

@Orangery said:

What is heavy?

Then what do you mean with "compile"?

@Orangery said:

I spent about 45 minutes with ChatGPT but there were still issues.

Not sure why you'd expect otherwise

You didn't mention that you need this patch to be compatible with Heavy, always good to mention beforehand.

Maybe share your patch so we can all tell what you're trying to do?

yes, but with some limitations: https://wasted-audio.github.io/hvcc/getting-started/patching/#known-limitations

@rewindForward said:

I'm using Plugdata in compile mode, so expr~ isn't available.

If you are on the latest toolchain release it is (mostly) available!

In the next release of plugdata (or the current nightly build) the warnings for expr/expr~ will be gone as well, but the toolchain will already work. So just ignore the warnings for now