Transient extraction comparison

[rodrigo.constanzo]

@a.harker

2 - I don’t think that the debounce can go over the Block size. That might be something to improve in the interface or to revisit in terms of the design.

Hmm, that seems quite short then if that’s the case (and confusing in terms of the helpfile).

In the case of the patch I posted the block size is 512, so the AM I’m (think I’m) hearing would be faster than that anyways. It sounds to me like my memory of when there was no debounce at all and it was just crunching on/off all the time.

@a.harker

The transients here will be short and blippy. That is the nature of the algorithm and was a question we asked within the project “what is a transient” - I would probably take something longer as a musical item, but PA requested the blippy stuff, and that is what the declikcing is designed for.

Yeah I’m more in line with you if that’s the case. The bit that’s not ideal really is that hpss is way too long, and in fact sounds like a filter, rather than having a temporal impact on slices, and then the other option is the transients~, which I can see having a use, but it is super extreme for every day use.

I guess the first toolbox is already at “feature freeze”, but having some kind of control/parameter for how transient vs onset the extracted transients arewould be "flexible and powerful"™. (edit: made a feature request thread)