|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Flucoma Core||60||a month ago||68||bsd-3-clause||C++|
|Core algorithms and objects for the Fluid Corpus Manipulation Library|
|Flucoma Sc||60||a month ago||23||bsd-3-clause||SuperCollider|
|Fluid Corpus Manipulation plugins for Supercollider|
|Cbpsc||15||10 years ago||2||gpl-3.0||SuperCollider|
|Corpus-based Processing for SuperCollider|
|Corpusdb2||2||9 years ago||gpl-3.0||Python|
|Second generation of CorpusDB --- corpus-based processing for Python, SuperCollider, and beyond.|
This repository hosts code for generating the SC objects and documentation resources for the Fluid Corpus Manipulation Project. Much of the actual code that does the exciting stuff lives in this repository's principal dependency, the Fluid Corpus Manipulation Library.
Note that on macOS you may need to dequarantine the binary files.
CMake will automatically download the other dependencies needed
mkdir -p build && cd build cmake -DSC_PATH=</path/to/sc> .. make install
This will assemble a clean package in
An alternative to setting up / running CMake directly on the command line is to install the CMake GUI, or use to use the curses GUI
Also, with CMake you have a choice of which build system you use.
Unix Makefiles. On macOS you can also use Xcode by passing
-GXcodeto CMake when you first run it.
In some cases you may want to use your own copies of the required libraries. Unless specified, the build system will download these automatically. To bypass this behaviour, use the following cache variables:
FLUID_PATH: location of the Fluid Corpus Manipulation Library
FLUID_DOCS_PATH: location of
fluid-docsrepository (e.g. for debugging documentation generation)
EIGEN_PATHlocation of the Eigen library
HISS_PATHlocation of the HISSTools library
For example, use this to us your own copy of the Fluid Corpus Manipulation Library:
cmake -DSC_PATH=<location of your SC source> -DFLUID_PATH=<location of Fluid Corpus Manipulation Library> ..
To find out which branches / tags / commits of these we use, look in the top level
CMakeLists.txt of the Fluid Corpus Manipulation Library for the
FetchContent_Declare statements for each dependency.
The build system generally assumes an x86 cpu with AVX instructions (most modern x86 CPUs). To build on another kind of CPU (e.g. older than 2012) you can use the
FLUID_ARCH cache variable to pass specific flags to your compiler. For example use
-DFLUID_ARCH=-mcpu=native to optimize for your particular CPU.
For ARM, we use the following default set of flags (with the Bela in mind):
-march=armv7-a -mtune=cortex-a8 -mfloat-abi=hard -mfpu=neon
This will assemble a package in
Owen Green, Gerard Roma, Pierre Alexandre Tremblay
James Bradbury, Francesco Cameli, Alex Harker, Ted Moore
This project has received funding from the European Research Council (ERC) under the European Union's Horizon 2020 research and innovation programme (grant agreement No 725899).