giuliomoro
Brilliant!
I made a wrong assumption from the start, namely assuming the Bela cape OUT would be disabled once the audio expander caplet is in place (don't know where I got that idea from...).
Therefore thought numbering would start from 0 from the expander capelet.
So, to summarise, in case anyone were to encounter the same issue:
Channels 0–1 --> Bela OUT 0–1
Channels 2–9 --> Audio expander caplet OUT 0–7
And here the code:
s = Server.default;
s.options.numAnalogInChannels = 8;
s.options.numAnalogOutChannels = 8;
s.options.numDigitalChannels = 0;
s.options.blockSize = 16;
s.options.numInputBusChannels = 2;
s.options.numOutputBusChannels = 6; //enable 2 channels on bela and 4 channels on expander caplet
// Sound sampling and processing
s.waitForBoot {
"Server Booted".postln;
a = {Out.ar(2, SinOsc.ar(100, 0, 0.1))}.play; // play 100 Hz sine from expander caplet OUT0
b = {Out.ar(3, SinOsc.ar(150, 0, 0.1))}.play; // play 150 Hz sine from expander caplet OUT1
c = {Out.ar(4, SinOsc.ar(250, 0, 0.1))}.play; // etc.
d = {Out.ar(5, SinOsc.ar(300, 0, 0.1))}.play;
};
ServerQuit.add({ 0.exit }); // quit if the button is pressed
Thank you for your support so far.
To close up the issue I would like to ask one more question regarding one of the points I mentioned in the first post, I now gather that understanding this has nothing to do with outputting sound from the right channels!
By reading this document, I learned that there are two ways of running SC on Bela:
1. sclang
and scsynth
run on the Bela board, interaction via IDE (this is how I am working)
2. scsynth
running on the board by running sclang
within SuperCollider on a separate machine and communicating with Bela through OSC messages. I therefore assume that the document Compiling SuperCollider scsynth on Bela provides the required setup for working in mode 2.
I understand the principle but cannot link it to its potential applications:
Can I do most things in mode 1?
In which circumstances would working in mode 2 be an advantage?