I have been thinking more about the virtual csound controller project, 
and thought of a couple of things that might ( eventually ) be good to 
address in the API. Please let me know if these are already possible.

Can the api check whether a table exists? And also how long it is? This 
could be important because presently trying to write to a non-existing 
table through an opcode crashes csound entirely. It would be nice if a 
virtual controller app could check whether the table the user wants to 
access is indeed there before making a call to the table. Or does the 
api handle attempts to write to a non-existing table more gracefully 
than the csound opcodes?

Ditto for instruments, is there someway to query csound as to the 
existence of an instrument? Also, it would be very nice to be able to 
find out how many instances of a certain instrument are active at any 
moment, and to be able to kill them off individually. I realize that 
might be a lot to ask, but it would sure be useful if it's not terribly 
hard. Ideally I'd love to see an ability to look at the number of 
current instances and kill off the oldest, youngest, etc, before adding 
a new one.

In addition, can the API replace/reload a table in it's entirety in one 
call? That would allow us to make really nice table editing and patch 
editing front ends with saved patch banks that could be loaded on the 
fly without turning off csound.

Thanks
Iain