Launchpad Mini MK2: Colors not changing on linux

[rrrnld]

I can't seem to set the colors of the buttons after initializing the launchpad. I have also tried to send the MIDI messages directly from SuperCollider using the encoding described in the Programmer's Manual, but it doesn't work.

The LEDs are functional: I see them blink when I plug the device in, and I can set them like so:

amidi -p hw:1,0,0 --send-hex='90003C'

Any idea what's going on? I'd be happy to write and send a patch if I knew where to look!

Thanks :)

[madskjeldgaard]

Hi! That's weird. Are you sure you are sending it to the right device?

[rrrnld]

I can set up callbacks and they react to button presses. There's only one MIDIOut for the launchpad, so I'm sure, yes.

[madskjeldgaard]

Okay, thanks. What version of the Launchpad do you use? Mk1 or mk2?

I am testing my Mk1 with Linux tomorrow so I can double check what it's like

[rrrnld]

Oh I always thought it's the MK1, because it doesn't say MK2 anywhere on the packaging or on any sticker. But the packaging and device look like this: https://medias.audiofanzine.com/images/normal/novation-launchpad-mini-mk2-2048247.jpg

Edit: It does say MK2 on the box, above the barcode in the front :)

[rrrnld]

I have managed to make it work with a minimal example, see here for some details:

MIDIClient.init;
~o = MIDIOut.new(1).connect()
~o.noteOn(0x00, 0x00, 0x3c) // light the button at (0,0) in green
// to turn the led off: ~o.noteOn(0x00, 0x00, 0x00)

So the crux is in how MIDIOut is created on Linux I think?

[madskjeldgaard]

Interesting. What does Midi client.init post ? Best regards, Mads Kjeldgaard 🐬 website: madskjeldgaard.dk 🐒 music label: exformal.art 🐸 creative tech: hyaline.systems

…

________________________________ From: rrrnld ***@***.***> Sent: Wednesday, February 12, 2025 10:07:56 PM To: madskjeldgaard/launchpadmini-sc ***@***.***> Cc: Mads Kjeldgaard ***@***.***>; Comment ***@***.***> Subject: Re: [madskjeldgaard/launchpadmini-sc] Launchpad Mini MK2: Colors not changing on linux (Issue #3) I have managed to make it work with a minimal example, see here<https://scsynth.org/t/launchpad-mini-mk2-midi-out/11237/6?u=rrr> for some details: MIDIClient.init; ~o = MIDIOut.new(1).connect() ~o.noteOn(0x00, 0x00, 0x3c) // light the button at (0,0) in green // to turn the led off: ~o.noteOn(0x00, 0x00, 0x00) So the crux is in how MIDIOut is created on Linux I think? — Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFLO64BXIZ2PVLG7PYNIPUL2POZ2ZAVCNFSM6AAAAABWZHLLFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUHA2DMMBSHA>. You are receiving this because you commented.Message ID: ***@***.***> [rrrnld]rrrnld left a comment (madskjeldgaard/launchpadmini-sc#3)<#3 (comment)> I have managed to make it work with a minimal example, see here<https://scsynth.org/t/launchpad-mini-mk2-midi-out/11237/6?u=rrr> for some details: MIDIClient.init; ~o = MIDIOut.new(1).connect() ~o.noteOn(0x00, 0x00, 0x3c) // light the button at (0,0) in green // to turn the led off: ~o.noteOn(0x00, 0x00, 0x00) So the crux is in how MIDIOut is created on Linux I think? — Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFLO64BXIZ2PVLG7PYNIPUL2POZ2ZAVCNFSM6AAAAABWZHLLFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUHA2DMMBSHA>. You are receiving this because you commented.Message ID: ***@***.***>

[rrrnld]

I think that worked by accident. :) There's another reply in the forum thread linked above. MIDIOut.new(1) does not refer to any destination at all.

The correct way to do it (on Linux) is (taken directly from the docs, and tested in SC):

m = MIDIOut(0);  // use virtual source port "out0"
m.connect(1);  // connect to MIDIClient.destinations[1]

This is what MIDIClient.init posts:

MIDI Sources:
	MIDIEndPoint("System", "Timer", 0)
	MIDIEndPoint("System", "Announce", 1)
	MIDIEndPoint("Midi Through", "Midi Through Port-0", 917504)
	MIDIEndPoint("Launchpad Mini", "Launchpad Mini MIDI 1", 1310720)
	MIDIEndPoint("SuperCollider", "out0", 8388620)
	MIDIEndPoint("SuperCollider", "out1", 8388621)
	MIDIEndPoint("SuperCollider", "out2", 8388622)
	MIDIEndPoint("SuperCollider", "out3", 8388623)
	MIDIEndPoint("SuperCollider", "out4", 8388624)
	MIDIEndPoint("SuperCollider", "out5", 8388625)
	MIDIEndPoint("SuperCollider", "out6", 8388626)
	MIDIEndPoint("SuperCollider", "out7", 8388627)
	MIDIEndPoint("SuperCollider", "out8", 8388628)
	MIDIEndPoint("SuperCollider", "out9", 8388629)
	MIDIEndPoint("SuperCollider", "out10", 8388630)
	MIDIEndPoint("SuperCollider", "out11", 8388631)
MIDI Destinations:
	MIDIEndPoint("Midi Through", "Midi Through Port-0", 917504)
	MIDIEndPoint("Launchpad Mini", "Launchpad Mini MIDI 1", 1310720)
	MIDIEndPoint("SuperCollider", "in0", 8388608)
	MIDIEndPoint("SuperCollider", "in1", 8388609)
	MIDIEndPoint("SuperCollider", "in2", 8388610)
	MIDIEndPoint("SuperCollider", "in3", 8388611)
	MIDIEndPoint("SuperCollider", "in4", 8388612)
	MIDIEndPoint("SuperCollider", "in5", 8388613)
	MIDIEndPoint("SuperCollider", "in6", 8388614)
	MIDIEndPoint("SuperCollider", "in7", 8388615)
	MIDIEndPoint("SuperCollider", "in8", 8388616)
	MIDIEndPoint("SuperCollider", "in9", 8388617)
	MIDIEndPoint("SuperCollider", "in10", 8388618)
	MIDIEndPoint("SuperCollider", "in11", 8388619)
-> MIDIClient

[rrrnld]

Note that this may be an upstream issue in supercollider, I have posted a bug report here: supercollider/supercollider#6619