I picked one up a few days ago and i've been checking out the stuff that's avaialable.

Quite a few people have developed apps so it can control other software like Alphapad. http://alphapadstepsequencer.blogspot.com/2010/11/alphapad-e nglish-version.html or nomone.

Seems like a good not-too-expensive solution for sequencing Vortex. What do you think Andy?

Do you know I went to a big music tech shop the other day, I was hoping they'd have one to have a play around with, I don't quite 'get' them. As I understand aren't they locked to Ableton? I'm supposing they use MMC or something similar to communicate with live.

But yep, they look perfect for Vortex if they could be interfaced!

Oh, right it can be mapped using the novation software, now that's interesting.. let me know how it goes with it. I guess you just have to build a Vortex friendly preset right?

Launchpad is open source http://blog.launchpad.net/general/launchpad-is-now-open-sour ce

Haven't really touched the automap yet, tried it with Geist but the pads were mapped all over the place, got to rtfm. I think all the pads are red though so it's hard to differentiate between controls but the launchpad side of it is really good for controlling live, though a bit buggy.

But there are apps developed with Max like nomone and then there's Alphpad which can be used as a pseudo-hardware step sequencer with any host. Made me think of Vortex.

It's the amount of control you can get, it's possible to adjust pitch, velocity, add scales, change the speed, length and timing of a sequence. it's not so good with knob values but i've seen people using the nanopads for stuff like that.

Interesting! I shall have to get one, it would be a nice combination

btw, can you check out the new vortex beta to see if you can make it crash, especially on the DSP side. Haven't fixed the Shift bug yet but I've added dlogging to identify where the error occurs

Will do tomorrow, need sleep.

Ok

I'm a big AutoMap fan. Personally, I think Nocturn would be much more useful due to having real encoders. It depends what you want to do. I use AutoMap to replace the mouse as much as possible to 'real time' manipulate parameters in instruments or effects ... which can of course be written as automation in most daws.

As far as triggering sequenes goes, a midi file, keyboard or a more tactile device like trigger finger/ Kontrol pad/ mpc, etc., would be my prefrence.

Of course, Launchpad will fit in the backpack nicely.


Como

For accurate control yeah but for step input and triggering the launchpad is perfect with the visual feedback. Alphapad can extend the sequence up to four bars i think, it's stuff like that that i've not found in another midi controller apart from maschine where i can play without having to look at the computer screen, i had no idea the launchpad had this kinda multifunctional capability outside of live. I've only had it a few days but colour me impressed.

I'll have to look at automap, most comments i've read are pretty disparaging so i haven't bothered with it. If i could i'd develop apps myself. Something like Vortex for the launchpad would be awesome. Like you i try to keep away from the mouse as much as possible.

The launchpad is pretty tactile imo, have you tried one? It's not velocity sensitive or anything like an mpc or drum pad but it's better than i expected, i originally bought it for the monome type stuff i'd seen and the performance control that's coming to FL.

But there are some nice apps and hacks around for it that expand it's functionality in other ways and you don't need a full license for Max or Live to get the most out of it.

Cheers.

No, I haven't tried one ... but I've read about them in detail and have it on my 'maybe, sort of' buy list. But as I had 3 other Novation AutoMap controllers when it came out, it didn't have that ooomph for me.

Have you got some links for the hacks and custom programs you've mentioned? I'd like to know more about them ... both to see if it could put me over the top with getting the Launch Pad and seeing if what they do translates to other AutoMap controllers.

Right now in Vortex, AutoMap is listing several hundred parameters ... many apparently still unassigned. I've got my little Nocturn set up for control of the Master Vol, Master FX Mix, Global Transpose and several other parameters.

Unfortunately, so far Andy has named most of them for his own benefit, not names that immediately reveal the function. I have determined that most of the knobs in the Midi Mixer, i.e., vol, pan, CC3 and CC4, can all be easily identified on a channel by channel basis, and therefore controlled with AutoMap.

I cannot understand why anyone who understands it could disparage AutoMap. It is, in my opinion, as brilliant a controller method as Vortex is an instrument.

What throws a lot of people off is that they think the name means that your controller will automatically map your software parameters as you'd like them to be. It doesn't and no controller software can ... but it gets you as close as a drop down menu and 'click and drag' to move the parameters around the gui and therefore the controller.

What AutoMap does is examine the addressable parameters of the soft and then 'handshake' them across all it's controls in the order that they are listed in the soft. Different designers set up that list (or how things are ordered in their code) in different ways and with different names.

For an example, in Vortex, what I consider a 'Master Volume' is about 10 or so down in the list and ... from memory ... has a parameter name like 'Ammonite II Level.' FX Mix ... which is right next to 'Volume' on the GUI, is about two hundred parameters later.

But check this. So far I haven't heard anything about midi learn from Andy with respect to Vortex ... but as it is midi learn capable, AutoMap already knows that and I'm controlling Vortex parmeters with my hardware!

Not something to be disparaged, in my view.


Como

I meant disparaging of the launchpad automap as it's pretty basic. The third party stuff makes it a non issue though. First hack that i tried was this http://forum.ableton.com/viewtopic.php?f=1&t=168495&hilit=no vation+launchpad

Which greatly improves the default live launchpad template. These are a few i bookmarked from the launchpad thread here.

http://machinaesoundscapes.wordpress.com/2010/04/07/make-it- go-the-launchpad-as-monome-part-1-startup-and-mlr/
http://www.aurexmusic.com/
http://www.audionewsroom.net/2010/01/novation-launchpad-hack ers-perspective.html
http://www.rngtng.com/mtXcontrol/
http://sample-hold.com/2011/12/19/make-fun-of-your-launchpad -with-launchplay-vst-plugin/
http://alphapadstepsequencer.blogspot.com/
http://parallelogram.cc/mlrv/

Then there's nativekontrol but again that's designed for Live;

http://www.nativekontrol.com/LPC-Live.html

And there are some visual hacks on youtube plus a heap of things you could do with Bome's. The nonome hack is cool cause you can use any of the Max monome stuff with the free runtime version. You need to use a virtual midi cable for most of the hacks but it makes the launchpad a pretty versatile control surface.

Re automap expectations, that's how Novation sell it! I think it makes more sense with the remote control surfaces but not so much for the launchpad but i could use it for key commands in studio one so that would be another way to utilise it.

Cheers.

Ah! It's the launch pad implementation in Live you don't like! LOL

Thanks for the links!

Como

I just read that the red buttons made it a bit counter intuitive but i came across these videos on using automap with native lunchpad mode http://www.youtube.com/watch?v=fPVaM7PboXc&feature=related

Worth watching those dsp project videos to show a few other ways the lp can be used. Will look at creating a template for Vortex but i'm not sure how to distinguish all th controls across 16 channels...

Just take a look ... most of the Midi Mixer channel knobs are near the end of the drop down list. You'll see things like "CC3 1, CC3 2, ... Vol 1, ... Pan 1, etc., ... with the ending number referring to the channel number.

I don't know if you have automap pro or the regular version ... but the pro adds quite a bit of fuctionality.

The challenge is simply figuring out how to use your controllers interface and the 'pages' in AutoMap to best lay something out.

I often use a page per channel in nocturn with usually master controls on each page. That way I know I have all the controls for that channel plus the overall volume, fx mix, etc., using Vortex as an example, then I set the consecutive pages the same way with now Channel 2, etc., but the same master controls.

The ideal tool for this with Vortex would be the Zero controller, which also includes 8 pads that can be used as triggers, MPC style.

Como