This repository contains the community collection of unit generator plugins for SuperCollider.
An installation extends the functionality of SuperCollider by additional UGens that run on
scsynth, the SuperCollider audio synthesis server.
Please note that the UGens in this repository are, on average, less stable and well-maintained than the core collection. Use at your own risk!
Note: Extensions for the SuperCollider programming language are different. They are collected within the Quarks packaging system.
Unzip the release and move it to your SuperCollider extensions folder. You can find it by evaluating
in SuperCollider. To evaluate code in SuperCollder, put your cursor on the line of code and press
Ctrl+Enter. Alternatively, you may install the extensions system-wide by copying to
The folder might not exist, so you may need to create it yourself. You can do this in your operating system's file explorer or from within SuperCollider by evaluating:
On some operating systems, these directories may be hard to find because they're in hidden folders. You can open
the user app support directory (where the Extensions folder is) with the menu item
"File->Open user support directory". On macOS, you can open a finder window and press
Cmd+Shift+G and enter the
name of the directory.
Compile from source
Download both the SuperCollider source and the source for this repository:
git clone --recursive https://github.com/supercollider/sc3-plugins.git git clone --recursive https://github.com/supercollider/supercollider.git
Be sure to use
--recursive, or to initialize the submodules after cloning, otherwise you will not have files
that are necessary to build the project.
Like SuperCollider, sc3-plugins uses
cmake. Execute the following commands in the directory where you cloned sc3-plugins;
/path/to/sc/ with the path to the SuperCollider source directory. That will probably be
../../supercollider if you cloned both repositories in the same working directory.
mkdir build && cd build cmake -DSC_PATH=/path/to/sc/ .. cmake --build . --config Release # to install the plugins cmake --build . --config Release --target install
SC_PATH is provided the build system assumes the SuperCollider include files are in
On macOS, the plugins will end up in
SC3plugins folder to your Extensions folder (evaluate
Platform.userExtensionDir in SuperCollider to find it).
NOTE: on macOS, if you want to install into
CMAKE_INSTALL_PREFIX, you have to specify it by disabling the
IN_PLACE_BUILD cmake option which defaults to ON (see below).
Note for SuperCollider < 3.9.1 The Supernova server on macOS and Windows incorrectly searches for plugins in the
/Extensions/plugins directory. The scsynth server correctly searches for plugins in
/Extensions. If Supernova is unable to find the sc3-plugins, make sure that they are located in
See the README in
source/HOAUGens for information on compiling the HOAUGens (higher-order
- Set install target
- (default on linux
cmake -DCMAKE_INSTALL_PREFIX=/usr/local ..
- (default on linux
- Install in cmake build folder instead of
- (OSX ONLY, default=ON)
- Build the plugins as quarks
- (default 'OFF')
cmake -DQUARKS=ON ..
- Build supernova-plugins
- (default 'OFF')
cmake -DSUPERNOVA=ON ..
- Print all cmake options
sc3-plugins/build/$ cmake -L ..
If you get an error while building that files are missing, it probably means that you didn't clone all the SuperCollider
submodules. Fix this by running
git submodule update --init in the SuperCollider source directory. If you still have the
issue afterwards, try clearing your build directory and starting your build from scratch.
If something went wrong and you want to start from scratch, delete everything in the build directory that you made:
make uninstall # only if you ran `make install` before cd .. rm -r build
Adding plugins to the repository
A SuperCollider plugin is a collection of UGens (and their supporting files) with a shared prefix in their name. If you add a new plugin, please keep to the following pattern:
- Add a folder in the
prefixmeans whichever standard pattern in the file name you have for your UGens. All source files go into this directory and its subdirectories.
- SuperCollider-specific files (
.sc|.schelp|...) should be located in a subdirectory named
- If your plugin makes use of external libraries that should be part of the sc-plugins sources (e.g. via
git-submodule), add them to
sc3-plugins/external_libraries/. As an example, the
GlitchUGensplugin directory lists as:
- Add your folder to the
- For the Quark-installable option, there is a SuperCollider script called
sc3-plugins/quarks/. Evaluating it indexes the base directory of the extensions for each UGen, and Help-file in each plugin directory. It then creates a help file for your plugin that lists all classes and help files, as well as a
.quarkfile for your plugin in the
How to create a DiskImage (OSX)
To create an OSX DiskImage, follow these steps on an OSX machine:
mkdir build && cd build cmake -DSC_PATH=/path/to/sc/ -DOSX_PACKAGE=1 .. make && make install
The DiskImage will be generated in
- Note: the quarks
DIRECTORY-folder is also included by default.
How to create a tarball/zip-file
mkdir build && cd build cmake -DSC_PATH=/path/to/sc/ .. cpack -G TGZ # `-G ZIP` also works
The package will end up in
List of plugins
In addition to the plugins listed below, this project contains several FAUST-generated UGens for
higher-order ambisonics ("HOAUGens"), which are not built by default. See the README in
source/HOAUGens for more information.
An auto-generated list of what plugins are available in this repository, linking to the autogenerated helpfiles: