There must be a sysex string that controls them. this means we should be able to control them with anything...as long as you convert your midi to sysex with midiox. Right?
So who can get the sysex code for us?
If you can mute/solo with mcu....
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
it's NOT sysex.
it is controlled via standard midi note-on / CC commands, but these are interpreted by a different part of the program than the standard MIDI inputs.
you must dedicate a MIDI input port to the control surface support implementation (e.g. MCU) and then all MIDI data will be read as system commands if they apply. To test this, you can set your general midi keyboard input to the MCU control surface support input port. try pressing random midi keys and you'll see "stuff happen". you COULD label your keys thru trial and error...
or you could wait til something else happens!
either way, you need a whole input (real or virtual) dedicated to the job of giving T2 the commands. Which means that you can only use your normal input device if you have a program/driver running that can split different messages into different virtual ports ( for example, MIDIOx with the MIDI Yoke virtual port drivers ). After all, the MCU device itself requires a whole midi port to itself. It's not just a simple case of sending a sysex message a normal input active for recording.
it is controlled via standard midi note-on / CC commands, but these are interpreted by a different part of the program than the standard MIDI inputs.
you must dedicate a MIDI input port to the control surface support implementation (e.g. MCU) and then all MIDI data will be read as system commands if they apply. To test this, you can set your general midi keyboard input to the MCU control surface support input port. try pressing random midi keys and you'll see "stuff happen". you COULD label your keys thru trial and error...
or you could wait til something else happens!
either way, you need a whole input (real or virtual) dedicated to the job of giving T2 the commands. Which means that you can only use your normal input device if you have a program/driver running that can split different messages into different virtual ports ( for example, MIDIOx with the MIDI Yoke virtual port drivers ). After all, the MCU device itself requires a whole midi port to itself. It's not just a simple case of sending a sysex message a normal input active for recording.
Kick, punch, it's all in the mind.
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
i think you should drink more oftenhaydxn wrote:i'm a little too drunk now to work on my main project so i'll see if i can get any work done on this
-
- KVRist
- Topic Starter
- 195 posts since 31 Dec, 2004
Im buying!djsubject wrote:i think you should drink more oftenhaydxn wrote:i'm a little too drunk now to work on my main project so i'll see if i can get any work done on this