Hi,

In the Changelog of vstplugin~ v0.5.4 it says ARM compilation is fixed though.

I think this refers to https://git.iem.at/pd/vstplugin/-/commit/ec1bb344512f1de6819cd2ca06fbfde793393326.

However, ARM support on Linux has been fixed only recently (https://git.iem.at/pd/vstplugin/-/commit/8cbdb1a971e2f4ac48953b9bc7be6370d42ea50f) and not merged into master yet.

Try the latest develop branch, people have successfully built it on RPIs.

@seb-harmonik.ar said:

@Obineg all of pd vanilla runs on 1 thread (well, the 'core' non-wish process anyways)
Message processing is simply interspersed w/ audio processing.

Almost. Pd does use a single thread for DSP and message processing, but this is not the same as the audio callback (unless "use callbacks" is enabled), so you have (at least) two threads.

Side note: In Pd, the audio callback does almost no work; it just reads/writes samples from/to a ringbuffer and returns. Pd's main thread waits on the ringbuffer (see sys_send_dacs), so it is indirectly (asynchronously) driven by the audio callback.

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

Hi!

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.

PSA: comport v1.2 has 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 [set foo( to [tabwrite], set is the selector.

another option is [iem_receive] from iemlib.

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.

Hi,

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
• new update message, 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

Have fun!

Christof

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.

Hi,

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.

Please upgrade!

As always, please report any bugs at: https://git.iem.at/pd/vstplugin/-/issues

Christof

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.