[OSC_dev] Newbie looking for OSC <--> Kyma Tool (PCI) communication

[Kevin Cole]

Hi,

First, is there an IRC channel where OSC folks hang?

Second, I'm relatively new to OSC, but have managed to get a bit of
communication going between SuperCollider and a Kyma "Sound". I'm
trying to find out if Kyma "Tools" (*.pci) can also make use of OSC.
Specifically, I'd like a bit of code in Python or maybe SuperCollider
to generate a pulldown menu with simple choices e.g. "Dog barking".
When a user picks a choice, I want to pass a file path associated with
the displayed choice, e.g. "/Users/Kyma/Samples/dog-bark-356.aif" or
"Macintosh HD:Users:Kyma:Samples:dog-bark-356.aif" to a Kyma Tool as
something it can then make use of.

Is that possible?

Thanks.

[Matt Wright]

I’m not aware of any IRC channel.

Yes, your use case totally makes sense: OSC strings work for file paths.

Looks like the Kyma OSC documentation is here:

http://www.symbolicsound.com/cgi-bin/bin/view/Learn/OSCSoftwareDevelopers

Somebody should add this to http://opensoundcontrol.org/implementations

good luck!

best,
-Matt

Post by Kevin Cole
Hi,
First, is there an IRC channel where OSC folks hang?
Second, I'm relatively new to OSC, but have managed to get a bit of
communication going between SuperCollider and a Kyma "Sound". I'm
trying to find out if Kyma "Tools" (*.pci) can also make use of OSC.
Specifically, I'd like a bit of code in Python or maybe SuperCollider
to generate a pulldown menu with simple choices e.g. "Dog barking".
When a user picks a choice, I want to pass a file path associated with
the displayed choice, e.g. "/Users/Kyma/Samples/dog-bark-356.aif" or
"Macintosh HD:Users:Kyma:Samples:dog-bark-356.aif" to a Kyma Tool as
something it can then make use of.
Is that possible?
Thanks.
_______________________________________________
OSC_dev mailing list
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Kevin Cole]

Thanks Matt,

But I'm hoping for a Kyma expert here. (I've asked on the Kyma list
for an OSC expert and not gotten far, so I decided to try the
reverse.) I was using the page you mentioned along with:

http://www.symbolicsound.com/cgi-bin/bin/view/Learn/OpenSoundControlImplementation

Kyma has very precise definitions for "Sound" and "Tool". Loosely
speaking a Sound is one of Kyma's components that can be patched to
other components, and accepts parameters, and a Tool is a SmallTalk
script with delusions of grandeur, composed within Kyma's interface,
which speaks communicates with the Paca (TM) digital signal processor
box. Tools have some limitations, and it was suggested on the Kyma
list that I might be able to overcome those by using OSC.

Prior to about a month ago, I hadn't heard of OSC, and I'm not an
electronic musician -- though I toy with the idea of finally learning
how to get started with Raspberry Pi's and Arduino's and will probably
try doing something audio. (I'm a programmer helping a research
scientist doing audiometric / psycho-acoustics research.)

So far, I've been able to use SuperCollider to query a Kyma Sound
about itself, and send MIDI notes to some Kyma Sounds. But I haven't
understood how to use the "Arbitrary OSC Messages" referred to in the
link above, to send file paths to Kyma, and I don't even know where to
begin making a Tool speak or listen to OSC.

Does that help clarify the question(s)?