#141

Thanks. Now it is attempting to find my device and and is not finding apcmini. No bother, I will figure it out, and thanks for your work on this. Maybe I will just buy a used launchpad.

#142

Ohā€¦ now you tell me :laughing:

I just submitted a PR on midigrid.lua. Suppose Iā€™ll have to go look at mg.lua instead.

is that supposed to be mg_128.lua? If so - does it matter if my device is only a 64?

EDIT - looks like my PR would still stand on mg_128 - same issue exists there.

Also - first draft of block_config.lua (2.0 KB)

#143

Sorry, I really shouldā€™ve waited until I renamed everything before posting. Thatā€™ll teach me for posting late at night.

mg_128 just got a lot shorter.

1 Like
#144

Iā€™m on freenode irc #monome and will be coding on and off for the next few hours hopefully. Donā€™t know if there is a better place to hang out and chat code?

#145

This is awsome. :grinning: how do i do this, i have 2 launchpad minis when i put this in Awake:-

local grid = include(ā€˜midigrid/lib/mg_128ā€™)
g = grid.connect()

its still only an 8x8 grid with no left right quadrant pages option?

#146

I still need to resolve a few more issues and I will post detailed instructions. Might be a few days yet.

4 Likes
#147

JaggedNZ Thank you for the revision to this code. Finally got it to work on my APC Mini after hacking around for awhile. Found an extra comma at at the end of line 3 of the apc_mini file in devices :grinning:

#148

@JaggedNZ Iā€™m running this on a single launchpad mini and it works until I press any of the four top right buttons at which stage it starts giving the following error after each keypressā€¦

/home/we/dust/code/midigrid/lib/vgrid.lua:101: attempt to index a nil value (field '?')

stack traceback:

/home/we/dust/code/midigrid/lib/vgrid.lua:101: in method '_handle_grid_key'
/home/we/dust/code/midigrid/lib/vgrid.lua:87: in field '_key_callback'
/home/we/dust/code/midigrid/lib/devices/generic_device.lua:86: in field 'event'
/home/we/dust/code/midigrid/lib/vgrid.lua:84: in field 'event'
/home/we/norns/lua/core/midi.lua:396: in function </home/we/norns/lua/core/midi.lua:391> </code>
#149

I have a branch that almost has the page switching (top right button) almost working. There is also a bug that causes buttons in the first column to light randomly.

Really keen to get it out but my health and work have been conspiring against me.

1 Like
#150

Look after yourself. The flashing lights can wait.

1 Like
#151

Hi, has anyone tried with a launchpad X or even the new launchpad pro mk3? using the configurations for the old launchpad does not seem to work

#152

I managed to get the Launchpad X to work, but in some scripts I have some problems.
For example in takt thereā€™s an error when calling all relatied to the brightness_handler:

lua: /home/we/dust/code/midigrid/lib/mg_256.lua:236: attempt to call a nil value (global 
'brightness_handler')
stack traceback:
     /home/we/dust/code/midigrid/lib/mg_256.lua:236: in method 'all'
     /home/we/dust/code/takt/takt.lua:1218: in method 'redraw'
     /home/we/dust/code/takt/takt.lua:901: in field 'event'
    /home/we/norns/lua/core/metro.lua:169: in function 
    </home/we/norns/lua/core/metro.lua:166>
1 Like
#153

has anyone gotten shfts or cheatcodes working for a launchpad (pro)? shfts displays grid functions on the lpp, but i donā€™t know how to page over to the 2nd screen. may be missing something there because it does kind of work.

Cheat Codes doesnt show any display on my launchpad. it responds to the controller though, so i guess thatā€™s maybe the best i can hope for. I have:

-- local config = include('midigrid/config/launchpadpro_config') local grid = include('midigrid/lib/midigrid') local g = grid.connect()

on line 1393

*sorry for all of the launchpad specific posts. i know i just need to buckle down and get myself a grid. until then im stuck using this thing

#154

Iā€™ve gotten as far as getting the leds to show on start up using the implementation listed in the wiki. But it wont update past the inital display. The dev uses a custom lib to do the ui for girds which i think is the issue.

2 Likes
#155

Hi @encephalitislethargi, this is not Cheat Codes related but I have a LPro (original) and I wanted to check if you are happy to share a basic workflow to get it working with midigrid and norns, as I found the instructions on GitHub a bit cryptic.

The issue I am having is that I get Error: no device found whatever device name I add on line 126 of config/launchpadpro_config.lua. Currently my fates devices menu displays three Launchpad Pro devices formatted as the following:

  • Launchpad Pro 16 1
  • Launchpad Pro 16 2
  • Launchpad Pro 16 3

Any ideas?

Thanks

#156

Iā€™m away from my setup for the day but Iā€™ll try. Iā€™m pretty sure you donā€™t have to edit the config file at all. Just make sure the midi grid folder is in your dust scripts directory then in whatever script you want to use it with, add:

ā€“ local config = include(ā€˜midigrid/config/launchpadpro_configā€™) local grid = include(ā€˜midigrid/lib/midigridā€™) local g = grid.connect()

(Without the line break between the first ā€œ=ā€œ and ā€œincludeā€)

Usually near the top of the code in maiden. I have specific examples that I can send you tomorrow morning but see if you can try that for now. So in mlr, just add those 3 lines near the top of the mlr.lua script and it will tell that script to point to that midigrid script

Like this:

Working MLR64 Script Code for Launchpad Pro
Working MLR64 Script Code for Launchpad Pro1573Ɨ752 44.3 KB

If you are using mlr though, grab the mlr64 version and same for less concepts

You shouldnā€™t have to even assign the launchpad as a midi device. With this code, it should replace the ā€œgridā€ device, which is itā€™s own controller category

I might be forgetting something but if youā€™re still having trouble tomorrow just message me and Iā€™ll figure it out. Donā€™t forget to put your launchpad into programmer mode too: setup button + orange top pad

2 Likes
#157

Thanks for your instructions :raised_hands: this is now working!

The issue I had was that my fates was giving the wrong name to the device as ā€œLaunchpad Pro 16 1ā€. I reset the firmware of the LPro and now it shows as ā€œLaunchpad Proā€, so I was able then to configure it correctly.

1 Like
#158

Has anyone ever gotten the page toggle ā€œtop 2 auxiliary buttonsā€ from the github instructions to work for the launchpad pro? I assume it means the top right (play symbols) that function as beat length or scene launch in ableton, but those have never done anything in any script Iā€™ve used. I think the only one I was ever able to toggle pages at all was mlr with the upper-left most pads on the grid

#159

If you mean to switch between two pages in 128 setup, you need to press the top left button outside the 8x8 grid (the page up and down, next to the setup button)

#160

This works for you? It Always seems to just switch back from programmer mode to note mode when I push those