benniy

i know this may be to vague to formulate a question but i'm kind of stuck at the very beginning.

my plan appears simple: i want every n-th (let's say third) note of a (midi-)sequence of eight notes to be routed

somewhere else than the remaining 7 notes.

i know this may be to vague to formulate a question but i'm kind of stuck at the very beginning.
my plan appears simple: i want every n-th (let's say third) note  of a (midi-)sequence of eight notes to be routed
somewhere else than the remaining 7 notes. 

routing-every-n-th-midi-note-to-somewhere-else

thanks so much — i've been spending a day with this (:

people like you make me feel ridiculous.
thanks so much — i've been spending a day with this (:


Don't feel ridiculous, I wasted my youth on this stuff. And, I think I messed it up -- this should work:

Don't feel ridiculous, I wasted my youth on this stuff.  And, I think I messed it up -- this should work:


i've actually found this mistake myself (*proud*)

your nice :) thank you.
i've actually found this mistake myself (*proud*)


you could try something with the 'cycle' object too

i'll lay my idea open and maybe you guys have an idea or could help me understand why what you did works :)

i'm basically simply trying to get the live-native arpeggiator a little more interesting.

therefore, my plan was to e.g. take every 3rd incoming note and delay it slightly (snyced or free in time).

i would like to keep it's original length, so i supposed i had to

1) make a note-counter (that bangs on eg every 3rd count)

2) have the current note of 3 reroute the current incoming note

3) leave this routing set until the note-off of this note passes through

how come the simple list-slicing works? i'm really new to lists -- isn't there a risk that depending on how many notes are played at the same time and/or how long these notes are, that suddenly the first slice of a list is no longer the one associated with the previously delayed note?

i'm sorry - this is really not well articulated.

i'll lay my idea open and maybe you guys have an idea or could help me understand why what you did works :)
i'm basically simply trying to get the live-native arpeggiator a little more interesting.
therefore, my plan was to e.g. take every 3rd incoming note and delay it slightly (snyced or free in time).
i would like to keep it's original length, so i supposed i had to
1) make a note-counter (that bangs on eg every 3rd count)
2) have the current note of 3 reroute the current incoming note
3) leave this routing set until the note-off of this note passes through

how come the simple list-slicing works? i'm really new to lists -- isn't there a risk that depending on how many notes are played at the same time and/or how long these notes are, that suddenly the first slice of a list is no longer the one associated with the previously delayed note?
i'm sorry - this is really not well articulated.


The Borax object handles noteOff's for you. The first outlet is an Event Number that is the same for the noteOn and noteOff for a given note. The voice allocation number is also the same for a pair of on/off events, although that voice number can be reassigned once it has sent a note off.

my coreservices have left me. i cant zip.

I'm at work so can't test it, but I think this should do the trick:

I'm curious - did my suggestion work for you?

sorry for not replying. i ended up using mzed's code (utilizing the borax object).

hei basvlk,
sorry for not replying. i ended up using mzed's code (utilizing the borax object).


routing every n-th midi-note to somewhere else