I'm a bit short on time so I'm going to go through this quickly...
All I use midi-ox for is to monitor midi messages. I'll just go ahead and post a few pics, maybe it helps.
First, I've got midi-ox installed and set up to receive midi from midi-yoke and to go back out again:
Do this by going to Options > Midi setup. If you have any midi devices plugged in (keyboard, controllers etc) they'll show up in the list of available inputs.
Just a side note - if I check my midi input devices in Ableton I can see midi-yoke there, which is good. All midi-ox is doing is it sits between my midi controller (be it an actual bit of hardware, or, in this case - a virtual midi contoller ala Glovepie) and Ableton, and monitors the midi messages. But for the sake of troubleshooting, I leave Ableton closed and only watch midi-ox to see if midi is being sent / received
So - back to Glovepie. A simple script to make the 'q' key output a midi note message:
Code:
midi.DeviceOut = 2
midi.channel1.c0 = Keyboard1.q
If you look at an actual controller - they have knobs and buttons. These don't send midi notes (like a c#), but they send program change messages / other types of instructions. However, for ease of setup and also for the fact that most DAW's use midi-note messages quite well for midi-mapping to various controls, it makes it easier to start of by making your DIy controller send midi note messages.
Ok, that Glovepie code is entered and I've hit 'Run' in Glovepie. Go back to midi-ox, press the 'q' key and I can see (in the midi activity window) that the 'q' key is sending a midi note on/off message:
That's all you need really. If I start up Ableton, make sure midi is set to receive from midi-yoke, then I can map my 'q' key (which is actually being mapped as a midi note rather than the key 'q') to whatever I need to.
Just a bit more about Glovepie:
Just open up Glovepie, and put the following code in:
Code:
debug=keyboard.count
and hit 'Run'. You should get a result of 3. One is your primary keyboard, another is Microsoft windows virtual keyboard or something, and the other should be the additional one you're using as your controller. As long as GlovePie sees all your keyboards, it's just a case of figuring out which one is the right one (but most likely it'll be keyboard.3) and getting midi-ox to see the messages Glovepie is sending.
Code:
midi.DeviceOut = 2
midi.channel1.c0 = Keyboard0.q
or
Code:
midi.DeviceOut = 2
midi.channel1.c0 = Keyboard1.q
or
Code:
midi.DeviceOut = 2
midi.channel1.c0 = Keyboard2.q
Just try em all until midi-ox receives something - doesn't matter which keyboard sends the midi messages. Once you're sending midi from Glovepie to midi-ox you're good to go.
Gotta run. Hope you come right with it.
Bookmarks