This may be useful information for the purchase:
https://www.youtube.com/shorts/J5lWjVjifQc
Didnt the response curves fix this in the update?
you can see in my video how fast i tweak the controller and I don’t experience anything like that, i bet something is either wrong with that guy’s unit or setup
7 Likes
I had a similar problem in XL 2 but I was heavily transforming midi messages through m4l devices ¯_(ツ)_/¯ and it wasn’t lagging on all messages just some
Thank you for your message and information.
I happened to see the video and wanted to point it out. If the problem no longer exists, all the better.
I just received my LaunchControl XL3 yesterday.
Connected it to the Mac, loaded Components, upgraded LaunchControl firmware, and started to create a config for Bass Station II.
Came back a bit later and it showed as disconnected.
Unplugged it, plugged it in… nothing.
Then it just magically appeared. Then disappeared and wouldn’t come back until ‘some combination’ of plugging/unplugging, launching/re-launching Components, logging out/logging in of Components worked.
But, it shows as disconnected 80%+ of the time, and I haven’t figured out why.
Logged in. Not logged in.
USB to M4. USB to dock.
Any ideas/thoughts/solutions people might have had? Wondering if I have a dodgy LaunchControl, or if the new firmware has issues, or I’m holding it wrong.
Thanks
1 Like
Have you tried a different USB cable? It could be a faulty unit, but that behaviour could also be a faulty cable.
Thanks for the reply.
Yeah (meant to put that in my original post)
Tried a few actually.
Hmm.
Are you connected directly to the Mac or via a usb hub, I’ve had probs in the past with hubs and a direct connection sorted it…
Edit… also are you trying to config for the bass station 2 plugin?, there’s should be a template for that already in the the side bar, I’ve not got an lcxl myself but theres one for my MK4 launchkey…
Thanks Symian,
I’ve tried directly on the M4’s 5 ports, as well as on a couple of the USB-A ports on my dock, and two USB-C ports on my dock.
After another round of troubleshooting, I ‘think’ it’s components and its behavior regarding the computer’s internet state (on/off).
LaunchControl fails to show up in Components 100% of the time the FIRST time I open it after the internet connection has changed state.
Example:
Internet ‘on’ and LaunchControl/Components working… cool.
Then close Components, toggle the internet state (off if it was on, on if it was off). Open Components: LC doesn’t show.
BUT in every case: if I then close Components and re-open, LC is there again.
Until I change the internet state again and then:
The first time it doesn’t show up… then every time afterward it does.
I just did that 30+ times and the behavior is the same.
This happens whether logged in to my Novation account or not, and without unplugging/replugging the LC across tests.
I think there’s a bug here somewhere, which is actually a good thing, since I’ve found a workaround, so I don’t think it’s hardware given the behavioral consistency.
Not sure if it’s within the version of Components I’m running (1.64.0), or LaunchControl firmware (also latest: 1.11…), or in the ‘handshake’ between them on startup.
I can live with it, but will share this with Novation and maybe there’s a fix (if it is indeed a bug)
1 Like
Here’s an RK-002 sketch that will do that - when you compile it, just tell it which CCs you want for AT and PB. There are only 128 positions for a CC vs 16,384 for PB so it just step-scales those values (64=0 PB):
#include <RK002.h>
//CC to AT and PB
RK002_DECLARE_INFO(“CC_ATPB”,“Paul”,“1.1”,“95ce3837-4ec2-4813-b23b-70c3c767d7b1”)
RK002_DECLARE_PARAM(ATCC,1,1,120,20) // CC for aftertouch
RK002_DECLARE_PARAM(PBCC,1,1,120,21) // CC for pbboolean RK002_onControlChange(byte channel, byte nr, byte value)
{
if(nr==RK002_paramGet(ATCC)) { RK002_sendChannelPressure(channel, value); }else if(nr==RK002_paramGet(PBCC)) { RK002_sendPitchBend(channel, value*128-8192); }
else { RK002_sendControlChange(channel, nr, value); }
return false;
}
void setup()
{
}void loop()
{
}
1 Like
Thank you very much, that looks like it’ll do the trick! I’m at a busy spot this week and won’t be able to test until the weekend, but I appreciate it.
Update; thanks again, @Paul_xyz that does exactly what I wanted, brilliant! And stepping through the code and finally happening upon the DUY reference manual have given me confidence for scripting further in the future. For others’ future reference, I found CC’s 7 and 8 are unused by DT2 and DN2, and those work great turned into PB and AT values (the value confirmations on compile are a nice touch in the DUY portal).
2 Likes
Is anyone using their LCXL with an iPad? There seems to be an issue with mine and I wanted to see if is affecting others. The problem is with it hooked up to the iPad, the onscreen iPad keyboard does not pop up when it is supposed to for typing. The issue happens regardless of which app that I am using.
This has been an issue on and off since the new raft of devices dropped, I think it’s an apple thing not a novation thing, I had it a couple of times with a launchkey MK4 plugged into an ipad…
Heres the workaround I used…
6 Likes
Thanks for the tip. I’ll give it a try as soon as I get a chance.
Edit: It worked. Thanks!
2 Likes
I hope we’ll get relative mode for the encoders and faders in custom modes someday
5 Likes
Just ordered one to control my DT and AR! Let’s hope it works!
1 Like
There’s a handy editor for XL MK3 Custom Modes at http://midi.guide that has built-in definitions for a bunch of devices. It doesn’t support setting LED color, or specific CC values on the buttons, but it’s handy for throwing together a control layout quick. You can load it up in Components, assign the colors and CC values, and upload it to the device.
1 Like
Great troubleshooting 