CMD MM1 RealSession

Description and Instructions

CMD_MM1_RealSession


If this script does not work for you check the following:
  • If the new directory you created in MIDI Remote Scripts contains any "-" or other weird characters Ableton will not be able to import it. "_" is ok thought.
  • It might me that your CMD-MM1 does not send on MIDI channel 1 In the file MM1.py change CHANNEL = 0 to CHANNEL = 4
--- VERY IMPORTANT --- 
Your startup template ( in ABLETON ) must have at least 4 tracks, otherwise the script will crash and wont load meaning no red box and you'll get error ( in log.txt file ) , even if ableton is receiving midi signals (note & CC )

This is a Ableton Live 10 and 9 Mapping for the Behringer CMD MM1

  • Faders move along with the moving red box in live. 
  • Knobs is auto assigned to the first device for each track when the box moves
  • You can use two CMD MM1, you just have to configure in two MM1 devices in Abletons preferences.
If you don't know how to install 3rd party remote scripts see


  http://sonicbloom.net/en/ableton-live-tutorial-how-to-install-midi-remote-scripts/

You can easily check which channel your CMD MM1 sends on in live by mapping a knob on the MM-1 to something and then check the channel in the midi mappings window in Live.

A big thanks too Behringer for releasing the CMD MM-1 and their remote scripts.

You can follow the project at:
https://github.com/lindroth/CMD_MM1_RealSession
YouTube Video URL
Upload new image
0.3.0 The folder name in the zip was incorrect, python can't import names with - in them edit delete 0.2.0 Fixed bug where the knobs was not remapped from a device if the new track had no device. edit delete 0.1.0 Initial release edit delete
< Back to mapping
<!-- track pageviews in edmund/keen -->
Problem downloading or other issues? Let us know on the forum.
-
Comments for v0.5.0
There are no comments for this version yet! Why don't you be the first.