Oli Mason

(Ive tried to post this once but it didn't seem to show up in the forum, so apologies if it repeats.)

Ive got an automated loop slicer working pretty well but am getting some pops and clicks,

I understand whats causing them but are unsure how to remedy them.

I assume i need some kind of envelope or ramp at the start and end of each slice but I'am not too familiar with the MSP objects so am not to sure where to start, [line~] seems like it might be useful but i can't get it to work!

so any advice on what objects to start messing with or any other input will be appreciated,

loop-slicer-popsclick-problem

There's a lot of ways to do this sort of thing. First up I would look at the grooveduck patch in the examples folder. Then search the forums as there are a few threads on clicks pops, ducking envelopes etc.

Trapezoid is one of the easiest ways to do a grooveduck also. I think the thing here is that you are triggering the loop point changes via the transport so whatever system you decide to use needs to be relative to the beat. I don't know if in this case trapezoid will do it but it might be worth trying.

insert [trapezoid 0.1 0.9] between the loop sync output of groove and the righthand inlet of the [*~] before the DAC.

Also I think [select] takes multiple arguments so you don't need more than one in your sub patch.

Also Also I don't think you can insert $1 as an argument in an object. If you want it to accept floats put 0. otherwise leave it blank.

There's a lot of ways to do this sort of thing. First up I would look at the grooveduck patch in the examples folder.  Then search the forums as there are a few threads on clicks pops, ducking envelopes etc. 

Also I think [select] takes multiple arguments so you don't need more than one in your sub patch.
Also Also I don't think you can insert $1 as an argument in an object. If you want it to accept floats put 0. otherwise leave it blank.


Loop Slicer Pops/Click Problem