See… I TOLD you it would only affect a small portion of users (namely, me). Or should I say the Send-to-Morph is briefly CPU intensive, or, has a “nice” value of zero? So I can’t tell if the issue is OSX CPU related, Live related, or conflicting sysex-related from the Morph data flash going over the same line as everything else. (All of this is an educated guess and noticed by the sysex call and reply from the Novation gear via MIDI Monitor OSX app, and, the audio interface hiccuping and failing = loss of digital clock sync). Add to this there’s a MOTU 828x Thunderbolt audio interface connected as well (and a Behringer ADA8200 connected to that over lightpipe). I can’t recall if Live was “running” (playhead rolling) or not, that could have had a role since I’m sending clock out to multiple sources over MIDI and the Morph flash interrupts that stream… that’s my best guess. I’ve gotten what seems like a MIDI kernel panic in Live (Live crashed twice on me, at spread apart events, but not all the time) or, an audio sync hiccup.
#LAUNCHCONTROL XL MIDI MAPPING PATCH#
I have the Morph connected via USB hub (AC powered Anker 7-port in my case) and also have an iConnect mio10 MIDI patch bay connected through the same USB Hub as well as an original model Launchpad AND LaunchControl XL on the same hub and possibly a LinnStrument connected, but this week it’s not. At least not for me and the shows I play or the type of workflow I do at the home studio.įWIW I should also point out that I’ve noticed something that could be considered a “bug report” in the send-to-Morph process, but it’s so minor and would affect such a small portion of the Morph population (namely, me), that it’s not worth it.īUT if you must know what’s happening? It goes a little something like this: Not terribly efficient if you’re at an improv gig and you’re hurriedly getting something ready in Abelton on the spot.
If you can think of a faster way, please bang out a reply here. But I think I’ve solved it on paper make six small boxes on the layout that have those six individual CC controls solely for just the assignment stage in Ableton Live and the XYZ pads use those same CC values respectively. The possibility is there for these easy-thought-up control setups, but the pathway is darn near impossible when you’re trying to be creative.
Ableton does not allow to manually type in CC# assignments either, so that’s not an option. Click the triangle above the XY Pad > hit Command-M for custom midi mapping > select a parameter > send a CC20, then again send a CC21, CC22 (Z) is optional, and you’re done.īut even that is difficult, since the Morph (and any other XY Pad) sends out multiple parameters constantly per touch, making it impossible to custom assign any one single CC, Abelton grabs the last CC in the string. Part of this problem is that Live does not allow Custom MIDI mappings for those fields underneath the XY Pad you have to go into the deeper parameter menu per plugin to do that.Į.g. Copy that to the second MIDI XYZ Pad make that CC23, CC24, and CC25 respectively.” “In Ableton Live, CC20 controls the X, CC21 controls the Y, and CC22 is an open-assignable Z for aftertouch. I just wish it was easy to define this, as I am actually trying to set up a Dual MIDI XYZ pad in the Innovator’s Layout: Hopefully where you would determine what those parameters that are being controlled after-the-fact. I’m trying to devise a fast method of assigning a MIDI XYZ Pad to always point to parameter X & Y of Ableton Live’s XY Pad that appears for any MIDI-controllable device (effect or instrument). Not sure but you could probably do something with MidiBridge/Midiflow that looks for the input coming from the LaunchControl and then sends back to it the feedback that would ideally come from gadget.EDIT: SCROLL DOWN a few messages. If this is the case then I suppose I'm out of luck because Gadget does not output MIDI, correct? My assumption is that some sort of MIDI output is required back to the LaunchControl to tell it to illuminate the LEDs.
#LAUNCHCONTROL XL MIDI MAPPING SOFTWARE#
If they work like the Launchpad then the software needs to send feedback to the controller.this would seem to be the case as you can control the LED color of the rotaries from within the template editor but not the pads. The functions do work just to light to indicate on/off. Is there supposed to be some sort of feedback message sent from Gadget to tell the buttons to illuminate? Otherwise it's not obvious if the function is triggered or not. I wanted to use 16 pads at the bottom as toggle switches which works fine using editor software but there doesn't appear to be a way to illuminate the led on the pads when they are pressed. I just received my Novation Launch Control XL and I'm setting it up to work as a standard midi controller with Gadget.
0 kommentar(er)
