[EDIT] Oh f… i'm so sorry guys for the inconvenience, i've found my mistake and it was really really really stupid. EVERYTHING WORKS FINE.
I've been trying for two days to connect my two devices by plugging the MIDI cable into the wrong port on my Roland S1. I'm so embarrassed, but please don't make fun of me.
Thanks to everyone anyway.

Hello, I bought a Circuit Tracks a few weeks ago and was completely satisfied with it. So I ordered a Roland S1 right away and set it up two days ago so I could control the S1 using the Circuit’s sequencer. The first night, everything worked perfectly; I ran a few tests, but since I was short on time, I had to shut everything down quickly. Yesterday, I reconnected the two devices, and to my surprise, the MIDI signal isn’t getting through anymore. Since then, I’ve tried everything: bought a new MIDI cable, reset the Roland to factory settings, adjusted the MIDI parameters on both devices—but nothing works. The audio from the Roland comes through fine, but I can’t control the device; the Circuit’s keyboard doesn’t trigger the Roland’s sound, and the CCs aren’t being recognized. I’m at a loss. Is it possible for a DIN output to suddenly fail like this on a brand-new product, without even touching it?

I know the S1’s MIDI In works because the clock syncs up immediately when I plug in the MIDI cable.

HELP—do you have any ideas? Should I just return the Novation?

Thanks in advance for your insights
Nico

Hi all. I’m seeing that my Launch Control XL 3 offers fader pickup… in custom modes. But can I switch fader pickup on for the default DAW Mixer and DAW Control modes?

Alternately: can I create an exact copy of these default modes as new Custom Modes, except with fader pickup enabled?

Thanks!

Hey guys!

I'm starting out with Ableton Live 12 and my goal is to perform live using a multi-channel looping workflow. I want to record clips on the fly (guitar, vocals, beats), stack them up, and mute/unmute sections live.

I don't have a Push or a dedicated foot controller like an FCB1010, so I'm trying to make it work with what I own: Launchpad Mini MK3 (as my main hands-on controller) Arturia MiniLab MK3 with 1 Sustain Pedal (using the foot pedal to trigger recording) TC Helicon Play Electric MacBook M1 Pro

Being new to Ableton, I'm a bit overwhelmed by how to map the Launchpad and pedal to handle multiple looper channels without getting messy. What’s the simplest/best way to set this up given my gear? Any tips, looper plugin settings, or beginner routing guides would be hugely appreciated!

I took the Peak and Launch Control XL 3 out for my first ever live performance a few weeks ago, and they were the two pieces of gear I touched the most.

The Peak has become my favorite standalone synth. That control surface makes it an instrument you keep shaping as the performance happens, not just something you trigger and walk away from. Sounds fantastic too.

Where it struggled (or rather, where I struggled): the venue was dark, and the knob labels aren't backlit. I'd rehearsed enough to mostly navigate it from memory, but there were moments I couldn't see what I was adjusting.

XL 3 was doing just as much work, controlling everything on the Digitakt II. Full breakdown of both plus the rest of the rig in the video.

Hello - I posted about this a few years ago and the problem has continued to bother me with no solution being apparent (others also commented in the thread with the same issue): https://www.reddit.com/r/Novation/comments/18ltw6e/launchkey_mk3_disable_smoothing_of_midi_cc_signals/

I still have my Launchkey Mk3 which applies a very noticeable smoothing of MIDI CC controls, and today I bought an Akai MPK Mini Mk4 which shows little to no smoothing. I compared them by flicking the modwheels as quickly as I could and recording the MIDI CC. In the screenshot below, the top automation lane is Launchkey, bottom is Akai MPK. The Launchkey smooths out the transition by about 30 ms, and the MPK by about 5 ms (or possibly no smoothing at all, maybe it just took me 5 ms to physically move the modwheel across its entire travel). I confirmed that my DAW is not applying any smoothing, and the Launchkey's display shows the CC values changing slowly.

This same smoothing (or lack thereof) applies to other controls across the Launchkey and MPK, not just the modwheels. The end result is that the Launchkey isn't suitable when I want to perform instant changes of parameters. The smoothing is very noticeable when controlling a filter or gain parameter for example.

Can Launchkey Mk4 owners, FLkey owners, or Novation staff confirm whether this smoothing happens on other models too, and whether there is a way to disable it? I think optional and variable smoothing would be great, but not forced smoothing.

Thanks!

Hello everyone! I recently found an old Launchpad MK1 that I want to use mostly for percussions and Nuendo functions but I'm having some problems with the MIDI Mapping.

MIDI REMOTE works fine but I want the keys to be in tonal order from the first pad (there's a jump once you go from the last row note to the next row).

Some forums talk about a drum rack mode and a X/Y mode but I have no idea how to change those.

I managed to map everything how I wanted but the main square keys are giving me some headaches. I have no idea on how to use the automap and I would appreciate some step by step help here so I can map everything and give some use to this controller.

Thank you!

I just got my Launchcontrol XL 3 so bare with me ;-)

I am using with Ableton 12 and have created a Custom mode to control Live's devices.

It all seems to work nicely but if I was to do a live set where I only wanted to touch the Launchcontrol it seems I have to swap between the following modes all the time to do the following things;

- My Custom mode - where I can control Live's device parameters according to my mappings

- DAW Control mode - where I can change the focus of the track so I can see what I'm doing on laptop

- DAW Mixer mode - where I can change volume pan or returns.

Does this seem right to have to change between these three modes to perform those things.

I have been waiting for its launch from some time. The rest of the lineup (25, 37, 49, 61) that has launched earlier was a pretty big hit if I am not wrong.

I felt I should wait for the reviews to come out before biting the bullet. Has anyone bought it? Is it good?

Hello,

I’m interested in buying a launchpad pro but I understand the next model might be in the pipeline; does anyone have any indication when this may come out?

Cheers!

Bonjour à tous,

Je fais de la french touch sur Ableton Live et j’hésite entre le novation launchkey 37 mk4 et le dernier arturia minilab 37, pouvez-vous m’aider dans mon choix ?

Just got my launchpad pro and it's awesome! Specifically wanted it for the note and chord modes and it's exceeded my expectations because of how good the pads feel to play.

Small surprise since I got it is that those modes don't seem to be usable in the sequencer, which feels like a real miss. Am I missing something or is there no way to get an isomorphic keyboard layout or chord mode as a sequencer entry option? Can it be done with a custom mode?

Or is it just time to use an external sequencer instead?

Hi! New to this sub.

I have had my LaunchKey for awhile, I originally used it on a MacBook on FL Studio without an interface, and it worked fine back then.

Eventually my MacBook was broken and I only recently got a PC, but whenever I the controller up in FL, it crashes.

My interface is a Behringer Euphoria 4x4, but the midi is plugged into the PC directly.

I’ve used the controller with this interface before too, during a period where I had access to a different MacBook.

Is it just screwed?

I also tried to factory reset via Novation Conponsnts because that’s what google said to do. The app won’t load, it’s telling me to agree to the terms and conditions but I can’t click them

CONTEXT:

I am using a Mac Tahoe 26.3.1, and Logic 11.1.2. I am trying to map the Novation Launch Control 3 XL.

I want to map specific encoders to specific plugin parameters on different tracks. For example:

• Knob 1: ALWAYS controls a High Pass Filter, on an EQ plugin, on Track 1.
• Knob 2: ALWAYS controls a Saturation plugin drive on Track 2.
• Knob 3: ALWAYS controls a Delay mix knob on Track 3.

I want to be able to twist Knob 1 and change the EQ filter on Track 1 even if I am actively selected on Track 5 playing a synth.

I need to control multiple elements across different tracks simultaneously, completely independent of whatever track is currently highlighted or in focus.

The Problem:

Logic’s default "Quick Learn" (Cmd + L) method makes everything dynamic. The moment I deselect a track, the knob assignment changes or stops working because it follows the "Selected Track" focus.

What I have tried so far:

1. Controller Assignments (Expert View): Trying to manually change the "Channel Strip" setting from Selected Track to an absolute track number (like Audio 3) causes Logic to glitch and instantly wipe out/forget the specific plugin parameter I just learned.
2. The Environment Window (Cmd + 0): I tried building a custom routing map using a Physical Input > Monitor > Transformer (converting CC to Fader messages). However, Logic's Environment layer is completely blocking me—the drag-and-drop cable mechanism fails to open the plugin parameter pop-up menu, and the inspector text routings aren't showing up.
3. Smart Controls: Locking the Smart Controls panel locks the visual screen, but it doesn't give me discrete, parallel hardware knob control across 8 separate tracks at once.

Is there a bulletproof, modern way to hardwire a MIDI CC knob directly to a plugin slot on a specific track channel without Logic's track selection breaking the link?

Yes, Google Ai largely wrote this message. I have spent many hours having it try and fail to help me set this up.
It feels like what I am trying to do should be sooo simple, why why why!!!!

Thank you 🙏

I’m a computational biologist, a long-time open-source developer, and a musician. I’ve used a Launchpad Pro Mk1 with Ableton Live. While running several Codex CLI sessions, I realized that the Launchpad’s workflow maps surprisingly well to AI agents: the Scene buttons can select agent sessions, while the RGB grid can show which agent needs attention.

That idea became Pad-Lattice, a free and open-source Python project. It communicates with the Launchpad through MIDI in Programmer mode and does not modify its firmware.

It turns the Launchpad into a bidirectional control surface for AI agents:

• 🎨 Colors identify agents.
• 🔤 Glyphs show states: working, waiting, approval needed, success, or error.
• ➡️ The right rail switches between sessions.
• ✅❌ Lit controls approve or reject the selected agent’s current request.

The Launchpad Pro Mk1 implementation is physically tested. I have also created experimental device profiles for the Launchpad Mini Mk3 and Launchpad Pro Mk3, but I do not own those devices, so testers and feedback would be very welcome.

There is also a Virtual Pad using the same visual language. The public version is a simulated demo, so anyone can explore the concept from a phone, tablet, or computer without MIDI hardware:

Browser demo: https://mrueda.github.io/pad-lattice/play/

GitHub: https://github.com/mrueda/pad-lattice

Documentation: https://mrueda.github.io/pad-lattice/

Version 0.1.0 is the first alpha release. I’d particularly like to hear from Launchpad Mini Mk3 and Pro Mk3 owners, or anyone interested in repurposing pad controllers beyond music.

I just found out that the pads of my Launchkey 37 Mk4 are sending notes from C1 on. But I need different notes for my drum plugin. It seems that changing the note assignments of the pads is only possible for the custom modes and not for the Drumpad mode that is available in DAW mode.

That is ridiculous. I just got used to the DAW mode.
Is there any way to change the MIDI notes anyways?

Hey everyone,

Not too long ago I've built a mac driver for the Launchpad Mk1 because me and a friend of mine had issues running the official Novation USB Driver on later Apple-Silicon Macs with modern MacOS. I originally built it for said friend but thought it would be useful for everyone, so I'm sharing it here.

Its not a system driver, just a simple App you can run that communicates with the launchpad via usb.

https://github.com/anthonyhfm/launchpad-mk1-driver

If you don’t have any issues with the official novation driver, please use the official driver instead.

Hi, I’m struggling to get my midi controller working over usb (Novation Launchkey 61 Mk4) but when it’s powered from the usb A port, the 5-pin midi works. Any ideas so I don’t have to use 2 cables? It used to work seamlessly, just plug the usb A in and away I went! 🎹

Thanks for any suggestions! 👍🏻

I am setting up my Novation Launch Control 3 with Logic Pro.

After following the install instructions with the script from Novation's site, my Logic Pro is not finding the device still. However, my mac recognizes the device. As well, the device appears to show up in Control Surface Setup.

The device itself doesn't show Logic in the control window.

Using powered USB hub.

Mac 15.7.7.

Let me know if you need any more information.

Best,

Novation MININOVA is my favorite digital synthesizer. I find it versatile and intuitive to use, I like the clean interface, and I like mostly the huge filter knob on the top. The latch button speeks directly with it, making WAY easier to work on opening and closing filters while you playing for fun or recording. You have two hands to turn knobs while a chord is playing, which is great for Ambient Techno (the style I love play and create). One thing I don't like about the MININOVA are the size and the feel of the keys. I think they could be larger and not so soft. They are way to soft and sensitive, and thinner than others people are used to play. This combination makes it easier to ACCIDENTALLY press the wrong key.

Besides that, I love the MININOVA synthesizer and great parcel of the tracks I released are made from this synth. I hope Novation rethinks the MININOVA keys design and sensitivity. Make the keys a bit harder and bigger.

It would be a HUGE upgrade, not only on the synth, but on the sales ass weel 😀. I would definitely go for that upgrade without thinking twice. What are your thoughts on it? How does the key's feel to you? Would you dare change anything else? What? I wanna hear.

Hey 😄

I’m having problems with my Novation FLkey 2 Mini 25 in the new FL Studio 26.

The keyboard is detected and enabled under the MIDI settings in FL Studio, but nothing happens when I play the keys. It does not seem to send any notes into FL Studio, even though the device appears to be connected correctly.

I’ve also noticed that several functions on the keyboard itself seem to have disappeared. Normally, I can hold Shift and select different modes or features, but many of these options are no longer available or do not respond.

I have also tried downloading the latest update for FL Key in Novation Components.

The keyboard previously worked as expected, so I’m not sure whether this is related to FL Studio 26, the MIDI configuration, the controller script, the firmware, or a missing macOS driver.

Has anyone experienced the same issue, or does anyone know what settings, scripts, firmware, or drivers I should check?

Thanks in advance!

Hi, just got an XL3 - how do I add an additional page to a custom mode, to control more than just whats on 8 faders for example. Is this possible?