Issues with Launchpad Pro MK3

I have a few issues with the Launchpad Pro MK3. Should I file bugs for those?

  • The up/down keys don’t work at all.
  • Once I press the left/right arrow keys, the scene buttons stop working.
  • Pressing the left/right keys erases all pad LEDs (but if a pad’s clip is currently playing, the pad will turn back on on the next bar).

And some nice to haves:

  • It would be nice if the pads that are currently playing would pulse at the current BPM.
  • It would be nice if pads would automatically be assigned their cue slot’s color.
  • It would be nice if selecting a track with the track buttons (the ones below the pads) would make the track button pulse or blink at the current BPM.
  • The logo in the top right keeps blinking and there’s no way to stop it. It’s a little distracting. Could this be used to make it do something useful? For example, blink at the current BPM when the transport is running?

I understand that Launchpad support is hot off the press, though, so no worries. Thanks for working on this at all. :slight_smile:

I will take a look at these items when I can, but it might be more than a week from now.

Pulsing the pads is intended to indicate “queued”, not “playing”.

The logo blinks in time with the current bpm. All pulsing will be also using the current BPM, if you have Ardour generate MIDI Clock and connect the MIDI Clock output to the launchpad.

Track selection already works with the buttons below the pads.

The pad colors are based on track colors, not slot color. To be honest, I had forgotten that we had per-slot colors … I am not sure if we should use them or the track color.

I will take a look at these items when I can, but it might be more than a week from now.

Like I said, no worries. Thanks for taking a look at all!

Pulsing the pads is intended to indicate “queued”, not “playing”.

Ah, I hadn’t noticed that during testing, thanks.

All pulsing will be also using the current BPM if you have Ardour generate MIDI Clock and connect the MIDI Clock output to the launchpad.

That’s definitely one for the manual.

Track selection already works with the buttons below the pads.

That means I’m not supposed to use the left/right buttons at all?

The pad colors are based on track colors, not slot color. To be honest, I had forgotten that we had per-slot colors … I am not sure if we should use them or the track color.

I propose using track colors for the track buttons (below the pads) and slot colors for pads :slight_smile:

Another bug(?): The logo only blinks in time with the current BPM once I hit Play.

Also, would you consider automatically connecting the MIDI clock to the Launchpad DAW MIDI port? Right now, I have to do that manually on every start of Ardour.

Hm, I don’t know if this is done via MIDI (Beat) Clock, but if it is, then it’s expected behavior I think. The same happens when you connect MIDI clock port to a MIDI keyboard and launch an arpeggiated sequence: unless you actually roll the transport, data will not be transmitted, and the keyboard will use its internal tempo (when set to auto) or remain “silent”, i.e. transmit no MIDI events (when set to external source).