Topic: Bass_vst wrongly reporting no editor on a VST plugin

[sveakul]

I have a simple 32-bit, VST-2 plugin that works in the MusicBee player when added (free open-source Wider32.dll from Airwindows), but it is impossible to bring up the interface in order to make adjustments.  The MB developer said that bass_vst.dll (ver. 2.4.1.2) is returning info that indicates the plugin has no config editor.  Yet below is the editor as shown by Foobar's new vsthost (a link to the plugin is below the picture).  Can this be fixed in bass_vst.dll?



https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg=

[jpf]

I believe that the control panel you pasted isn't provided by the VST effect itself but by foobar2000, as a way to adjust parameters on VSTs not providing a UI.

I noticed you (was it you?) complained about the same issue on the foobar2000 forum on 2022-11-21, saying that the UI was present until v .6 and is lost on v .7.

The MusicBee developer may want to add some sort of default UI for the UI-less VSTs if you show him/her the one foobar2000 provides.

I've included such sort of default UI in my VB6 audio apps (for personal use only). The code is quite simple and straightforward. bass_vst.dll provides all the info and parameters exposed by the VST. Besides, the foobar default VST control panel looks barebones. Infos like units (dB, Hz, %, etc.), default values, and human readable captions are missing on the sliders. The human readable name of the effect, the manufacturer, version info are missing. All those are provided by bass_vst.dll if the VST exposes them.

Off topic:
VST 2.x/3.x Adapter and other foobar2000's plugins would be really useful if supported by Bass. Specifically VST 2.x/3.x Adapter supports vst3 and allows 32 and 64 bit VSTs to be mixed on both 32 and 64 bit flavors of the host. Those are highly wished features. I don't know if it would be legal to use foobar2000's plugins for free, and if an adapter for them can be made for Bass, but it would be great if so.

[Falcosoft]

Besides, the foobar default VST control panel looks barebones. Infos like units (dB, Hz, %, etc.), default values, and human readable captions are missing on the sliders.

It's because the Wider32.dll plugin itself does not provide such information so the host can only show the raw float values without meaningful interpretation.

Otherwise jpf is right. According to VST 2.4 specification a GUI editor is an optional feature for plugins but providing a default interface for such "editorless" plugins is mandatory for VST hosts.
You can do this by:
1.Using BASS_VST_GetProgramCount() to get the number of programs provided by the plugin then loop through them and use BASS_VST_GetProgramName() to get the program names. BTW providing more programs are also optional for plugins. In case of Wider32.dll there is only 1 and it has no name...
2. After the above for each program you can use BASS_VST_GetParamCount() to get the number of parameters for the program then loop through them and use BASS_VST_GetParamInfo() to get the parameter name, meta info about iits value etc.
3.Finally you can use BASS_VST_GetParam() to get the value of a parameter and BASS_VST_SetParam() to set the value of a parameter.

[sveakul]

Thanks to both for the replies.  I have passed along the relevant info to the MusicBee VST host's developer.