Chris Cannam - 2014-02-26

Historically there were a few reasons I didn't do this --

  • The main plugin set available when SV was first released was the QM plugin set, but this was initially released under a more restrictive licence -- without any source code at all, in fact. So it could not be bundled. It was only later relicensed under the GPL.

  • Because there were few plugin sets available, and I wanted to encourage people to make more, I was keen to avoid making it look as if some plugins were "privileged" -- I wanted to give all plugin sets the same status.

  • SV was originally designed to be a single binary, not a directory or bundle (the Windows installer arrived very late).

  • Also, frankly, I didn't anticipate how much trouble people would have installing plugins (partly because my home platform is Linux and it's easy there). On OS/X it's hard to find the right directory, and on Windows it's hard to even know what the right directory is.

In an ideal world, even now I would much prefer to make it easier to install plugins than to start bundling them with SV -- although I would like to make a separate application (an "SV Mini") with some plugins installed and with instant access to the most common ones.

But in the absence of any good way to make it easier to install plugins (which seems possible but not trivial), bundling some might be a start.