Ruby keyboard splitter-needs some fixes

[kortezzzz]

Here is a very simple schematic that shows how to split the midi keyboard into 2 (or whatever number you need) zones and play 2 different instruments with each zone. It works well, but suffers from lack of the ability to pass midi messages other than note's pitch\velocity, like pitch-band and modulation wheel.

Any chance that the Ruby people here would take a look at it and add a solution?

Thanks.

[Nubeat7]

these are 3 different midi messages, while the keyboard produces note on and note off messages the modwheel is a control change message and pitchbend is an own midi message type, you can use the pitchbend primitive control pitchbend, and the midi cc primitive to receive modwheel changes using the ccnr 1

[kortezzzz]

these are 3 different midi messages...

Nubeat7, Yes, I know, but was hoping to combine at least the pitch band messages feature inside the ruby code, because in some cases, projects don't deal with audio but output only the generated midi signal, so using
pitch-band prim' + pitch-band to frequency combination is not relevant(?)
Or- maybe it is? Thought about adding a float input into the ruby code and connect the pitch primitive straight to the code so the midi's notes pitch values would be multiplied with the pitch-band's messages values, but just dunno how to do that. My desired result is to let 1 ruby module to take care of those midi manipulations and output them through 1 midi output so the midi signal would continue to it's next address in the schematic. possible?

[Nubeat7]

what you want to achieve is not possible because the "notepitch" on the keyboard is sent via note on / off messages which have a fixed integer noterange from 0-127, pitchbend and finetune or pitch to Hz needs to be done in the stream part

[kortezzzz]

Yep, was afraid that that's the case
My project streams the midi data that played by a midi keyboard from a standalone app to the daw by using virtual midi cables, so there's no ability to extract pitch band messages in that way, because there is no direct communication between the midi signal and the addressed vsti's audio part inside the daw. Tried some ideas but they all failed. Seems like that pitch band manipulation feature would work only in projects that combine midi and audio.

Thanks for trying helping, Nubeat7.

[KG_is_back]

what you can do is to remove all note on/off messages and send this to all midi outputs. That would mean, both/all midi outputs would share pitch bend, mod wheel etc. but would have keys filtered separately.

[kortezzzz]

KG, you mean filtering only the 128,144 messages and sending it directly to the midi output? Well yes, it might work
I'll test it ASAP.

Thanks!

*Edit: tried it and it doesn't work as expected.The played notes just freak out and give random pitches, even when
the pitch isn't manipulated at all. That's really weird. Tried both green and ruby solutions and it didn't worked here (unless my ruby code was written badly).