Grrrrrrr... HID to MIDI frustration

Home :: Reviews of DJ equipment :: Grrrrrrr... HID to MIDI frustrationReply
Grrrrrrr... HID to MIDI frustration
Posted on: 30.06.2011 by Madeline Seneff
Ok I've been trying really really hard to try and not post something which is clearly a fairly common topic, but I really just can't find anything.

Truthfully, the underlying thing I've been trying to do is use a second QWERTY keyboard with Traktor Pro/ Traktor Pro 2. So what I've been trying to do is find an easy way to convert the HID signals to MIDI, so that way the keyboard commands between my laptops built in keyboard and the external keyboard. I also need keys that have the same command, like the shift keys, to send different signals, but actually if that cant happen thats ok.

Anyway I've tried a whole slue of programs, and none of them seem to work properly. Mjoy, joy to key, fergo, bomes, mousekeyboard200, etc. I have a plain old Logitech external keyboard, something I plan on ripping apart later and modding, and I run Windows 7 64-bit on a Dell XPS 17, and like I said I'm looking to convert the signals, or a similar alternative, to use for Traktor Pro / 2.

I'm sort of believeing this just isn't a possibility at this time, but thanks in advance for anyone who helps!
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
ok, so this code above worked. Its the second code you posted, just instead of keyboard1.A/B I used keyboard2.A/B which worked for my external. keyboard1 is for my internal keyboard as it would seem.
sure - but that indicates that there's some issue with writing to the midi device - as the var update bit works - but not when u put the midi assignment before it.

i'll fire up glovepie etc later and have a play and see if i can believe of anything else.
Chantelle Dellosso
21.07.2011
Originally Posted by chaomocha
Is this the midi activity window? lol I dont even know:
That's the one. It's the little square icon to the left of the round green icon...

Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
yeah, nothings happening. I only have two keyboards though, and I try them both each time, and try the script with "keyboard0.q" each time as well, just in case. So technically I'm pressing Q 4 different times and none of them seem to work. Do I need an output or something because I'm really trying hard to notice everything right now in MidiOX and in the bottom left it says I have "No Output Device" where as over near the left side on the bottom it says I have "1 Input Device" which makes sense because that's all I've highlighted in the "Select MIDI Device to Open" window.
you don't need an output device selected since you're just using midiox to dump whats being set to that midi device by glovepie.

what about a slightly different script:

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.csharp0 = Keyboard1.A
midi.d0 = Keyboard1.B
var.csharp0 = Keyboard1.A
var.d0 = Keyboard1.B
if you go to the "Variables" tab in glovepie you should see two variables now called csharp0 and d0 which should show **TRUE** (ish) when you press A or B on keyboard1.

if you dont see the variables change in that tab then try this one:

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
var.csharp0 = Keyboard1.A
var.d0 = Keyboard1.B
midi.csharp0 = Keyboard1.A
midi.d0 = Keyboard1.B
if you only see the variables changing in that 2nd one then that means theres an error writing to the midi device.
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
Yeah all those things are there, still nothing when I hit Q though... idk why its not working, after I click the midi input name and hit ok from the box and everything, the Monitor Input reads "Opened Midi Input", and if I un-highlight it, it says "Closed Midi Input." So it recognizes me opening and closing the midi input, but open or closed it doesn't do anything when I type the letter "Q" which is currently the only key I have scripted out.
so you're running the script below - glovepie is displaying your qwerty device name in its debug window and you are pressing 'q' on your first keyboard?

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.channel1.c0 = Keyboard1.q
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
Alright, did what you said and I didn't get an error message this time, woot! But now I'm pressing "Q" and nothing is happening on MidiOX. Is something supposed to be happening even? And where would I go to see it happening in MidiOX?
from the midiox port "Select MIDI Devices to Open" page have you double clicked on your virtual devicename in the "MIDI Inputs" panel so you now see it listed in the "Portmap Objects" box at bottom right?

you should then see midi data dumped in the "Monitor Input" window. in theory
Madeline Seneff
21.07.2011
Originally Posted by zestoi
somehow i managed to totally miss updates to this thread. odd...



only one app can write to a midi device at a time - and glovepie is trying to. i'm pretty sure thats the cause of that error.

make sure you only open the input port in midiox - you just want to use it to check that the correct data is being sent to the virtual midi device from glovepie.
Alright, did what you said and I didn't get an error message this time, woot! But now I'm pressing "Q" and nothing is happening on MidiOX. Is something supposed to be happening even? And where would I go to see it happening in MidiOX?
Chasidy Heckenbach
20.07.2011		somehow i managed to totally miss updates to this thread. odd...

Originally Posted by chaomocha
Then I opened MidiOX, went to options, midi devices, clicked it, highlighted the midi input port and the midi output port which were both labelled as QWERTYkeyboard, hit ok, then I got an error message saying "QWERTYkeyboard: Undefined external error"
only one app can write to a midi device at a time - and glovepie is trying to. i'm pretty sure thats the cause of that error.

make sure you only open the input port in midiox - you just want to use it to check that the correct data is being sent to the virtual midi device from glovepie.
Madeline Seneff
27.07.2011		sorry just wanted to bump this again cause I havent heard from anyone about it in a while, and havent been able to figure it out for myself yet either... :/
Madeline Seneff
23.07.2011		Any luck? I've been trying to do the same and have been reading up at some others sites and community s but still nothing seems to be what I need
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
ok, so this code above worked. Its the second code you posted, just instead of keyboard1.A/B I used keyboard2.A/B which worked for my external. keyboard1 is for my internal keyboard as it would seem.
sure - but that indicates that there's some issue with writing to the midi device - as the var update bit works - but not when u put the midi assignment before it.

i'll fire up glovepie etc later and have a play and see if i can believe of anything else.
Chantelle Dellosso
21.07.2011
Originally Posted by chaomocha
Is this the midi activity window? lol I dont even know:
That's the one. It's the little square icon to the left of the round green icon...

Madeline Seneff
21.07.2011
Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
var.csharp0 = Keyboard2.A
var.d0 = Keyboard2.B
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
ok, so this code above worked. Its the second code you posted, just instead of keyboard1.A/B I used keyboard2.A/B which worked for my external. keyboard1 is for my internal keyboard as it would seem.

Anyway, that's working, but I go back to MidiOX and nothing is showing again when I press A or B. I closed the port and reopened it too just incase. Also just to be sure, this is the window I've been looking at in MidiOX, but I have some feeling that I shoud be looking at a different one, idk why though, I believe it was because of something scyn wrote but I didn't fully understand it:

Originally Posted by scyn
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
Is this the midi activity window? lol I dont even know:



And yes this was the window I've been pressing "Q" "A" or "B" in, accordingly.
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
yeah, nothings happening. I only have two keyboards though, and I try them both each time, and try the script with "keyboard0.q" each time as well, just in case. So technically I'm pressing Q 4 different times and none of them seem to work. Do I need an output or something because I'm really trying hard to notice everything right now in MidiOX and in the bottom left it says I have "No Output Device" where as over near the left side on the bottom it says I have "1 Input Device" which makes sense because that's all I've highlighted in the "Select MIDI Device to Open" window.
you don't need an output device selected since you're just using midiox to dump whats being set to that midi device by glovepie.

what about a slightly different script:

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.csharp0 = Keyboard1.A
midi.d0 = Keyboard1.B
var.csharp0 = Keyboard1.A
var.d0 = Keyboard1.B
if you go to the "Variables" tab in glovepie you should see two variables now called csharp0 and d0 which should show **TRUE** (ish) when you press A or B on keyboard1.

if you dont see the variables change in that tab then try this one:

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
var.csharp0 = Keyboard1.A
var.d0 = Keyboard1.B
midi.csharp0 = Keyboard1.A
midi.d0 = Keyboard1.B
if you only see the variables changing in that 2nd one then that means theres an error writing to the midi device.
Madeline Seneff
21.07.2011		yeah, nothings happening. I only have two keyboards though, and I try them both each time, and try the script with "keyboard0.q" each time as well, just in case. So technically I'm pressing Q 4 different times and none of them seem to work. Do I need an output or something because I'm really trying hard to notice everything right now in MidiOX and in the bottom left it says I have "No Output Device" where as over near the left side on the bottom it says I have "1 Input Device" which makes sense because that's all I've highlighted in the "Select MIDI Device to Open" window.
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
Yeah all those things are there, still nothing when I hit Q though... idk why its not working, after I click the midi input name and hit ok from the box and everything, the Monitor Input reads "Opened Midi Input", and if I un-highlight it, it says "Closed Midi Input." So it recognizes me opening and closing the midi input, but open or closed it doesn't do anything when I type the letter "Q" which is currently the only key I have scripted out.
so you're running the script below - glovepie is displaying your qwerty device name in its debug window and you are pressing 'q' on your first keyboard?

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.channel1.c0 = Keyboard1.q
Madeline Seneff
21.07.2011		Yeah all those things are there, still nothing when I hit Q though... idk why its not working, after I click the midi input name and hit ok from the box and everything, the Monitor Input reads "Opened Midi Input", and if I un-highlight it, it says "Closed Midi Input." So it recognizes me opening and closing the midi input, but open or closed it doesn't do anything when I type the letter "Q" which is currently the only key I have scripted out.
Chasidy Heckenbach
21.07.2011
Originally Posted by chaomocha
Alright, did what you said and I didn't get an error message this time, woot! But now I'm pressing "Q" and nothing is happening on MidiOX. Is something supposed to be happening even? And where would I go to see it happening in MidiOX?
from the midiox port "Select MIDI Devices to Open" page have you double clicked on your virtual devicename in the "MIDI Inputs" panel so you now see it listed in the "Portmap Objects" box at bottom right?

you should then see midi data dumped in the "Monitor Input" window. in theory
Madeline Seneff
21.07.2011
Originally Posted by zestoi
somehow i managed to totally miss updates to this thread. odd...



only one app can write to a midi device at a time - and glovepie is trying to. i'm pretty sure thats the cause of that error.

make sure you only open the input port in midiox - you just want to use it to check that the correct data is being sent to the virtual midi device from glovepie.
Alright, did what you said and I didn't get an error message this time, woot! But now I'm pressing "Q" and nothing is happening on MidiOX. Is something supposed to be happening even? And where would I go to see it happening in MidiOX?
Chasidy Heckenbach
20.07.2011		somehow i managed to totally miss updates to this thread. odd...

Originally Posted by chaomocha
Then I opened MidiOX, went to options, midi devices, clicked it, highlighted the midi input port and the midi output port which were both labelled as QWERTYkeyboard, hit ok, then I got an error message saying "QWERTYkeyboard: Undefined external error"
only one app can write to a midi device at a time - and glovepie is trying to. i'm pretty sure thats the cause of that error.

make sure you only open the input port in midiox - you just want to use it to check that the correct data is being sent to the virtual midi device from glovepie.
Madeline Seneff
20.07.2011		ooooooooook, so I ran into some problems of course lol. So to begin with, here's the code I've been using:

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
So I ran that, GlovePIE recognized the port I made in loopMIDI (which is what I'm using instead of MidiYoke) which is named QWERTYkeyboard, and that was all fine and dandy. Then I opened MidiOX, went to options, midi devices, clicked it, highlighted the midi input port and the midi output port which were both labelled as QWERTYkeyboard, hit ok, then I got an error message saying "QWERTYkeyboard: Undefined external error"

So, the next thing I did was run the debug program you gave me to check how many keyboard devices I have. turns out I only have 2. Just to double check I unplugged the external keyboard and ran it again and only got 1, so I know that it included the external keyboard when it ran it. So then I modified the code to be this instead, which included changing the keys from "A" and "B" to "Q":

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.channel1.c0 = Keyboard0.q
Ran everything again, same error message. Tried it again with a different keyboard.

Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.channel1.c0 = Keyboard1.q
Same thing, ran it again, didn't work again.

So where I stand now is:
I have a code in GlovePIE that talks to loopMIDI.
I have a port in loopMIDI that talks to GlovePIE.
The code is fine.
MidiOX recognizes the input and output of the loopMIDI port.
MidiOX does not work.

Thoughts?

Screencaps will be on their way here momentarily because I fail to see why this works fine for you guys but not fine for me.

EDIT: Screencaps:

Step 1: Open GlovePIE, load script.


Step 2: Open loopMIDI, create port (QWERTYkeyboard).


Step 3: Run GlovePIE. The debug recognizes the QWERTYkeyboard.


Step 4: Open MidiOX.


Step 5: Options -> Midi Devices


Step 6: Midi Devices now open, now what? Before I was highlighting the QWERTYkeyboard input and outputs, but that was giving me the error messages.
Chantelle Dellosso
20.07.2011		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.
Madeline Seneff
20.07.2011		Sorry for the double posts, I know theres an edit button but i prefer new information and updates to be in seperate posts, idk just kinda how i tick.

anyway, the new information.
Code:
midi.DeviceOut = 2
debug = midi.OutDevName
midi.DefaultChannel = 1
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
Finally got this working with loopMIDI by changing the midi.DeviceOut to 2. idk why I didn't try going down from 8 to begin with haha, I kept counting up last evening , must've made it to like 80 or 90, don't really remember. Anyway, I've got GlovePIE talking to loopMIDI, now how does midiOX come into play? I don't have a clue what to do with that program
Madeline Seneff
20.07.2011
Originally Posted by scyn
I'm using midi-yoke on Win7 32bit and it's working fine, but I"ve also heard of people having problems on Win7 - though it might just pertain to 64bit Windows.

chaomocha, I'd maybe leave Traktor out of it for now. Get Midi-ox installed, and it'll allow you to monitor any midi messages being received by your system. That way, you can get Glovepie and your keyboard working correctly / how you want it. I'll upload a few screenshots some time later to show you how I've got mine set up.
oh wow yes fantastic maybe someone elses screenshots will help. I do have windows 7 64 bit though so maybe that is an issue. I'll just keep trying to get loopMIDI to work in the meantime.
Chantelle Dellosso
20.07.2011
Originally Posted by zestoi
glovepie needs a virtual midi driver to be able to send out midi. i read about people having problems with midi yoke on windows 7 so i tried loopMIDI and it has worked flawlessly.
I'm using midi-yoke on Win7 32bit and it's working fine, but I"ve also heard of people having problems on Win7 - though it might just pertain to 64bit Windows.

chaomocha, I'd maybe leave Traktor out of it for now. Get Midi-ox installed, and it'll allow you to monitor any midi messages being received by your system. That way, you can get Glovepie and your keyboard working correctly / how you want it. I'll upload a few screenshots some time later to show you how I've got mine set up.
Madeline Seneff
20.07.2011
Originally Posted by zestoi
kudos for the fact you keep trying and don't sound to be giving up
haha, college student, no money, extra keyboard, not many other options at this point
Chasidy Heckenbach
20.07.2011		kudos for the fact you keep trying and don't sound to be giving up
Madeline Seneff
20.07.2011		sigh, nope, it very much did not work yet again lol. I believe I'll just record what I'm doing using a screencap or something and just post that, because maybe there's just something that I'm doing wrong that I might be misunderstanding what you said, or maybe there's something I'm just not doing right in general. idk, either way all I know is I'm a little less confused, but it's still not working properly and it's difficult to explain how when I'm not sure what's going on anyway. I'm also kinda tired so that probably is not helping any either, so I'll just log in again tomorrow and continue from there. I'm pretty determined on making this work though, even if it requires me making a new program and everything, even though I know even less about programming lol.
Madeline Seneff
20.07.2011		Ok I'll give that a try then. If it doesn't cooperate with me this time around though I may have to call it a evening because its really late; maybe even early o_O, and I can always come back to it tomorrow. but for now, away with MidiYoke, and in with loopMIDI. I do have midiox too btw, thats been in the shadows this whole time I suppose.
Chasidy Heckenbach
20.07.2011
Originally Posted by chaomocha
not too sure if MidiYoke is the same as GlovePIE, in the installation instructions it says for GlovePIE to even work properly I should also be running MidiYoke, so I downloaded that a while ago. And I'm not really sure what the problem is exactly between GlovePIE, MidiYoke, and Traktor, but it must be somewhere in those three because regardless of whether loopMIDI was running, the same problem was occuring. I've been looking for somewhere where Traktor would accept MidiYoke, but I don't see one thing in Traktor for MidiYoke or GlovePIE or even loopMIDI for that matter.
glovepie needs a virtual midi driver to be able to send out midi. i read about people having problems with midi yoke on windows 7 so i tried loopMIDI and it has worked flawlessly.

in traktor you just select whichever virtual midi port you are using - whether its from midiyoke or loopMIDI.

if it was me i'd probably uninstall midiyoke and go with loopMIDI as other people have had problems with that combination - but it could be something else ofc. plus i don't know if you're using midiyoke for anything else.

to first take traktor out of the equation you could download midiox and use that to sniff if data sent to the midi device from glovepie. very handy for debug and works fine on windows 7.
Madeline Seneff
20.07.2011
Originally Posted by zestoi
midiyoke does the same kind of thing as glovepie afaik - tho i havent used midiyoke in years. if glovepie is sending out to midi yoke 7 then u need to set traktor to recieve from whatever port midi yoke is sending to.

quite possibly midi yoke and loopMIDI dont play nicely together... i've also found problems when i create more than about 8 virtual midi ports here on windows7 so you might have hit some kind of limit like that maybe.
not too sure if MidiYoke is the same as GlovePIE, in the installation instructions it says for GlovePIE to even work properly I should also be running MidiYoke, so I downloaded that a while ago. And I'm not really sure what the problem is exactly between GlovePIE, MidiYoke, and Traktor, but it must be somewhere in those three because regardless of whether loopMIDI was running, the same problem was occuring. I've been looking for somewhere where Traktor would accept MidiYoke, but I don't see one thing in Traktor for MidiYoke or GlovePIE or even loopMIDI for that matter.
Chasidy Heckenbach
20.07.2011		midiyoke does the same kind of thing as glovepie afaik - tho i havent used midiyoke in years. if glovepie is sending out to midi yoke 7 then u need to set traktor to recieve from whatever port midi yoke is sending to.

quite possibly midi yoke and loopMIDI dont play nicely together... i've also found problems when i create more than about 8 virtual midi ports here on windows7 so you might have hit some kind of limit like that maybe.
Madeline Seneff
20.07.2011		Well unfortunately it didn't work, and I'm not quite sure why. So here's what happened. I downloaded loopMIDI, installed it, etc. opened it, added a port name with the default name of "loopMIDI Port" then I went to GlovePIE, pasted the script you gave me directly into the space available for text, deleted everything after the "//" on any of the lines that had it, then hit run. But next to the stop buttoen read "Out To MIDI Yoke: 7" but I gave it a try anyway and opened traktor. It was clearly not working because a whole bunch of random stuff was happening like my FX were cycling through for whatever reason. The GlovePIE popped up with a message saying "GlovePIE Programmable Input Emulator (Bird + 5DT ver) has stopped working, Windows is collecting more information about the problem, this may take several minutes..." and then a few seconds later a second message popped up pretty much saying it didn't find anything but wants to ask if I want to report it anyway. So, I cancelled out of traktor, glovePIE, and loopMIDI, and thought maybe my problem was that I had loopMIDI and MidiYoke running at the same time, so then I tried everything again except this time I didn't open loopMIDI. Instead, MidiYoke was open, GlovePIE was opened, the same script was pasted in, run, traktor, same errors occured, then they were followed by the same error messages. so yeah that's where I'm at now... lol and I thought I'd just be able to plug in a keyboard and start mixing, not gunna give up that easy though! any thoughts?
Madeline Seneff
20.07.2011		haha ok I believe I finally understand! I am running windows 7 so I'll go get loopMIDI and give that a whirl, then report back here hopefully with some good news.
Chasidy Heckenbach
20.07.2011		the keyboard lights are nothing to do with this. you can get your keyboard to send out midi via glovepie - but it cant then receive midi to change lights etc.

you need an app like loopMIDI that creates a virtual midi device - which is what you'll set as the IN port in traktor.

you then set glovepie to send OUT to that loopMIDI virtual device so you end up with this:

your keyboard => glovepie => loopMIDI device => traktor

the only script you need is the one i pasted several posts ago:

Code:
midi.DeviceOut = 8 // device number to use
debug = midi.OutDevName // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
which (assuming u tweak the 8 to be whatever virtual device is created by loopMIDI or other virtual midi device) would send out a "c sharp octave 0" if you press the "A" on your 2nd keyboard and a "d octave 0" if you press the "B" on that keyboard.

if you're on windows i recommend using loopMIDI as its very easy to use - just create one virtual midi port. if on a mac you'd need to scan the community for info on that.

first get glovepie talking to your virtual midi device by tweaking that DeviceOut parameter - then get traktor connected to the same virtual midi device.

once you have at least one keypress getting into traktor then keep adding to the glovepie script like those 2 lines above and adding the entries in your traktor tsi...
Madeline Seneff
19.07.2011
Originally Posted by zestoi
np lol. when u connect midi devices they each have a 'name' of some type that will show up in the device list in whatever software you are using. so thats all it means.

any device that can send data (like a midi keyboard) and receive midi (like a pad that lights up on a launchpad) have both a midi IN and an OUT port.
so say I'm running Traktor pro 2. I've got my QWERTY keyboard plugged in, so its considered a generic keyboard in the drop down menu under controller manager. However I can only ever have one generic keyboard, which brings me here with all these questions lol.

so, I know the keyboard I have has 3 lights on it, for caps, scroll, and number lock. are these my midi OUTs then, similar to the launchpad lights? and would that make all the keys on the keyboard all of my midi IN? I believe I might be jumping ahead of myself a bit. I understand mapping on Traktor, just this glovePIE program is a whole new world for me.

but anyway, based on what I just said, is this the proper way of pluggin in all that information in the code you gave me?

Code:
midi.DeviceOut = 3 // device number to use
debug = midi.GenericMidi // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
Chasidy Heckenbach
19.07.2011
Originally Posted by chaomocha
lol ok, I know you're doing your best with helping me, but this is like my first ever time using anything midi related apart from just plugging in the controller and downloading a map for it, so bear with me when I ask, what the hell is a midi device out? xD yeah, I'm the essence, meaning, and picture in the dictionary of the word "Rookie" lol
np lol. when u connect midi devices they each have a 'name' of some type that will show up in the device list in whatever software you are using. so thats all it means.

any device that can send data (like a midi keyboard) and receive midi (like a pad that lights up on a launchpad) have both a midi IN and an OUT port.
Madeline Seneff
19.07.2011
Originally Posted by zestoi
you're mapping keys on the keyboard to midi note events or cc's i guess yes - if thats what u mean.



first line is to select the midi out device - the number will vary depending on what you have plugged in - they should appear in the same order as in any other midi app. the "debug =" line is so that glovepie will display the name of the device you have chosen - so if its not right just change the number and rerun.

i did also write this glovepie code that allows you to select by the device name - but tbh entering a number in the line above is probably simpler overall.

Code:
var.DevName = "test"

if (var.Init == 0) then
   for var.Count = 0 to 20 do
       midi.DeviceOut = var.Count
       if (midi.OutDevName ~= var.DevName) then
          debug = "Selected: " + midi.OutDevName + " at id=" + floor(var.Count)
          var.Count = 21 // end the loop
       end if
   end for
   var.init = 1
endif
if you wack this code at the top of your glovepie script you then just put the *exact* name of your midi device into "var.DevName"
lol ok, I know you're doing your best with helping me, but this is like my first ever time using anything midi related apart from just plugging in the controller and downloading a map for it, so bear with me when I ask, what the hell is a midi device out? xD yeah, I'm the essence, meaning, and picture in the dictionary of the word "Rookie" lol
Chasidy Heckenbach
19.07.2011
Originally Posted by chaomocha
ok so correct me if I'm wrong, but I'm just labeling all the keys on the keyboard with notes on a instrument?
you're mapping keys on the keyboard to midi note events or cc's i guess yes - if thats what u mean.

and another question but could you explain this a bit more:

Code:
midi.DeviceOut = 8 // device number to use
debug = midi.OutDevName // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
I just don't really know what I'm supposed to do with it or if I'm supposed to change anything or insert something myself, but even if I don't have to do anything, I'd still like to understand what it's doing just in case I ever do this all again.
first line is to select the midi out device - the number will vary depending on what you have plugged in - they should appear in the same order as in any other midi app. the "debug =" line is so that glovepie will display the name of the device you have chosen - so if its not right just change the number and rerun.

i did also write this glovepie code that allows you to select by the device name - but tbh entering a number in the line above is probably simpler overall.

Code:
var.DevName = "test"

if (var.Init == 0) then
   for var.Count = 0 to 20 do
       midi.DeviceOut = var.Count
       if (midi.OutDevName ~= var.DevName) then
          debug = "Selected: " + midi.OutDevName + " at id=" + floor(var.Count)
          var.Count = 21 // end the loop
       end if
   end for
   var.init = 1
endif
if you wack this code at the top of your glovepie script you then just put the *exact* name of your midi device into "var.DevName"
Madeline Seneff
19.07.2011
Originally Posted by zestoi
just map via glovepie using KeyboardX instead of JoystickX as most people use. there's plenty of example scripts around this community .

as a guess this kind of syntax should work fine:

Code:
midi.DeviceOut = 8 // device number to use
debug = midi.OutDevName // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
so midi would only get sent from keyboard2 and buttons A and B in that example.
ok so correct me if I'm wrong, but I'm just labeling all the keys on the keyboard with notes on a instrument? and another question but could you explain this a bit more:

Code:
midi.DeviceOut = 8 // device number to use
debug = midi.OutDevName // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
I just don't really know what I'm supposed to do with it or if I'm supposed to change anything or insert something myself, but even if I don't have to do anything, I'd still like to understand what it's doing just in case I ever do this all again.
Chasidy Heckenbach
17.07.2011
Originally Posted by chaomocha
ya that doesnt sound like it would be much of an issue. lemme make sure im clear on what your saying, if i were to set lets say "t" as an FX or something, the entire duration im holding t, if i also had a word document open and typing in it it would look like this: "ttttttttttttttttttttttttttttttttttttttttttttttttt ttttttttttttttttttttttttttttttt" or however long i hold the button? if so then that shouldnt be a problem with traktor at all. so how would i go about doing this though?
just map via glovepie using KeyboardX instead of JoystickX as most people use. there's plenty of example scripts around this community .

as a guess this kind of syntax should work fine:

Code:
midi.DeviceOut = 8 // device number to use
debug = midi.OutDevName // show device name in use
midi.DefaultChannel = 1 // midi channel to send on
midi.csharp0 = Keyboard2.A
midi.d0 = Keyboard2.B
so midi would only get sent from keyboard2 and buttons A and B in that example.

<< Back to Reviews of DJ equipment Reply
  • Page:
  • 1
  • 2
  • >>
  • Total: 60

Copyright 2012-2023
DJRANKINGS.ORG n.g.o.
Chuo-ku, Osaka, Japan

Created by Ajaxel CMS

Terms & Privacy