So i’ve been working on this for a few days, and i’m finally done.
A 4 deck (deckalized) launchpad. Each 4x4 grid works just like the midifighter deckalized mapping.
There are some issues with the lights for the loops not working, they’ll work sometimes but and sometimes they won’t. Feel free to try and fix this, but i’m probably not going to, as i really like the 4 deck mapping i’m using, and i just made this for the forum/fun. The rest works perfect. Light feed back and all. The zip file i’m uploading has a .tsi for each deck, as well as a .tsi for the whole thing. I did this in case someone only wanted 2 decks, then they could use the rest of the buttons for something else.
works great indeed. there is also an issue in juggle mode, only every second cue point lights up when mapped. at any rate very cool, thanks!
actually its so much fun to use, i might sit down and map out all 4 decks via bome’s, so that i can use the official mapping. seems like that might be the better long term approach in case they tweak the official MF mapping, because the midi notes on the launchpad and MF obviously will not change.
That’s the way the leds light up on the midi fighter in juggle mode. It’s so you can tell the difference between juggle mode, and re-sample/sample chop mode which has them all lit.
ah ok. isnt the difference visible based on if the sampler button is lid or not? but of course if only the buttons light up that are mapped and no buttons are mapped you might not know you are in juggle mode. then again, usually when you go into juggle mode you want immediate map some hot cue points.
ah well .. will test this with the “original” mapping and give my feedback to ean.
OK, so i was playing around with this the other day, and it seems there are more problems than i first noticed. I’m pretty busy the rest of July, but should have some free time in august to get this all sorted out.
I Actually completed porting two decks of Instant Gratification,
Mapped to TopLeft TopRight (Device Target)
I use individual TSIs for each with the Launchpad i didn’t need to implement MultiBank
mode since we have a 8x8. I mapped everything to channel 1, probably shouldn’t have
since default is channel 5, but i just morph the channel in Ableton. I could remap again
but i am lazy. I also tweaked it just a tiny bit so any docs still apply…
Eliminated “Bank 1-4” , kept Effect Lock, so three open pads on top row for now.
Added a beat phase meter on upper row
Added a play/pause out LED state to upper left corners corresponding to Effect Lock
I also ported the standard deckalized to all four corners too.
top Left, top Right, bottom Left, bottom Right
I also have a Track/Browser Loader/EQ kill with Lock mapping for the circular buttons
This one is rather proper in the LED states and function.
However I am not happy with the LED states on any of this with launchpad.
I have the complete breakout of all LED states and modes so I’m working
on a coherent LED feedback modality and more importantly on a color initialization
routine so when i switch from Ableton modes to USER1, it will set all the states
…no luck yet
Oh yeah this completely preserves the function of the built in functions of the
Launchpad. I’m using this with Ableton and Traktor at the same time.
I will create a bangup post with the TSIs soon enough
WARNING, these are meant to be used thru ableton to launchpad.
Meaning they work for the DEFAULT LAUNCHPAD User 1 mode.
They are all mapped to channel 1.
I do not support these, i will answer basic questions.
I have tested them but i have one bug i can’t kill, sndA
lights up and gets stuck.
Correct, I slave Ableton to Traktor. It works like this for me, it doesnt matter who is CLOCK master whatsoever.
Launchpad uses a ControlSurface/script mapping. When you connect launchpad to
Ableton there are different pre-mapped configurations for Mixer and Clip and USER1,
USER2.
I implemented this mapping on USER1 which uses midi channel 5. And is freely assignable
In Ableton you select it as a control surface and select the Launchpad as IN/OUT, like
any other control surface. In the midi preferences also enable IN/OUT (no sync) on
Launchpad In/Launchpad Out.
In Traktor i use the Traktor Virtual Midi, i create a new generic midi, set one OUT command for clock. I do not enable the input on this “clock” device, output only.
In ableton i take the input from Traktor Virtual Midi and enable SYNC only. This
works like a charm transport in Traktor starts Live.
Here is the tricky part, in Ableton i create two midi tracks, then in Traktor, i create
another Generic Midi device and set input to Traktor Virtual in/out.
In Ableton,
1st track is set to Launchpad IN channel 5, output on that channel is Traktor Virtual
2nd track is set to Traktor Virtual on channel 1 routed to Launchpad Output channel 1.
This allows we to pass LED states to the Launchpad from Traktor bi-directional.
Implementing it like this also preserves the full function of Launchpad.
