hey fellow csounders
ive been enjoying for a while writing instruments that process audio and
are controlled by this cheep korg kontrol pad. now i'm discovering that
to use them all together, routing is really important. i'm looking for
some examples of realtime routing of collections of control midi and
audio signals and theier interfaces. snapshoting of the routing graph
would be really awesome. text representations at the console would be
super fine. anyone seen this in csound yet?

kelly

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Kelly,

I think it makes sense to use a table to hold the routing values, and
then write the table to disk for later recall.
A text interface beyond just a series of numbers would have to be
generated by hand, depending on your needs.
For Hadron states design I use the format
modulator to parameter scaing_value
for example
LFO1 to GrainRate 110
meaning that the LFO at maximum amplitude will affect the grain rate by +/- 110.

In a small routing matrix you may use something like:
k1, k2, k3, k4, k5 (read values from table)
kparm1 = kmod1*k1+kmod2*k2+...

For a big routing matrix, you can use the modmatrix opcode.
It will essentially do the same job as above but much significantly
optimized (less CPU usage).

best
Oeyvind

2015-10-29 6:49 GMT+01:00 Kelly Hirai :
> hey fellow csounders
> ive been enjoying for a while writing instruments that process audio and
> are controlled by this cheep korg kontrol pad. now i'm discovering that
> to use them all together, routing is really important. i'm looking for
> some examples of realtime routing of collections of control midi and
> audio signals and theier interfaces. snapshoting of the routing graph
> would be really awesome. text representations at the console would be
> super fine. anyone seen this in csound yet?
>
> kelly
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

thanks oeyvind, i will have a look at modmatrix and im excited to look
into the hadron source!

k.
On 10/29/2015 03:37 AM, Oeyvind Brandtsegg wrote:
> Hi Kelly,
> 
> I think it makes sense to use a table to hold the routing values, and
> then write the table to disk for later recall.
> A text interface beyond just a series of numbers would have to be
> generated by hand, depending on your needs.
> For Hadron states design I use the format
> modulator to parameter scaing_value
> for example
> LFO1 to GrainRate 110
> meaning that the LFO at maximum amplitude will affect the grain rate by +/- 110.
> 
> In a small routing matrix you may use something like:
> k1, k2, k3, k4, k5 (read values from table)
> kparm1 = kmod1*k1+kmod2*k2+...
> 
> For a big routing matrix, you can use the modmatrix opcode.
> It will essentially do the same job as above but much significantly
> optimized (less CPU usage).
> 
> best
> Oeyvind
> 
> 2015-10-29 6:49 GMT+01:00 Kelly Hirai :
>> hey fellow csounders
>> ive been enjoying for a while writing instruments that process audio and
>> are controlled by this cheep korg kontrol pad. now i'm discovering that
>> to use them all together, routing is really important. i'm looking for
>> some examples of realtime routing of collections of control midi and
>> audio signals and theier interfaces. snapshoting of the routing graph
>> would be really awesome. text representations at the console would be
>> super fine. anyone seen this in csound yet?
>>
>> kelly
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> 
> 

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here