Hi,

I am happy to announce a new bug fix release for [vstplugin~] - a Pd external for hosting VST2 and VST3 plugins on Windows, macOS and Linux.

It is available on Deken (search for "vstplugin~").

Here is the full change log: https://git.iem.at/pd/vstplugin/-/releases

Please report any issues at https://git.iem.at/pd/vstplugin/-/issues

Have fun!

Christof

Here is a bug fix release for [vstplugin~] v0.5 (see https://forum.pdpatchrepo.info/topic/13507/vstplugin-v0-5-0).

Binaries are available on Deken or can be downloaded here: https://git.iem.at/pd/vstplugin/-/releases

If possible, please report any issues at https://git.iem.at/pd/vstplugin/-/issues.

Changelog

bug fixes

• VST3: fix silent multibus output (when using automatic channel distribution)
• Linux: fix crash when opening the editor in a sandboxed/bridged Linux plugin
• macOS: don't filter by empty extension when looking for binaries in plugin bundles (a few plugins use extensions like .bin)

improvements

• Linux: suppress stdout/stderr when checking the wine command and the wine host processes
• VST3: disable unneeded auxiliary busses, but still enable all main busses (otherwise some plugins would crash)
• bridge: redirect logging output from subprocess to parent process (useful for debugging purposes!)

There is an easy way to find out: ask them to explain the code!

I'm happy to announce the final release of [vstplugin~] v0.5.0 - a Pd external to load VST plugins on Windows, macOS and Linux!

Binaries are available on Deken or can be downloaded here: https://git.iem.at/pd/vstplugin/-/releases

If possible, please report any issues at https://git.iem.at/pd/vstplugin/issues or leave a comment here.

Big thanks to all my beta testers!

Change log overview:

• support for multiple input/output busses (VST3 only)

• [offline( method for better offline processing support

• Linux: allow to run 32-bit and 64-bit Windows plugins (via Wine)

• improve UI handling on all platforms

• [size( method to resize plugin UI (if supported)

• Linux: fix VST3 editor

• fix some race conditions (= better stability)

• fix broken transport methods for multi-threading

• fix bugs in VST3 preset reading/writing

• new -x (= exlude path) and -t (= timeout) flags for [search( method

See the release page for the full change log.

Have fun!

Christof

I'll check vb-audio.com but I think I will give a try to puredata aoo (audio over osc) external .

I'm not sure what your setup is, but at the moment Aoo only allows to interconnect Pd and Supercollider instances (over local networks or the public internet). You would still need something like Jack or vb cable to connect Pd and VCV locally, right? Or are some people using only Pd and some only VCV?

You can use the Jack ASIO driver.

Like iemlib's [iem_receive] or iemgut's [oreceive] ?

Note the following caveat with settable receives: https://github.com/pure-data/pure-data/pull/604#issuecomment-487890771

TL;DR: settable receives work fine most of time, but under specific circumstances they can crash Pd. Use with care.

I know that using send~ and receive~ introduce latency

Not necessarily. You can in fact force the receive~ to be scheduled after the send~, in which case there is no latency, just like with delwrite~ and delread~.

and am wondering whether using subpatches via inlet~ and outlet~ also introduce latency.

No, unless the inner patch has a bigger blocksize than the outer patch. In that case, the latency is the difference between the two block sizes.

Does send (without tilde) introduce any latency?

"latency" doesn't exist in the message domain. When you send a message to [send], it is delivered instantly to all receivers. There is no semantic difference between using [send] or patch cords.

Does using subpatches rather than one big page introduce latency?

No.

Generally: if you encounter issues with Pd, don't just complain on the forum (which only few Pd devs read), but rather file an issue on GitHub!

@oid

How exactly is one supposed to keep up to date on new features?

Read the release notes: http://msp.ucsd.edu/Pd_documentation/x5.htm#s1

The changelog is 12 years out of date.

Good catch. This needs to be fixed. Also, the change log should reside in the toplevel directory and not buried in the "src" folder. I'll make a PR on GitHub.

Usually, features can be discovered by browsing the help files. The problem in this case is that there's no real help file for "pd" messages. This needs to be done.

Anyway, "fast-forward" is a very useful feature. Before I've made an external called [batchrecord~] which achieved the same thing. I don't know if Miller became aware of it, or if it was just a coincidence. Either way, I think it's great that it's now part of Pd vanilla!

Christof