Instant Mapping on LaunchPad without Max or Python scripting

[oddstep]

1) Install Automap
2) Download these files and put them in the right place.
http://drop.io/launchpaduserremote/asse ... ration-txt
http://drop.io/launchpaduserremote/asse ... e2-automap

you might have to change the - to a . (-txt becomes .txt)
The user config file should be put in a folder with a good name.

3) plug in the launchpad, start automap server and load up the .automap file.
4)start live.
5) in the midi section of preferences add a new control surface the name will be what ever you called the folder that holds the userconfiguration.txt
make the midi to and from automap midi
6) stuff might happen now. to switch between automap and the standard launchpad controls press and hold session, user1, user 2 and then down (view)
7) user 2 might start flashing - press this... the remote control script is accessed through this automap object.
in the automap mapping page one controls the 8 macros of a device, page 2 two is 8 track volumes and page 3 is 8 send 1s. I got bored of typing into the automap editor after this.
It's a wind up that the session,user1,user2,down automap switch is like an easter egg that I only found by going on a google quest. It should line 2 on the launchpad quick start guide.

I'd like to say cheers to 3dot who gave me the idea. "Cheers 3Dot".

[carrieres]

hi,
i don't have a launchpad so excuse my ignorance but what is the difference between both mode ?
best regards

[oddstep]

I don't understand your question.

[carrieres]

what is the added functionality of your configuration ?

[oddstep]

the standard launchpad remote control has clip launcher and mixer controls (volume, pan, send 1, send 2) but doesn't have any ability to control the 8 macros on ableton device racks. automap can control non ableton plugins but can't engage with native devices. the automap file and the user configuration file serve to add device control functionality to the launchpad (through the use of automap midi as a second midi output from the launchpad).
What I have done is totally irrelevant if you don't have a launchpad, but handy if you have a launchpad but don't own max for live.
I was initially looking into writing a python control script that augmented or replaced the standard launchpad one, but the launchpad script is very complex and I haven't got enough python experience to get thru the task in the time I have available.

[carrieres]

thanks for your explanation,
i don't have a launchpad but i want to buy one or a apc40 this year
best regards

[Hermanus]

great work, I will reinstall automap then.

cheers

[oddstep]

yeah that's what I had to do as well. It turns out that automap is quite useful, sort of a novation specific midi translator. and not the hassleware I had initially thought it was.

[3dot...]

[Bainesy]

yeah that's what I had to do as well. It turns out that automap is quite useful, sort of a novation specific midi translator. and not the hassleware I had initially thought it was.

+1 Well said

[Pasha]

I can't miss it! Giving it a try today....

THANKS!

[#1thelark]

I just tried it... doesn't work yet. Dunno if the name of the Launchpad in the midi configuration matters? According to the USB-ports on my laptop the LP is named either Launchpad, Launchpad 2 or Launchpad 3... ?

[oddstep]

I'd say that you have got a confusing situation with the Launchpad being installed on muliple ports. The input midi device for the user config should be automap midi, not launchpad.

[alex.the.forge]

can't get this working - the blue hand doesn't show up on a device

anyone else get this working?

[transology]

Really interested to know if that works for other user also !

THanks