I've attached a simple QLC workspace to test all the buttons, backlights & faders of a Novation Launch Control Mk2. Also attached is the profile.
I find it useful for checking the hardware is operating ok, especially the button colours/colors.
.
QLC Workspace for testing a Novation Launch Control Mk2
-
- Posts: 5
- Joined: Mon Dec 09, 2019 1:18 pm
- Real Name: Craig
Hi Allan,
Thanks for this, very helpful for debugging.
Just wondering if you know if there is any way to get QLC to support the templates that the Launch Control has (8 factory and 8 user).
It seems it's tied to one template by the single channel restriction in the input mapping (and that moving templates changes the channel). This seems to dramatically restrict the usefulness of the controller, as I'd love to flick over to say template 2, and suddenly have all the controller inputs now focused on controlling just the lasers.
Been googling and github searching, but no idea if this is a fundamental restriction in the way QLCplus handles midi data, or just a qxi file issue?
Thanks for this, very helpful for debugging.
Just wondering if you know if there is any way to get QLC to support the templates that the Launch Control has (8 factory and 8 user).
It seems it's tied to one template by the single channel restriction in the input mapping (and that moving templates changes the channel). This seems to dramatically restrict the usefulness of the controller, as I'd love to flick over to say template 2, and suddenly have all the controller inputs now focused on controlling just the lasers.
Been googling and github searching, but no idea if this is a fundamental restriction in the way QLCplus handles midi data, or just a qxi file issue?