Hi all,

As I write bigger and bigger things in CSound I'm looking to
organise things as best as possible. For instance, in order
to reuse instruments and UDOs I might have:

      my_udo.udo
      my_inst.inst

which are accessed from one or more CSD files using #include:

      #include "my_udo.udo"
      #include "my_inst.inst"

The problem occurs when either the UDO or the instrument require
a function table. Part of the problem is that function tables are
identified by numbers.

How do people organise these things?

Wouldn't it make sense to have one or more of:

  - Named function tables, possibly with a way of doing a 
    function table name to number lookup during the CSD parse
    stage.

  - A way to specify function tables in the orchestra rather
    than the score.

Obviously the older functionality can be kept for backwards
compatibility, but it would be nice to clean this up for
people writing new pieces.

Erik
-- 
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

hi erik -
what about using ftgen statements in the orc header with 0 as table
number (=let csound assign the number)?
	joachim

Am 04.02.2011 11:16, schrieb Erik de Castro Lopo:
> Hi all,
> 
> As I write bigger and bigger things in CSound I'm looking to
> organise things as best as possible. For instance, in order
> to reuse instruments and UDOs I might have:
> 
>       my_udo.udo
>       my_inst.inst
> 
> which are accessed from one or more CSD files using #include:
> 
>       #include "my_udo.udo"
>       #include "my_inst.inst"
> 
> The problem occurs when either the UDO or the instrument require
> a function table. Part of the problem is that function tables are
> identified by numbers.
> 
> How do people organise these things?
> 
> Wouldn't it make sense to have one or more of:
> 
>   - Named function tables, possibly with a way of doing a 
>     function table name to number lookup during the CSD parse
>     stage.
> 
>   - A way to specify function tables in the orchestra rather
>     than the score.
> 
> Obviously the older functionality can be kept for backwards
> compatibility, but it would be nice to clean this up for
> people writing new pieces.
> 
> Erik

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net