Will work on it, thanks!

I’m looking forward to Thierry’s input. In the meantime, you might be interested in this: One of my Facebook colleagues, https://www.facebook.com/dick.valentine, just put up a Supercollider example video, along with a description of his patch.

Cheers,
–Bob

Hi there,

Bob pointed me to the forum here after I posted my first (ever) IanniX/SuperCollider example at <<https://www.facebook.com/video/video.php?v=2115690658718>>. My goal in constructing the patch was simply to figure out how to to use the two software capabilities together. I posted the example with the hope that it would be useful to demonstrate the minimum conditions for making it work. So with Bob’s encouragement I’m submitting some details here.

My researches suggest there are three basic approaches to using IanniX together with SC:

1. Communicate to the SuperCollider server directly from IanniX. SCserver listens on port 57110, but it’s vain to send just any commands there. The IanniX score must emit commands recognized by the server, documented exhaustively at <<http://supercollider.svn.sourceforge.net/viewvc/supercollider/trunk/common/build/Help/ServerArchitecture/Server-Command-Reference.html>>.

My example is a beginner’s effort. It seemed simpler to start with one of the scores in the IanniX distribution.

2. Use a IanniX-distributed score (unchanged) to communicate with an intermediate environment (say Processing or pd or Max), drive SuperCollider from there. A lot of flexibility might be latent in an approach like this, but it’s just a little too Rube Goldberg for me.

3. Communicate to the SuperCollider language from IanniX. SC has library objects for this, in particular OSCresponderNode filters incoming OSC messages by command. I get the impression SC developers intended to make this the preferred, or anyway easiest path.

OSC is a foundation capability in SC. SCserver and SClang use it communicate with each other. Traffic between the two is constant when the server’s running, but normally invisible to the user. Observe the traffic in the server with s.dumpOSC.

SClang cannot be directed to listen on an arbitrary port number. It has a listening port open (51720, unless it found that one in use on startup), so that’s the port IanniX messages should be directed to. The IanniX distributed scores talk on 2001, so I changed that to 51720. It can also be made an input parameter, like “number of circles” etc.

A SynthDef should be loaded in the server for the score to activate and interact with. My example uses a Karplus-Strong plucked string implementation. All that’s needed then is to start an OSCresponderNode listening. The SClan code is short and quite simple:

g = OSCresponderNode(nil, ‘/trigger’,
{ |time, responder, msg|
var pitch, octave, triggerIndex = msg[1];
var scale = [ 28, 29, 31, 33, 35, 36, 38 ].midicps;

note = scale[ triggerIndex % 7 ];
octave = (triggerIndex / 7).floor;

Synth(“KSpluck”, [ pitch, note*(2**octave), amp, 1.5]);
}
).add;

This responder is now listening for trigger messages, calculating pitches based on trigger_id (in msg[1]) and instantiating a sounding Synth for each one.

That’s about it for the highlights. I’m pretty excited about getting this to work, there’s so much potential latent in the objects that IanniX affords. Thanks you guys for a nicely thought out piece of software!

–Dick Valentine

Very nice writeup, Dick. It tempts me to consider taking up Supercollider. However, I’ve been fooling around on the periphery of Pd and Max for a decade and still haven’t gotten past novice stage there!

Cheers,
–Bob

is it possible to have a look at your KSpluck synthdef aswell?

thanks a lot for the help! 😉

Inspector > File inspector > Scripts & Styles > Current project

Double-click “New script”

@Guest wrote:

another question how do i show up the script editor for a new document ?

Cheers,
–Bob