Super Collider unreliably reading digital in pins?

rrvvzz

Seems like there's a problem reading digital inputs in SC?
I'm using a Salt with a Salt + expander, latest release of SC3 / SC plugins libs, and the bela-remote extension from: https://github.com/sensestage/bela-remote
I'm trying to control SC remotely through the SC IDE.

I ran scsynth with this command:

scsynth -u 57110 -z 16 -J 8 -K 8 -G 16 -i 2 -o 2 -o 2 -B 0.0.0.0

And I wrote a small script in SC to test:

(
{
	var tr3 = DigitalIn.kr(15);
	Out.ar(0, tr3 * SinOsc.ar(440))
}.play;
)

When running this script, sometimes SC correctly gates the sine wave, but other times it seems to be reading that the pin is always HIGH (I get a solid tone).

Any ideas here?

giuliomoro

can you clarify where you got your "latest release of SC3 /SC Plugins"? Is it the 3.11.2 I put up here https://github.com/BelaPlatform/supercollider/releases/tag/v3.11.2-bela ?

I have seen a weird pin number number warning recently and I am wondering if there is anything wrong with the build. If you could send me the full code you are running, that would greatly help me debug the issue.

rrvvzz

From the releases page on github.

root@bela:~# scsynth -v 
scsynth 3.11.2 (Built from branch 'develop' [4989ef982])
root@bela:~# sclang -v
sclang 3.11.2 (Built from branch 'develop' [4989ef982])
root@bela:~# dpkg -l sc3-plugins
ii  sc3-plugins  3.11.2 armhf  sc3-plugins built using CMake

Here's the full source:

s = Server.default;

s.options.numAnalogInChannels = 8;
s.options.numAnalogOutChannels = 8;
s.options.numDigitalChannels = 16;

s.options.blockSize = 16;
s.options.numInputBusChannels = 2;
s.options.numOutputBusChannels = 2;

s.latency = nil;

s.waitForBoot({
(
{
	var tr3 = DigitalIn.kr(15);
	Out.ar(0, tr3 * SinOsc.ar(440))
}.play;
)
});

I'm not sure about DigitalIn.ar vs DigitalIn.kr. *.kr in this context here (audio rate vs. control rate for a trigger input?)
I'm trying to run through the Bela IDE as opposed to connecting to the server remotely now.
*.kr gives this error:

DigitalIn error: digital pin must be between 0 and 16, it is -2147483648

*.ar gives no error, but also doesn't seem to be reading the pin.

giuliomoro

thanks I am looking at this right now. We had a similar issue in the past which I didn't manage to reproduce, hopefully this time I will!

DigitalIn error: digital pin must be between 0 and 16, it is -2147483648

This one was new, found and fixed it now.

rrvvzz I'm not sure about DigitalIn.ar vs DigitalIn.kr. *.kr in this context here (audio rate vs. control rate for a trigger input?)

the digital I/Os are sampled at 44.1kHz (just like the audio) so .ar gives you the full bandwidth.

rrvvzz

giuliomoro wow very quick thank you! Awaiting a new build 🙂

Should I expect the above code with DigitalIn.ar to gate that sine by the way?

by the way if you have a PR / commit on the sc repo I'd love to see the fix

giuliomoro

sorry food break

Release:
https://github.com/BelaPlatform/supercollider/releases

Fix commit:
https://github.com/BelaPlatform/supercollider/commit/c91c4980a14433bb575528367ba80e7c28360b4f

rrvvzz Should I expect the above code with DigitalIn.ar to gate that sine by the way?

Yes

HOWEVER the pin you are using (15) is not the right one for T3IN (which I think is what you are referring to by "tr3")? Channel 15 is T1IN (only the jack input, the switch is wired to pin 6). T3IN is pin 1(both the jack input and the switch)

Check out the full channel pinout here ("physical channel" column): https://github.com/BelaPlatform/Bela/wiki/Salt#salt-io
Or you could just look at the Salt/supercollider-quickstart example in the Bela IDE.