I've just put the vstplugin folder into the /extras folder
If by "vstplugin folder" you mean the source code, then this certainly doesn't work.
I have no experience with compiling, so was hoping to avoid that
Well, you definitely need binaries. But there is a way to avoid compiling from source: use one of the pre-built binaries https://git.iem.at/pd/vstplugin/-/releases
I was trying to get this to work in Purr Data, but don't seem to have had any luck.
"It does not work" is not all too helpful for an error report Can you give more details?
Also, please consider opening a ticket at https://git.iem.at/pd/vstplugin/-/issues.
comport v1.2has been released and is available on Deken. This issue should be resolved now. Please test!
would use their own selectors and that selectors would be a thing, but they are not and it does not help in any way
Selectors are used all the time. Every method - apart from float, symbol and pointer methods - starts with a selector. For example, if you send
setis the selector.
another option is
This feature seems trivial on surface, but it is really not. If implemented naively, it can crash Pd under certain circumstances. For a technical discussion, see https://github.com/pure-data/pure-data/pull/604. Making it safe would require some changes to Pd internals, see https://github.com/pure-data/pure-data/pull/849.
here's a new bug fix release for
[vstplugin~]- an external to load VST2 and VST3 plugins on all platforms. Please upgrade!
Binaries can be found on Deken (search for "vstplugin~") or here: https://git.iem.at/pd/vstplugin/-/releases.
Most important changes/fixes:
- fix crash with bridging + multi-threading (regression introduced in v0.5.1)
- bridge/sandbox: allow to write large presets
- cmake: add NATIVE option for native code generation
- cmake: support Apple M1 + x86_64 plugin bridge (see the README for build instructions); no official binaries yet
updatemessage, sent when several parameters have changed at once
Full change log: https://git.iem.at/pd/vstplugin/-/releases
As always, please report any bugs at https://git.iem.at/pd/vstplugin/-/issues
I guess there's no other way.
Here is the PR: https://git.iem.at/pd/comport/-/merge_requests/1
In the meantime, you can grab the following branch and build from source: https://git.iem.at/ressi/comport/-/tree/input-fix
Martin Peach (who wrote [comport])
[comport]has been written by Winfried Ritsch.
Funnily enough, someone else has already brought up this issue in the past (https://lists.puredata.info/pipermail/pd-list/2019-05/125271.html) and I even came up with a fix, but then forgot to make a PR . I found the git branch with the fix on my laptop, so I can do that later this day. Will post a link to the PR here.
here's a new bug fix release for
[vstplugin~]- an external to load VST2 and VST3 plugins on all platforms:
Binaries can be found on Deken or here: https://git.iem.at/pd/vstplugin/-/releases.
This release fixes a critical bug where
[vstplugin~]would fix crash when switching samplerate or blocksize while a plugin is loaded. Even worse, Pd would also crash when loading a plugin with
[loadbang]or as a creation argument at samplerates other than 44.1 kHz.
As always, please report any bugs at: https://git.iem.at/pd/vstplugin/-/issues