Need help with ambitious project - DJ Hero Midi Control for windows.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

BestBeat — Sat, 27 Jul 2013 12:22:22 +0200

HELP ME !!!!!!!!!!

The dj hero Controller ins connected Tor my PC's Bluetooth
And it works with glovepie's key mapping but MIDI dosn't work
Glovepie US connected to Thema wiimote with TT
Pole ins activate and IT says true
But i can't mapping IT in Traktor
Im using MIDI Yoke

WHATS WRONG ??????????????????

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Thu, 21 Feb 2013 01:56:41 +0100

Ok sorry to be that guy posting his terrible code in the forum, but right now I'm that guy.

I went back to the original code. Right now I have two wiimotes working. One has a mixer and two turntables. The other has only the mixer. Everything works as it should except my wiimote2 only sends data from the remote. It is ignoring the mixer. The variables all read at their highest , CS at 7, SX and SY at 32, ED at 31.

Will a mixer work by itself or does it have to have at least 1 turntable to function? Here is what I have

Quote

/// Wii DJ Hero Midi Output
// Jezzick (Thanks to Facing Tomorrow and Guy from GlovePie.org)
// Traktor/Osculator changes by Moz

debug="<"+wiimote.Exists+"> "

if(wiimote.Exists) then
if(key.Space) then
debug+=" *** POKE!! ***"
var.space=true
var.ini=true
endif
if(!var.space) debug+=" Safe to connect. Press SPACE to poke"
else
debug+=" ..waiting to connect.."
wait 10ms
endif

if(var.ini) then
debug+=" Active :D"
if(!var.init) then
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type

midi.DeviceOut = 2
midi.DefaultChannel = 1

var.init = true
endif

var.SX = (wiimote1.Exp0 & 0x3F) - 31
var.SY = (wiimote1.Exp1 & 0x3F) - 31
var.BE = !(wiimote1.Exp5 & 0x10)
var.BM = !(wiimote1.Exp4 & 0x10)
var.BP = !(wiimote1.Exp4 & 0x04)
var.ED = ((wiimote1.Exp2 & 0x60) >> 2) + ((wiimote1.Exp3 & 0xE0) >> 5)
var.CS = ((wiimote1.Exp2 & 0x1E) >> 1) - 8
var.RTT =((wiimote1.Exp0 & 0xC0) >> 3) + ((wiimote1.Exp1 & 0xC0) >> 5) + ((wiimote1.Exp2 & 0x80) >> 7)
if (wiimote1.Exp2 & 0x01) var.RTT = var.RTT - 32
var.RBG =!(wiimote1.Exp5 & 0x20)
var.RBR =!(wiimote1.Exp4 & 0x02)
var.RBB =!(wiimote1.Exp5 & 0x04)
var.LTT = (wiimote1.Exp3 & 0x1F)
if (wiimote1.Exp4 & 0x01) var.LTT = var.LTT - 32
var.LBG =!(wiimote1.Exp5 & 0x08)
var.LBR =!(wiimote1.Exp4 & 0x20)
var.LBB =!(wiimote1.Exp5 & 0x80)

var.WONE = wiimote1.One
var.WTWO = wiimote1.Two
var.WA = wiimote1.A
var.WDOWN = wiimote1.Down
var.WUP = wiimote1.Up
var.WHOME = wiimote1.Home
var.WPLUS = wiimote1.Plus
var.WMINUS = wiimote1.Minus

var.SX2 = (wiimote2.Exp0 & 0x3F) - 31
var.SY2 = (wiimote2.Exp1 & 0x3F) - 31
var.BE2 = !(wiimote2.Exp5 & 0x10)
var.BM2 = !(wiimote2.Exp4 & 0x10)
var.BP2 = !(wiimote2.Exp4 & 0x04)
var.ED2 = ((wiimote2.Exp2 & 0x60) >> 2) + ((wiimote2.Exp3 & 0xE0) >> 5)
var.CS2 = ((wiimote2.Exp2 & 0x1E) >> 1) - 8

var.WONE2 = wiimote2.One
var.WTWO2 = wiimote2.Two
var.WA2 = wiimote2.A
var.WDOWN2 = wiimote2.Down
var.WUP2 = wiimote2.Up
var.WHOME2 = wiimote2.Home
var.WPLUS2 = wiimote2.Plus
var.WMINUS2 = wiimote2.Minus

if(var.CS<0)var.CS++

if not var.BE == var.BE1 then midi.Control0 = var.BE
if not var.BM == var.BM1 then midi.Control1 = var.BM
if not var.BP == var.BP1 then midi.Control2 = var.BP
if not var.ED == var.ED1 then midi.Control3 = MapRange(var.ED,0,31,0,1)
if not var.RBG == var.RBG1 then midi.Control4 = var.RBG
if not var.RBB == var.RBB1 then midi.Control5 = var.RBB
if not var.RBR == var.RBR1 then midi.Control6 = var.RBR
if not var.RTT == 0 then midi.Control7 = MapRange(var.RTT,-30,30,0,1)
if not var.CS == var.CS1 then midi.Control8 = MapRange(var.CS,-7,7,0,1)
if not var.WONE == var.WONE1 then midi.Control9 = var.WONE
if not var.WTWO == var.WTWO1 then midi.Control10 = var.WTWO
if not var.WA == var.WA1 then midi.Control11 = var.WA
if not var.WDOWN == var.WDOWN1 then midi.Control12 = var.WDOWN
if not var.WUP == var.WUP1 then midi.Control13 = var.WUP
if not var.SX == 0 then midi.Control14 = MapRange(var.SX,-31,32,0,1)
if not var.SY == 0 then midi.Control15 = MapRange(var.SY,-31,32,0,1)
if not var.WHOME == var.WHOME1 then midi.Control16 = var.WHOME
if not var.WPLUS == var.WPLUS1 then midi.Control17 = var.WPLUS
if not var.WMINUS == var.WMINUS1 then midi.Control18 = var.WMINUS

var.SX1 = var.SX
var.SY1 = var.SY
var.BE1 = var.BE
var.BM1 = var.BM
var.BP1 = var.BP
var.ED1 = var.ED
var.CS1 = var.CS
var.RTT1 = var.RTT
var.RBG1 = var.RBG
var.RBR1 = var.RBR
var.RBB1 = var.RBB
var.LTT1 = var.LTT
var.LBG1 = var.LBG
var.LBR1 = var.LBR
var.LBB1 = var.LBB
var.WONE1 = var.WONE
var.WTWO1 = var.WTWO
var.WA1 = var.WA
var.WDOWN1 = var.WDOWN
var.WUP1 = var.WUP
var.WHOME1 = var.WHOME
var.WPLUS1 = var.WPLUS
var.WMINUS1 = var.WMINUS
endif

if(var.CS2<0)var.CS2++

if not var.BE2 == var.BE12 then midi.Control50 = var.BE2
if not var.BM2 == var.BM12 then midi.Control51 = var.BM2
if not var.BP2 == var.BP12 then midi.Control52 = var.BP2
if not var.ED2 == var.ED12 then midi.Control53 = MapRange(var.ED2,0,31,0,1)
if not var.CS2 == var.CS12 then midi.Control58 = MapRange(var.CS2,-7,7,0,1)
if not var.WONE2 == var.WONE12 then midi.Control59 = var.WONE2
if not var.WTWO2 == var.WTWO12 then midi.Control60 = var.WTWO2
if not var.WA2 == var.WA12 then midi.Control61 = var.WA2
if not var.WDOWN2 == var.WDOWN12 then midi.Control62 = var.WDOWN2
if not var.WUP2 == var.WUP12 then midi.Control63 = var.WUP2
if not var.SX2 == 0 then midi.Control64 = MapRange(var.SX2,-31,32,0,1)
if not var.SY2 == 0 then midi.Control65 = MapRange(var.SY2,-31,32,0,1)
if not var.WHOME2 == var.WHOME12 then midi.Control66 = var.WHOME2
if not var.WPLUS2 == var.WPLUS12 then midi.Control67 = var.WPLUS2
if not var.WMINUS2 == var.WMINUS12 then midi.Control68 = var.WMINUS2

var.SX12 = var.SX2
var.SY12 = var.SY2
var.BE12 = var.BE2
var.BM12 = var.BM2
var.BP12 = var.BP2
var.ED12 = var.ED2
var.CS12 = var.CS2
var.WONE12 = var.WONE2
var.WTWO12 = var.WTWO2
var.WA12 = var.WA2
var.WDOWN12 = var.WDOWN2
var.WUP12 = var.WUP2
var.WHOME12 = var.WHOME2
var.WPLUS12 = var.WPLUS2
var.WMINUS12 = var.WMINUS2
endif

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Wed, 20 Feb 2013 19:10:35 +0100

One thing for sure wrong with my script is I have LTT assigned twice. Since last post I have decided to just use the right turn table on each mixer to eliminate the need for the LTT variable.

I have managed to get my computer to recieve midi from the wiimote/djhero/glovepie/midiyoke configuration again. However, in the bottom corner of Deckadance (the software I am using) it displays incoming midi signals. It just cycles over and over let its getting constantly hit with midi notes. Must be some place in the script causing an infinate loop of midi notes or something like that.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Wed, 20 Feb 2013 13:32:35 +0100

I stepped away from this project for a while after breaking down and spending money on a new Launchpad but once again have a need for the Wii DJ Hero Midi controller. I'm not sure how I messed things up but my script no longer works.

I was getting an error from MidiYoke saying that feedback was detected. I took that to mean I was sending to the same Midi channel twice. I'm in Windows XP Pro, in sound settings, my default Midi playback device was set to MidiYoke 1. I changed the option to my Tascam US-122. Microsoft GS Wavetable was the only other option. Well that and 16 MidiYoke channels.

So now I see the variables changing in Glovepie as they should, I am getting no feedback errors, but I am not sending Midi from my Wiimotes.

There is another script out, Wii2MIDIv1.4. It differs from this script in the following ways:
1.) It sends Midi notes rather than controls
2.) does not have a line giving a midi.DeviceOut and
3.) rather than saying generic Midi.ControlXX it has Midi.Yoke1.Channel1.C5 listing specific notes

The Wii2MIDI script works. With no deviceout and with the full name of the midi channel. So my thinking was, I will change the DJ Hero script to work the same way. It does not! I even tried taking out all variables except the ones listed in Wii2MIDI and it still doesn't work.

I am almost certain that my error is in the way I have Glovepie using 2 Wiimotes and 2 DJ Hero sets. In setting up 2 sets of variables and 2 Wiimotes I may have messed something up in the configs.

For example, for the crossfader there is a line: if(var.CS<0)var.CS++

That statement is ended at the bottom of the script. But having a CS and CS1, do I not need to have the same line of code with CS1? When I place an End If between the two sets of variables and include: if(var.CS1<0)var.CS1++ Glovepie locks up and my PC fans kick into overdrive.

I would be happy with either:1 Mixer with 2 turntables on right and left and the other mixer being just a mixer, or using a mixer and turntable together as 2 sets. What I REALLY want are the 2 mixers anyway, the turntables are mostly for looks and the 3 extra buttons. So if a 2 turntable 1 mixer on the same Wiimote is the easiest way, I would still like for there to be a way to use other mixer by itself.

Here is the script I have been trying to fix. Any advice would be great. It must be something simple that I'm just not seeing. Either that or I have a bad component in one of my mixers sending errors.

Quote

debug="<"+wiimote.Exists+"> "

if(wiimote.Exists) then
if(key.Space) then
debug+=" *** POKE!! ***"
var.space=true
var.ini=true
endif
if(!var.space) debug+=" Safe to connect. Press SPACE to poke"
else
debug+=" ..waiting to connect.."
wait 10ms
endif

if(var.ini) then
debug+=" Active :D"
if(!var.init) then
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type

midi.DeviceOut = 2
midi.DefaultChannel = 1

var.init = true
endif

var.SX = (wiimote2.Exp0 & 0x3F) - 31
var.SY = (wiimote2.Exp1 & 0x3F) - 31
var.BE = !(wiimote2.Exp5 & 0x10)
var.BM = !(wiimote2.Exp4 & 0x10)
var.BP = !(wiimote2.Exp4 & 0x04)
var.ED = ((wiimote2.Exp2 & 0x60) >> 2) + ((wiimote2.Exp3 & 0xE0) >> 5)
var.CS = ((wiimote2.Exp2 & 0x1E) >> 1) - 8
var.RTT =((wiimote2.Exp0 & 0xC0) >> 3) + ((wiimote2.Exp1 & 0xC0) >> 5) + ((wiimote2.Exp2 & 0x80) >> 7)
if (wiimote2.Exp2 & 0x01) var.RTT = var.RTT - 32
var.RBG =!(wiimote2.Exp5 & 0x20)
var.RBR =!(wiimote2.Exp4 & 0x02)
var.RBB =!(wiimote2.Exp5 & 0x04)
var.LTT = (wiimote2.Exp3 & 0x1F)
if (wiimote2.Exp4 & 0x01) var.LTT = var.LTT - 32
var.LBG =!(wiimote2.Exp5 & 0x08)
var.LBR =!(wiimote2.Exp4 & 0x20)
var.LBB =!(wiimote2.Exp5 & 0x80)
var.WONE = Wiimote2.One
var.WTWO = Wiimote2.Two
var.WA = Wiimote2.A
var.WDOWN = Wiimote2.Down
var.WUP = Wiimote2.Up
var.WHOME = Wiimote2.Home
var.WPLUS = Wiimote2.Plus
var.WMINUS = Wiimote2.Minus

var.SX1 = (wiimote1.Exp0 & 0x3F) - 31
var.SY1 = (wiimote1.Exp1 & 0x3F) - 31
var.BE1 = !(wiimote1.Exp5 & 0x10)
var.BM1 = !(wiimote1.Exp4 & 0x10)
var.BP1 = !(wiimote1.Exp4 & 0x04)
var.ED1 = ((wiimote1.Exp2 & 0x60) >> 2) + ((wiimote1.Exp3 & 0xE0) >> 5)
var.CS1 = ((wiimote1.Exp2 & 0x1E) >> 1) - 8
var.RTT1 =((wiimote1.Exp0 & 0xC0) >> 3) + ((wiimote1.Exp1 & 0xC0) >> 5) + ((wiimote1.Exp2 & 0x80) >> 7)
if (wiimote1.Exp2 & 0x01) var.RTT1 = var.RTT1 - 32
var.RBG1 =!(wiimote1.Exp5 & 0x20)
var.RBR1 =!(wiimote1.Exp4 & 0x02)
var.RBB1 =!(wiimote1.Exp5 & 0x04)
var.LTT1 = (wiimote1.Exp3 & 0x1F)
if (wiimote1.Exp4 & 0x01) var.LTT1 = var.LTT1 - 32
var.LBG1 =!(wiimote1.Exp5 & 0x08)
var.LBR1 =!(wiimote1.Exp4 & 0x20)
var.LBB1 =!(wiimote1.Exp5 & 0x80)
var.WONE1 = Wiimote1.One
var.WTWO1 = Wiimote1.Two
var.WA1 = Wiimote1.A
var.WDOWN1 = Wiimote1.Down
var.WUP1 = Wiimote1.Up
var.WHOME1 = Wiimote1.Home
var.WPLUS1 = Wiimote1.Plus
var.WMINUS1 = Wiimote1.Minus

if(var.CS<0)var.CS++
midi.Yoke1.channel1.C1 = var.BE
midi.Yoke1.channel1.C2 = var.BM
midi.Yoke1.channel1.C3 = var.BP
midi.Control3 = MapRange(var.ED,0,31,0,1)
midi.Yoke1.channel1.B1 = var.RBG
midi.Yoke1.channel1.B2 = var.RBB
midi.Yoke1.channel1.B3 = var.RBR
midi.Yoke1.channel1.B4 = var.LBG
midi.Yoke1.channel1.B5 = var.LBB
midi.Yoke1.channel1.B6 = var.LBR
midi.Control6 = MapRange(var.LTT,-30,30,0,1)
midi.Control7 = MapRange(var.RTT,-30,30,0,1)
midi.Control8 = MapRange(var.CS,-7,7,0,1)
midi.Yoke1.channel1.C4 = var.WONE
midi.Yoke1.channel1.C5 = var.WTWO
midi.Yoke1.channel1.C6 = var.WA
midi.Yoke1.channel1.C7 = var.WDOWN
midi.Yoke1.channel1.C8 = var.WUP
midi.Control14 = MapRange(var.SX,-31,32,0,1)
midi.Control15 = MapRange(var.SY,-31,32,0,1)
midi.Yoke1.channel1.Csharp1 = var.WHOME
midi.Yoke1.channel1.Csharp2 = var.WPLUS
midi.Yoke1.channel1.Csharp3 = var.WMINUS+
endif
if(var.CS1<0)var.CS1++
midi.Yoke1.channel1.Csharp4 = var.BE1
midi.Yoke1.channel1.Csharp5 = var.BM1
midi.Yoke1.channel1.Csharp6 = var.BP1
midi.Control22 = MapRange(var.ED1,0,31,0,1)
midi.Yoke1.channel1.A1 = var.RBG1
midi.Yoke1.channel1.A2 = var.RBB1
midi.Yoke1.channel1.A3 = var.RBR1
midi.Yoke1.channel1.A4 = var.LBG
midi.Yoke1.channel1.A5 = var.LBB
midi.Yoke1.channel1.A6 = var.LBR
midi.Control25 = MapRange(var.LTT,-30,30,0,1)
midi.Control26 = MapRange(var.RTT1,-30,30,0,1)
midi.Control28 = MapRange(var.CS1,-7,7,0,1)
midi.Yoke1.channel1.Csharp7 = var.WONE1
midi.Yoke1.channel1.Csharp8 = var.WTWO1
midi.Yoke1.channel1.E1 = var.WA1
midi.Yoke1.channel1.E2 = var.WDOWN1
midi.Yoke1.channel1.E3 = var.WUP1
midi.Control34 = MapRange(var.SX1,-31,32,0,1)
midi.Control35 = MapRange(var.SY1,-31,32,0,1)
midi.Yoke1.channel1.E4 = var.WHOME1
midi.Yoke1.channel1.E5 = var.WPLUS1
midi.Yoke1.channel1.E6 = var.WMINUS1
endif

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Fri, 21 Sep 2012 18:07:49 +0200

I have returned to publicly confess that I have totally been doing this all wrong. Only now did i realize that there is a cover on the side of the mixer that pops off allowing for two decks to connect with one remote. I have really gone out of my way rewriting the midi mappings for two remotes with two totally different sets of variables... all of the questions I had about why this script is written the way that it is were answered the moment I knocked my mixer off the table and the side covering popped off.

I've been a fool, a noob even, it's so obvious! I cannot believe I have had this stuff since Christmas and I JUST NOW noticed, and now the variables LTT and RTT finally make sense. I have written the MAC address of each wiimote on its assigned set of turntables, and on the wiimote, so I would not have to worry getting them mixed up. My logic was functional, but still incorrect, my perspective on this issue was just so wrong. I suppose the universe has it's own way of dealing out justice and I probably had it coming anyway.

On the other hand it forced me to learn how to script with Glovepie and I have used that knowledge to tackle several other issues I have had with controlling midi in a DAW or DJ program. Thanks for taking the time to post this topic and to help out a random stranger.

Ive been using these things almost every day for 9-10 months and just now noticed.... ridiculous, the shame!

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Thu, 26 Jul 2012 00:29:04 +0200

if you like glovepie scripting, you might check out virtual dj pro. it's got a scripting language that makes midi mapping and custom controls waaay easier. i considered switching over to traktor, but once i started mapping the midi, it really wasn't easy, if even possible, to do the same things.

haha, yeah. it took quite some time to even find a bit of info about doing this, and i'm not sure i can even find the original again.
but yeah, if you need any help with any of the scripting, feel free to ask.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Sun, 22 Jul 2012 07:24:21 +0200

bout to test it out. got the balance board run'n midi through a script i found, another wiimote w. nunchuck in a differnt prog in VM sending midi over vlan, 3 oldish blackberry bluetoothd with different keymapping input apps, 2 ati old school wonder remotes mapped, but i do have at least have a real midi keyboard from radioshack lol. if i was a rich man, i'd go buy some gear to do all this... but im not so i gotta be creative.

basically, this script isnt just saving me time producing but its saving me $$$ cause i can use all these other perephrial devices to do the same thing expensive midi controllers do pretty much, i wouldnt call these things professional equipment by themselves but it can be done well if its done right. plus most of them are light, portable, cross platform, not going out of style ever, cheap, can do other stuff besides just be a $2000 keyboard, so many advantages to using scripting programs like Glovepie.

im loving glovepie, this loopbe, midiox midi yoke stuff, bluetooth'n up some random stuff in my house, turn'n them into FL studio and ableton midi controllers, traktor is actually fun to use now when before i hated it when someone insisted on me using it, and the ppjoy virtual joystick midi controllers, its like omg.

best forum thread, ever, official. thanks so much for this i can't tell you how much this has improved my daily life lol thats probably sad but i stand by it.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Sun, 22 Jul 2012 04:45:46 +0200

yeah, if i remember right, just change all the 'wiimote' to 'wiimote1' and 'wiimote2' for the second controller. it's been a while since i was messing around with that stuff, but that should work
pointless hobbies ftw!!

'Anti-spam software on this server has detected that your message might be spam. You are still allowed to post this message, but it will not be visible in the forums until a moderator approves it. You can now try to re-submit your posting.' O.o

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Sun, 22 Jul 2012 03:23:57 +0200

ok yes, there are two sets of variables listed on the variables tab in glovepie once the script has been activated.

but, both sets of data were mapped to 1 wiimote. i can see that my other remote is indeed connected, i can open the properties of both remotes and see that i am getting a signal.. so not a pairing problem.

any advice on how i can get glovepie to split the data between the two remotes? if you'd rather not explain it, a link to a tutorial or simple statement to google will do... i dont mind doin the work to figure it out but if someone already knows well then... reinventing the wheel never got anyone anywhere :)

thanks to everyone here for their contributions you guys make my pointless hobbies possible and thats just great. any info on the topic would be greatly appreciated.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Sun, 22 Jul 2012 02:43:50 +0200

really? i never tried it i just assumed that since it wasnt described as two decks that it would need to be altered. ill give that a shot thanks for your quick response i do appreciate it.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Sat, 21 Jul 2012 05:44:03 +0200

it looks like that script should already allow the left and right decks, with each deck having its own data and variables..

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

gnunoob — Sat, 21 Jul 2012 02:22:27 +0200

Moz77, I am using your script for my dj hero deck and its working great thank you for your contribution it has been of great value to me.

lets say i want to use both decks... and both decks to have individual midi controls not share the same variables. How can I change the script to recognize two decks?

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Sat, 10 Dec 2011 06:48:16 +0100

alright, hope all is going well on your guy's endeavors!
so i finally played the actual dj hero game today and noticed something that would normally go un-noticed
it appears that the euphoria button has a light, which is obviously controlled by the game
anyone know of a way to control this light, so you could like make it show the state of an fx or flash to the beat

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Wed, 14 Sep 2011 20:41:40 +0200

o hey, one thing i noticed is that when you use a low number control (control5, etc.), it appears that it also doubles it on a control message 32 higher. so if you happen to expand you code to use more than 32 control messages, once you map the 33rd it'll also react to the first one. i believe this is from the actual midi, having a LSB and MSB for certain values.

nice Moz, though the different syntaxes throughout the code can get a bit confusing :P
also, one thing you might put in your code is a way so the script finds the proper midi device to use incase your loopbe/midiyoke isn't the first device
o and is the ' for not? it looks like it might be, but then you use it on var.sx (non-boolean)
and like i say earlier, i would suggest you try out virtual dj pro, even if you don't plan on using it. the scripting is amazing on it

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

moz77 — Wed, 14 Sep 2011 20:19:49 +0200

Thanks to everyone that has contributed before..

Here's a short tutorial on how I got everything working + a modified script:

I've changed all of the mappings to be the same as the Osculator template.
Some of the code is commented out (the Left Turntable + Unused buttons) as I found that the more midi traffic you have the slower my pc gets!
The code isn't complete and is a bit crude, but at least everything including the turntable is working :)

Software used:
Windows 7 x86
GlovePIE 0.43
Midiyoke
Traktor 2.03

Install everything, for Midiyoke on windows 7, Disable UAC, Reboot, Install Midiyoke, then Reboot again!
To help with the Bluetooth, Right mouse on the Bluetooth icon, click Open Settings and tick the Allow Bluetooth devices to find this computer
Then go to Control Panel / System and Security / System and click Advanced System Settings on the Left
Click the Hardware tab and then Device Installation Settings, Change to: No, let me choose what to do and tick Install driver software from Windows Update.. (this speeds up the driver install as the wiimote is normally asleep by the time it's finished)

Now you are good to go:
Open Glovepie, load up the script below, click the Run button
Make sure that the remote is not plugged into DJ Hero then hold down 1+2 at the same time, so the Wiimote tries to Pair with your pc.
The Wiimote should install and the GlovePIE message will change, plug the DJ Hero in and press the Space Bar (make sure that the GlovePIE Stop/Run button isn't highlighted or else the Space Bar will click Stop!)

Now open Traktor and go to: File / Controller Manager, click Add / Import and open the DJ Hero.tsi file (from the Osculator template)
It installs a few different Keyboard and Midi templates, so delete the ones that you don't want.

Now change the following:
Set In-Port to: In From Midi-Yoke: 1
Change:
X-Fader to Direct
Scratch to 4% Sensitivity
Play/Pause to Toggle
Filter On to Toggle

Also for a bit of fun (Master Level on the Wiimote LED's)
Set Out-Port to: In From Midi-Yoke: 1
Add 4 Out's as:

Out / Master Level / Ch01.CC.101 / Midi Range: 0 / 95
Out / Master Level / Ch01.CC.102 / Midi Range: 0 / 85
Out / Master Level / Ch01.CC.103 / Midi Range: 0 / 75
Out / Master Level / Ch01.CC.104 / Midi Range: 0 / 65
All with Controller Range: Min: 0.000000 / Max: 1.000000

If you don't need the output's then you can comment them out in the code.

Have Fun!
Moz

Original Osculator template which is available here:
Osculator Template

// Wii DJ Hero Midi Output
// Jezzick (Thanks to Facing Tomorrow and Guy from GlovePie.org)
// Traktor/Osculator changes by Moz

debug="<"+wiimote.Exists+"> "

if(wiimote.Exists) then
if(key.Space) then
debug+=" *** POKE!! ***"
var.space=true
var.ini=true
endif
if(!var.space) debug+=" Safe to connect. Press SPACE to poke"
else
debug+=" ..waiting to connect.."
wait 10ms
endif

if(var.ini) then
debug+=" Active :D"
if(!var.init) then
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type

midi.DeviceOut = 2
midi.DefaultChannel = 1

var.init = true
endif

var.SX = (wiimote.Exp0 & 0x3F) - 31
var.SY = (wiimote.Exp1 & 0x3F) - 31
var.BE = !(wiimote.Exp5 & 0x10)
var.BM = !(wiimote.Exp4 & 0x10)
var.BP = !(wiimote.Exp4 & 0x04)
var.ED = ((wiimote.Exp2 & 0x60) >> 2) + ((wiimote.Exp3 & 0xE0) >> 5)
var.CS = ((wiimote.Exp2 & 0x1E) >> 1) - 8
var.RTT =((wiimote.Exp0 & 0xC0) >> 3) + ((wiimote.Exp1 & 0xC0) >> 5) + ((wiimote.Exp2 & 0x80) >> 7)
if (wiimote.Exp2 & 0x01) var.RTT = var.RTT - 32
var.RBG =!(wiimote.Exp5 & 0x20)
var.RBR =!(wiimote.Exp4 & 0x02)
var.RBB =!(wiimote.Exp5 & 0x04)
'var.LTT = (wiimote.Exp3 & 0x1F)
'if (wiimote.Exp4 & 0x01) var.LTT = var.LTT - 32
'var.LBG =!(wiimote.Exp5 & 0x08)
'var.LBR =!(wiimote.Exp4 & 0x20)
'var.LBB =!(wiimote.Exp5 & 0x80)

var.WONE = Wiimote.One
var.WTWO = Wiimote.Two
var.WA = Wiimote.A
var.WDOWN = Wiimote.Down
var.WUP = Wiimote.Up
var.WHOME = Wiimote.Home
var.WPLUS = Wiimote.Plus
var.WMINUS = Wiimote.Minus

var.WLED1 = midi.Control101
var.WLED2 = midi.Control102
var.WLED3 = midi.Control103
var.WLED4 = midi.Control104

if(var.CS<0)var.CS++

if not var.BE == var.BE1 then midi.Control0 = var.BE
if not var.BM == var.BM1 then midi.Control1 = var.BM
if not var.BP == var.BP1 then midi.Control2 = var.BP
if not var.ED == var.ED1 then midi.Control3 = MapRange(var.ED,0,31,0,1)
if not var.RBG == var.RBG1 then midi.Control4 = var.RBG
if not var.RBB == var.RBB1 then midi.Control5 = var.RBB
if not var.RBR == var.RBR1 then midi.Control6 = var.RBR
if not var.RTT == 0 then midi.Control7 = MapRange(var.RTT,-30,30,0,1)
if not var.CS == var.CS1 then midi.Control8 = MapRange(var.CS,-7,7,0,1)
if not var.WONE == var.WONE1 then midi.Control9 = var.WONE
if not var.WTWO == var.WTWO1 then midi.Control10 = var.WTWO
if not var.WA == var.WA1 then midi.Control11 = var.WA
if not var.WDOWN == var.WDOWN1 then midi.Control12 = var.WDOWN
if not var.WUP == var.WUP1 then midi.Control13 = var.WUP
'if not var.SX == 0 then midi.Control14 = MapRange(var.SX,-31,32,0,1)
if not var.SY == 0 then midi.Control15 = MapRange(var.SY,-31,32,0,1)
if not var.WHOME == var.WHOME1 then midi.Control16 = var.WHOME
if not var.WPLUS == var.WPLUS1 then midi.Control17 = var.WPLUS
if not var.WMINUS == var.WMINUS1 then midi.Control18 = var.WMINUS
Wiimote.Led1 = var.WLED1
Wiimote.Led2 = var.WLED2
Wiimote.Led3 = var.WLED3
Wiimote.Led4 = var.WLED4

'var.SX1 = var.SX
'var.SY1 = var.SY
var.BE1 = var.BE
var.BM1 = var.BM
var.BP1 = var.BP
var.ED1 = var.ED
var.CS1 = var.CS
'var.RTT1 = var.RTT
var.RBG1 = var.RBG
var.RBR1 = var.RBR
var.RBB1 = var.RBB
'var.LTT1 = var.LTT
'var.LBG1 = var.LBG
'var.LBR1 = var.LBR
'var.LBB1 = var.LBB
var.WONE1 = var.WONE
var.WTWO1 = var.WTWO
var.WA1 = var.WA
var.WDOWN1 = var.WDOWN
var.WUP1 = var.WUP
var.WHOME1 = var.WHOME
var.WPLUS1 = var.WPLUS
var.WMINUS1 = var.WMINUS
var.WLED1 = var.WLED11
var.WLED2 = var.WLED21
var.WLED3 = var.WLED31
var.WLED4 = var.WLED41

endif

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Sun, 04 Sep 2011 05:41:40 +0200

the channels are actually 0 indexed, so channel="1" is channel 2
if that doesn't work, on mine, i made the name the same as the driver name, though not sure if that makes a difference (anywhere at all...)
other than that, it looks good so far

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Thu, 01 Sep 2011 23:28:11 +0200

Well, I can get VDJ to respond to my equipment, but only in Simple MIDI Mapper... which doesnt support Rotary encoders of any sort. >_<

I need to know how to write the midi messages and the definition so that it will work in vDJ
Heres the Glovepie Script I used -

midi.Control7 = MapRange(var.CS,-7,7,0,1) // crossfader
midi.Control8 = MapRange(var.RTT,30,30,0,1) //Turntable

and the VDJ Definition -

< device name="WiiDJHero2" author="Jezzick" type="MIDI" decks="2" drivernamein="LoopBe Internal MIDI">
< encoder cc="0x08" zero=0" name="Turntable" channel="1" deck="2" />
< slider cc="0x07" name="Crossfader" channel="1"/>
< /device>

Do you have an Idea of why it doesn't respond?

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Thu, 01 Sep 2011 22:30:20 +0200

yeah, i made a device definition, which will let you name all the midi signals with name, so it's waay easier to see what's what in vdj. it'll also let you do output (LED control, etc.). o and one thing you might notice is that because this scripting is a repetitive type, unlike most other programming, i'll sometimes do weird things. like if you map a button to 'play_stutter', you might find that holding it down causes it to stutter so fast it doesn't move. what i've done with most of the messages is make it so it only updates it when you need to. for most of the buttons you only need to send the 'true' value to trigger it and you only want to actually send it once the button is pushed (not the whole time it is pushed). it might be alright for a while, if you can make it work for you, but if you keep expanding you code and it passes the magical barrier, you have issues. really what i mean is LoopBe seems to have two ways to detect feedback, sending a unique message that if found on the input will then mute the routing, and if it has too many messages at once (like all you controls are trying to send messages at once). i annoyingly found this out the hard way. if you have things like using the wiimote pitch, turntables, and other things that use a good amount of data always going, it will overload it. so you might keep a variable, and only when that variable changes then update the midi message. it'll also make it easier for debugging. for me, i just used my daw to look at the midi stream, thus telling me what messages/values are being sent. if one is being sent continuously, it's really hard to see the stuff that isn't
i see i'm being kinda vague, so if you have specific questions, i can answer them more directly :P

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Thu, 01 Sep 2011 21:23:34 +0200

VDJ recognizes my midi commands now... Heres what Ive got so far:

----------------------------------------------------------------------------

// Wii DJ Hero Midi Output
// Jezzick (Thanks to Facing Tomorrow and Guy from GlovePie.org)

debug="<"+wiimote.Exists+"> "

if(wiimote.Exists) then
if(key.Space) then
debug+=" *** POKE!! ***"
var.space=true
var.ini=true
endif
if(!var.space) debug+=" Safe to connect. Press SPACE to poke"
else
debug+=" ..waiting to connect.."
endif

if(var.ini) then
debug+=" Active :D"
if(!var.init) then
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type

midi.deviceOut = 2
var.MidiOut = midi.OutDevName
midi.defaultChannel = 1

var.init = true
endif

var.SX = (wiimote.Exp0 & 0x3F) - 31
var.SY = (wiimote.Exp1 & 0x3F) - 31
var.BE = !(wiimote.Exp5 & 0x10)
var.BM = !(wiimote.Exp4 & 0x10)
var.BP = !(wiimote.Exp4 & 0x04)
var.ED = ((wiimote.Exp2 & 0x60) >> 2) + ((wiimote.Exp3 & 0xE0) >> 5)
var.CS = ((wiimote.Exp2 & 0x1E) >> 1) - 8
var.RTT =((wiimote.Exp0 & 0xC0) >> 3) + ((wiimote.Exp1 & 0xC0) >> 5) + ((wiimote.Exp2 & 0x80) >> 7)
if (wiimote.Exp2 & 0x01) var.RTT = var.RTT - 32
var.RBG =!(wiimote.Exp5 & 0x20)
var.RBR =!(wiimote.Exp4 & 0x02)
var.RBB =!(wiimote.Exp5 & 0x04)
var.LTT = (wiimote.Exp3 & 0x1F)
if (wiimote.Exp4 & 0x01) var.LTT = var.LTT - 32
var.LBG =!(wiimote.Exp5 & 0x08)
var.LBR =!(wiimote.Exp4 & 0x20)
var.LBB =!(wiimote.Exp5 & 0x80)
if(var.CS<0)var.CS++

midi.Control1 = MapRange(var.SX,-31,32,0,1)
midi.Control2 = MapRange(var.SY,-31,32,0,1)
midi.Control3 = var.BE
midi.Control4 = var.BM
midi.Control5 = var.BP
midi.Control6 = MapRange(var.ED,0,31,0,1)
midi.Control7 = MapRange(var.CS,-7,7,0,1)
midi.Control8 = MapRange(var.RTT,30,30,0,1)
midi.Control9 = var.RBG
midi.Control10 = var.RBR
midi.Control11 = var.RBB
midi.Control12 = MapRange(var.LTT,30,30,0,1)
midi.Control13 = var.LBG
midi.Control14 = var.LBR
midi.Control15 = var.LBB

endif
--------------------------------------------------------------------

Now I just need to figure out how to map the jogwheels in VDJ to the turntables. everything else works, but I have yet to figure out how to wire them. I will most likely have to write a definition and a mapper to do so, but we will see. ^_^

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Thu, 01 Sep 2011 08:58:09 +0200

Wow. That was pretty cool... I like your mix too. ^_^

I was using Traktor, because thats what the other person who used the dj hero tables to do used. He was on mac tho. >_<

I have loaded up VDJ now, And found I do like it better. Just need to figure out how to map the midi and im good. Thus far I have not once gotten CDJ to recognize my midi signals, on MIDI yoke or LoopBe

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Thu, 01 Sep 2011 05:35:15 +0200

for the turntable, the dj software usually has options to whether the 0 velocity is at 0 or 64 so it doesn't matter too much, as long as you know when you start mapping it. for the buttons, you can just assign the boolean value, which will end up sending 0x00 (false) or 0x7F (true). for the rest, just make it so you assign the midi value something between 0 and 1. it'll do all the complicated stuff. so if it's just say 0-63, just say like midi.control23=var.CS/64. o and for the crossfader, i noticed if you slightly nudge it (in center position) without actually moving it, you'll probably end up with 1 or 0, so you might just make it subtract one if it's positive, making it -7 to 7 and seems to be more consistent values on both sides.

now are you using traktor? cause i got the demo, and tried to map the stuff to that, and it never really worked well.. though i'm also doing like syncronized data to the wiimote (lights for beat of the measure, vu bars, active decks, etc.) and that seems even more of a pain.. o and you have to assign every single action to a single midi message... with vdj, you can actually assign the midi message several actions, making easier, do more what you want, and it's much easier. even if you don't buy it, you should definitely try it out. though don't think anything but the pro will let you do scripting (might be wrong)

check out part of what i got (there's waay more where this comes from.. think 900+ lines of code) and a new song i put together:
[www.youtube.com]

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Thu, 01 Sep 2011 02:54:21 +0200

Thanks again! I was making do just using Midi3 but This is much more efficient. And I'll be sure to check out LoopBe.

Now I'm just need to figure out how to format the individual midi messages.

The buttons are easy, just noteon and noteoff I presume.
I was fidgeting with the crossfader to begin with, the script sets var.cf as -7 to 8 depending on position, and it looks like I should use inrange to convert it to 0-127, but I'm a bit clueless as to how to actually format the message.

I think The Turntable shoul be 0-63 for velocity of counter clockwise movement, and 65-127 for clockwise, but Im not positive, and I am clueless as to how to send that. >_<

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Wed, 31 Aug 2011 23:27:46 +0200

first as a note, glovepie ignored capitalization, so cause i'm lazy, i'll only capitalize stuff if it makes more sense :P

i'm using LoopBe. then you have to use the right midi device, just like you would if you had several wiimotes. 'midi1.' refers to the first and 'midi2' is the second and so on. now really 'midi.' refers to the selected device (1 by default) and can be changed by setting 'midi.devicein' or 'midi.deviceout' as the number of the device you want to use. there is also a 'midi.DevNameIn' and a 'midi.DevNameOut' which will give you the name of the device. for my scripts, i would put a part at the top that would only run when the script starts, which goes through all the devices and checks their names and assigns the appropriate number to be used in the script. you could just use the number as 'midi3.' (or what ever it is), but this way, even if the midi devices get reordered it'll still work correctly without needing to be manually changed. also, you can then just use the 'midi.' making everything that much shorter :D

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Wed, 31 Aug 2011 22:31:28 +0200

Yeah, MIDIyoke is the one that is supposed to work with glovepie, But I haven't gotten anything to work yet. How are you doing it?

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Wed, 31 Aug 2011 20:34:46 +0200

i've got it all working and more or virtual dj, if you're interested. i might suggest trying out vdj pro if you haven't already. customizability is to the extreme :D great for comp sci people. for the midi, i assume you have a internal routing program? it's not too hard, but you have to make sure to use the right midi device.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Wed, 31 Aug 2011 20:29:17 +0200

Awesome, Thank you so much.

Ive got the code in GlovePie, and it runs great!

Now I just need to figure out how to format the midi signals to send them to traktor.

I'll keep you guys updated on my progress!

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Wed, 31 Aug 2011 18:41:04 +0200

@molarkey
yeah, i've got win 7 and got the laptop with bluetooth, so just using that works for me :P once you get the bluetooth working, the rest should be pretty easy. glovepie allows for a variety of syntaxes, so you can make the same thing work slightly different ways. for the most part, the easiest way is just to type it out. to make sure you can connect the wiimote, just use a simple script:

debug=wiimote.exists

debug refers to the little window that shows up next to the run button once the script runs. this should state 'true' once it has connected (and the wiimote should have led 1 lit up). after that would be to get the wiimote to control the keyboard by saying something like:

key.a=wiimote.a
keyboard.b=wiimote.b

key and keyboard both refer to the keyboard buttons, so once you do this, it should type a when you push a on the wiimote, and b when you push b
o and when you type 'key.' or 'wiimote.' it should come up with a window telling you all the different things you can add

hope that helps a bit.

@Jezzick
yeah, i'm not even sure if i can find the original post again, but i do have a copy of it
i've edited it a bit for ease and convenience
-------------------------------
//based of some dude's alteration of the ghwt script
// (sorry, couldn't find your post again to get your name)

debug="<"+wiimote.Exists+"> "

if(wiimote.Exists) then
if(key.Space) then
debug+=" *** POKE!! ***"
var.space=true
var.ini=true
endif
if(!var.space) debug+=" Safe to connect. Press SPACE to poke"
else
debug+=" ..waiting to connect.."
endif

if(var.ini) then
debug+=" Active :D"
if(!var.init) then
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type
var.init = true
endif

var.SX = (wiimote.Exp0 & 0x3F) - 32
var.SY = (wiimote.Exp1 & 0x3F) - 31
var.BE = !(wiimote.Exp5 & 0x10)
var.BM = !(wiimote.Exp4 & 0x10)
var.BP = !(wiimote.Exp4 & 0x04)
var.ED = ((wiimote.Exp2 & 0x60) >> 2) + ((wiimote.Exp3 & 0xE0) >> 5)
var.CS = ((wiimote.Exp2 & 0x1E) >> 1) - 8
var.RTT =((wiimote.Exp0 & 0xC0) >> 3) + ((wiimote.Exp1 & 0xC0) >> 5) + ((wiimote.Exp2 & 0x80) >> 7)
if (wiimote.Exp2 & 0x01) var.RTT = var.RTT - 32
var.RBG =!(wiimote.Exp5 & 0x20)
var.RBR =!(wiimote.Exp4 & 0x02)
var.RBB =!(wiimote.Exp5 & 0x04)
var.LTT = (wiimote.Exp3 & 0x1F)
if (wiimote.Exp4 & 0x01) var.LTT = var.LTT - 32
var.LBG =!(wiimote.Exp5 & 0x08)
var.LBR =!(wiimote.Exp4 & 0x20)
var.LBB =!(wiimote.Exp5 & 0x80)
if(var.CS<0)var.CS++
endif

-----------------------
pretty much you want to make sure that the turntable is not connected when you start (so glovepie sees it as a wiimote, not a wiiturntable), then once it notices a wiimote is connected, it'll tell you to connect it, then press space (as seen in the debug window) then, click on the variables tab and you should see the appropriate numbers changing. the wiimote buttons can be accessed with the 'wiimote.' and get the turntable data from the saved variables 'var.'
this should be able to get the data, so the midi part is alls that's left. now one thing i noticed is that if you spin a turntable really fast, it'll actually act like it's spinning slowly. this might be because of a missing bit or probably just overflow (cause, i doubt you'll really need to spin it that fast).

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

Jezzick — Wed, 31 Aug 2011 08:47:35 +0200

@Facing Tomorrow
Definitely interested... I have found no sign of the script you speak of... >_<

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

molarkey — Tue, 23 Aug 2011 01:25:26 +0200

I've been working on this same project for the past couple of weeks. My biggest hurdle has so far been a Vista/Bluetooth driver issue. Ended up using BlueSoleil (was the only thing that made any bluetooth work w/ my PC).

I see what you're getting at above would appreciate any help since I haven't coded anything in 10 years. Been getting my info by doing a lot of forum digging & a little trial & error w/ the GUI in GlovePie.

Re: Need help with ambitious project - DJ Hero Midi Control for windows.

FacingTomorrow — Tue, 16 Aug 2011 06:16:49 +0200

hey, i got it to work! wii dj hero turntable on a pc (using glovepie). though glove does support the device and the buttons, it doesn't work for any of the others. to make it work, you have to get the data from the wiimote and interpret if yourself. luckily, i found a script that demonstrates this (it took a lot to find). thus alls you have to do is add in the midi output. and for those who happen to have two, you can actually double it up. as you might notice, the mixer has a connection on each side (for lefties). despite the fact they do the same thing in the game, they are actually separate data from each other, meaning you can have a 2 deck controller :D
hit me up if you're interested