schlam

each string sends data on a different channel

string 1-->channel 1 , string 2-->channel 2 etc.

In live, there is one track per string receiving data on its own channel.

In each of these tracks there is only one device that sends data to a Master device in another track.

image.png

I need then to receive all these informations in another device that route them to the corresponding track where I have an "external Instrument" device in each.

Then in each track with my synths I have a device with :

With the matrixctrl object I can easily choose which string will plays what synth..

The problem is that I have hang notes and data loss.

Since Live doesn't handle multichannel per track (a pity!)

I tried with a max standalone alongside that send routed data via 6 loopMIDI ports.

I play with a midi guitar
each string sends data on a different channel
string 1-->channel 1 , string 2-->channel 2 etc.

In live, there is one track per string receiving data on its own channel.
In each of these tracks there is only one device that sends data to a Master device in another track.

Then in each track with my synths I have a device with :

[r NoteGeneral]
|
[route versX]
|
[midiparse] etc ...

It's working good.
With the matrixctrl object I can easily choose which string will plays what synth..

Since Live doesn't handle multichannel per track (a pity!)
What can I try to achieve what I want.

For information, :
I tried with udpsend
I tried with a max standalone alongside that send routed data via 6 loopMIDI ports.

Hello
I play with a midi guitar
each string sends data on a different channel
string 1-->channel 1 , string 2-->channel 2 etc.
In live, ... 

-data-loss-communication-between-live-devices-to-route-midi

You send program change on every received note ???

that buddy looks suspicious to me in sreenshot 2.

i don't get what you are trying t do, but buddy played few tricks on me

But after all, why don't you send 6 guitar midi channels directly to 6 tracks which host synths ?

I played midi guitar since (I don't even remember it is so far back)

into Max without any midi data loss ever.

On much slower computer than what one has today.

a brief look 
You send program change on every received note ???
Screenshot 1.

that buddy looks suspicious to me in sreenshot 2.
i don't get what you are trying t do, but buddy played few tricks on me
in the past.

But after all, why don't you send 6 guitar midi channels directly to 6 tracks which host synths ?
I played midi guitar since (I don't even remember it is so far back)
into Max without any midi data loss ever.
On much slower computer than what one has today.


the program change is "dummy", I just use the PC inlet of midiformat to send this information.

when they are received, there are not treated as PC messages, they just allow me to know from which string an information comes from.

I need to attach for each note's information the string it came from.

that's why I need to send the dummy PC for each note.

The reason I don't want to send 6 strings directly in 6 tracks which host synths, 

it's because I have a lot of presets that are routing the strings. It's the main goal of the patch.

I am often on the fly changing the routing "Strings-----Hardware Synths"

sometimes one string will play 3 synths, the string above another synth etc..

That's why I use [buddy], I send notes, CC and pitch bends info to several synth in the same time from 6 channels. It's the dummy PC number which routes for each information in what synth it have to go,

[buddy] ensures me (maybe not in fact..) that this route information comes allways before the information..

One thing I didn't try is to see if it's possible to change on the fly with API the Midi In channel of each track..

the program change is "dummy", I just use the PC inlet of midiformat to send this information.
when they are received, there are not treated as PC messages, they just allow me to know from which string an information comes from.


I need to attach for each note's information the string it came from.
that's why I need to send the dummy PC for each note.

The reason I don't want to send 6 strings directly in 6 tracks which host synths, 
it's because I have a lot of presets that are routing  the strings. It's the main goal of the patch.
I am often on the fly changing the routing "Strings-----Hardware Synths"


That's why I use [buddy],  I send notes, CC and pitch bends info to several synth in the same time from 6 channels. It's the dummy PC number which routes for each information in what synth it have to go,
[buddy] ensures me (maybe not in fact..) that this route information comes allways before the information..

One thing I didn't try is to see if it's possible to change on the fly with API the Midi In channel of each track..


I would drop midi after receiving 6 strings, and use

send / receive to route notes, cc and pitch bend.

Or better say only midi events that you use,

I guess that PG change and buddy are not doing the job well,

because anytime more strings could send midi, and interrupt

the flow of midi data, which is controlled by gate 7.

For example you receive something from string 3 ( which opens gate outlet 3)

but before all message from string 3 get through, another string

like for example 4 sends PG 4 and opens gate outlet 4.

You get wrong cc values or stuck pitchbend value ...

What is the purpose of append C1 C2 etc ?

that ends nowhere, also pitchbend seems not to be routed at all...

again, I would receive 6 strings, prepend ID per string and send it to

router device, but without that midi mess.

All you need is to prepend some IDs for notes, PB and the rest in use.

Screen shot 2021-09-30 at 21.22.35.png

Also you need to take care when you disconnect one string from a synth,

to send all notes off, reset pitchbend etc.

because it could get disconnected before a note got turned off

I would drop midi after receiving 6 strings, and use
send / receive to route notes, cc and pitch bend.
Or better say only midi events that you use,
reducing number of objects.
I guess that PG change and buddy are not doing the job well,
because anytime more strings could send midi, and interrupt
the flow of midi data, which is controlled by gate 7.
For example you receive something from string 3 ( which opens gate outlet 3)
but before all message from string 3 get through, another string
like for example 4 sends PG 4 and opens gate outlet 4.
You get wrong cc values or stuck pitchbend value ...

What is the purpose of append C1 C2 etc ?
that ends nowhere, also pitchbend seems not to be routed at all...

again, I would receive 6 strings, prepend ID per string and send it to
router device, but without that midi mess.
All you need is to prepend some IDs for notes, PB and the rest in use.
It could look like this :


Also you need to take care when you disconnect one string from a synth,
to send all notes off, reset pitchbend etc.
because it could get disconnected before a note got turned off

