@ excalibur: thank you very much! it's not that i only want positive feedback like yours (although i'm very happy about that, haha), but a little feedback at all is not demanded to much, is it? .... anyway, thank's!
@ pulsed:
oh, my "transient detection" is that f'ck'n simple that i feel ashamed to publish it here, but for me it works pretty well:
every time a loop is loaded a tabplay~ will play the new loop. tabplay~ goes into a [env~] to put out the envelope followed values in db, this then goes into a [moses] where you can now set the threshhold, e.g. 75, so the smaller values go to the left outlet of [moses] wich then trigger a [0( message, the greater ones go to right outlet wich then trigger a [1(.
both message boxes now go into a [change] to avoid repetitive output of numbers. and then it goes into a [sel 1].... this now always sends out a bang, when the threshhold gets exceeded. now i only measure the time between the bangs with a timer, subtract it by 14 (this i figured out by try and error) to offset the markers and make a list of it. so i got a pretty simple peak detection and for me it works good enough. i guess for other loops than drumloops, bonk~ would be the better choice but also more expensive.
so here again:
[tabplay~]
|
[env~]
|
[moses] <--- here set threshold for peaks
| |
[0( [1(
| /
[change]
|
[sel 1]
|
[timer] <- feeded into its right inlet, the left must be
| banged immediately before tabplay~
now make a list with
or whatever.