I did something like this a while back using one instrument that does
nothing but instantiates other instruments. I was building a sampler and I
didn't want any limitations on the number of samples I could capture, or
the number of sampling instruments that could be run at one time. I was
able to communicate and interact with each of my instrument
instances(classes if you like) through the named software bus. I would
keep a track of each instance by assigning it a unique ID so that changing
my on-screen controller would affect the correct instance only. All in all
it turned out to be quite a hack, I had to stop it in the end but the
basic prototype worked Ok and I learned a lot along the way. I can show
you the code if you like.
Rory.
> Hi there,
> As you'll remember i was working on a tangible interface (reactable) to
> control csound.
> The work at school was so hard and i had to give it a break. Now i'm
> workin'
> on it again.
>
> I wonder if it's possible to define an instrument like a class, so i'll be
> able to call it by using something like "new" statement in most
> programming
> languages.
>
> What I'm trying to do is exactly that, when I put an object on the control
> surface, I want it to create an instrument from a skeleton in real time.
> Conventional definition of instruments like "instr 1", "instr 2" and etc.
> causes some kind of limitation. I want it to be more flexible.
> Thank you.
>
> --
> Arda EDEN
> Cumhuriyet University
> Faculty of Fine Arts
> Department of Music Technology
>> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"