BUG - misidentification of plugin presets

[aMUSEd]

This is odd - Waveform seems to think some plugins are something else - eg Both for both Rhino and Nemesis it is trying to load presets from Blue II

Screenshot 2017-04-07 16.55.48.jpg

[aMUSEd]

Ah I see what's happening, they are all in a folder of FM synths, evidently Waveform is going by the first plugin in that folder and somehow assuming that's where to look for presets. Would be useful I think to be able to predefine some preset paths for Waveform to look in like you can in Bitwig, on Mac at least plugin presets are very rarely in the same folder as the plugin (there are 2 system defined places, although not all devs see fit to use them).

[dRowAudio]

Well it looks in the two system places[1] and then also the directory that contains the plugin file as that's what seems to be common with VSTs.

[1] On the Mac these will be:
/Library/Audio/Presets/<ManufacturerName>/<PluginName>/
~/Library/Audio/Presets/<ManufacturerName>/<PluginName>/

Perhaps what's happening here is that you only have preset files for Blue2 in the directory containing the Nemesis Plugin?

[aMUSEd]

There's no presets for anything in that folder. Blue is just the first plugin alphabetically. Would be good if we could add a couple of custom paths to the preset locations (Nemesis for example puts its presets in a stupid place all of its own)

[dRowAudio]

So what appears under the sub-menu? I wonder if Blue has fxb files in it's .vst package somewhere.
Yes, it seems like having user definable options is the only way for these non-standard locations.

[aMUSEd]

Yes it appears to be looking inside the plugin itself - but there's just one bank (Introduction)

Amazingly when I click on it it actually manages to load into Nemesis without it crashing - but of course doesn't make a sound

Screenshot 2.jpg