Are there any errors in matron? (Find it in maiden)

I just started my Shield (no Launchpad) so this is a screengrab from that:

its not shown up as a device:

Can you unplug Launchpad, then shut down Shield?
Then find a different USB cable for Launchpad, and reconnect to Shield with that.
Then restart Shield.

If it still doesn’t work, try again but use a different USB port on the Shield.

Did you buy the Launchpad new?

no change, tried a different usb-port. i bought it second hand today, i will try with ableton later. maybe its broken?

i`ll report back, thx for help!

hmm. the maiden printouts suggest that the launchpad isn’t being seen by norns as a MIDI device – using the MIDI device section of the docs, i’m curious if the launchpad is available in the SYSTEM > DEVICES > MIDI menu?

1 Like

This must be very annoying for you :face_with_symbols_over_mouth: But thank you for being patient with me as we try to troubleshoot.

What we know and what we have tried so far:
1 The Shield has been working just fine with no other devices connected.
2 Today you edit the awake script and then start up Shield with a used Launchpad Mk2 - The Launchpad doesn’t start correctly.
3 You try again with the Launchpad connected to a different USB port on the Shield, but the Launchpad problem remains.

I think it would be useful to connect the two devices with a different USB cable - then we would know if the problem is with the cable.

But, if you have Ableton, it is a good idea to see if the Launchpad works correctly with that, also.

I don’t know anything about the Launchpad, but you say it flashes lights on starting, which makes me think the Shield and Launchpad are communicating. If the Launchpad was truly ā€œdeadā€, then I think nothing at all would happen with it. But I am no expert and I could easily be wrong :frowning:

Please try with Ableton later, and report back, to let us know what you find out.

Good luck!

@dan_derks : it doesnt show up in SYSTEM > DEVICES > MIDI

@helen: i tried different cables & different ports, i`ll try with ableton soon.

thanks for the patience, thx for the advise.
i report back soon.

I have this problem occasionally with one Launchpad Mini Mk3, and it’s due to a dodgy USB-C cable (which i just turn upside-down and it usually - mostly - works). So maybe there is something wrong with the Launchpad?

1 Like

@DoS most probably.
it also doesnt show up under APPLICATIONS>UTILITIES>SYSTEMINFORMATION>USB in my mac os 10.9.5, let alone in my ableton live suite 9. I CAN enter the bootloader mode on the launchpad …
i think i just got fucked up in a second hand buy w/out testing properly.

oh, my. its a monday, isnt it?

Ouf. Not good. Is it possible to do a factory reset, assuming you’ve not done one already?

1 Like

@DoS: yupp, didnt do the trick either. serious bummer. i mean, i have to blame this on myself, literally, BUT how fucked up is it to sell a faulty unit anyway?

2 Likes

Just wanted to hop in here and say thank you to @Helen for the wonderful launchpad work!! I just got my norns shield this weekend and I’m going to be hooking up my Launchpad Pro Mk3 to mess with some things so glad there’s already some headway :slight_smile:!

2 Likes

Does this work with a Launchpad Mk2 or Mini Mk2, as well? If not, I may have to spring for the Mk3.

Thanks in advance!

PS - thank you, @Helen, for the fantastic instructions! I haven’t used them yet, but skimming through it seems like just what this noob needed :).

@JaggedNZ Thanks for the fine script! Having a lot of fun and just barely started. Any chance for Deluge compatibility in the future? Deluge’s grid is 128 pads (8x16) so it would be a killer combo with the Norns.

Cheers and thank you again!

Launchpad mk2 should be supported but it is not fully implemented and I don’t think anyone’s tested it yet? At a minimum if you could commit to testing and let us know the correct midi device name ( note there maybe two devices names for the one device ) then I’m game to finish off what is there.

@Chico unfortunately it looks like the deluge does not expose its grid via midi messages, rather via ā€œclipsā€. Unless someone can advise otherwise I’m not sure it’s possible.

@thmshckr Unfortunately usb connectors, particularly micro and mini are prone to failure from abuse. My second launchpad mini was sold with a bent usb plug, luckily the socket was still in good order. But yeah, selling undisclosed in that state is not good form.

If you get stuck with it then do ask around any DIY electronics minded friends you may have, usb socket replacement is not an uncommon repair. The usb sockets pretty close to some other components on the launchpad though. Btw is the usb cable loose, can you gently wiggle it up and down? (If yes the socket is likely damaged) there might be a hacky fix if it works when you push the plug down…

3 Likes

Thanks - that is a very generous offer! I have both the Mk2 and the Mk2 Mini, and would be happy to help in any way I can (given my limited knowledge and my day job). As an initial matter, how would I determine the midi device name(s)?

Plug in one device ONLY and go to
SYSTEM > DEVICES > MIDI
And tell us exactly what you see, capitalisation matters.

I’m expecting ā€œlaunchpad mk2ā€ and not sure for the mini?

Edit: Then plug in both devices and see if the names have changed? (This should only happen if they both have the same device name)

Tell me both device names and you should be able to use them both as a 128.

@blueroses can you make sure you are using mg_128.lua and not the default midigrid.lua ?

Great - thanks! Will do.

:frowning: … but anyway, Launchpad is awesome as well! Thank very much!

this is what i’ve got for Awake:

this gives me the right hand side of the grid:

but none of the ā€˜outside edge’ pads do anything (except the session button, which still works to access options). Changing the script to midigrid/lib/midigrid gives the left had side of the grid.
I’m wondering if it’s something to do with the way it’s connected as a midi device - still a little confused about the way the Mk3 presents as two midi devices, although I feel like i understand it in principle. In SYSTEM>DEVICES>MIDI i currently have things allocated as

  1. none
  2. Launchpad Mini Mk3 1
  3. Launchpad Mini Mk3 2
  4. none

edit to add: also changing to midigrid.lua results in the ā€˜up’ arrow being lit rather than the down arrow, so it seems like something is being recognised as representing the two halves there, but the key press isn’t recognized :thinking: