Handling VST3 plugins with automation parameters not in the list

[PB-fr]

Does Bitwig have any means of accessing parameters that don't appear in the list (seems to be limited to about 75?)? I have a VST3 plugin (S-Gear3) which is my mainstay plugin for my guitar rig, but I fear I may have run into a show-stopper as far as migrating to Bitwig is concerned as the SG parameter count goes way over 75.

I can't see any option in Bitwig where you can select which you parameters you want to use from a plugin (unlike the Live "Configure" option) and S-Gear 3 doesn't allow any de-activating of parameters on the "inside" either (unlike a plugin like NI Guitar Rig), so it feels like a dead-end.

Can anyone confirm whether there are any ways around this apparent limit?

[Kirkwood West]

Does Bitwig have any means of accessing parameters that don't appear in the list (seems to be limited to about 75?)? I have a VST3 plugin (S-Gear3) which is my mainstay plugin for my guitar rig, but I fear I may have run into a show-stopper as far as migrating to Bitwig is concerned as the SG parameter count goes way over 75.

I can't see any option in Bitwig where you can select which you parameters you want to use from a plugin (unlike the Live "Configure" option) and S-Gear 3 doesn't allow any de-activating of parameters on the "inside" either (unlike a plugin like NI Guitar Rig), so it feels like a dead-end.

Can anyone confirm whether there are any ways around this apparent limit?

unlike live configure option Bitwig actually shows you all available parameters in a searchable list. It also shows you the last parameter touched in the vst gui.

Screenshot 2024-07-18 at 8.23.49 AM.png

plugins that have modular parameters like vcv rack, guitar rig and reason seem to manage great in bitwig. They use a parameter pool and update the names, values and display values.

VCV Rack 2 is a shining example of implementing this. VCV Rack for example has 1024 available parameters to shuffle for mapping. And a great plugin within Rack like Surge XT implements proper parameter values and display values: like frequency or filter type.

From there what I do is make a preset with the parameters i want to manipulate for that patch.

Screenshot 2024-07-18 at 8.23.49 AM.png

[nowiamone]

Does Bitwig have any means of accessing parameters that don't appear in the list (seems to be limited to about 75?)? I have a VST3 plugin (S-Gear3) which is my mainstay plugin for my guitar rig, but I fear I may have run into a show-stopper as far as migrating to Bitwig is concerned as the SG parameter count goes way over 75.

I can't see any option in Bitwig where you can select which you parameters you want to use from a plugin (unlike the Live "Configure" option) and S-Gear 3 doesn't allow any de-activating of parameters on the "inside" either (unlike a plugin like NI Guitar Rig), so it feels like a dead-end.

Can anyone confirm whether there are any ways around this apparent limit?

This could also be a specific problem with that plugin. I'd highly recommend confronting its support email with that question.

I, for example, asked Audiomodern about Loopmix having ZERO mappable parameters handed out to the DAW. They answered that this is "intended", and when i want to map thing, i shall use the midi-mappings feature inside of Loopmix. Which is a real joke, imho, as this is completely redundant and tedious work compared to just handing out the parameters to the DAW... In your specific case (parameters being cut off above 75 it seems like a bug, or whatnot. I dont know )

loopmix.jpg

[PB-fr]

Thanks for the replies. It is indeed a problem with the plugin! It uses a mixture of static and dynamic parameters, and since the developer was having problems with the dynamic ones in Bitwig he chose to completely disable them for now - hence the very short list I am seeing. It should hopefully be sorted in the near future. I am very relieved to see that Bitwig doesn't have any of the restrictions that Ableton has!