The Living Thing / Notebooks :


a less irritating audio programming language

Cabbage Studio for Csound is an alarmingly modern experience
  for people used to the classic Supercollider_ UI,
  whose characteristic widget is
  ERROR: Message 'foo' not understood. RECEIVER: nil. *(sic)* Source: Cabbage audio

Csound is an audio coding language. It is Supercollider’s uncle by marriage. Actively developed. Eccentric. Permissive licensing. Smallish. Clean API. Thus, it works beautifully with other languages, which is unusual.

Learning resources

There are various books:



Check out this minimal invocation of the csound api.

#include "csound.h"
int main(int argc, char **argv)
  // Create Csound.
  void *csound = csoundCreate(0);
  // One complete compile/perform cycle.
  int result = csoundCompile(csound, argc, argv);
  if(!result) {
    while(csoundPerformKsmps(csound) == 0){}
  // Destroy Csound.
  return result;

You’ll need this API capability, because its interactive capabilities are, AFAICT, minimalist; a decent external sequencer is necessary for live work.

Csound committer Michael Gogins has put it to me that javascript is natural for this niche, and indeed, he has written a lot of code to this end.

Examples of various Foreign Function Interface invocations (lua, python, go) are in the manual. There is a repository of such examples, in fact.


There are a few confusing options and you have to track the release notes to grok the difference.

I recommend you ignore most of them.

Use ctcsound, which is newer, based on ctypes, and runs in python 3. It is clean and easy. Note you may need to compile the latest version of csound to use it. It includes a port of icsound, which makes things easy.

The older interfaces are placed by the csound installer in an idiosyncratic fashion into the system python 2 packages folder, which is asking for trouble and I don’t recommend it.

python import CsoundAC csound.load("c:/projects/csound5/examples/trapped.csd") csound.exportForPerformance() csound.perform()

It’s not clear to me yet how good this is for live control.

Moreover, python is, in turn, embedded in csound. Fractal infinite recursion left as an exercise.


Cabbage is a Csound frontend that provides users with the means to develop audio plugins and standalone software across the three major operating systems. While Cabbage makes use of underlying plugin technologies such as Steinberg’s VST SDK, ASIO, etc, Csound is used to process all incoming and outgoing audio. Cabbage also provides a growing collection of GUI widgets ranging from simple sliders to automatable XY-pads. All GUI widgets in a Cabbage plugin can be controlled via host automation in a plugin host, thereby providing a quick and effective means of automating Csound instrument parameters in both commercial and non-commercial DAWs.

IDEs, front-ends

There are in fact many frontends.

In addition to Cabbage, mentioned above,

A cross-platform composition-oriented front end written by Steven Yi in Java. The user interface provides a timeline structured somewhat like a digital multitrack, but differs in that timelines can be embedded within timelines (polyObjects). This allows for a compositional organization in time that many users will find intuitive, informative, and flexible. Each instrument and score section in a blue project has its own editing window, which makes organizing large projects easier. Blue can be downloaded at Blue Home Page.

CsoundQt is a versatile, cross-platform GUI (graphical user interface) which is bundled with the standard Csound distribution. Created and maintained by Andres Cabrera, QuteCsound provides a multi-tabbed editor, graphic widgets for real-time sound control, and an opcode help system that links to this manual.


Things I am currently reading: