Organelle~ running csound

Csound works obviously though you can pac-man install it and start hacking away or play with some design patches so you have choices


What is the price of entry for access to csound on your patreon?

It’s tiered like all patreon and after next month it’s being revised to include Custom ETC, SuperCollider M4L and Organlle patches. We have a set of ETC pygame modes that are just astounding.

Send me a PM and i’ll get you some fun free pd/csound patches to play with with csound that get you going

Hello shreeswifty!

I would love to be running my Csound instruments and effects on my organelle M.

  • can you help me get things rolling?

Can I just run things as .csd files?
Do I need to use the csound6~ opcode and convert things into PD patches?

I would appreciate your advice and what you might be able to share.

Is there an installer?

Hope you are well. This is exciting news. I do love the Organelle M. Awesome.

Dr.B. (csounder)

Hello thetechnobear,

I don’t know if you ever created the Csound installer for the Organelle.

  • I hope that you did.

I love the Organelle M and I would love to be using Csound on it directly.

Any advice that you could offer would be great.

  • and, not only would I use it, but I would be using it to teach Csound at Berklee
  • I already show and use the unit in my Circuit-Bending class there and in my DSP class too
  • And, I have recommended it to many.

I just found out today, from my chairman Michael Bierylo, that you or others at Critter and Guitari are running Csound on the Organelle M. Hope so. And hope that there are some examples that you or others might be able to share about the process and about their progress.

Dr. B. (csounder)

I think Csound is already installed on the latest Organelle M OS, but I’ll have to double check… There should be a minor OS update coming soon anyway with some small fixes and I’ll take a look at the Csound situation too if it isn’t installed already.

Thanks! Please keep me posted. It’s a fantastic platform that will be even more amazing with Csound inside!

Dr. Richard Boulanger
Electronic Production and Design
Berklee College of Music

1 Like

I just wanted to bump this thread and see if there are any news?

Like the esteemed Dr B above I would love to run Csound on the organelle.

In fact, I hooked up the organelle to a monitor and kbd and found Csound installed, and after a bit of searching found the example csd files on there too, so I have already successfully run Csound playing the obvious first-try composition Trapped in Convert by none other than the famous @csounder himself. Success!

But I would really like to interact with Csound using the keyboard and knobs/buttons. Csound has excellent OSC support, so if there is a list of OSC adresses for the keys, knobs and display, that would really be easy.

The thing that remains would then be to be able to start Csound like a patch from the menu. Maybe a small c++ program utilizing the Csound lib and pointing to a simple default csd file would be a way? Unfortunately I’m not a programmer, so I wouldn’t know how to do that…


You can get the Organelle to run things other than a Pd patch by creating a patch folder and inside place a So it would look like this:

    Csound Synth/
        csound and other files ...

It would show up in the Organelle menu as ‘Csound Synth’ and it would execute the file when you selected it. So in the is where you want to start Csound and do whatever configurations.

The best place to understand the OSC messages being sent and received is in the mother.pd patch that opens with any Pd patch. You can download the mother.pd patch here

Also look at the Graphics Demo patch that has OSC messages for controlling the OLED screen.

I wonder how to most easily handle shutting Csound down when switching to some other patch?
It seems the overall main.pd or similar is running because when I turn the encoder knob I immediately scroll through the patches and other items, but when I press the encoder to choose e.g. a synth patch, Csound is still running in the background. I could add a kill command to my script, and then restart when Csound shuts down, perhaps?
But what process should I kill when starting csound?
…or I could try to trap the signal to the dash script. The question then is what signal is sent to kill the script?
It doesn’t seem to be SIGINT, because when starting manually from terminal, Csound automatically quits too, when pressing ctrl+c to quit the script, but when turning the encoder and choosing some other patch, the script quits, but Csound keeps running. So it is most likely some other signal. I hope it isn’t SIGKILL because that cannot be trapped.

EDIT: It is SIGTERM that’s being sent. Now that I actually bothered to learn some more about how shell scripts behave, I managed to trap the SIGTERM signal and shut down csound. Now for some proof of concept sound generation.

Well, here is a proof of concept for Csound running (without using the Csound pd wrapper) on the organelle m.

My script contains

#!/bin/bash -e

cleanup() {
  kill $(pidof csound)

trap cleanup TERM HUP INT

/usr/bin/csound organelle.csd > /dev/null 2>&1 &

wait $(pidof csound)

and the accompanying csd file (organelle.csd in this case) contains

-odac           -iadc     -d     

sr      =  44100
ksmps   =  128
nchnls  =  2
0dbfs   =  1

; Organelle OSC -> Csound inbound messages port 4000
;    /key ii 
; keys send two values - the key number (0-24) and the key value (0 or 100)

;    /knobs iiiiii 
; knobs have vaules between 0 and 1023
; Csound -> Organelle OSC outbound messages port 4001
;    /led i
; the led accepts values between 0 and 7:
; 0=off
; 1=red
; 2=yellow
; 3=green
; 4=cyan
; 5=blue
; 6=magenta
; 7=white
; Lines of text and values can be sent to the oled screen:
;    /oled/line/1
;    /oled/line/2
;    /oled/line/3
;    /oled/line/4
;    /oled/line/5
; There is also the /oled/vumeter OSC address, as well as /oled/gSetPixel and other versatile functions to explore
; which can be found in the graphics demo patch at
; From that demo patch we can identify an address for clearing the screen: /oled/gClear 
; the inputs of which seems a bit unclear but two integers 3 and 1 seems to do the trick (copied from the demo patch).

gilisten OSCinit 4000   ;keys and knobs send OSC data on port 4000
                        ;the display and led receives OSC data on port 4001

turnon 1

        instr 1
        gkkey1 init 1
        gkkey2 init 1
        gkkn1 init 1
        gkkn2 init 1
        gkkn3 init 1
        gkkn4 init 1
        gkkn5 init 1
        gkkn6 init 1

kmsg    OSClisten gilisten, "/key", "ii", gkkey1, gkkey2
kmsg2   OSClisten gilisten, "/knobs", "iiiiii", gkkn1, gkkn2, gkkn3, gkkn4, gkkn5, gkkn6

        OSCsend     kmsg+kmsg2, "", 4001, "/oled/gClear", "ii", 3, 1
        OSCsend     kmsg+kmsg2, "", 4001, "/oled/line/1", "sisi", "KEY", gkkey1, "VOLUME", gkkn5
        OSCsend     kmsg, "", 4001, "/led", "i", 7*gkkey2/100

gic     = 440/2^(9/12)

kcps    = gic*2^(gkkey1/12)             ;the first key value is the key numeber
                                        ;from 1 (low c) to 24 (high b)

kamp    = 0.01*gkkn5/1024*gkkey2/100    ;knob5 is the volume knob
                                        ;the second key value toggles
                                        ;between 0 and 100, lika a simple
                                        ;velocity level

a1      vco2 kamp, kcps                
        out a1, a1                         


I hope this is useful for someone!


1 Like

Thanks for sharing this!

1 Like

I think I have a my upcoming rainy summer days covered right here…

One question though for @oweno or @chrisk

Is there an easy way to “trap” the encoder knob? I notice that some patches make use of the encoder wheel to flip between parameter pages, but others just scroll through the patches list, which is also what my Csound patch does right now. It would be great if I could use the encoder to choose parameters and such, and then hand back to the “mother” patch/program through some “home” menu item like some patches do (“edrums” comes to


You may want to check out patches that use the ‘Aux Button Menu’ to select pages. This is achieved by holding Aux and pressing one of the 10 ‘black’ keys. For example, the right hand column of the Zample patch selects pages.

1 Like

The following OSC messages help with this:

/enablepatchsub 1

This enables encoder usage in your your patch. The encoder values are then received at:


Then your patch (pd or csound or whatever) is responsible for sending this message to get back to the main menu:

/gohome 1
1 Like

Thank you both @chrisk and @oweno!!!

The subpatch and gohome was exectly what I was hoping for, but I may just have use for the auxmenu as well - I think the combination can be really powerful.

Thank you again, and thank you for your great work with this wonderful machine!


hi I’m back and will be hacking some csound stuff again on M


Yes! Awesome. Thanks so much. Dr.B.


I have good experience using csound with the csound6~ object in PD. Until now it has been pretty stable for my use, though it’s not that reliant when sending MIDI to it. Would recommend it for FX etc.

I’m trying to get csound running from within pd via the csound6~ object.
For that I need to install the pd-csound package.
I’m trying to do this via “sudo apt install pd-csound” but getting a lot of errors with respect to different things (see screenshot). Not sure what the problem is here and where to start.

The following solved the above issue I had:

  • Somehow the problem of resolving the did not happen anymore after turning off and on the Organelle and connecting again to my network/router and turning vnc on.
  • Run /home/music/fw_dir/scripts/ before trying to install csound-pd and after that run