[maxmsp] Re: Re: comb~ and alternatives

On 19 Apr 2008, at 18:59, Roth Michaels wrote:
>
> thanks for remembering to mention this.  Not necessarily a  
> "problem" (I've been known to use comb~ and tapin~/tapout~ for  
> slightly different processes) but it is good to know that when you  
> use comb~/teeth~ they could have different spectral effects.

not necessarily a problem, true - often it is desirable to have a  
high frequency rolloff.
but you can't control the filter effect independently since it is  
connected to the delay time setting, i.e. you get changing spectral  
results for different delay times.

>
> When I was looking at Volker's example, I noticed something that I  
> was unaware of.  Signal vector seems to be an issue setting delay  
> time for tapin~/tapout~ (see Axiom's suggestion to put it in a  
> poly~), but not for comb~.  Is comb~ one of the lucky objects that  
> can take delay times smaller than allowed by the signal vector?  I  
> guess I feel silly for taking signal vector precautions with comb~  
> in the past.

the sigvs limit is only a problem if you build the feedback path in  
max (tapin/tapout or send/receive stuff).
inside an external you have access to all samples of a vector.  
otherwise you couldn't build any useful filters, e.g.

>
>> finally, i got a delay external somewhere on my disk that uses
>> allpass-interpolation (osx only).
>> this is slightly more cpu intensive and not made for rapid delay time
>> modulation, but gives you 'endless' ringing without
>> any unwanted high frequency loss. kevin, get back to me, if you want
>> to try it.
> Also not Kevin, but would like to see that external ;)

for anyone interested in trying it, i've put a version + helpfile here
http://www.esbasel.ch/Downloads/MaxMSP-Objects.htm


volker.