Novation Nocturn causing launchpad to misbehave

[rude_NHS]

using both at once in ableton causes problems. turning the rotaries on the nocturn cause launchpad leds to flicker then turn off, rendering the session view on launchpad useless.

has anyone noticed this and found a solution?

are ableton planning on control surface support for the nocturn at any point?

[rude_NHS]

anyone?

[napalmbrain]

don't use CC0...just avoid it! if Launchpad receives it via some routing somehow in Live it will think its a reset message.

I think Nocturn has CC0 as its first knob...which is usually ok, unless you have some funky routing in live to send it back to the launchpad.

[SegusvanVegas]

Cheers dude! Having the same problem, so glad I found this post! ;o)

[holistic]

Great! I'll be sure to avoid the CC0...
Many thanks for this napalmbrain!

Maybe you could be able to solve it with some of the preferences input/output-thingy in Live?
Any ideas?

[Warrior Bob]

From what I understand Live combines the signals sent from all MIDI devices used for MIDI remote control. So if you've got two different devices both using CC0, there's no way to distinguish them.

You have to make sure that the devices aren't sending the same control signals, which can be a giant pain. Either reprogram the devices (what I've done so far...) or in a pinch you could use something like Bome's or MIDI-OX to intercept the MIDI signal and change it around somehow, maybe to a different channel. Unfortunately, if you do it this way, you lose control surface support, where those values are hard-coded.

I wonder if there is a way to hack the control surface list and make your own "recognized" control surfaces. If Ableton doesn't want to build in some kind of editor for this (which is understandable) it'd be nice to be able to roll your own.

[holistic]

hi again,
I e-mailed Novation about this problem.

They answered that it's a known problem. Using cc0 and cc16 in user mode (on the Nocturn) will produce this error on the Launchpad. So until there's a fix, maybe we should just avoid these cc-messages.

Peace

[holistic]

From what I understand Live combines the signals sent from all MIDI devices used for MIDI remote control. So if you've got two different devices both using CC0, there's no way to distinguish them.

You have to make sure that the devices aren't sending the same control signals, which can be a giant pain.

This is no problem for me. I've got some cc-messages that are sent from both the Launchpad and the Nocturn (controlling the same thing in Live of course). For example an effect-group's on/off-switch. And it works great. When i turn it "on" from the Launchpad, the corresponding button lights up on the Nocturn and vice versa.

Or maybe I misunderstood what you where saying...

[wehkah]

the simplest way is to use another midi channel for you nocturn. ive fixed a similar problem with my bcr & launchpad yesterday by chaning the midi channel for all bcr elements to channel 10.

peace&sun
T