How come we cannot specify midi channel for each K/V zone ??

runeharpun · Post by **runeharpun** » Wed Sep 30, 2009 7:45 pm

Being used to other keyboards over the years, not being able to define different midi channels for each keyboard zone (combi P4 zone/delay) seems like a strange design. I know you can set the global channel used, but that means all zones share the same global channel.

There is a hack involving the EXT parameter (in combi P3) and a midi cable hooked between midi in and out. But then you'll have delay introduced and the possibility of midi feedback.

It would open up so many more possibilities if we could split zones into different midi channels.

R

mocando · Post by **mocando** » Thu Oct 01, 2009 12:33 am

Please excuse my ignorance, runeharpun, but I don't quite understand your request. I can assign different midi channels to each timbre, and I can set each timbre in a different zone on a combi. Even on different keybeds.

I have a setup with the M50 hooked to a midi controller using a midi cable and I set many timbers in both surfaces and different zones.

Isn't that the same thing?

Again, forgive my lack of knowledge on this matter.

runeharpun · Post by **runeharpun** » Thu Oct 01, 2009 7:20 am

It is possible to specify which midi channel each timbre should RECEIVE on, that's true. But it is not possible to have the M50 trigger midi notes with different midi channels for each zone defined in combi mode, screen P4.

I just want to divide the keyboard so all sounds on the left are triggered on midi channel one, and the ones on the right ride are triggered on channel two. But this approach needs two keyboards, since it's not possible to have one zone sending on channel 1 and the other zone on channel 2.

Hopefully, there is something I've overlooked here ...

R

kanthos · Post by **kanthos** » Thu Oct 01, 2009 12:52 pm

Sure it is. If the timbre's type is set to EXT, it sends MIDI data on the channel used by the timbre. I've been doing this on my TR for a year; the M50 is no different, I believe.

What you *can't* do is have a timbre that plays internally *and* sends MIDI data externally (the equivalent of the BTH type of track that the sequencer uses). The solution is easy: have one EXT timbre for each external MIDI channel you need to send on, and have one INT timbre for each internal sound you need to use.

I never had problems running out of available timbres on the TR which only has 8 timbres available in combi mode; I believe the M50 gives you 16.

runeharpun · Post by **runeharpun** » Thu Oct 01, 2009 3:58 pm

The EXT parameter "transform" the midi channel into the one specified in the Midi ch field - like you write. But then the midi signal is sent out, and needs to be rerouted into the M50 again. It's this detour that bugs me. If I set a midi channel other than the global channel and status=INT for a part, then it will not sound because the keys of the M50 only generate notes with midi channel=Global channel.

So plugging a midi cable between midi in and out "solves" the problem, but I want to get rid of the cable-loop to do this.

kanthos · Post by **kanthos** » Thu Oct 01, 2009 4:32 pm

Think you missed what I said. Use an EXT timbre to send, an INT timbre to receive and/or get triggered by the M50 keybed. If you need to send and receive on the same channel, use two timbres instead of one, so you don't have to loop the out to the in.

runeharpun · Post by **runeharpun** » Thu Oct 01, 2009 4:46 pm

The trouble is that using the INT, means all sounds need to be on the same midi channel (I know I can have multiple parts be triggered by the same channel).

I want to be able to send separate patch changes to different midi channels in combi mode, so I can control the sounds mapped on the lower and upper part of the M50 keys separately. If I use the same midi channel for all parts, then a patch change would change the sound for all parts (unless filtered out for a spesific part).

R

mocando · Post by **mocando** » Thu Oct 01, 2009 5:04 pm

runeharpun wrote:It is possible to specify which midi channel each timbre should RECEIVE on, that's true. But it is not possible to have the M50 trigger midi notes with different midi channels for each zone defined in combi mode, screen P4.

I just want to divide the keyboard so all sounds on the left are triggered on midi channel one, and the ones on the right ride are triggered on channel two. But this approach needs two keyboards, since it's not possible to have one zone sending on channel 1 and the other zone on channel 2.

Hopefully, there is something I've overlooked here ...

R

Ok, I'm beginning to grab the idea. Still unclear to me is the applications of this. Why would you want to send different midi channels for left and right zone?

Yeah, I know. I'm slow

runeharpun · Post by **runeharpun** » Thu Oct 01, 2009 5:25 pm

It's confusing to talk about channels and parts, especially when they are layed out the way they are, so I understand your confusion

The reason I want to do this is because I have a midi pedal board I can use to send out patch changes to different channels. So to play some solo parts using my right hand, I could just send a patch change on channel 2, leaving the sound I use on my left hand untouched (and still playing without a sound gap). Also, controlling volume and other CC based functions can be set up easier if I could send different values on different midi channels.

I'm still on the journey to find a setup allowing me to switch sounds quickly with plenty of options when I play live. I'm also thinking about just using an extra keyboard so I'm not depending on patch changes at all - just staying at the same performance the whole song.

R

kanthos · Post by **kanthos** » Fri Oct 02, 2009 12:30 am

You can filter out program changes, so you might be fine that way. You might want to think instead about playing in sequencer mode, so that you can change your sounds by changing the active sequencer track (though you can't do that from a foot controller).

runeharpun · Post by **runeharpun** » Fri Oct 02, 2009 7:08 am

Perhaps the sequencer mode is what I end up using. I'll play around and post if I find anything usefull

R