light settings for launchpad (help please)

[mrpud]

Hi,

I'm making a mapping for my launchpad and the lights are driving me mad!!!

I have seven buttons all set up for 'loop set + size' each with a different loop size, the lights are set up so that they are green and then turn red when loop is active, the problem is if any of the loop buttons are activated all the lights turn red.

What I'd like to happen is, when a loop is turned on for 1/4 loop only that button turns red (so it would be easier to know which loop button is on).

Can this be done??? if so how please??

Thanks M.P

[zestoi]

Hi,

I'm making a mapping for my launchpad and the lights are driving me mad!!!

I have seven buttons all set up for 'loop set + size' each with a different loop size, the lights are set up so that they are green and then turn red when loop is active, the problem is if any of the loop buttons are activated all the lights turn red.

What I'd like to happen is, when a loop is turned on for 1/4 loop only that button turns red (so it would be easier to know which loop button is on).

Can this be done??? if so how please??

Thanks M.P

how are u setting up the initial green color? by the sounds of it you need to use a single modifier and a whole stack of extra mappings...

something like this i suspect for the first button to make it light up red:

* add in > loop size set, size = 1/16 (or whatever size u want)
* add in > modifier M1 > set value=1
* add out > loop size set, size = 1/16 AND condition modifier M1=1 AND loop=active

that in theory should make only one light up red at a time, if u use a value of 2 for M1 for the next loop size etc.

making them turn green again is more tricky tho as there's no way of saying "M1 doesn't equal 1" as a condition so i suspect you'd need to add 8 extra "outs" per button to change back to green depending on loop active status and the value of the M1 modifier.

much less work ofc if you don't need them to be lit at all when that loop isn't active.

i could be missing something obvious, but thats what i think you'd need to do.

[mrpud]

Hi Zestoi,

Thanks for your reply.

The way I have it mapped for the light is via loop size/set.

I tried doing it via mods but I got all confused as the buttons I've set up to be the loop buttons are already on a modify to the m1 value.

See I understand the mods for the functions but I lose it when it comes to the lights. I might add that this is the first mapping I've ever done and I may have bitten off more than I can chew. It's just I'd like to have everything perfect before movingh on the next stage of my masterplan!!! I am slowly coming to just settling for the fact that the function works lol.

So how would the mod work for the lights if I try to go down that route for one last try. Would one mod be enough to use for 7 buttons?

Thanks MP

[zestoi]

The way I have it mapped for the light is via loop size/set.

to set them green initially as well as red when selected?

I tried doing it via mods but I got all confused as the buttons I've set up to be the loop buttons are already on a modify to the m1 value.

So how would the mod work for the lights if I try to go down that route for one last try. Would one mod be enough to use for 7 buttons?

so you're using M1 to turn these buttons into loop buttons from something else? then just add an "in M2" for each of the buttons with a condition that M1=1 and set M2 to a value from 1-8 depending on which button is pressed and hence loop size. worth trying just on 2 first tho to see if u can make it work before replicating to all the rest.

with M2 having this value (from 1 to 8) you then know which was the last button pressed. and so if "M2=3 and loop=active" then u know that it was the 3rd button pressed that activated the loop (unless from other midi controllers etc) and then so that OUT should make the light red.

how are u disabling the loop? by pressing the same button again? if so then you'd need another IN for each button that only turns the loop off if "M2=3 and loop=active" for button 3 etc. or you're using a type of "toggle" in traktor itself?

this kind of stuff can get complicated and one of the reasons i created my midimasher. released a lot of launchpad support yesterday btw, checkout the link in my thread. it sits between your launchpad and traktor in the same way bomes or midikatapult do. it's still a work in progress but is definately getting there.

i think @muffintop wanted to create similar behaviour for loop buttons on the launchpad via midimasher, not sure if he managed that or not. if not i'll probably look at it as it seems a sensible thing to do if you have a spare 8 buttons which i will have once my "twitch" like code is tested that emulates those bottom two areas on a twitch on any area on a launchpad.

basically a 4x3 grid of buttons, top row toggles between 4 "sub pages" for the 8 buttons below it. i was planning on mapping cues+loops+beatmasher+slicer to those 4 sets of buttons by default.

oh btw - you almost never need to use the controller manager when mapping via midimasher as it uses a massive tsi that maps all the controls it needs already. it's worth finding your way around traktors controller manager first tho.

[mrpud]

Hi Zestoi,

Thanks for your reply,
To do the initial green light I have an output for loop set/size (though I'm not getting the option to set the loop size for output, just the standard light/midi options) and I have that set up as M2=1.

I tried out what you put in the above post, but I'm not sure if I did it correctly but unfortunately it didn't work. I added in another output for loop active M5=1 then on the next button I added loop active M5=2 but niether worked. I then tried to cross ref this to the input setting for loop set/size M5=0, still no joy, then I tried pairing them so that the input loop set/size M5=1 and the output loop active M5=1.

sorry if this is all a load of b****ocks and does make much sense lol.

one thing I will mention though, I didn't make an input for M5, I wasn't sure if it needed to or not and if so, what button do I assisgn to? do mods still work if there is no input button for mod?

thanks again
MP
P.S. thanks for the info on midimasher, looks good but really wanted to stay away from third party software as when I used midiyork it really messed my system up, also using a Mac now.

[zestoi]

one thing I will mention though, I didn't make an input for M5, I wasn't sure if it needed to or not and if so, what button do I assisgn to? do mods still work if there is no input button for mod?

well it's not going to work at all if you don't add an 'in' for the M5. you need to add an 'in' for M5, which sets it to a value of one for the same button you use to set the shortest loop length. i.e: click learn and press the same button. then add another in and use learn with the 2nd button that sets M5 to 2 and so on...

P.S. thanks for the info on midimasher, looks good but really wanted to stay away from third party software as when I used midiyork it really messed my system up, also using a Mac now.

i haven't used midiyoke in years but have had no issues at all with loopMIDI on windows 7. it should be fairly simple to port midimasher to osx but i don't have any hardware to be able to do that yet.

[mrpud]

well it's not going to work at all if you don't add an 'in' for the M5. you need to add an 'in' for M5, which sets it to a value of one for the same button you use to set the shortest loop length. i.e: click learn and press the same button. then add another in and use learn with the 2nd button that sets M5 to 2 and so on...

Blush, thanks I understand it now, will try it tomorrow when I get home.

[mrpud]

Hi,

I tried it, but still no success, just changed from permanent green to permanent orange. I think I'm just gonna give up and leave it as it is, thanks for all your help zestoi.