Novation LaunchControl XL Mk2 - Support for templates (i.e. multiple midi channels)

[Shanness]

Just wondering if anyone knows 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 (which auto updates all the lights, making it clear the controller is in another mode), and suddenly have all the controller inputs now focused on controlling just the lasers. Make the changes I need there, then swap back to primary template.

I.e. having fine grained control of certain fixture groups in different templates would be very useful

Been googling and github searching, but still no idea if this is a fundamental restriction in the way QLCplus handles midi data, or just a qxi file issue?

[AllanR]

OK, I've just been experimenting with my LaunchControl XL Mk2, and I'm successfully switching templates to control different sets of fixtures. Is this what you what you want to achieve?

If so, the key is to select the Novation Launch Control MIDI device in I/O Mapping and edit both the Input and Output settings to show "1-16", instead of the default "1" under the MIDI Channel column.

This allows QLC+ to auto-detect and assign different (unique) values to the Launch Control faders and buttons depending on which template is active.
The formula applied is: QLC Value= (CC# or Note#) +1 + (4096 x (Template# -1))
[This is described in QLC Manual MIDI I/O Section, QLC+ Channels map]

My test workfile demonstrates this by using Factory-1 template to show possible colour combinations using the bottom buttons.

If this is isn't what you have in mind, explain and I'll try to assist.

Cheers,
Allan

[pille]

i'm interested in this, as well
did you achieve syncing the template switch with virtual console, e.g. as pages?

[AllanR]

When you change the User or Factory template on the LaunchControl, no MIDI signal is transmitted. Therefore QLC isn't immediately aware of the change, and so auto-sync of frame page(s) doesn't seem possible.

You could however assign e.g Button 3 on the LaunchControl to a frame's page 3. That way immediately after selecting User Template 3 on the LaunchControl, press Button 3 on its own which switches to Page 3 of the frame. It's a two step process but you'd be using the same button for Template then Page select. A reasonable solution?

[pille]

actually there are midi codes emitted, when changing templates and they are even distinguishable.
however - it's not something like a note or fader. these are the events when changing user1-8 and factory1-8:

Code: Select all

user@S410B:~$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source  Event                  Ch  Data
 24:0   System exclusive           F0 00 20 29 02 11 77 00 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 01 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 02 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 03 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 04 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 05 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 06 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 07 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 08 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 09 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0A F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0B F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0C F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0D F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0E F7
 24:0   System exclusive           F0 00 20 29 02 11 77 0F F7
 24:0   System exclusive           F0 00 20 29 02 11 77 08 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 07 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 08 F7
 24:0   System exclusive           F0 00 20 29 02 11 77 07 F7

your workaround is not an option, since it wastes the 16 buttons and seems cumbersome.

[AllanR]

pille,
OK, I should have said that the QLC I/O Profile Wizard does not detect a change of the User or Factory template.

Please detail how a standard user could implement a synchronised template/frame-page solution.

[pille]

i know, that's why i subscribed to this thread.

i don't think it's possible for a user to configure this, as the MIDI subsystem would need to implement support for these events.
my goal would be to have them implemented. the actual good thing is, that they are emitted and can be dumped using a MIDI monitor.
so in case this would not be picked up by QLC+, there may be an (ugly) workaround to capture them with an additional tools that translates them into virtual notes/faders that can be fed back to QLC+.

[pille]

sending those SysEx messages to the controller actually makes it change templates, so the other way around may also be implemented, if page changes would emit them.