RANGE command does not work with Receives / Senders

MIDIbox NG
1

Hey,

I’m trying to split an incoming MIDI signal into two zones just like this:

EVENT\_RECEIVER id=1 type=NoteOn key=any fwd\_id=SENDER:1 range=0:36 EVENT\_SENDER id=1 type=NoteOn key=any range=0:36 chn=1 ports=100010000000 EVENT\_RECEIVER id=2 type=NoteOn key=any fwd\_id=SENDER:2 range=36:127 EVENT\_SENDER id=2 type=NoteOn key=any range=37:127 chn=2 ports=100010000000

Unfortunately the “range” parameter has absolutely no effect here. Regardless what values I enter, it does output two NoteOns for each key (one on ch.1 the other on ch.2) over the whole range. It does have an effect on the velocity though. I could limit the velocity through the range-parameter. But thats not what I want to do :slight_smile:

Is that a bug in the firmware? And if yes, who can fix it? :slight_smile:

Thanks,
Chris

2

Hi Chris

IIRC range= is not a split but a scale function, so range=0:36 change value 0–>0, 127–>36 and linear ponderation in-between.

maybe try with conditional function, if_=

Cheers

Zam

 

3

1 hour ago, Zam said:

Hi Chris

IIRC range= is not a split but a scale function, so range=0:36 change value 0–>0, 127–>36 and linear ponderation in-between.

maybe try with conditional function, if_=

Cheers

Zam

 

Thanks for your reply. 

How could “if_” help here?

What I now did (and what worked) is to create an EVENT_RECEIVER for every single note like

EVENT\_RECEIVER id=1 type=NoteOn key=20 fwd\_id=SENDER:1 EVENT\_RECEIVER id=1 type=NoteOn key=21 fwd\_id=SENDER:1 EVENT\_RECEIVER id=1 type=NoteOn key=22 fwd\_id=SENDER:1

Since they all listen to the same ID, its easy to activate / deactivate that with meta events. This is not beautiful because it’s a lot of code. But at least its a working solution :wink:

4

2 hours ago, FantomXR said:

How could “if_” help here?

it’s a conditional, it will activate the event according to value

don’t remember precise form, I don’t write NGC since years now, but something like if_less=37, your receiver will forward only data from 0 to 36

 

5

On 9/2/2022 at 5:51 PM, Zam said:

it’s a conditional, it will activate the event according to value

don’t remember precise form, I don’t write NGC since years now, but something like if_less=37, your receiver will forward only data from 0 to 36

 

This might also be valid only for the velocity but I’ll give it a try!