beginners question: get notes of currently playing clip

[bennniii]

When using the send and receive functions if you include a "---" in front of the symbol name it becomes a local patch route. [s emptyslot] should probably be [s ---emptyslot], etcetera. The only global route you need is [s keyboardnotes] which then allows you to send information between different devices. What you did isn't wrong, it's just too broad in scope.

absolutely excellent! i was giving the send / receive objects weird names (like adding "0x" to the end) because i was afraid of a possible other patch in ones liveset that might conflict (:

This is a neat device idea! I was able to build a six note arpeggio structure and then substitute different chords with both clips and the keyboard in the second track. This might work nicely with PUSH since you could build the desired structure using the note step sequencer on the first track and then overlay any six notes that you want using the note mode on the second track. Nice work!

well.. it's working thanks to you (: !
the push thing is a really neat idea... i'll try that.. although one conflict comes to my mind: the live LOM doesn't offer a native readout of a clips notes (or at least i didn't find it); it can only read out "selected" notes in a clip.. (you'll see in the patch).. for that reason i initiated a very short "select_all_notes" (followed by "deselect_all_notes") in order for a list with notes to be created on every start of a (new) clip... this made it difficult to edit an active (running) clip — i dont exactly know why. you can give it a try: e.g. move a note of a running (track1-)clip. anyhow — maybe it'll work with push; indeed it'd be a very handy application. let's test that in the beta version (:

[clydesdale]

Your timing problem is opposite of what you think. When you press the play button your track 2 keyboard note is getting there too late. You can test this by nudging the first note of your track 1 clip to the right using Alt-RightArrow. Three nudges to the right and it starting picking up the note correctly for me. What you might try to do is add logic to check for the play button and add a small delay on the very first note only. Does that make sense?

[bennniii]

Your timing problem is opposite of what you think. When you press the play button your track 2 keyboard note is getting there too late. You can test this by nudging the first note of your track 1 clip to the right using Alt-RightArrow.

mh.. i don't really get that... this may be my lacking knowledge, but: i basically keep the keyboard(track2-)notes pressed all the time. so they should be "arriving" at track1 all the time, too. or?
when i press the keyboard notes and change the (track1-)clips whilst doing so, the first note is still left out. are you absolutely sure about your assumption?
my suspicion is, that the route-object receives its selector (=notes from the clip on track1 via LOM) too late and therefore doesn't pass the first incoming (midi-)note-ON from the clip / track 1.
reason for me to believe this is: if i have 2 clips in track1 which have the same first note, it works well. in my imagination this is, because the route-object's selector doesn't have to change as soon as the "new" clip is started.

Three nudges to the right and it starting picking up the note correctly for me. What you might try to do is add logic to check for the play button and add a small delay on the very first note only. Does that make sense?

it does, yes.. but this would also confirm my assumption: if we give the route-selectors more time to be initiated (ergo send the clip's first note-on to the route-object later), it works.

[bennniii]

i think i may have confirmed my suspicion..
if i pre-define the selectors of my route object (eg "route 80, 81, 82, 83") and make one or several clips playing these exact notes (= G#4, A4, A#4, B4) — it works fine.
the route object "immediately" knows how it should route (i.e. which note-ONs and -OFFs from the clip to let through).

therefore, it might actually be necessary to:
a) delay the first (midi!-)note coming the clip (track1) or
b) make some sort of buffer that stores the first midi note (from track1) until the clip-play-button is pressed (or rather "received" by the route object).

of neither i have a clue how to do so O:

edit: additional confirmation, far simpler than what i did before .. i connected a print object to the last route-outlet, which outputs any message that doesn't match — and there we go. the first note after every change of clip is output.