Sign In:     

Forum: VirtualDJ Technical Support

Topic: Novation Launchcontrol XL 3 - Page: 1
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!
 
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.
 
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.
 
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.
 
 
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:
 <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!
 
 
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?
<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" />
 
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.
 
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.

Ok great, so if my single led can vary in intensity, I should use the bar element instead?
 
Yes
 
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.
 
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 ?
 
Can only offer perspective as a mk2 user
Samples obviously,
4 decks of pads
I think 1 page devoted to entry level basics is obligatory despite me never using it

I can totally see page devoted to stem solo/cut not via padpage, a problem with stems is you only have 2 hands, having all 4 decks on one hand [maybe 2 is you're really going for it] is so much better than 2 hands split left and right pads on a controller


Now we venture into my weird custom world.
I had a page for video, called videofx, called specific shaders [when I was off decks and doing visuals side] maybe lean into that, even as a tutorial ;-P
I had one novelty page just showing deck levels [no real purpose but it looked cool]

my main page was catering to my ravey nature, selected deck based, it had a line of beat jumps, it had a line of loop lengths, a section for short loop rolls, 4 lines of padfx style effect calls [before padfx was a thing] [went to town with colouring buttons to help remember what was what, went that way with other buttons too, short beat jumps red, longer went into the blue and blink mixing colours]
You can't please everybody with that kind of page, but as a set of working examples, table d'hôte vs À la carte vs sur mesure , the average user starts asking above average questions.

*PS Edit, I guess I'm ranting now*

One thing I don't envy you on, however deep you map it, is mapping it;
8 var queries just for the page before dealing with the conditions of the thing you want on that button, zero chance of column typing that efficiently in np++

I tried using excel to keep things workable, [half an idea there but it got messy between outside vdj work with extension changing and changes I made in app because I just thought of it.]

Didn't mean to go this way with this post but launch pads are a pig to map [inside and outside vdj]

If you could isolate text down to controller_var 4 ? = true etc, it gets better,
then there's button versus LED, normally it's a section of buttons you map then you have to do the LEDs but the mapping entries are 64 lines apart,

so then it's scroll down, do a bit on 1 led then scroll up to remember exactly what the button is doing and then scroll back down. If you could sort entry names by alphabetical [as it is now] but have a second sort option of button entry above led entry for button. that would be a useful thing

I sound like I'm arguing against customising launch pads, I'm not, you'll have more buttons than you'll ever have ideas, but how it is now gets attrit.
 
@Locodog, are we talking about the same unit ?
 
oh no, I'm well off course, I was thinking a box of 64 pads, that makes most of my post completely wrong.
8 channel, 16 pads layout like that primary use would be fx, there's maybe a off decks video guy thing there, but that's a second screen and a skin window idea - so VERY unlikely.

I could use it... but I could use a coil of wire you shake magnets at if it will send midi, 8ch control fits perfect with my remix skin, but I've no commercially practical ideas for this
 
Haha! Launchpad is cool too but we're talking Launchcontrol.

To answer Phantom:

1-First use is to add extra buttons to my FLX4. The initial Lauchcontrol Template 1 is probably that.

2-Second would be to facilitate the use of deck 3 and 4

3rd is to do use it as a small dj controller.

I can for sure give more details but I guess it would be better to exchange a Word document or something similar. Is it of interest?
 
@Yan Duval, please share your thoughts.

However, my question is more generic.
What I ask is what a typical user would expect to use this device for ?
So that the default mapping provided with VirtualDJ is a good starting point, before tailoring the mapper down to "compliment my FLX4, and provide access to channels 3+4"

I mean, those are valid points from a personal point of view. But they are not good points from a generic point of view. I hope you understand what I mean.

So, I'm open to suggestions..
 
The Launchcontrol XL3 looks great.

I don't know if I could justify a purchase, or realestate, as I currently have a Midi Fighter Twister and Launchpads for needed knobs and buttons.

For use would maybe like, one bank to allow control of all the FX 3 slots and each of their parameters, with the strength using the fader, plus any additional knobs for maybe 2 or 3 extra CFX knobs (effect_colorfx 1-4)

Another maybe useful bank, to have deck 1, and deck 2 being knob rows 2 and 3, respectively, with the knobs being the stems (maybe EZ-Remix), and the Frequency EQs (Hi, Med, Lo) and the faders below each of the Stems would be used as Stems crossfaders, to Crossfade the respective stem above it, or crossfade the Frequency EQ, above it between decks 1 and 2.
(and fill in any unused knobs with CFX (effect_colorfx 1-4).

And use the pads for, Jumps, and setting loops, maybe on each of banks, and maybe a few instant filters (quicksearchs), and some gotofolder and gotolastfolder pads, for quick navigation.)


I would be interested in feedback for use as a DJ controller. I have peeked at the reviews and some report the knobs at times are bit stiff.

and another issue, maybe, to watch for, (possibly fixed with firmware update by now), one recent Amazon review mentioned:
----------------------------------------
Reviewed in the United Kingdom on November 22, 2025
Style: Launch Control XL 3Verified Purchase
While it is integrated with Logic a bug means if you touch the lowest rotary knob on channel strip 7 the fader on strip 2 ceases to work until you reboot it. It’s been on the market for 6 months now and Nivation are aware but have to release a patch. Disappointing I sold mine.
---------------------------------------
 
PS *(off topic)

Locodog's post about editing a Lauchpad mapping, reminded me that, it would be so awesome if the Mapping editor "Action" script editing, window was able to be resized larger, or to have an entirely full screen VDJ script editor.

Currently, my only workaround is to create many multibuttons, which allow for many lines of script to be consolidated to a single phrase, which allows one to view the entire logic of a pad's script, within the currently limited view area.
 
69%