Hello NativeKontrol! I've recently been trying to integrate the original Novation Launch Control into my Live setup, but I'm having a problem. Basically, any Launch Control knob that's sending CC1 is switching the device to different user and factory templates. The template that it switches to seems fairly random. I've seen User 3, Factory 8, User 4, and User 5.
This seems to only happen when I'm using it with DDC. Here's a video which shows the issue in action, as well as my preferences: youtu.be/mIW3YvpapEM
I haven't used the DDC Mappings from the repository because I wanted to create my own using the DDC Editor. I also customized the control number definitions and set it up to very simply control the macros of Live's "Instrument Rack" device.
Here's what I've tried so far: - Rebooted the computer - Swapped the USB cable - Ran the Launch Control Updater to make sure the device itself is up to date - Deleted / Re-added the Launch Control from the Mac's Audio MIDI Setup application - Used a different user template slot on the Launch Control (same results regardless of template slot used) - Assigned CC1 to different device knobs (CC1 switches the template regardless of which hardware knob is sending it)
OK, so looking at the repository files, it seems like this controller may require unique CC mappings to be used with DDC. It also seems like I may not be able to use my own user-created templates with DDC (which would be unfortunate)... The repository file dictates that "In order to use the controller with DDC, you'll need to put the controller into Factory Template 8." Factory Template 8 sends on MIDI channel 16, and from what I can tell, this can't be changed.
Initially, my goal in creating my own template was to prevent interference by putting DDC2 on a MIDI channel other than 16. I'm already using channel 16 for a lot of other things, so I figured it'd be wise to have DDC2 use something else. Am I totally locked into using Factory Template 8 and MIDI Channel 16 with this controller?
Last Edit: Nov 14, 2019 12:00:56 GMT -5 by exlxaxd
Apologies for the delay. In regard to CC1, that's undocumented functionality of the controller. Sending CC1 to the controller will cause it to switch between templates. CC0 also has special functionality associated with it. So you shouldn't assign controls to either of those CCs.
As far as setting up/using a template for DDC, the easiest thing to do would be to use the files provided for the controller on the repository. If you strictly use the controller for DDC (and not for things like MIDI mapping), it's not possible for other controllers to conflict with it. If that's not possible in your case, you can use whatever template/assignments you want. You'd just have to use the Control Number Definitions file from the repository in order to tell DDC what CC/note numbers to use.
If you strictly use the controller for DDC (and not for things like MIDI mapping), it's not possible for other controllers to conflict with it.
Thanks so much for this info, Stray! Just to make sure I'm clear: Let's say I've got a knob on my MPK Mini sending CC21 on channel 16, and I've also got DDC + the Launch Control sending CC21 on channel 16. Any Live tracks that are set to receive MIDI from "All Ins" and "Ch. 16" generally won't respond to the Launch Control, but will respond to the MPK? That is, unless that track includes one of the devices specifically targeted by the DDC script.
Am I understanding this correctly? I also have a couple more questions if you don't mind...
If I use the repository files and the Launch Control's "Factory Template 8" as you recommend, would there be any issues with me switching to other Launch Control templates (User 1-8 or Factory 1-7) for other purposes such as manual MIDI mapping?
Somewhat unrelated: The Launch Control ZIP on the repository contains a readme file that hints at some unique functionality of the device's Pad LEDs. Here's an excerpt, but I could use some additional context... So far in using it, I haven't seen the LEDs doing anything unique, and I don't understand what the listed values represent nor how they can be useful:
>>>>>>>>>> PAD LED VALUES <<<<<<<<<<
Pads 1 - 8 have multi-colored LEDs. The value for each color is listed below.
Red_Full = 7 Red_Half = 6 Red_Third = 5
Green_Full = 52 Green_Half = 36 Green_Third = 20
Yellow_Full = 62
Amber_Full = 55 Amber_Half = 38 Amber_Third = 21
Thanks again for your help, Stray. Your tools have been absolutely ESSENTIAL for my creative workflow... so, in the spirit of Thanksgiving, I am forever grateful for you and your superior intellect!
Last Edit: Nov 20, 2019 12:36:22 GMT -5 by exlxaxd
Yes, your understand is correct. In regard to the other questions: 1. Possibly as Live's takeover feature only works correctly for absolute controls (like the knobs on the Launch Control) that always send the same MIDI message. If you're switching between templates such that the knobs have different MIDI assignments in each template, that would not work with Live's takeover.
2. When editing the assignment of a button in the DDC Editor, you can choose an On and Off LED value for the button. The list there tells you which values correspond to which colors/states.