Akai LPD8 LED feedback

[Aless Ice]

Hi everyone,

I'm looking for information about LED feedback for Akai LPD8 in Traktor Pro 2. I found some information but it all seems a bit complex. I'm a noob in "complex" MIDI mapping and I'm looking for simple but precise explanations.

I have an Traktor Kontrol S4 and a Akai LPD8. I mix with the S4 and I would transform the LPD8 as a FX box like the Midi Fighter. I use Traktor Pro 2 and I'm on Mac OSX 10.5.8.

The problem is I can't configure the LED feedback.

Examples:
- Modifier #1 = 1, pad 1 (note C2) -> on;
- Effect 2 of FX Unit 2 is turned on, pad 1 (note C2) -> on;
- Effect 3 of FX Unit 1 = 1.00000, pad 1 (note C2) -> on;
- Etc.

I read that you could use software like MidiPipe or MIDI Monitor but actually I don't get anywhere and I don't understand it.

Could someone help me? Thanks in advance

[zestoi]

each pad sends and receives the same note or cc - so if you know how to map from the lpd8 u also know the midi to send back to it for led feedback *but* the catch with the lpd8 is that the pad led will always turn off when u release the pad - even if mixxx/vdj/traktor/etc has send the midi to turn that pad led on.

i did come up with a solution to fix that in vdj or use my midimasher middleware. i'll create a mapping for mixxx sometime that also works around the issue. in traktor u could probably work around it by using an inverted control - tho not sure off hand u can do that for "out".

[Rowanov]

I posted a solution/hack for it here: http://forum.djtechtools.com/showthr...444#post460444

[zestoi]

cool, that will do it real shame you need to go thru hurdles with the lpd8 for led feedback. the cool thing about using midimasher is that it handles this for all pads allowing you to map as normal inside traktor - the downside is needing to run midimasher - if all u want is the led fix. i create my lpd8 mappings actually within a midimasher config.

ofc what would be really nice is just having the option to turn off this behaviour in the lpd8 and make it act more like a launchpad where nothing happens without midi feedback or have midi feedback have a higher precedence to pressing/releasing a pad or something. can't see what the problem would be so long as the default behaviour would be how it is now...

[Aless Ice]

Hey guys,

Thanks for your answers.

The solution of Rowanov doesn't work for me.


In fact, I try to route the effects in the decks that I have previously chosen via the LPD8. I use a change to recognize the decks.

PAD1 = in deck A
PAD2 = in deck B
PAD3 = in deck C
PAD4 = in deck D

When I press on a pad, the value of MODIFIER#1 changes depending on which pads are on.

MODIFIER #1 = 0 --> in all decks (all pads are off)
MODIFIER #1 = 1 --> only in deck A (PAD1 is on)
MODIFIER #1 = 2 --> only in deck B (PAD2 is on)
MODIFIER #1 = 3 --> only in deck C (PAD3 is on)
MODIFIER #1 = 4 --> only in deck D (PAD4 is on)
MODIFIER #1 = 5 --> in decks A and C (PAD1 and PAD3 are on)
MODIFIER #1 = 6 --> in decks B and D (PAD2 and PAD4 are on)
MODIFIER #1 = 7 --> in decks A and B (PAD1 and PAD2 are on)

So far, no problems, it is the simple mathematical logic.

What will happen afterwards when I pressed an effect or a combo of effects is that the function "Effect Unit X On" will activate in the decks that I have chosen in advance, and only in these decks.

For example:
I press on to route PAD1 effects only in the deck A, then I activate the effect of X and the effect will only be active on the deck A.

Actions configured:
When I press on the PAD1: MODIFIER#1 set to 1
When I press on the pad that activates my effect: (my fx settings) + EFFECT UNIT X ON (assignment DECK A)

As in Traktor, I have no visual tool to see what decks I route the effects, I need to have at least a return to the LPD8 to know what I do.

So I add the output MODIFIER#1 with the condition M1=1 to get the LED feedback.

But it doesn't work.

That's what I want to do.

I read the solution could come from software as MidiPipe or MIDIMonitor (by reprogramming MIDI?!) but I really don't understand anything.

[zestoi]

i do have a midimasher config that will fix your issue if u wanted to try it. i haven't released midimasher in a while due to coding for mixxx instead, but i can release a version that will work for you if u want.

you wouldn't need to do any complex setup of midimasher for this - but if you're on windows you would need an app that can give u two virtual midi ports. i used to use loopMIDI i think when i used windows.

you'd then run midimasher and have it connect to the lpd8 - run traktor and select the virtual ports in traktor instead of the real lpd8 ones.

u then wouldn't need to mess about with any hacks in traktor as midimasher would basically turn the lpd8 led back on when u release it if it's had midi feedback from traktor saying that it should be lit. u would ofc have the added hassle of needing to run midimasher but u wouldnt need to edit any midi code or anything like that

[Aless Ice]

Yeah aright! I'll test it this afternoon and I'll repost. Thanks for help

[Aless Ice]

Finally, I found another solution more practical. I don't know why I didn't think before... Instead of using pads, I use a knob. The mapping is easier and routing is more convenient to use.

About the visual appearance, once I completely finished my mapping, I intend to make and print a cover for LPD8 and this way I can more easily identify effects and routes.

But I downloaded the Midimasher because it interests me and I intend to experiment with my Launchpad and my LPD8

Thank you very much for help.

[zestoi]

But I downloaded the Midimasher because it interests me and I intend to experiment with my Launchpad and my LPD8

cool the next update will include a whole new config file format kind of similar to VDJ, which means u shouldn't need to be a (LUA) coder to do some very advanced midi coding/routing. it's just been on the back burner for a while now...