Well, the core reverb algorithms are already in Csound, especially if
you include the new nested-allpass opcodes. My question is,  what makes
a configurable reverb? Most  systems I have seen offer high-level
parameters such as room size, absorption, echo density, and predelay.
These parameters impact on both early reflections and the dense
reverberation, but arguably most significantly on the former. And
certainly, without the use of early reflections, the current Csound
reverbs do not do quite enough. The Moorer 7-tap and 19-tap examples
work very well, but reverb really starts to cook when you have 40 to 80+
of them (more for smaller rooms).

I think an opcode to complement 'multitap', but taking data from a
table, would spring new life into the current reverbs. Most of the
configurability work would then need to go into the GEN functions to
create the reflection data (e.g. into distinct directional streams),
rather than to the reverb opcodes themselves. 

On the other hand, a reverb opcode that is both self-sufficient ~and~
fully-configurable could easily be rather enormous... 



Richard Dobson



Ed Hall wrote:
> 
> If you'd like to contribute the algorithms (or code) I'm sure someone
> on the list would be happy to opcodify it.  Csound sorely lacks a good,
> configurable reverb!  My only worry is that a complex configuration
> mechanism might wind up adding yet another oddball file format to
> Csound (even if it's based on something like XML).
> 
> As for OS wars, source code makes them irrelevant, one of the very nice
> things about Csound...
> 
>                 -Ed

-- 
Test your DAW with my Soundcard Attrition Page!
http://wkweb5.cableinet.co.uk/rwd