MIDI Data Output Monitoring + Launchpad Mini Mk2 Pad Backlight Issue (Lua)

[ghost]

Hello,

I have a Launchpad Mini Mk2. The MIDI reference document for it is here.

Pre-requisite

The monster.cfg file is: `[backend winmidi] list = on detect = on

[winmidi launchpad] read = Launchpad Mini 16 write = Launchpad Mini 16

[lua lights] script = mapping.lua

[map] lights.set_launchpad_pad{0..1} > launchpad.ch0.note{0..1}`

The mapping.lua file is: output("set_launchpad_pad0",58) output("set_launchpad_pad1",58)

The MIDIMonster.exe command prompt output is: MIDIMonster v0.6 Registered backend artnet Registered backend loopback Registered backend lua Registered backend maweb Registered backend mqtt Registered backend openpixelcontrol Registered backend osc Registered backend rtpmidi Registered backend sacn Registered backend visca Registered backend wininput Registered backend winmidi Reading configuration file monster.cfg Created winmidi instance launchpad Created lua instance lights winmidi Detected 1 input devices winmidi ID 0: Launchpad Mini 16 winmidi Detected 2 output devices winmidi ID 0: Microsoft GS Wavetable Synth winmidi ID 1: Launchpad Mini 16 winmidi Selected input device Launchpad Mini 16 (ID 0) for name Launchpad Mini 16 winmidi Selected output device Launchpad Mini 16 (ID 1 for name Launchpad Mini 16 winmidi Registering 1 descriptor to core core Routing 2 sources, largest bucket has 1 entries winmidi Incoming data on channel launchpad.ch0.note0, value 1.000000 winmidi Incoming data on channel launchpad.ch0.note0, value 0.000000

As can be seen, the incoming MIDI data works perfectly when pressing pad 0.

The issue Upon running MIDIMonster, the correct pads (0 and 1) light up orange on the launchpad. However, according to the Launchpad MIDI reference document, when I send a velocity of 60 (which my Lua code does, I believe) the pad should be green. Furthering this, I can type in any number (0.1, 11, 90, etc.) in place of the 60 in the Lua code and the correct pads still light up orange (which they shouldn't). This is very confusing to me!

To sanity check myself as to what MIDI data I was sending out to the launchpad, I installed a MIDI monitoring tool, MIDIView. This tool can see traffic from the Launchpad to MIDIMonster, but not traffic going from MIDIMonster to the Launchpad (which is what I need to snoop on). I have also tried another MIDI monitor, but I get the same issue of not being able to snoop on MIDI traffic being sent to the Launchpad from MIDIMonster. This brings me to my first question... How can I see exactly what the MIDI data coming from MIDIMonster is to debug?

My second (but less important) question is... Have I misunderstood what I am sending to the Launchpad? I am new to the MIDI protocol.

My third (and final) question is... Why does MIDIMonster report the MIDI data from the Launchpad as coming from channel 0 whereas both MIDI monitors report the data coming in through channel 1 (which is backed up by the Launchpad MIDI reference document).

Any help would be greatly appreciated.