Michael Gounelas

I was wondering if there is any workaround to avoid clipping when using selector~.

I've come up with a solution that uses some short of very fast cross-fading, but the patch is rather complex for such a simple task, so any suggestions are more than welcome.

I was wondering if there is any workaround to avoid clipping when using selector~. 

avoiding-clipping-in-selector

On 18 mai 08, at 18:32, Michael Gounelas wrote:

> I was wondering if there is any workaround to avoid clipping when 

> I've come up with a solution that uses some short of very fast cross- 

> fading, but the patch is rather complex for such a simple task, so 

> hi,
>
> I was wondering if there is any workaround to avoid clipping when  
> using selector~.
>
> I've come up with a solution that uses some short of very fast cross- 
> fading, but the patch is rather complex for such a simple task, so  
> any suggestions are more than welcome.

you might also want to try Eric Lyon's clean_selector~ object

http://www.sarc.qub.ac.uk/~elyon/LyonSoftware/MaxMSP/

I think I'm gonna give a try to both objects, although I usually tend to use 'internal' objects wherever possible.

> I think I'm gonna give a try to both objects, although I usually tend

> to use 'internal' objects wherever possible.

Michael Gounelas schrieb:
> I think I'm gonna give a try to both objects, although I usually tend
> to use 'internal' objects wherever possible.

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


yes I know. However it looks like I'm getting the same results as with selector~.

I haven't tried the clean_selector~ object yet though.

here is a simple patch. Should this normally not produce clipping?

I haven't tried the  clean_selector~ object yet though.

> here is a simple patch. Should this normally not produce clipping?

matrix can operate in two different modes: binary and non-binary.

give matrix a third argument (1.) and send it a message "ramp 100".

This way it will create 100 ms fade on switching.

matrix can operate in two different modes: binary and non-binary.
give matrix a third argument (1.) and send it a message "ramp 100".
This way it will create 100 ms fade on switching.

On 18 mai 08, at 22:32, Michael Gounelas wrote:

> yes I know. However it looks like I'm getting the same results as 

> I haven't tried the clean_selector~ object yet though.

matrix~ have a non-binary mode which allow interpolation. The ramp 

message defines the interpolation time in ms. I simplified the routing 

> yes I know. However it looks like I'm getting the same results as  
> with selector~.
>
> I haven't tried the  clean_selector~ object yet though.
>
> here is a simple patch. Should this normally not produce clipping?

matrix~ have a non-binary mode which allow interpolation. The ramp  
message defines the interpolation time in ms. I simplified the routing  
too ;-)

much better now Emmanuel:) 
it works really nice!
thanks for your help..


avoiding clipping in [selector~]