YOu can't "turn off" that behavior. What you can do is to not send in
the data as remote control data for Live but rather as a pipe right
into the Mobius plug-in. The place to set that up is in Live's
preferences, the "MIDI Sync" tab. The MIDI In port that you use to
control Mobius (given you control it by direct MIDI Input and not by
Live's parameter, which is what Ableton usually recommends but we
loopists don't usually prefer) should be set to "Track". The MIDI In
port that you use to control Live should be set to "Remote". When
these preferences are correct you also have to set up a MIDI Track in
Live that snags your external MIDI data, aimed for Mobius, (as the
Live track's "Input") and directs the stream into Mobius (addressing
as "Track Output" first the track that hosts Mobious and then the
plug-in Mobius). This is just the normal way of routing MIDI in Live,
well explained in Live's manual. To set up more complex routing you
may send MIDI through the OS as well (IAC Bus on a Mac and by using
the third-party hack MIDI Yoke on a Windows machine).
On Wed, Dec 16, 2009 at 7:18 AM, George Ludwig
> I've got a looping plug-in (Mobius) and I want to control some of its
> parameters with a Korg nanKontrol. No problem, Mobius lets me do the mapping
> for midi control.
> The problem is, when I run it in Live, Live intercepts the volume control
> that I have mapped to Mobius' track 1, and uses it to control the volume of
> Live's track 1. I've deleted all the midi volume mappings in Live, but
> still, Live insists on changing the volume of track 1 when I really just
> want to change the volume of Mobius' track 1.
> I've heard that Live has a default midi mapping, besides the one that you
> can edit, and it seems like this is the culprit. How do I turn it off this
> defualt behavior?! This is giving me major headaches.