Sean Costello wrote:
> 
>  I'm not sure what to call them, however. My first
> attempt is allpassn, 

> in the spectrum having independent controls over frequency, width, and depth.
> What would be a good name for this? phshift? phaseshift (is this too long)?

In one case there were reportedly complaints about long names,
the problem being that they destroy tabbing. The opcodes were
the "butter*p" set, and the solution was to provide aliases
called butbp, butlp etc. But now there are many 8/9-letter opcodes
around (and a couple of 10-letter ones), so you're safe around 
there somewhere. ((is phashift too witty maybe?))

You probably know that the initial letter should usually not be 
an a, k or i, as this disrupts the orchestra variable namespace. 
(If you call it alpassn you would normally risk having it renamed 
to eg lpassn or something, but this case would of course pass 
as there already is an alpass opcode...)

Keep up the good work!