Ableton Forum

I just got my LP. I downloaded Live 8.1, set the midi settings up, loaded up a project, hit an amber pad and *drumrolls*:

-Lights on my Launchpad are blinking randomly. Like everywhere on the grid. I have to switch to usermode and back to session to stop this.
-When i fire a clip from a slot, it fires a clip on a completely different slot.
-Top row is the most problematic, but some randomness is happening on other pads aswell....
-I tried to have visual feedback from a drum rack (with the midi I/O trick), the page and scene buttons on the session view are changing color and blinking aswell

I tried to call DV247's customer support, but they hung up on me 2 times.. (wtf really?)

Should i contact Novation directly or the dealer (sensorship-edit: maybe this was not so approprite)? Are the DV247 people just gonna send my launchpad forward for repair and around the world it will travel for many moths? I dont know anything about British customer care laws..

Starting to regret ordering from UK. Should have waited for local dealer to have these on stock.

you're sending midi to it from a track, don't do that.

Feed back only works in User 1 mode. If you send MIDI back to the Launchpad in any other mode weird shit will happen. Manually map one of your buttons to the Monitor "In" switch on the MIDI feedback track. When you are about to switch out of User 1 mode to any other mode, de-activate the "In" switch to prevent unwanted feedback.

Could it be that your liveset has existing mdi assignments for the clips? Like you fired clips with a different midicontroller before?

This is causing similar behaviour in my big liveset. I have to find a solution, as I need to assign a couple of clips via midi in order to trigger them with reactivision. Apparently launchpad doesn't like it when you have clips assigned to midi notes.

does anyone else have the same issue?

I wonder if it can get resolved by changing the midi-configs in preferences, right now I enable both track and remote for both ins and outs for the launchpad.

I need to check that this afternoon when I get home.

Tomorrow I have my first gig with the launchpad. Would be nice if I can resolve it before.

It's not really an issue, as it's designed this way.

I agree that's lame.
And really annoying sometimes.
If you wanna use USER1 as mdi keyboard [without velocity but...], you can't really use it efficiently.

As for the led feedback, Forced to add a midi track receiving the desired midi chan.
Nice for composing slice by slice... but not real time proof

Well for the price I imagine users can't wait too much from it [sales policy?]

I don't get what the problem is. Either you use it with instant mapping to fire clips. Or you use it in user mode.

To switch between the two you press a button and mute the track sending feedback to your Launchpad.

.m

hi lofi,

look, if you assign clips to trigger them by certain midi-notes (which I do with some clips that I trigger via IAC/reactivision - for the fun of it), then this seems to conflict with launchpad's session-matrix.

I have a couple of clips assigned to the notes A1, A#1, B1, C1, C#1, D2. Once they have been triggered some of the pads on the launchpad start blinking and seem to be fix-assigned to thoses clips instead of their usual function. This is especially bad with one (C1 I believe) of the assignments as it seems to collide with the session-button on the launchpad.

I tried to use a different midi channel for my assigned clips, but it didn't help.

Hi Rosti,

Neil here from Novation technical support.

Do you have Automap installed on your computer? I have seen similar issues when Automap is loaded alongside Ableton/Launchpad.

Please check out this article as it may be relevant - http://www.novationmusic.com/answerbase ... php?id=547

If you continue to experience problems, please contact me though the Novation contact form and I will be happy to assist further:

http://www.novationmusic.com/answerbase/en/contact.php

Best regards,

Neil Marron
Novation Technical Support

Thanks for all the help! <3

pepezabala wrote:Could it be that your liveset has existing mdi assignments for the clips? Like you fired clips with a different midicontroller before?

That could fix it! I used to have pads on my Remote SL triggering clips on 8 tracks by default on every project. And i allso use automap so it could allso couse some conflicts. I have to try these out when i have more time.

Sort of relieving to now that this is probably a software bug (wich could be maby be fixed with a driver update?) rather than broken unit

edit:
called my friend "im gonna come little later, have to play with my new toy" and tested removing the clip assigments. Worked fine!
Now if they just made the driver better so i could have visual feedback on the drum racks and use the session mode (without the light blinky stuff on session grid) at the same time, beat making would be soooo much fun! I hope i dont lose my self in the making again and miss E.V.P + Reality Grid show tonight

Thank you again!

How i can change the focus of Automap pro software to Remote SL?! It allways offers Launchpad for me. Now every time i want to control a plug-in, i have to choose the mapping separetly from the SL.. REALLY ANNOYING! Like... Have novation even tested this stuff out before they released it?

Is there a way to choose a default controller on Automap PRO? I dont really want to control any parameters with buttons when i have knobs and faders.

(ok, i had to restart live and automap, bring focus to a plug-in choose "focus on remote sl" close the plugin and reopen it )

rosti wrote:Now if they just made the driver better so i could have visual feedback on the drum racks and use the session mode (without the light blinky stuff on session grid) at the same time, beat making would be soooo much fun!

Just map a button to the monitor button on the midi feedback track and turn it off before you flick to session view, or mixer. Works fine. Light feedback for drumracks and session and mixer working fine.