Midi conflicts between launchpad

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
geiseric
Posts: 10
Joined: Mon Aug 24, 2009 1:39 am

Midi conflicts between launchpad

Post by geiseric » Sun Apr 04, 2010 11:32 pm

I realize there is many existing topics on this, too many, in fact, for me to find a reasonable answer- all of this talk of midi channels and so forth is honestly confusing the hell out of me. I won't be offended if this is ignored. My specific problem:

I mainly use my Xponent and launchpad with live, controlling fx and levels on my xponent, and launching clips from the launchpad. I use the user1 mode to produce my drum loops by hand (I prefer the more human feel that I get in my loops from that) but I'm fine just having the launchpad consistently on its session mode for live sets for the sake of reliability (as in no mess ups while switching modes). However, there are a few buttons on my xponent that conflict with the launchpad clip launch buttons in session view, so I end up leaving precious buttons unused on the xponent. Is there a simple way for me to end this conflict and get on with my life?

*edit*
Stumbled on a quick fix, switching to bank B did something to ease this particular conflict, but I'm sure it will pop up again.. what do I need to learn to resolve this when it does pop up again?

chapelier fou
Posts: 6357
Joined: Mon May 15, 2006 12:15 pm

Re: Midi conflicts between launchpad

Post by chapelier fou » Mon Apr 05, 2010 8:49 am

Check out the launchpad's programmer's reference on novation's website.
The better thing to do is to change the midi channel of your xponent. Launchpad is a fascist device.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1

keppy
Posts: 26
Joined: Thu Aug 13, 2009 5:23 pm
Location: SF

Re: Midi conflicts between launchpad

Post by keppy » Mon Apr 05, 2010 4:52 pm

another quick fix, just turn off the remote switches for the input and output on the launchpad. you won't be able to midi map anything to it though.

geiseric
Posts: 10
Joined: Mon Aug 24, 2009 1:39 am

Re: Midi conflicts between launchpad

Post by geiseric » Mon Apr 05, 2010 8:42 pm

Thanks. I love my launchpad, but I wish I had had the change to drop on an APC40 instead. I'd like to sell my xponent and axiom and pick up either an APC40 or a Zero SL Mk II (with the rebate) but nobody wants a classic axiom 25, its knobs are awful.

NF
Posts: 91
Joined: Tue Mar 23, 2010 1:04 pm
Location: Berlin

Re: Midi conflicts between launchpad

Post by NF » Mon Apr 05, 2010 9:47 pm

Your problem is caused by a conflict of the midi channels.
Both of your devices are on Midi Channel 1.
Lanuchpad sends and receives, without automap in "native mode", on midi channel 1.
Just tell each of your other midi devices to send globally on extra midi channels.
I recognized the same funny problem with LP and BCR2000.

It´s not a Launchpad problem, its a user problem :roll: :wink:
With APCs and other midi devices the same could happen if they send/receive on the same channel.

greetz
The cool thing about techno still, comparing it to most jazz is the improvisation coupled with raw energy.

outershpongolia
Posts: 2230
Joined: Wed Dec 31, 2008 8:40 am

Re: Midi conflicts between launchpad

Post by outershpongolia » Mon Apr 05, 2010 9:58 pm

NF wrote:Your problem is caused by a conflict of the midi channels.
Both of your devices are on Midi Channel 1.
Lanuchpad sends and receives, without automap in "native mode", on midi channel 1.
Just tell each of your other midi devices to send globally on extra midi channels.
I recognized the same funny problem with LP and BCR2000.

It´s not a Launchpad problem, its a user problem :roll: :wink:
With APCs and other midi devices the same could happen if they send/receive on the same channel.

greetz
Launchpad can't be edited for which messages to send and if I remember correctly neither can the Xponent..

^^^ User error? nahh.. just no damn MIDI editor for either one.. It's understandable why not, the Launchpad has it's native control and talkback stuff with Live, and the Xponent has it's deal with Torq.. so they aren't really MEANT to be customizable as far as what MIDI messages to send, but definitely not user error if you can't do anything to help it... The axiom, sure, but the other 2 is just a shitty situation, could be wrong about the Xponent though..

We sold the Xponent for like $550 or something after buying it for retail which was like $599 or something and using it for a few months, maybe the buyer was a sucker but we ended up with most of our cash back so post that bitch on craigslist if you wanna get rid of it, as for the Axiom. shhhh no one will know about the knobs until they try them at home :twisted:

NF
Posts: 91
Joined: Tue Mar 23, 2010 1:04 pm
Location: Berlin

Re: Midi conflicts between launchpad

Post by NF » Thu Apr 08, 2010 9:38 pm

Ok, I forgot to say that I only have experience with vestax VCI-100 and Traktor. I thought that you also can reconfigure every parameter by hand like you ca do in Traktor.
Can´t you edit the midi parameter for the M-Audio??? That sounds like a fixed on hard and software bundle... It´s Av** :twisted:
Individual configuration rulez - BCR rulez :wink:
The cool thing about techno still, comparing it to most jazz is the improvisation coupled with raw energy.

anybody human
Posts: 1049
Joined: Fri Jun 05, 2009 2:27 pm

Re: Midi conflicts between launchpad

Post by anybody human » Sat Apr 10, 2010 12:48 pm

I hear ya on Axiom's knobs- awful. Wish I had known better when I got an Axiom 49, after getting an APC40, I really want an Akai MPK 25 key now. U can change midi channels on the Axiom's front panel.
I've had the same problem with my Nocturn and Axiom's mod wheel (only thing I map on it), had to put them on seperate midi channels.

Locked