#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'
#399

Interesting - thanks!

Do you know if the same applies to the Launchpad Mk2? As I mentioned, I currently have both a Mini Mk2 and a standard Mk2, and am debating whether to buy an additional mini or standard to give me a consistent grid of 128 pads. I am leaning toward a second standard Mk2 (the lights are nicer), but want to make sure that the Norns can see both of the standard devices and that midigrid can be edited to run them as a single set of 128 pads (as I understand has been done for the Mini Mk3).

#400

@delineator btw your PR is merged but I have not tested on my setup. Not sure if launchpad mini mk1 devices are working, I will try test and update here in the next few days.

I think I have the launchpad mk1 and mk2 all mixed up, it looks like the implementations are almost identical, potentially only the device name is slightly different. I think I should be able to cover launchpad mk1, mini mk1, mk2 and mini mk2 with the same configuration.
I just need to tweak the supported device list slightly and we should be good.

@bharris22 pick what you think works for you best, support is based of what devices people have to test with …and I have two lp mini mk1’s (At least I think they are mk1’s :confounded:)

Ps. Allergy shots suck :face_with_head_bandage:

#401

Excellent - thanks @JaggedNZ ! Hope to have a second Mk2 on the way shortly :).

#402

Have you had any issues with random led lights? This can easily be seen on awake at high BPM, but might only be a mk1 issue (suspect Linux driver issue)

#403

Hi @JaggedNZ - if this is a question for me, I have not yet tried using my Mk2 with Norns at all yet. I will try to install minigrid this week and let you know. Do I need to wait for you to make any adjustments to the code first based upon the device ID I posted? Once I get the second Mk2 and identify its device ID, then the code can be added for the two Launchpad Mk2 setup (i.e., 128 pads), correct?

Sorry again for the questions and imprecise terminology - still very new to this.

Thanks as always!

#404

Ugh sorry I’m beginning to realise how much the notation LP model naming is a complete mess …

It looks like the launchpad MK2 is similar feature wise to the launchpad mini MK3. The launchpad mini mk1 & 2 should work about the same?!?

I will advise when I think I have something that should work. Shouldn’t take much work luckily.

#405

Excellent - thanks!

Once you let me know it’s ready, I will try my Launchpad Mk2 and Launchpad Mini Mk2 individually with the 64 pad version of minigrid. Once that works correctly, and I get my second Mk2, I can test the 128 pad version.

#406

Just received two LP mini mk3s today and super happy how everything is working! @Helen’s instructions are great, just need to change the reference to mg_128. Special thank you to @JaggedNZ and the genius who made sure the two LPs could line up without the black row of buttons interrupting the ‘grid plane’.

I even took a few minutes to change to a custom blue palette (can share once I’ve honed it more. To edit one yourself, reference the Launchpad programmers reference and look at the brightness_map in launchpad mk3 device file). Not sure it’s a perfect gradient but seems to work well enough.

I am getting occasional random buttons lighting up with colors outside of the ‘brightness map palette’ on a few scripts I tried (awake-mod, initenere, arcologies), but they are actually kind of charming. Arcologies is absolutely mind blowing.

3 Likes
#407

Glad to hear you’re happy with your two LP mini mk3 setup. I have the same setup - and added that code for rotating the 2nd device to not interrupt the ‘grid plane’. :blush:

I also added that LP mini mk3 ‘brightness map palette’ using the mk3’s predefined RGB colours. There’s a way via sysex to set custom RGB values on the mk3. At some point we could add that to define a palette with brightness in a single hue - e.g. emulate the monome grid button hue.

@bharris22 Once you get your second LP mini mk2 for testing, it would be possible to test altering midigrid to rotate the 2nd LP mini mk2 device grid to not have the ‘grid plane’ interrupted by the function buttons. Like we do for the LP mini mk3.

1 Like
#408

Excellent - thank you! Just to be clear, and I’m not sure it matters for this limited portion of the discussion, I will actually have two LP Mk2s, not two LM Mini Mk2s. This is the one I will have two of:

image
image677×673 146 KB

I do also have a LP Mini Mk2, shown below, but only have one of these (which I am happy to test once @JaggedNZ advises that he has made the changes to the main midigrid script).

image

#409

has anyone had any luck using midigrid with a launchpad s? is it supported or not? i’m trying to set it up with the new version of cheat codes, but no luck so far. the launchpad appears under midi devices and is connected fine, and i’ve successfully installed midigrid and gone through the steps to activate midigrid in cheat codes. restarted norns and tried different usb ports. kind of lost what to try next, so any help would be greatly appreciated!

#410

just to confirm whether it’s the device or the script – how do you fare using helen’s instructions above with awake?

1 Like
#411

seems to be the device. editing awake.lua following helen’s instructions unfortunately doesn’t work either.

just looked through the midigrid library files, and there’s even a supported_devices.lua file that does not mention launchpad s – so i guess that’s it!
i’ll try to make sense of midigrid and see if i can add support for the s. it should technically be possible: it has 16 variable colours, and setting midi output from any script to the launchpad s gives me visual feedback on the pad for outgoing notes. comparing the midigrid scripts for different devices in combination with novation’s programmer reference for the s and already supported versions might get me there : )

#412

Past reports indicate that the launchpad S did not work with earlier versions of midigrid, this is likely due to the slower speed of the device. However my version reimplements some “buffering” that should allow some scripts (like awake) to work.

If you have even the most basic inclination towards editing scripts then please try add you device to supported_devices.lua with the default launchpad configuration and test.

@delineator @bharris22 I do have ideas regarding a more generalised rotation of second devices… main thing I need to sort out is how to deal with the rotation of the edge buttons.

1 Like
#413

I did all this steps but my MK3 does not seem to light up in any way in Awake. Is there anything i’m missing?

#414

hey that was a lot easier than i feared!
i simply added { midi_base_name= 'launchpad s', device_type='launchpad' }, to supported_devices.lua and changed row 52 in lauchpad.lua to launchpad.device_name = 'launchpad s' – and it works! got awake running smoothly now, thanks!
now over to try cheat codes : )

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

Do you see any errors in Maiden when launching Awake with your LPP plugged in?

#416

No errors, i have 3 devices in my midi devices Launchpad pro mk 3 1/2/3, is it ok?

#417

So small correction, for Launchpad pro mk3 to work the device should be
{ midi_base_name= ‘launchpad pro mk3 1’, device_type=‘launchpad_promk3’ },
in supported_devices.lua

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