Midi ox and led problem!

DJ Life & Community General Discussion
1

Midi ox and led problem!

so i changed the channel of my novation launchpad using midi ox so it would be out of the way from my other midi controllers which were on the same channel, but now the led’s dont work. im using the launchpad for traktor pro, the midi commands themselves work fine but just not the darn leds. i make sure the LED’s messages are being sent to the new channel (10) and nothing happens. how can i fix this problem so i can map LED’s and still keep the channel changed!

Traktor Pro 2
apc20
launchpad
Kontrol
Lpd8
Audio 8
HP g-62
Windows 7
2.14 ghz 4 g

2

didn’t know midi-ox could be used to reroute messages? presume you’re not using automap if you have a app sitting between the lp and traktor now?

3

i thought that was one of midi ox primary job? haha but no i am not using automap or anything else. just the midiox/yoke. no matter who i route it i cant seem to get the led’s to respond :disappointed:

4

i only ever (well used to before i wrote my own app) use it to dump out raw midi data when debugging something.

if you’re using it to route then you just also be able to see what data is being sent/recv’d so should be able to work it out?

you’re using a virtual midi device that sits between midi-ox and traktor?

5

yes im using midi yoke as the virtual midi device. i can see the whats going in and out and it all matches up to be the same. ive mapped led’s with the launchpad before when its not running through midiox/yoke and its worked fine. i cant seem to find any other post about led issues when changing channels with midi ox…

6

in native mode the launchpad sends/recv’s on channel 1 - so just make sure midi-ox (or whatever) or converting the midi channel to that.

seems to work fine in my midimasher app anyway. you having issues with feedback for all buttons or just the notes or just the cc’s?

-- define the top row buttons

add_control("up",       1, "cc", 104);
add_control("down",     1, "cc", 105);
add_control("left",     1, "cc", 106);
add_control("right",    1, "cc", 107);
add_control("session",  1, "cc", 108);
add_control("user1",    1, "cc", 109);
add_control("user2",    1, "cc", 110);
add_control("mixer",    1, "cc", 111);

-- define the right hand buttons

add_control("vol",      1, "note", 8);
add_control("pan",      1, "note", 16 + 8);
add_control("snda",     1, "note", 2 * 16 + 8);
add_control("sndb",     1, "note", 3 * 16 + 8);
add_control("stop",     1, "note", 4 * 16 + 8);
add_control("trkon",    1, "note", 5 * 16 + 8);
add_control("solo",     1, "note", 6 * 16 + 8);
add_control("arm",      1, "note", 7 * 16 + 8);

-- define the grid buttons, 8x8, cc number is row x 16 + col

for row = 0, 7
do
for col = 0, 7
do
local note = row * 16 + col
add_grid_control(col, row, 1, "note", note)
end
end
7

none of the led’s for any of the buttons seem to work. i think the problem may be that im changing the channel of the midi controller though midi ox so the actual channel is still 1 on the launchpad, once i close midi ox it goes back to channel 1. so maybe its not receiving the led data because of this? is there a way to permanently change the channel of the lp? ive tried using automap but that was one big joke

8

afaik the launchpad itself can only receive data on channel 1 - except for the slight hack with channel 3 for bulk updates (useful for changing all led’s when you switch between virtual pages etc if your middleware software supports that)

how are you trying to use midi-ox to change the launchpad’s midi channel? if you’re using midi-ox somehow to route from 1 to something else on the way out and then from there back to channel 1 on the way back to the launchpad then ofc you need to keep midi ox running.

i don’t know of any sysex type way of actually changing the lp’s native midi channel?

9

Same(-ish) problem

I have a Citronic MP-X10 and am having similar LED issues… the unit uses 3 channels to transmit/receive data (L deck/R deck/mixer). I have got one deck working with my rather large and complex mapping. I saved it out, re-imported it, and changed all the channel numbers of both buttons (easy using midi learn) and the LED’s (picking out notes from that useless Traktor mapping interface (grrrr..)). Now both sides work fine, but where the two sides are using the same modifier, the button to signal a modifier lights up on say deck A, but then pressing the same button on deck a, activates the modifier function, but doesn’t light the light. Pressing again then removes the modifier, still no light.. only when I press it a 3rd time to reactivate the modifier, do I get lights!
I am about to test in MIDIOX, once I can get a damn MIDI loopback cable working…
Thought it was my hardware, but reading this thread, now not so sure.
Will report back in a bit…

A.

10

is this with traktor pro 2? i dont know about previous versions but modifiers in tp2 are local/specific to each mapping so in theory they shouldn’t affect each other.

11

goddammit!

OK, after much fiddling (well 20mins!) have got the midi outputs displayed via MIDI OX. Now, I have hotcues 1-4, and a button to switch them to 5-8. The button to switch them is on a modifier, as are all the hotcue buttons’ leds (so that the mapped hotcues light up accordingly).

When changing hotcue banks (from 1-4 to 5-8, or vice versa) on a single deck, all is ok. I get a flurry of midi messages telling the ‘bank change’ switch’s led, as well as the hotcue’s leds (2 per button) to switch on/off.
If I press again, all ok.

Now if I set bank 5-8 on deck A (which equates to m6=1), then when I try to switch deck B to bank 5-8 (also m6=1, but on a completely different logical device AND midi channel), I don’t get one solitary midi message. Nothing!

My “devices”, at the top of the midi mapping screen are as follows:

MP-X10 (a) - In=MP-X10; Out=MP-X10 (well, is actually running through LoopBe internal midi at the moment, so that I can see what is happening)
MP-X10 (b) - In=MP-X10; Out=MP-X10
MP-X10 (mixer) - In=MP-X10; Out=MP-X10
Decks C&D - In:BCD3000; Out=BCD3000

I have created these as separate devices so that I could use modifiers per deck.

If I look in the ‘modifier state’ strip along the top of the mapping window, they all act like they should… coming on with 0s and 1s depending on their state - not like the LEDs!

Is this a bug in Traktor? I thought initially that it was my midi controller, but it looks like my end is working fine, and it is traktor refusing to send out the led states when I change mod.

I have tried this on all my modifiers that I can, and always get the same result.

Using TP2.

Any help gratefully accepted!

Thanks

escapemcp
Intel Core Duo | Echo Audio Layla 3G 8in/8out Soundcard | Citronic MP-X10 | Behringer BCD3000 | Numark EM-460 Mixer with built-in Kaoss Pad | + 20 years experience :wink:

12

UPDATE: It is only the 1st message when the modifiers are not the same that does not get sent. On the second press, midi data gets sent out, (but of course, it is telling the leds to switch on/off in the same layout as it already is, so there is no visible change to the leds, but the midi messages ARE being sent. Hmmm… what about a 3 way modifier… hang on!

EMCP

13

Hmmm.. on a 3 way mod, it ONLY doesn’t sent out a message when the modifiers are lining up! OK.. I have a tempo range, that can be either 6% (m=1), 10% (m=2) or 16% (m=3.)

Starting both on 6% - this is what that SHOULD show and the results (in brackets)
A B
6% 6% - start - ensuring both decks are reflecting their true values (6% 6%)
10% 6% - A changes fine (10% 6%)
10% 10% - B ‘sticks’ on 6% (10% 6%), pressing B again:
10% 16% - B moves to 16% (10% 16%), so ok there
16% 16% - A sticks on 10% (10% 16%)
6% 16% - A moves to 6% (6% 16%)
6% 6% - B sticks again (6% 16%)

starting again (this time with double adjustments each time)
6% 6% - again both decks are m=0, which means the LEDs are correct
10% 6% - fine (A)
16% 6% - fine (A)
16% 10% - fine (B)
16% 16% - fine (B)
6% 16% - fine (A)
6% 6% - B sticks (resulting in 6% 16% on the controller)

And finally:
6% 6% - start again
10% 6% - A moves fine (10% 6%)
10% 10% - B doesn’t move (10% 6%)
16% 10% - I pressed A, but BOTH A&B moved a notch (A was because it should have done, B was just ‘catching up’ from the previous line), so now the led’s read right (16% 10%)
16% 16% - B sticks (16% 10%)
6% 16% - A moves, and again, B also moves (ending up 6% 16%)

Oh, one more
6% 6%
6% 10% B moves fine (displaying 6% 10% on controller)
10% 10% we KNOW now that A will stick, and it does! (so still have 6% 10% showing)
16% 10% A unsticks (now reads correct (16% 10%)
6% 10% fine (6% 10%)
10% 10% - now even though the mod values are lining up (which is what has caused the problem in the past), the leds act like they should and A goes to 10%, and B stays at 10% (as it should.. I haven’t touched B since my first ‘move’)).

Hmmm.. ideas? Anyone?

Thanks
emcp