im trying to hook up the first knob k1 to the dry/wet effect in traktor scratch pro, works fine but no lights.
what i want is the four led’s to come on as i raise the knob from min to max, i.e 25% wet pad 5 comes on 50% pads 5 and 6 come on …100% pads 567 and 8 come on.
So this is where im at.
iv’e got an add out from fx dry wet hooked up to the corresponding knob, nothing happens.
ok so after a bit more experimentation, im still totally lost.
I decided to go back to basics, when the fx 1 button is on the led stays on untill I turn it off
so add out, effect unit one on, routed it to the corresponding button, it then turned on but wouldnt turn off, after mashing some other buttons it turned off but will not turn back on again.
Congratulations on your successful LED mappings of the LPD8. You seem to be the only person on the net that has it working without any third party workarounds.
I’ve imported your mappings and they don’t seem to control anything at all for me. Strange as I was happily using my lpd8 with my own mappings.
I have tried to look at your mappings and apply the same things to mine - looks like basically where there is an In for a button with note E7 for example you have a corresponding OUT mapped to the same note (E7) and that should work?
You seem to use a lot of modifiers are these required to keep the lights on or just because you are using lots of secondary functions for each button?
k so everything with an in is sending a signal into traktor from your controller, these are youre basic settings that for example at the top of my mappings ive got a select cue point. look at the first line of the mappings.
now if you want the led to turn on your need to tell traktor to send a message OUT to the controller.
Look at the 5th line in the mapping, this line correponds to the 1st line.
so, the thing which i found is that (and this is why there are so many modifiers) everything has to have a separate state, there can be no crossover if a button has more than one use, and it has an out assigned to it, it will get confused and simply not work. so i used a bucket load of modifiers so that I could tell the led what to do all of the time.
also i found that some leds would turn on but not turn back off again so I added more modifiers.
for example,:
button 1 (not pressed) mod state 0 - led off
button 1 (pressed once) mod state 1 - led on
button 1 (pressed second time) mod state 0 - led off
right i hope that helps, if i get time im gonna iron out some more wrinkles and ill record what I do post it up for you.
A video would be great!!! Looking forward to it. I kind of figured out some stuff but still, there seems to be combinations that trigger stuff and etc., so a video would help clarify things up.
Right buddy here’s a video, i’ve just realised that i’ve missed a couple of things out so, when i’m talking about changing tracks and I say twist the thing im talking about k4 also, i possibly didn’t explain well enough that pads 5,6,1 and 2 are deck A and pads 7,8,3 and 4 are deck b on all modes except sample mode where 5,6,1,2 are deck c and 7,8,3,4 are D and fx mode where 5 = a, 6 = b, 1 = c, 2= d.
also for the filters, I added them this afternoon so heres the new new .tsi
On the contrary, to make 'em more sensitive. I don’t know about yours but mine and apparently his is/was too darn stiff. I’m thinking of doing it one of these days, I’ll share my thoughts.
from what i’ve read the mod is good if u mainly want to use the pads for cue points - u need less pressure to activate them - but less good if u also want to use it for programming drums.
as for led midi feedback i haven’t had any issues with my lpd8 except for:
if you’re in PAD mode and the lpd8 gets a message to turn on/off a pad in CC mode then it gets ignored (and vice versa)
even if it gets a midi message to turn a pad led on, when u release it it gets turned off - but i presume u can just map led feedback from traktor with “inverted” checked as well as not to fix that?
