[S37E] Ableton CC conflicting with Editor automation

The Moog Forum Moog Beta Forum
1

Is there a solution for the problem of the Sub 37 Editors recorded automation conflicting with the recorded cc automation in the clips of Ableton live?
I love the editor but the only solution I found so far is deleting all recorded cc automation from lives clips and just leaving in the recorded automation values from the editor!

I’m on 1.2.0 Firmware and 1.0.0 Editor on Mac OS X 10.9

Using the Sub 37 via USB in Ableton Live 9.7.1

What I know so far:

  • Live records CC Data into MIDI Clips only, not into Automation Lanes like for example when recording automation on a VST Plug-In
  • Live records Automation Data into Automation Lanes only. (In the Arrangement View, In the Session View, it only Records Automation Data into the Clips)
  • The Editor only reads the Automation Data from the Automation Lanes
  • The Sub 37 doesn’t ignore CC Data when the Editor Plugin is connected to the Sub 37
  • Therefore the Sub receives Midi CC from Ableton’s MIDI Clips AND the Editor at the same time → Conflict

My idea for a solution:
Whenever an instance of the Sub37 Editor is connecting with the Sub37 the automation data that controls the editor should be sent on different Midi channel that has to be defined in the settings. Now add an option in the midi settings whether the Sub37 should receive midi cc either from channel 1 or 2 (for example 1 is cc from live, channel 2 is cc from the editor).

This way you preserve both automation data and can decide if you want the sub37 to listen to the cc written in the clips or the cc generated by the written automation for the editor.

Is this even possible or am I just thinking “too easy”?

Unfortunately this idea is not possible right now because you can’t define different midi channels for midi notes and midi cc right now in the sub37.

Can someon of the developers make a statement to this post?

Cheers

Jan

2

Hi,

This has been discussed before and has a workaround provided by Amos:

Go into Mapping mode (command-M), click the controls of the Editor plugin and then turn the corresponding synth knobs to map MIDI CCs to the Editor (the Editor already knows about the association, which is why automation is recorded “automatically” — but Live doesn’t know about it until the mapping is done manually) … once the MIDI CCs are mapped to the Editor controls, then Live should stop recording separate MIDI CC data in the MIDI clips.

3

I tired this before and it didn’t work but now it does…

But still it’s just an awkward workaround because this way I can’t use the moog as a controller for other synths anymore :frowning:

Also this could bring problems with other synths and vst, that have the same CCs mapped to something…

So workaround yes but no fix for the issue.

Even if I changed the midi channel for the moog it would make all my projects I did before obsolete and I would need to change the channel on every track where I used the sub on…