Hi all!
I have one on the way and I had not realized that it's not yet supported. Is it someting underway?
If not, anyone has worked with it that could share the required files?
Thanks!
I have one on the way and I had not realized that it's not yet supported. Is it someting underway?
If not, anyone has worked with it that could share the required files?
Thanks!
Posted Fri 28 Nov 25 @ 1:47 am
No, it's not yet planned, but we could add at some point, especially if you re willing to help with remote assistance sessions.
btw, it's not that it's not yet supported. Even if it was, you couldnt use (after the first 30 days of Trial ) the device with your Plus license which is for another controller.
btw, it's not that it's not yet supported. Even if it was, you couldnt use (after the first 30 days of Trial ) the device with your Plus license which is for another controller.
Posted Fri 28 Nov 25 @ 3:53 pm
I was aware of my licence, thanks anyway for reminding me. It's just that I figured that part was already supported :)
I am willing to help for the mapping and the other files for the Launchcontrol. If we are in contact, I also have suggestions for the FLX4 and something else I will PM you about.
I am willing to help for the mapping and the other files for the Launchcontrol. If we are in contact, I also have suggestions for the FLX4 and something else I will PM you about.
Posted Sat 29 Nov 25 @ 12:51 pm
Ok, found some useful info in their manual. Will create some test Mapping files and will email you once i have them ready to test.
Posted Sun 30 Nov 25 @ 4:12 pm
Just in case you were referring to the actual user guide, there is also a programmer guide available which seems quite clear. https://userguides.novationmusic.com/hc/en-gb/sections/27840433446546-Launch-Control-XL-3-programmer-s-reference-guide
Posted Sun 14 Dec 25 @ 10:42 am
Hi!
While waiting for a potential Launcontrol XL3 device defintion, I started building a simple one. I have trouble sending back info to the device.
Le's put an exemple. A 360 rotary encoder is used to control deck 1 gain.
In the definition file:
In the mapping file:
If I use a midi app and send on Channel 3, the value 64 with CC 0x0f, both the LED intensity and the actual value of the pot will be modified correctly.
I didn't manage to achieve the same thing within VDJ. I tought autoled would generate a LED_D1-GAIN that I could use but I don't see it. I also don't know what actions I should use with that key to to send the proper midi message.
Can someone advise me?
Thanks!
While waiting for a potential Launcontrol XL3 device defintion, I started building a simple one. I have trouble sending back info to the device.
Le's put an exemple. A 360 rotary encoder is used to control deck 1 gain.
In the definition file:
<slider cc="0x0f" name="D1-GAIN" autoled="true" deck="1" zerorange="1" channel="2"/>
In the mapping file:
<map value="D1-GAIN" action="deck 1 gain" />
If I use a midi app and send on Channel 3, the value 64 with CC 0x0f, both the LED intensity and the actual value of the pot will be modified correctly.
I didn't manage to achieve the same thing within VDJ. I tought autoled would generate a LED_D1-GAIN that I could use but I don't see it. I also don't know what actions I should use with that key to to send the proper midi message.
Can someone advise me?
Thanks!
Posted 4 days ago @ 2:53 am
<slider> is an input element.
You can use <bar> for output, as explained here https://virtualdj.com/wiki/ControllerDefinitionMIDI
autoled is currently only available for <button>
You can use <bar> for output, as explained here https://virtualdj.com/wiki/ControllerDefinitionMIDI
autoled is currently only available for <button>
Posted 4 days ago @ 4:05 am
Thanks.
I figured what you meant but I'm still stuck. I have two questions.
1-The LCXL3 has 4 devices: (in+out) normal MIDI mode and (in+out) for DAW MIDI mode. I figured that VDJ input is on port 1 and VDJ output should be on port 2 for normal MIDI mode. VDJ discovers the 4 devices. As we speak, data is well recieved on port 1, but I cannot send on port 2. Do I need to prepare a second definition file? Should the vid or pid be different for VDJ to figure out which port is which?
2-Let's pretend that I want to use the following definition element but I want to vary the value.
Is it ok to suppose that the definition file must be static, or can use variables but only once at startup?
To change the value, is it valid to do this in the mapper?
I figured what you meant but I'm still stuck. I have two questions.
1-The LCXL3 has 4 devices: (in+out) normal MIDI mode and (in+out) for DAW MIDI mode. I figured that VDJ input is on port 1 and VDJ output should be on port 2 for normal MIDI mode. VDJ discovers the 4 devices. As we speak, data is well recieved on port 1, but I cannot send on port 2. Do I need to prepare a second definition file? Should the vid or pid be different for VDJ to figure out which port is which?
<device name="LCXL3" author="Yan Duval" description="Novation Launch Control XL3" version="2026" type="MIDI" vid="0x1235" pid="0x0148" >
2-Let's pretend that I want to use the following definition element but I want to vary the value.
<led cc = "0x4A" value = "0x5C" ccoff = "0x4A" zero = "0x2C" sendstatic = "true" name = "LED_EFX1_BTN" default = "EFX1_BTN" deck = "1" channel = "0" />
Is it ok to suppose that the definition file must be static, or can use variables but only once at startup?
To change the value, is it valid to do this in the mapper?
<map value="LED_EFX1_BTN" query="deck 1 eq_high_freq" />
Posted 2 hours ago
Yes (but note that led is on/off, so your example of mapping it to eq_high_freq doesn't make much sense)
Also you don't need "deck 1" in your script, since you already define in your definition that this element is for deck 1.
Also you don't need "deck 1" in your script, since you already define in your definition that this element is for deck 1.
Posted 2 hours ago
Adion wrote :
Yes (but note that led is on/off, so your example of mapping it to eq_high_freq doesn't make much sense)
Also you don't need "deck 1" in your script, since you already define in your definition that this element is for deck 1.
Also you don't need "deck 1" in your script, since you already define in your definition that this element is for deck 1.
Ok great, so if my single led can vary in intensity, I should use the bar element instead?
Posted 2 hours ago
Yes
Posted 2 hours ago
Great, thanks!
And for my first question? Should I do a single definition file and create 4 mappings (out-MIDI, in-MIDI, out-DAW and in-DAW) and assign them to the respective controllers shown in this image?
They are not described better but I can find which is which by trial and error.
And for my first question? Should I do a single definition file and create 4 mappings (out-MIDI, in-MIDI, out-DAW and in-DAW) and assign them to the respective controllers shown in this image?
They are not described better but I can find which is which by trial and error.
Posted 2 hours ago
We are expecting a unit to arrive in our labs very soon.
Therefore we will be able to provide official support for the device soon.
So, what I would like to ask you, is how you intend to use this unit.
As a MIDI mixer ?
Obviously it's layout is more suited to DAW software to control channels, rather a DJ software.
So, once everything is defined, how do you intend to use/map it ?
Therefore we will be able to provide official support for the device soon.
So, what I would like to ask you, is how you intend to use this unit.
As a MIDI mixer ?
Obviously it's layout is more suited to DAW software to control channels, rather a DJ software.
So, once everything is defined, how do you intend to use/map it ?
Posted 59 minutes ago





