jarkob

I spent the last hours researching how to do this and just can't figure it out.

What I want is receiving messages in a track and route these messages according to the track number, and convert them to midi as input for the track.

The message is a list whose first argument is the "ch"+tracknumber and the following items represent the midi message.

This works "perfectly" fine when I do it like this:

The massive downside: I have to manually fill in the tracknumber each time I start up Live.

That is tedious, since I have around 40 tracks using each one of these MFL-patches...

Is there a way to automatically get the number of the track or the name of the track, so I don't have to do this?

It seems like a trivial task to me... I found some topics discussing apparently the exact same issue, but nothing seems to work.

Please help, I am getting a terrible headache.

Just for completion, this is the patch sending the messages.

It receives an osc message on port 9009 consisting of 5 integers, and forwards it internally if the address matches the routing.

Another (less elegant) solution would be, if I could 

store the track numbers for each track in the Max MIDI-Effect.

So that I have to assign them only ONCE, and they would be recalled when I close/open Ableton Live.

Anybody can point me in the right direction?

I spent the last hours researching how to do this and just can't figure it out.
Please help.

What I want is receiving messages in a track and route these messages according to the track number, and convert them to midi as input for the track.
The message is a list whose first argument is the "ch"+tracknumber and the following items represent the midi message.

The massive downside: I have to manually fill in the tracknumber each time I start up Live.
That is tedious, since I have around 40 tracks using each one of these MFL-patches...

Just for completion, this is the patch sending the messages.
It receives an osc message on port 9009 consisting of 5 integers, and forwards it internally if the address matches the routing.

Another (less elegant) solution would be, if I could store the track numbers for each track in the Max MIDI-Effect.
So that I have to assign them only ONCE, and they would be recalled when I close/open Ableton Live.

use-track-id-for-routing

 to generate a unique number. Since I do this once in every effect, these should indicate the track numbers.

Not very elegant, but it works for now. I am not sure though if 

 will generate the same number each session....

Okay, this is how I do it now... I use --- to generate a unique number. Since I do this once in every effect, these should indicate the track numbers.
Not very elegant, but it works for now. I am not sure though if --- will generate the same number each session....


Hm.. I have the feeling I must ask very stupidly, though I'm really trying - I swear!

It seems like a trivial problem, but somehow it's not happening and that's super frustrating.

Also, none of the examples I found here in the forum work for me (Live 9.1, Max 6.1.6).

I must do something fundamentally wrong with the Live API it seems to me.

Anyway, using the three dashes (as I did show in the previous post) to generate a unique number also does not work, since the numbers are unique, but the order is obviously unreliable.

What I came up with, is utterly inelegant.

So... I create a live.number, which I can control via OSC.

Then, after the Ableton file is started up, I run a little script to set the track numbers for the tracks 

It works reliably, but it also makes my heart sigh.

I just want the track number of the current track. Shouldn't that be easily achievable within MFL without sacrificing my firstborn?

Hm.. I have the feeling I must ask very stupidly, though I'm really trying - I swear!
It seems like a trivial problem, but somehow it's not happening and that's super frustrating.
Also, none of the examples I found here in the forum work for me (Live 9.1, Max 6.1.6).
I must do something fundamentally wrong with the Live API it seems to me.

What I came up with, is utterly inelegant.
So... I create a live.number, which I can control via OSC.
Then, after the Ableton file is started up, I run a little script to set the track numbers for the tracks remotely from outside Live.
It works reliably, but it also makes my heart sigh.

I just want the track number of the current track. Shouldn't that be easily achievable within MFL without sacrificing my firstborn?


first: how to store values in Max MIDI Effects. Apparently if you use live.number instead of normal numbers, it is saved when you open live next time.

second: I totally changed my plan and instead of routing internally in Live, I wrote a little OSC callback function for LiveOSC which changes live.numbers to desired values and then hits a bang to send it to the midi-out.

in my case, this is always the first device on the track, if you use it yourself, you might have to add another parameter for that.

# in LiveOSCCallbacks.py
self.callbackManager.add("/live/midi", self.oscToMidiCB)

def oscToMidiCB(self, msg, source):
   if len(msg) != 7:
      self.oscEndpoint.send("/live/midi", "wtf are you doing. try to send [track,pitch,velocity,on/off,channel]")
   else:
      LiveUtils.getTrack(msg[2]).devices[0].parameters[2].value = msg[3] #PITCH 
      LiveUtils.getTrack(msg[2]).devices[0].parameters[3].value = msg[4] #VELOCITY
      LiveUtils.getTrack(msg[2]).devices[0].parameters[4].value = msg[5] #ON/OFF
      LiveUtils.getTrack(msg[2]).devices[0].parameters[5].value = msg[6] #CHANNEL
      LiveUtils.getTrack(msg[2]).devices[0].parameters[1].value = 1 #BANG ON
      LiveUtils.getTrack(msg[2]).devices[0].parameters[1].value = 0 #BANG OFF
      self.oscEndpoint.send("/live/midi", "[" + str(msg[2]) + "," + str(msg[3]) + "," + str(msg[4]) + ","  + str(msg[5]) + "," + str(msg[6]) + "]")


So finally it works and is kinda elegant.

I would document this more detailed, but there doesn't seem to be much interest.

If anybody runs in the same problem, just pm me.

second: I totally changed my plan and instead of routing internally in Live, I wrote a little OSC callback function for LiveOSC which changes live.numbers to desired values and then hits a bang to send it to the midi-out.
in my case, this is always the first device on the track, if you use it yourself, you might have to add another parameter for that.

I would document this more detailed, but there doesn't seem to be much interest.
If anybody runs in the same problem, just pm me.


Use Track Id for routing OR storing numbers in effect permanently