You may want to take a look at athenaCL's Python Csound orchestra generator.

Regards,
Mike

-----Original Message-----
>From: Tim Mortimer 
>Sent: Feb 14, 2008 3:39 AM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd] Re: Creating an instrument like a "class"
>
>
>This recent discussion about "an instrument class" was one i saw, & the
>wheels were already grinding deep inside the cesspit of my head on the
>subject, too deeply & primordially in fact to even consider making a comment
>at the time.
>
>All i want to say is that at present my take on it is rather than using a
>lot of macro's & opcodes etc etc, i'm looking at possibly simply having all
>the necessary elements of csound code reduced to Python string variables, &
>then hopefully the Csound orchestra can simply "write itself" on demand from
>the input score. (with the string variables having things like %d replaced
>with table numbers or expseg trajectories allocated as required..). 
>
>Hopefully this means longer term i can have the Class structure inherant in
>Python to organise my instruments & sonic modular elements (which are
>essentially just "slabs of csound code"), & I simply assemble the required
>.orc & .sco on demand, possibly even to the point of deleting the csound
>code again once the necessary audio &/or MIDI has been generated.
>
>Am I being trivial at this point? Has anybody else "gone to town" already
>with this kind of approach? it certainly overcomes any issues to do with
>requiring "variable length p fields" or the like, & many of my SDIF &/or
>Phase Vocoder type instruments tend to sooner or later be about the same
>types of things, they just require differing numbers of source data files,
>or ftables for masking etc etc... Hopefully this is a way therefore to make
>what is generic more, err, "generic", & takes the Class notion off to a
>Class based language that can handle it comfortably in the first place -
>laeving csound simply to execute the toppling of the dominoes once the
>scripting language has lined them up to be toppled...
>
>My "solution" to this therefore may be trivial &/or bleeding obvious - but
>to someone who might be bashing their head againt a Csound wall on this one
>(a sensation I am certainly familiar with) my idea of simply taking the
>"Class" notion off to somewhere suitably equipped to handle it in the first
>place may be worthy of consideration. For anyone not across Python at all,
>simply "generating text files" (essentially what i'd be doing in this
>scenario) is something you could get your head around very quickly IMHO...
>
>Anyway, as a wrap up, this seems like as gooder time as any to wheel out
>what is essentially a kind of "newsletter" on the state of play of my
>Parseval Python / Csound project i have drafted over the last few days, & i
>encourage anyone who is vaguely interested to take a look. 
>
>www.phasetransitions.net/parseval
>
>There was discussion back before christmas as to turning it into an Open
>Source project. All I can say is that i'm still having too many ideas of my
>own to let go of it at the mo, but hopefully at some point soon it will be
>stable enough to release the code in some form that people can see what kind
>of goodies (& baddies) are in it, & how much might be of use to others
>(particularly Blue users, as I'm still keen to potentially offer this as an
>"out the box" python object (sic) for use in that environment if that were
>to be possible...)
>
>
>
>
>
>-----
>*******************
>www.phasetransitions.net
>hermetic music * python * csound * possibly mindless ranting
>various werk in perpetual delusions of progress....
>
>-- 
>View this message in context: http://www.nabble.com/Creating-an-instrument-like-a-%22class%22-tp15292772p15475859.html
>Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"