Now in CVS and in manual (as soon as commit finishes).  At present
limited to i-rate window, but might alter if there are requests.
==John ffitch

------------------------------------------------------------------------------

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have been thinking about th emedian filter.  At present the window size
is irate, but I can see how to make it k-rate at a cost, and an additional
i-rate argument for the maximum window.  I can see how to avoid thi sis th
ewindow shrinks but not if it increates -- one has to maintain the last
max-window size values.

So, is it worth the extra cost?


> Now in CVS and in manual (as soon as commit finishes).  At present
> limited to i-rate window, but might alter if there are requests.
> ==John ffitch
>



------------------------------------------------------------------------------

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

>>>>> "jpff" == jpff   writes:

 jpff> I have been thinking about th emedian filter.  At present the window size
 jpff> is irate, but I can see how to make it k-rate at a cost, and an additional
 jpff> i-rate argument for the maximum window.  I can see how to avoid thi sis th
 jpff> ewindow shrinks but not if it increates -- one has to maintain the last
 jpff> max-window size values.

 jpff> So, is it worth the extra cost?

having received numerous requests... well 2 actually... I have change
the opcode to have a k-rate window size.  Code in CVS and manual CVS


==John ffitch

------------------------------------------------------------------------------

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net