Ah I see. What is the result of the filtering? Do fewer CC messages get through?
In plugin chain, any plugin/device behind any VST3 doesn’t receive MIDI CC. Perhaps CC#1 (modulation wheel) isn’t filtered, but other CCs are blocked. I don’t have tested all, however…
If you’re using Bitwig maybe try the new CLAP version?
Windows 10.
The CLAP plugin isn’t detected by Bitwig Studio (I’m using lastest 4.4.3).
Not sure, but the development team know about this issue (I think I have read this info somewhere in community).
ah ok, must admit I’ve yet to try it. I’ve not done much with VCV last week or so, too busy at work.
I just got the release notes for the latest Reaper and 6.7.1 is supposed to have CLAP support too.
Edit: nvm, tried to load it in Reaper and it failed.
That’s on Win 11 Pro, Ryzen 9 5900XI appreciate that VCV Rack is a way more complex plugin than my other CLAP plugins, but it’s the only one that has failed to install, 6 others work fine.
FWIW I tried it both in the default CLAP path and a bespoke one and no joy with either.
VCV Rack CLAP crashes on REAPER 6.71 (during launch / plugins scan process) - other CLAP plugins I’m using seems okay (Dexed 0.9.7 Beta Nightly, Vital, Filterjam, TAL Reverb 4, Odin2, Surge XT, Diva demo).
Can be translated as: Process entry point … can’t be found in link dynamic library C:\Program Files\Common Files…
Notice the VCV Rack CLAP plugin is automatically discarded by Bitwig Studio (either 4.4.3 or 4.4.4), no error message, but VCV Rack isn’t visible from CLAP plugin browser.