[LAU] - an on the fly midi re-mapper?

[Ken Restivo]

On Fri, Nov 28, 2014 at 10:58:06AM +0100, Edgar Aichinger wrote:
> Am Freitag, 28. November 2014, 06:35:39 schrieb Ralf Mardorf:
> > On Fri, 28 Nov 2014 06:18:21 +0100
> > Ralf Mardorf <ralf.mardorf at rocketmail.com> wrote:
> > 
> > > On Fri, 28 Nov 2014 06:12:44 +0100
> > > Ralf Mardorf <ralf.mardorf at rocketmail.com> wrote:
> > > 
> > > > On Thu, 27 Nov 2014 17:48:10 -0800
> > > > Ken Restivo <ken at restivo.org> wrote:
> > > > > http://www.restivo.org/blog/archives/midi-splitter
> > > > 
> > > > "It listens on channel 16 for MIDI events to split." -
> > > > http://www.restivo.org/projects/midisplit/README.txt
> > > > 
> > > > Several old keyboards send on MIDI channel 1 only.
> > > > 
> > > > Can this be changed by changing the "15" value in splits.c or is it
> > > > done somewhere else?
> > > 
> > > Sorry, I don't know this language, I suspect it tests, if the value is
> > > <= 15? and somewhere else the default channel is set?
> >   ^^^ of output channels set by command line or a config file?
> > 
> > I couldn't find where the listening/input channel is set :(.
> 
> midisplit.h has this constant defined:
> 
> #define MIDISPLIT_META_CHANNEL 15
> 
> 
> Then, in midisplit.c, in main()
> ...
> 		if(cmdchan == MIDISPLIT_META_CHANNEL){
> 			split_special(ev, evtype);
> 		} else {
> 			switch_by_channel(ev, evtype, cmdchan);
> 		}
> ...
> 

Yep, sorry it wasn't designed to be very user-configurable.

That's indeed the number to change.

There was a very good reason why I picked chan 16 to handle all the meta-controls, but I don't remember what it was now, 7 years later.

-ken