#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

#161

It doesn’t on mine. It works very well with scripts such as Awake for example.

#162

So, good misters, wich is the best option as an alternative of Grid so far? I mean, wich one is the easist to make it works pretty flawlessly with a Norns shield?

Thanks in a advance for your input! :slight_smile:

1 Like
#163

TouchOSC on a tablet for some scripts is the most immediate solution I’ve found.
Specially Cheat_Codes, the layout works beautifully.

1 Like
#164

Are you using @okyeron’s lua script for this?

I’ve been meaning to try it out.

#165

Cheat Codes has its own dedicated TouchOSC template.

The oscgrid stuff above is very experimental and will likely cause problems - if you use it be sure to unload the script afterwards.

2 Likes
#166

I have one of the original 40h monome grids and would like to use with Norns - but can’t get it to work on Norns. The default buttons lights up when the usb plugged in but when i start any script, it just goes blank. Is there any firmware updates on the 40h that are required? It would be good to work with MLR - i tried the 64 MLR Norns patch but it didn’t work. Zellen i was told should work with a 64, but no joy also.

#167

You could try my grid-test script to test various grid functions.

Loom is a good test too as I believe it looks at grid dimensions

Edit: it could be the 40h is pulling too much power? Check console for under voltage warnings?

1 Like
#168

hi all, op of the script here who has been mia for a really long time… long story! but I am back, and have been working through this again, and realize now that I should be working through this whole discussion too! I’ve just been off of lines and unemployed and stuff (before the virus, now I actually have a job weirdly), and hadn’t really realized people were working on this! I have a fork I have been working on I think I am about to merge (after looking at the prs)

What I have done on my branch (apc_dev, but its more than that) is made a core.lua file that handles has all the device management and common connection stuff, which passes on the half formed midigrid object to any number of “view” files.

the midigrid.lua file/lib is for straight conversion of midi to led, based on the config file. It wouldn’t make sense to do a, e.g., midigrid.init(128), to a generic midigrid, because I think we should leave the possibility open of there being native 128 button midigrids, and because of this, that init argument is confusing: are we talking about the grid itself, or the emulation?

emulation should still be separate files, but we shouldn’t talk about “quads” anymore in those files, although I have left the config options the same. we should simply say that mg_128.lua has a 128 grid buffer, with two separate “views”, and mg_256 is a 256 buffer with four views on it. But, the catch can be, the views of the buffer can easily be arbitrary, and one can make versions like a three view cheatcodes version. there is still some stuff to be hammered out, on my end, but I will look at all this other work and synthesize and we can figure out the right master branch.

really sorry I haven’t been around to discuss and troubleshoot and pr receive! great to see this so active.

1 Like
#169

Hi beepboop, have you looked at my current development / rewrite? ( here: https://github.com/jaggednz/midigrid/tree/vgrid_wip )

I’ve created a virtual grid buffer and abstracted the device away from it. This allows for things like multi devices (i.e. I use two launchpad mini’s as a 128 grid)
It still has some bugs (mostly LED’s lighting when they should not, might be a device / midi layer issue) and I still have to implement support for the current set of devices, which is why I have not PR’s yet.

Keen to chat about where to take all this… I could really use a hand with what I’m working on as I find I don’t have much energy to hack on this after working from home all day, so I’ve been finishing other hardware projects.

2 Likes
#170

Thanks, I tried the grid test script and it works ok
I tried Loom and that works fine with clear lights.
Zellen script i can only see barely flickering lights, the same with mlr64.
Not sure if its the brightness or the ON/OFF rate that is causing it.
Both apps work, but the script code settings, needs to match whatever is being done in Loom.

this is the mlr64 and not sure of the z numbers.

v.gridredraw[vREC] = function()
g:all(0)
g:led(2,focus+1,15)
for i=1,TRACKS do
local y = i+1
g:led(1,y,3)–rec
if track[i].rec == 1 then g:led(1,y,9) end
if track[i].tempo_map == 1 then g:led(3,y,15) end – tempo.map
g:led(4,y,3)–rev
g:led(8,y,3)–stop
g:led(6,y,3)–speed=1
g:led(6+track[i].speed,y,9)
if track[i].rev == 1 then g:led(4,y,15) end
if track[i].play == 1 then g:led(8,y,15) end
end
gridredraw_nav()
g:refresh();

#171

Could be brightness - I think on monobright grids, anything over brightness 7 is on and under is off?

So you could try changing g:led(4,y,3) to g:led(4,y,8) for rev and see if that shows up? (and then modify the various LED calls to suit your needs)

1 Like
#172

no, as far as the norns software stack is concerned, 40h should work totally fine. norns uses the same library as serialosc to manage device protocols. (does the device work with serialosc on other systems?)

of course as noted it is a monobright grid. levels 0-7 are “off”, 8-15 are “on.”

my guess is that the 40h can’t handle the refresh rate these scripts are running. this is one aspect that was greatly improved by later editions.

the refresh rate in MLR is set by this line (and TBH seems a bit overkill to me at 50hz anyways)
{ https://github.com/tehn/mlr/blob/master/mlr.lua#L457 }

#173

hey wow that’s looking like a good direction, and 64 led output works out of the box for me on my apc! I am going to look at this.

tbh the two launchpads or whatever as one 128 grid is a use case I hadn’t actually considered a lot… but it looks like if we want that, a separate vgrid thing like you have done is the sensible solution, but also changes a lot of things up.

I have pulled out your code and am working on a branch of it now, going to see if I can get it all working for me and be back.

for those who want to try a small update for better 128 grid emulation of the original library, please test the apc_dev branch of the original repo and tell me if it works!

1 Like
#174

I own a Synthstrom Deluge, which has 128 pads, and I think it would be a fantastic Grid alternative. Every pad can show a lot of different colours, and even intensities.
Do you think I could use the Deluge as an alternative grid?

1 Like
#175

beepboop

Thanks for having the time to work on this again. Tested and works following reset. When I switch between things sometimes I get an “ERROR (i2c/hp) failed to write.” Also for your lower quadrants try 88 and 89. Works for me.

#176

So I’m pretty new to all this, but I’ve got the midigrid folder in dust/scripts and now I need to edit the files.
I’m just not sure what I edit? I’ve opened the lua, but I don’t know what to change.
I’m using a launchpad mini.
Can anyone give me a very layman explanation?
Thanks!!

#177

On the git hub wiki there is a guide that tells you exactly what to edit for each script

1 Like
#178

Yeah, so I’ve followed that but it’s quite vague, I pasted in the provided line but it doesn’t work.
Is there a specific spot I have to paste the line into?