Dear Christof,

Thanks for the resources!

Edwin 

On 2 Mar 2024, at 13:47, Christof Ressi <info@christofressi.com> wrote:


(taken it back to the list)

Do you have a suggestion for ambisonic plugins?
Here are some free and open source ambisonic plugins:

IEM plugins: https://plugins.iem.at/

SPARTA: https://leomccormack.github.io/sparta-site/

ICST plugins: https://ambisonics.ch/page/icst-ambisonics-plugins

Personally, I use the IEM plugins. One very nice thing about those is that they can automatically deduce the ambisonics order from the channel count. For example, let's take the following stereo encoder:

[vstplugin~ -e -m StereoEncoder 2 16]

Here I create it with 16 output channels, so the StereoEncoder will automatically output a 3rd order ambisonic signals

If I send the [channels 24( message to [vstplugin~] it will switch to 24 output channels and the StereoEncoder will automatically switch to 4th order.

If you want to change the ambisonics order of your whole patch, you just need to send the same [channels <n>( message to all your [vstplugin~] instances and the [send~]/[receive~]/[catch~] objects that make up your "ambisonic busses". (You don't have to do this for [throw~].)

Christof

On 02.03.2024 09:51, Edwin van der Heide wrote:
Dear Christof,

Very nice!

Do you have a suggestion for ambisonic plugins?

Best!

Edwin

On 1 Mar 2024, at 23:24, Christof Ressi <info@christofressi.com> wrote:



Hi,

I have just released [vstplugin~] v0.6.0! Binaries are already available on Deken (search for "vstplugin~").

The most important new feature is support for multichannel signals: a single input or output signal can now contain multiple channels. This is particularly handy for spatialization plugins with many channels, such as higher-order ambisonics. Not only does it save you from drawing lots of patch cords, it also allows you to change the channel count dynamically! For example, you can now freely change the ambisonics order without rewriting your patch.

IMPORTANT: previous versions would hide certain (non-automatable) parameters in VST3 plugins. This has been fixed, but as a consequence, parameter might have changed. [vstplugin~] prints a warning for every plugin that is affected by this change!

Here is the full changelog: https://git.iem.at/pd/vstplugin/-/releases/v0.6.0

Please test and report any issues at Issues · Pure Data libraries / vstplugin · GitLab.

Have fun!

Christof

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list