Continuing the discussion from Elk Audio OS 0.9.0 (major SUSHI update):
Regarding the VST3 plugin:
It could well be that the uid is incorrect. Also likely, your plugin is not x-compiled properly, or (also very likely) the sub-folder structure is not as expected for VST3.
To figure out which it is do take a look at our example VST3 configurations if you haven’t already. Currently the examples using VST3 happen to be for Linux desktop, but may still be of help.
In the Sushi repo look at config_play_vst3.json, or in the elk-examples/mda-jx10-vst3 - both configuration files are identical.
Your path looks correct, but the uid, and perhaps the folder structure under SourceSamples.vst3 bears double checking. Look at the structure for the mda vst3 to check - these are part of the sdk.
The uid is the unique plugin name, which indeed may not be straightforward to deduce - many plugins can be in the same binary. For the MDA VST3’s I’ve gleaned them from the source code, in the mdafactory.cpp file, the fields labelled “name”.
As for the sensei config, our Blackboard examples are ported and verified to work with this release - is it a Blackboard you have? Then using these first will probably be a good step towards fault-seeking. The sensei log file should be appearing in /udata on your Elk Pi.
Ilias of Elk