Author |
Topic: Mapping (Read 1751 times) |
|
paul.alexander
New Member
I love YaBB 1 Gold!
Posts: 1
|
Firstly - what a giant product. I have lots of "kit"; software and hardware, and this is the guts of anything computer-related. I use the PC to do a lot of mapping of midi, so the map function is heavily used. And there are a couple of mapping-related additions that would be really useful. * Map all function keys and actions to midi messages: This will allow full remote control from keyboards & other midi surfaces - one of the prerequisites for using this live. * Allow midi control to select/change translation maps. Again - remote control and extra felxibility * In translation tables, the ability to put in variables in sysex/strings which are subsititable with messages. Lots of synths now expect small sysex strings with fader values embedded. * A bigger (wider), and single translation map window. Ie. Have the "define mapping" window as the main window, putting the Input and Output sections side-be-side (instead of down), and having multiple entries on screen. When translation maps get complicated, editing would be easier. Paul
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Mapping
« Reply #1 on: Nov 16th, 2001, 6:10pm » |
Quote Modify
|
Thanks for the suggestions. Quote:Allow midi control to select/change translation maps. Again - remote control and extra felxibility |
| This one's available now, although only via Program Change. Quote:In translation tables, the ability to put in variables in sysex/strings which are subsititable with messages. Lots of synths now expect small sysex strings with fader values embedded. |
| There are 3 substitution codes that can be used today for output SysEx strings (FC, FA, FB). When any of these values appear inside a SysEx message, the associated triggering MIDI bytes are substituted.
|
« Last Edit: Nov 16th, 2001, 6:11pm by Jamie OConnell » |
IP Logged |
--Jamie Music is its own reward.
|
|
|
|