|
|
Post by alfredr on May 18, 2013 8:09:54 GMT
Hi Nic, thanks for the update. It is allready proving to be very usefull.
I would really like to change aftertouch (poly and channel) into a cc.
Is that possible?
Alfred
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 18, 2013 9:41:13 GMT
Hi Alfred,
This one's a bit tricky. You can map poly after touch to a controller like so:
# map poly aftertouch to controller 07 on all channels
AX = BX 07
This is fine if you are 'aftertouching' one note at a time, but if playing multiple notes you might hear strange things since poly aftertouch events are sent on a per note basis.
Channel aftertouch is possible but laborious - needs 128 rules like:
# map each possible channel after touch value to controller 7 equivalent
DX 00 = BX 07 00
DX 01 = BX 07 01
DX 02 = BX 07 02
...
DX 7E = BX 07 7E
DX 7F = BX 07 7F
I hope to improve the above situation in a future update.
Edit: new byte swap notation in 1.51 means it can be done with one rule:
DX = BX 07 X2
|
|
|
|
Post by alfredr on May 18, 2013 12:14:03 GMT
Nice, so it is easy to convert poly aftertouch to cc.
Is it also possible to convert cc to poly aftertouch easily like:
BX 07 = AX
Guess not...
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 18, 2013 13:20:41 GMT
alfredr > BX 07 = AX That will map the value of controller 7 to poly aftertouch for note 7 only, so probably not of much use. In theory you could do something bizarre like (again 128 rules): BX 07 = AX 00 +C BX 07 = AX 01 +C ... BX 07 = AX 7E +C BX 07 = AX 7F +C This will map the CC to poly aftertouch, but it will generate 128 aftertouch messages (one per note) per controller event as you move the controller, so not sure how feasible this will be given the speed of MIDI (hardware). I think the fundamental issue is that poly aftertouch is on a per channel+note basis and controllers operate only on a per channel basis. I think the only way of thinning this would be to monitor which notes where being used and only issue the aftertouch messages for those notes. I'm just thinking out loud. This sort of logic isn't something the Stream Byter would cater for right now.
|
|
