#379

I’ll go ahead and start from! I did find this in my search for more info related to programmers mode and the LPPmk3 in the following PDF. Not much usage to me as of yet, but for future use.

#380

@lylem kindly helped out with this when I was running buoys with just one Launchpad Mini Mk3, allowing the 4 keys needed to load samples to be moved to somewhere more convenient for midigrid:

2 Likes
#381

dude…nice… :+1: worked a treat!

1 Like
#382

Installed a fresh version of this from your fork and I’ve added the name to the supported_devices.lua and sent that over to norns. Attempted to boot up the midigrid tests (LED/device test) on there with no luck at all. Just getting “no script information”. Norns is receiving the midi signals so it’s just that I have no clue what to do from here. Not sure how to exactly “call” other libraries into scripts. Scripting is very new territory so bear with me as I get used to some of this…ELI5 level sometimes. Midi device name is “Launchpad Pro MK3 1” which transmits midi in both session mode and programmers mode.

The LPP mk3 has 2 other midi channels (it has 2 midi cv outs and 1 midi cv in). Here are some diagrams from the pdf I found relating to CC values and LED color values (in decimal and hex values). Source

The CC values in both decimal and hex.

LPPmk3 CC Information
LPPmk3 CC Information1183×598 121 KB

LED colors in decimal.

LPPmk3 Color Palette Decimal
LPPmk3 Color Palette Decimal864×432 66.7 KB

LED colors in hex

LPPmk3 Color Palette Hex
LPPmk3 Color Palette Hex864×432 64.5 KB

#383

The note and cc values are mostly the standard launchpad layout (except for the left side and bottom buttons), the colour map is also the same and It does look like the MK3 pro still uses the same midi implementation…

Is there a “Launchpad Pro MK3 2” and have you tried to use that?

If you get the test to work then look at Helen and Bluerose’s posts on how to modify scripts to load midigrid.

#384

No midi values are transmitted via that device when in programmer mode and that device selected in norns. While in session mode or programmer mode, midi ccs are transmitted on Launchpad Pro MK3 1. Test scripts just say no script available when loading… :sweat_smile::sweat_smile:

New to monome, and monome + modular: ask questions here
#385

Discovering the norns after working with the Zoia for a few years, I’ve finally learned what this quirky, welcoming forum is really about. I’ve lurked here for ages without knowing. Now I’m awaiting a Shield and a few cases and wondering if any of the many gridded controllers that have perhaps copied the grid can be used in its place. Said grid looks to be out of stock at monome, so I’m wondering about alternatives (Launchpads being an obvious but not exclusive example).

I’m one of those old-school foonts with a composition degree who is still addicted to music paper, so I’m excited to inject as much chance into through-composed tracks as my feeble psyche can tolerate.

(It’s a tad humbling to introduce myself in the wake of Mr. Devine, whose work I’ve savored for over a decade!)

1 Like
New to monome, and monome + modular: ask questions here
#386

you’re in luck. there’s an exact thread for just that! Norns: alternative grids - #384 by Cubeinthebox

1 Like
#387

Thanks so much for the link!

#388

no problem. it is also worth looking at this thread: DIY monome compatible grid w/ Adafruit NeoTrellis. this is sort of the ‘shield’ version of the grid. HOWEVER afaik you have to souce everything yourself. I built one with no issues with some diy experience. It is obviously not as nice as an actual grid, but it can get pretty damn close. Including a case, mine cost around 180 usd.

2 Likes
#389

Thanks again.

I find the DIY version of the grid to be beautiful and the work that went into designing and building it inspiring. I suck desiccated gnu forelegs when it comes to realizing projects like that (let alone the scripting), but perhaps reading about it will bring me closer to action.

I admire that laser-cut acrylic case. I’d love to see a translucent version; perhaps I will later in the thread.

1 Like
#390

@Cubeinthebox Not sure if you saw my post, but I got the Launchpad Pro mk3 running with midi grid.

You need to edit supported_devices.lua and paste the following line (after line 6)
{ midi_base_name= 'launchpad pro mk3', device_type='launchpad_promk3' },

Then duplicate launchpad_minimk3.lua (in the devices folder) and rename it launchpad_promk3.lua
You can open it and replace line 41 with launchpad.device_name = 'launchpad_promk3'

Now all you need to do is add local grid = include "midigrid/lib/midigrid" to your scripts, and set your Launchpad to programmer mode.
I tested it on Awake, Arcologies, mlr64, Zellen and a few other scripts.

Hope that’ll help!

4 Likes
[cheat codes 2] (rev 210208: macros, transport, midigrid, midi config, w/syn, even more stuff)
#391

I did not, this thread has got a lot of launchpad mk3 going on in it! Thank you, @MentalSandal I’ll be trying this later today!

How did you settle on the name launchpad pro mk3 vs the reported names like Launchpad Pro MK3 1?

#392

Great question, the honest answer is : purely out of luck! :wink:
I read that the Mini mk3 was showing up as Launchpad Mini MK3 1, so I tried the same name formatting, since both devices have a similar note/CC layout.

Now a better answer would be :
When you look at supported_devices.lua, line 33 :

midi_device.name contains ‘Launchpad Pro MK3 1’ because of a midi.devices() query in midigrid.lua . See this doc for more info
So this line is converting our string to lowercase, and if ‘launchpad pro mk3 1’ matches one of the midi_base_name values plus any digit (because of %d), then it returns device_type .

This is why this extra line comes in handy :
{ midi_base_name= 'launchpad pro mk3', device_type='launchpad_promk3' },

As you can see, it’s essentially saying : “if the device shows up as ‘Launchpad Pro Mk3 1’, let’s reference it as launchpad_promk3 from now on.”

A least that’s how I understand it, @JaggedNZ or anyone, do let me know if I’m talking rubbish!

Hope that will help!

2 Likes
#393

Thank you, logically that all makes sense and thank you for the additional references! I’m going to take a look at some of the studies to get some more bearing on the scripts that norns utilizes.

Would this be in the opening of a script where it details pulling a grid or other midi info?

#394

I’ll try fold these changes back into the code when I get a chance. :slight_smile:

4 Likes
#395

I’ve gotten awake and a couple of the other scripts you mentioned working correctly with the LPPmk3, well as much as I can tell with some that I need to read more into! Thank you for the help!!

1 Like
#396

@JaggedNZ I’ve tested the master branch of your repo with two LP mini Mk3. Also with an older LP mini, and an APC mini.

I’ve created a PR on your repo with a fix for two LP mini Mk3 setup.

I copied log output into the PR so you can see what the change does.

I haven’t started looking at any sysex changes to the code yet to set an LP mini Mk3 into programmer mode automatically.

3 Likes
#397

OK - here is what I see:

For the Launchpad Mini Mk2 (when plugged in separately): Launchpad Mini
For the Launchpad Mk2 (when plugged in separately): Launchpad MK2

No change when both are plugged in at the same time :).

Thanks again!

#398

Note: You can optionally set a hardware ID to a value in the range 1-16 on older launchpad mini models. This ID gets appended to the midi device name.

For example, when you have set the hardware ID to 4 then this appears as midi_device.name: Launchpad Mini 4

I’ve added code to match on that in the PR JaggedNZ’s merged to the master branch of jaggednz/midigrid:

 if string.lower(midi_device.name):find 'launchpad mini %d' then
    return 'launchpad'