MIDI conflict issue

MarkR

After setting up some midi learn in AUM I've got two midi overlaps that I'm trying to undo.

The set-up: a Novation Launchkey Mini Mk3 and a Korg Nanocontrol2 plugged into AUM. The 'nano sliders have been mapped for channel volume control (and its Solo and Mute buttons have also been assigned), and the Novation so far is strictly key input. I've done no other mapping.

Problem 1: the ch. 2 slider on the 'nano also affects a modulation filter in AUM ch. 4 (bs-16i app).

Problem 2: the mod strip on the Novation also affects the volume slider in AUM ch. 2! (Pipa app)

I didn't assign these, so how do I undo them?

Thanks!

wim

If you dive into the AUM parameters, do you see anything mapped there? If so, you can turn them off there.

_ki

1) Is the nano somehow routed to bs16i in the AUM midi matrix ? Maybe the app reacts to the same CC that the ch.2 slider is sending.

2) Is the novation keys routed to ‚Midi Control‘ in AUMs matrix ? The if mod strip sends the same CC/channel combination as the nano volume slider for channel 2, the mod strip would also change the volume.
If the novations keys are planned as ‚strictly key input‘, it should not be routed to ‚Midi Control‘

uncledave

@MarkR The control in bs-16i may be responding to Apple Core MIDI directly, bypassing AUM (assuming you're referring to a modulation filter inside bs-16i). If you're not, do you mean another AU, or an AUM built-in AU?

Also, you can use MIDI Wrench or MIDISpy to learn exactly what CCs your controllers send, so you can design a workable configuration.

MarkR

Thanks folks. I was indeed about to download something like MIDI Wrench or MIDISpy, and then realized that the problem likely arose because I was using an AUM session that had been modded quite a few times. I started a new session with identical apps and both problems no longer exist.

Thanks again!