This happens to you?

[gustavo bravetti]

I just realise that while using PUSH as control surface and a secondary MIDI Controller, selecting a track or device that has custom MIDI maps assigned (to be used with the secondary MIDI Controller), it seems Push´s script forces Ableton to send a MIDI CC/Note for each custom MIDI map in the whole project, through the MIDI controller Out Port.

So for example let´s say you have a dozens Custom MIDI maps assigned. Each time you select a track or device, dozens of MIDI CC clutters your MIDI Controller Out Port.

Any?

[login]

havent noticed, I normally use push and lemur and havent seens this.

[gustavo bravetti]

havent noticed, I normally use push and lemur and havent seens this.

Would you do this simple test for me?

With PUSH enabled

1) create an empty project (you'll have tracks: 1 MIDI, 2 MIDI, 3 AUDIO, 4AUDIO).
2) create two faders in Lemur then assign them to the 3 AUDIO and 4 AUDIO ´s Volume sliders.
3) check if control is working in both directions.
4) Now go to Ableton, Preferences, MIDI Tab, and turn OFF Remote for the Daemon # IN. So Ableton controls Lemur but Lemur doesn't controls Ableton.
5) move faders on Lemur so values on Lemur will differs from Ableton´s
6) with your mouse, or the arrow keys, or from push, navigate from the first to the last track and back

Then you'll see (I hope) that somehow Ableton sends CCs to Lemur updating its value.

Looking forward for your results,
Gustavo

[gustavo bravetti]

anyone?