Ableton Forum

hey guys,
Im having one slight niggling problem with my Launchpad. For some reason it keeps sending out a signal on Ch1 CC16

Im using a Vestax VCM600 for mixing, filter and EQ, and using the Launchpad for triggering clips and playing drums.
All is working well, except for some kind of interference with Note/Controll CC 16 on channel 1. I've got this set up as a gain pot on my VCM 600, but when i am using the Launchpad, the knob automatically starts to swing to either extreme. It's either -35dB or +35dB. I've tried changing the midi mapping with the VCM 600, so that ch 1 CC 16 is assigned to something else, but then the same thing happens with that other device, it either moves to one extreme, or the other. Regardless of what I assign it to, ch 1 CC 16 won't work as it's meant to. As soon as I unplug the Launchpad, it works how it's supposed to.

I've been through the Launchpad Programmer's Reference, and i can't work out what ch 1 CC 16 is.
Is there anyway to change the Launchpad's MIDI output channel so that it's not on ch 1, that way it wouldn't clash with the VCM600? (I'm pretty sure this cant be done with the VCM-600 - I'm sure it's locked to its MIDI out channels).


is there anyway i can solve this or get around it? Is my Launchpad faulty? Surely it isn't meant to trigger a command all the time (even when it's stationary and no clips are launched)?

cheers,
sam

Yep, you're right. There should be nothing coming from the Launchpad on Ch 1 CC 16. The top row buttons are CCs, but they go from 104 to 111.

Have you tried looking at the output using something like MIDI-OX?

Either it is defective (not unheard of) or there is something strange with your MIDI routing.

MIDI-OX seems to be PC-only (im on a Mac).

anyone know of something similar for Mac?

PS ive sent Novation's tech support a similar email. so waiting to hear what they say.

there's also another wierd thing...
in user1 mode... it sends inconsistently some pads send notes on ch1 and others on ch5...
I don't get it..

samtastic wrote:MIDI-OX seems to be PC-only (im on a Mac).

anyone know of something similar for Mac?

Midi monitor is free and works ok.

Using MIDI monitor, it says the rogue message is a Control message coming from Channel 1 and the data is General Purpose 1 (Course).


Anyone know if there is a way to send the Launchpad's data down Channel 13-16. The VCM-600 uses channels 1-12. Can Bome's MIDI Translator re-route the MIDI? And if you can, will the Launchpad still work automatically with Live?

cheers

Editing the remote scripts docs could be a solution, don't have bought one yet so I don't know how its protocol is set up.

madlab wrote:Editing the remote scripts docs could be a solution,

how ?!

ok well i went back to DJ Warehouse (Melb, Australia) and chatted to the friendly fellas there, and they helped sort it out.

Im using Live 7.0.18, which they suggested could be part of the problem, but we managed to fix it.

The set-up booklet that came with the Launchpad suggested i set it up in Live's MIDI prefs so that the Launchpad's input/output ports were:

INPUT: Track: On --- Sync: Off --- Remote: On
OUTPUT: Track: On --- Sync: Off --- Remote: On

However, by changing it to:

INPUT: Track: On --- Sync: On --- Remote: Off
OUTPUT: Track: On --- Sync: On --- Remote: Off

it solved my sliding gain-pot problem (which was caused by channel 1 CC16 signals being sent.

But once i got home, i realised that the above set-up wont let me assign MIDI functions to the Launchpad (and i wont the bottom 8 pads to be clip view buttons, so i can quickly view the current audio playing in all 8 tracks).

So by changing my settings to:


INPUT: Track: On --- Sync: On --- Remote: On
OUTPUT: Track: On --- Sync: On --- Remote: Off

I can now assign MIDI functions to pads, and no rouge signals are being sent out that interfere with my VCM 600.

I still haven't got my Launchpad coming down different midi channels (it's still down 1 & 2) - which means I had to remap a few things on my VCM600. But it all works now, and i can get on with mixing and making some music : )

hope this helps someone else

i worked out that this was something to do with using Live 7. In Live 8 i dont have the problem.