Setting Up Midiyoke And Glovepie On Windows 7
Setting Up Midiyoke And Glovepie On Windows 7 Posted on: 25.05.2011 by Joan Kollmorgen I've had a few people asking for help getting Midiyoke and Glovepie working together on Windows 7 in order to run scripts for modded gear.I still like using XP but decided to install Windows 7 64 today to try and see why people were having problems. I can understand some of the confusion because it's so much easier to set up on XP. The problem is the lack of a midimapper in Windows 7. Anyway here's how to get them communicating. Edit: Because me and fbonito have had a similar problem with Midiyoke I'm going to recommend that you use LoopBe instead of Midiyoke as it seems to be more stable on Windows 7. 1, Download and install LoopBe1 from here http://www.nerds.de/en/download.html 4, Download and open Putzlowitsch's Vista MIDI Mapper Control Panel from here http://www.sierrahelp.com/Utilities/...DI_Mapper.html From the drop down menu select Loopbe Internal Midi then click apply 5, Download and install Glovepie from here. http://glovepie.org/poiuytrewq.php I used the top link. Now start Glovepie and load a script or make your own then run it Here is the script i made the other evening for 2 gamepads which works great on XP and 7 http://www.mediafire.com/?dyap2duo5025mo6 | |
| Jacqualine Arroyos 27.05.2011 | hi, thanx, toevening i will try it, just one question, how do i select by index? what is devide8? is there a script to chose the device in glovepie? well... 3 questions after all ... ;-) |
| Chasidy Heckenbach 27.05.2011 |
Originally Posted by fbonito
Code:
midi.DeviceOut = 8 // device number to use debug = midi.OutDevName // show device name in use |
| Jacqualine Arroyos 27.05.2011 |
Originally Posted by zestoi
just a quick not, how do you make glovepie to send data to a specific virtual midi driver? i'm using Putzlowitsch's Vista MIDI Mapper Control Panel to do that, but sometimes it doesn't work well, for instance if i have midiyoke and configure to send data through loobe it still sends data throught midiyoke... |
| Chasidy Heckenbach 26.05.2011 |
Originally Posted by extraclassic
i use loopMIDI to create my virtual midi ports and have had no reason to connect ports together - which is what loopBE does by the looks of it? i just create one loopMIDI port, make glovepie send data to it and make traktor read from it. so i'm actually confused where loopBE would actually be useful at all in this setup... ah... loopBE also has a virtual midi driver as well as doing routing i guess... i'll still stick with loopMIDI as has caused me no issues at all atm and i have about 10 virtual ports created using it atm. |
| Jacqualine Arroyos 25.05.2011 |
Originally Posted by extraclassic
tomorrow i will give it another try... it seams that it's not a problem of loopbe, i've reinstalled midiyoke and the problem is the same if i turn the pots to zero, the buttons don't work, if i turn a know and leave it, buttons work... very strange... very strange... |
| Joan Kollmorgen 25.05.2011 |
not stable here...
I've removed midiyoke and left loopbe and the buttons don't work correctly, the pots work great, the buttons no... in some cases just one game pad works well, the other as a lot of latency, sometimes the buttons only work iff a pot is sending data... i've reinstall midiyoke, and now it's working... lets see till when... Need to get some sleep now before work |
| Jacqualine Arroyos 25.05.2011 |
Originally Posted by extraclassic
I've removed midiyoke and left loopbe and the buttons don't work correctly, the pots work great, the buttons no... in some cases just one game pad works well, the other as a lot of latency, sometimes the buttons only work iff a pot is sending data... i've reinstall midiyoke, and now it's working... lets see till when... |
| Joan Kollmorgen 25.05.2011 | No I haven't tried loopmidi but LoopBe seems stable so far. Ive tried for the last half hour to make it crash but it's solid It might be a good idea to try LoopBe on its own and uninstall the other programs. |
| Jacqualine Arroyos 25.05.2011 |
Originally Posted by extraclassic
if i select loopbe and loopmidi the midi data is still being sent throug midiyoke... maybe there is some kind of conflict or bug with the yoke, i will remove it to try the other software have you tried loopmidi? |
| Joan Kollmorgen 25.05.2011 |
Originally Posted by fbonito
I wrote that script so i could use my gamepad mod's in Traktor. |
| Joan Kollmorgen 25.05.2011 |
well... this is strange...
i was playing around and now it does not work Traktor stopped responding to my gamepad? I tried a few different scripts in Glovpie to see if that was the problem but there was no midi activity at all. Next up i deleted Midiyoke and installed LoopBe and Everythings been working fine for the last 25 minutes I'm believeing zestoi is right. It might be worth using LoopBe instead of Midiyoke Think I'm going to edit the Original post. |
| Jacqualine Arroyos 25.05.2011 |
Originally Posted by extraclassic
|
| Jacqualine Arroyos 25.05.2011 | well... i tryed loopbe and nothing, loopmidi, and nothing... then i uninstall midiyoke and reinstall again, and it's working... strange thing, when i open midiox, it freezes all midi data... :-| it seams that there was a "feedback" i believe problem is solved by now... |
| Chasidy Heckenbach 25.05.2011 |
Originally Posted by fbonito
if his glovepie script stops working again you could always connect midiox to see if midi data is still getting sent out - to make sure its not automap that is buggering things up. you can also monitor values in glovepie (in the "variables" tab) by assigning what you want to look at to variables like this: var.joy_btn1 = Joystick1.Button1 var.joy_btn2 = Joystick1.Button2 etc... i found that more useful when debugging my script than the single debug= line which i just left to show me the midi device i had selected. |
| Chasidy Heckenbach 25.05.2011 |
Originally Posted by extraclassic
atm i'm working on my own code in C++ that will allow me to aggregate my controllers together and use them to control ableton and traktor at the same time. plus be able to do all my traktor mapping using lua (a game programming language that i hadnt heard of until i looked for a simple embeddable scripting language) for all the logic. i love the mapping stuff in traktor but hate the interface so this will allow me to create one massive traktor tsi that maps everything (without any modifiers) and then have complete control over them using lua. i bought midikatapult (a bargain at 20$ if you ask me) but it can't quite do what i need and is only really for the launchpad ofc - so i'll be using my app instead of that too. plus it will allow me to use my launchpad for ableton5 more like how it works in ableton8, with scrolling etc, as i dont want to fork out for a full copy of ableton8 yet. |
| Jacqualine Arroyos 25.05.2011 |
Originally Posted by extraclassic
i was mapping in ableton and all of the sudden it's not responding, i will try loopbe |
| Joan Kollmorgen 25.05.2011 | Are you using Midiyoke or LoopBe? Are you using my script? |
| Jacqualine Arroyos 25.05.2011 | well... this is strange... i was playing around and now it does not work... :-| |
| Joan Kollmorgen 25.05.2011 |
Originally Posted by fbonito
Did you use my script? If so let me know if you want anything adding to it. |
| Joan Kollmorgen 25.05.2011 |
nice tutorial. i guess the only reason to use that midi mapper app tho is to select the default midi output port?
Selecting the midi output port is the where some people seem to be getting lost. I believe Putzlowitsch's midi app will be nice and easy for most people.
in my glovepie script i just used this to select the port:
midi.DeviceOut = 8 // device number to use debug = midi.OutDevName // show device name in use which then also shows the name of the selected device in the glovepie window. That's why i come to these community s in sponge mode (To soak up all the knowledge) |
| Jacqualine Arroyos 25.05.2011 | great men, everything is working ;-) it seams that the problem was the missing Putzlowitsch's Vista MIDI Mapper Control Panel... i owe you two guiness... ;-) |
| Chasidy Heckenbach 25.05.2011 | nice tutorial. i guess the only reason to use that midi mapper app tho is to select the default midi output port? in my glovepie script i just used this to select the port: midi.DeviceOut = 8 // device number to use debug = midi.OutDevName // show device name in use which then also shows the name of the selected device in the glovepie window. i must admit it was a bit trial and error though until i wrote some C++ code to just list the devices. not sure why glovepie doesn't let you select via device name instead of number. i've seen some people mentioning issues with midiyoke on win7 64bit so i'm using loopMIDI with no issues at all. |
| Janell Selser 25.05.2011 | Thanks for taking the time to do this. Bookmarked. |
<< Back to Reviews of DJ equipment Reply