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
4, Download and open Putzlowitsch’s Vista MIDI Mapper Control Panel from here
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.
Yes that’s true.
Selecting the midi output port is the where some people seem to be getting lost. I think Putzlowitsch’s midi app will be nice and easy for most people.
[quote]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.
[/quote]
Thanks for sharing that code. I didn’t know you could do that
That’s why i come to these forums in sponge mode (To soak up all the knowledge)
definately me too… i didn’t even realise there were apps to convert gamepad type input into midi until reading this forum.
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.
definately try loopMIDI - i’ve had no issues with it at all. i use it to create about 10 virtual midi ports at the moment.
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:
i was playing around and now it does not work[/quote]
lol same thing happened to me just after you made that post
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 thinking zestoi is right. It might be worth using LoopBe instead of Midiyoke
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…