VSTPlugin v0.6.0 -- final release!

Resources Libraries and Quarks
1

Hi everyone,

I have just released VSTPlugin v0.6.0: v0.6.0 · Pure Data libraries / vstplugin · GitLab

It contains lots of bug fixes and improvements, so please upgrade!

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

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

Have fun!

Christof

18 Likes
2

hi christof!

i was trying to install Signalizer from
https://bitbucket.org/Mayae/signalizer/downloads/

but got this error:

probing /usr/lib/vst/Signalizer Linux VST 0.3.2/Signalizer.so... couldn't load! /usr/lib/vst/Signalizer Linux VST 0.3.2/Signalizer.so: undefined symbol: snd_pcm_hw_params_test_rate

do you know how can i fixed it?
thx in advance!!

igor

3

Looks like the plugin requires libalsa (for whatever reasons).

4

i have alsa-lib and pipewire-alsa here (i’m on arch linux)… :thinking:

5

i think its a plugin problem
[old, changed juce/cmake/gcc something that i just dont know :confused: ] –
thx anyway

6

I am now trying out the VCV Rack 2 plugin and it seems that the parameters are for some reason not accessible from the host. E.g. in Reaper or Max when a preset is open, there is a list of parameters automatable in the host (representing knobs on certain modules within VCV Rack), and the rest of the list are unassigned parameters (e.g. [75] Unassigned #0076 ()), which is correct. The list starts like this:

“Level (VCV Audio 2 [7964931035519306])”
“#1 (VCV VCO [2592833091119326])”
“Sync mode (VCV VCO [2592833091119326])”
“Frequency (VCV VCO [2592833091119326])”
“#4 (VCV VCO [2592833091119326])”
“Frequency modulation (VCV VCO [2592833091119326])”
“Pulse width (VCV VCO [2592833091119326])”
“Pulse width modulation (VCV VCO [2592833091119326])”
…

Whereas the VSTPluginController (in SC) only shows the list of unassigned param names and values as if the list wasn’t updated after opening the clean plugin with no modules - so all params are labeled as “Unassigned #XXXX”, except for the first parameter “0 Level (VCV Audio 2 [7964931035519306])”. I suppose this is a bug? It would be great if the parameters could be automated and would be at least updated based on the loaded preset, if not in real time (when the module gets added in VCV Rack).

7

Whereas the VSTPluginController (in SC) only shows the list of unassigned param names and values as if the list wasn’t updated after opening the clean plugin

Yes, VSTPlugin currently uses fixed parameter names.

It would be great if the parameters could be automated and would be at least updated based on the loaded preset

Please open a feature request: Issues · Pure Data libraries / vstplugin · GitLab

1 Like
8

Just checking in, curious if or when this could be implemented?

9

I want to implement this for VSTPlugin v0.7.0, but I can’t give a timeline… Definitely not before November.

1 Like
10

Hi, just curious if you have any estimation of an update regarding this?

11

Not really, I’m afraid. This is something for v0.7 and it might take a while. At the moment I’m too busy with other things.

12

When I boot the server, run my code in s.waitForBooth and load VSTPluginControllers etc I get a bunch of messages like this:

Timers:
                       General@info
                        Errors@warn
                       Sockets@warn
                 ServerSockets@warn
                 ClientSockets@warn
                         Mixer@info
                        Engine@info
                        Plugin@info
                         Async@warn
                      MIDISync@warn
                          UAPW@info
                          HBGF@info

What do they mean and is there a way to suppress them? I don’t see them if the server is already booted.
EDIT: The messages appear once after I boot the server and run my code. When stopping and re-running code without rebooting server, I don’t see them.

13

It appears to be only Universal Audio plugins posting this, so I totally understand if it is outside the realms VSTPlugin, which btw is great, thank you so much for this addition to SC.

This line causes \done to be posted after the message, so I could work around it if there is no way to suppress the messages.
VSTPluginController(x).open("uaudio_century_channel_strip.vst3", action: { \done.postln } );

The overlying issue is that the posting of these messages causes glitches in the code of different sorts.