Does Sushi handle presets for VSTs?

Elk Audio OS Sushi
1

According to the Steinberg web site, managing presets for VSTs is theoretically the responsibility of the Host DAW. However I can find no discussion of this in the Sushi documentation. Is it supported?

https://developer.steinberg.help/pages/viewpage.action?pageId=9798267

2

Hi Larry, Sushi has rudimentary support for loading presets, but that is as far as it goes at the moment. There is no provision for saving presets from a running instance of Sushi yet.

For VST 2.4 plugins you can load those presets (programs) that are exported by the plugin, if any. Usually that means those that are build in to the plugin.

For VST 3 plugins, Sushi also scans the default locations (se https://developer.steinberg.help/pages/viewpage.action?pageId=9798275#VST3Locations/Format-PresetFormat under Linux) for *.vstpreset files and enumerates those.

1 Like
3

Thanks for the response Gustav. I don’t know what other people think but that would be pretty high on my list of desired features for the future. I no sooner get something cool set up than I want to save it somewhere.

DL

1 Like
4

This is also important for me!

5

We’re working on it and the next release of Sushi will have preset/state saving and loading in some form. It’s too early to say exactly how feature complete/comprehensive it will be though.

6

Thanks for the update, this is a very interesting!!

7

I’m reviving this old topic, since I can’t find docs on any of the above. I’d like to trigger presets for a VST3 via OSC, and I’m also interested in saving presets for a Sushi configuration. I don’t see in the docs or in the configuration dump that exposes all the OSC paths how either is handled. Is it possible?

8

Currently there are 2 ways of making a VST3 load presets at runtime:

  1. Using vst preset files as described in the post above, sushi will enumerate these if put in the default locations defined by the vst3 specs. Those can be changed by using the OSC interface, see details here Controlling Sushi using Open Sound Control — Elk DevKit documentation . Though there is no possibility to save presets this way.
  2. Using the gRPC api (or the elkpy or slkcpp wrappers) you can save and load a state, which is the full state of a plugin. See the set_processors_state() and get_processor_state() reference here: elkpy.AudioGraphController — Elk DevKit documentation This way you can both save and load presets at runtime, though you can’t access it directly over OSC, you would need some kind of bridge app than can take OSC and output gRPC.
9

Thanks for the details.

1 Like