gridkeys mod (now w/ q7 layout, crow & jf outs)

apologies for the docs lag! in the middle of revamping studies – will switch focus next week!
prelim mod usability docs have been made!

this is it – mods were introduced with norns: update 210927 (Sept 27 2021). any previous software versions will not know how to make use of installed mods.

@eigen , until we get docs up, would you want to add update 210927 to the list of requirements in the top post?


20 chars of done-di-doo

1 Like

Yes, thanks @dan_derks! I did an update a week ago and thought I am done but I wasn’t. Just checked for 210706 and it is currently running…

EDIT: Done and working. Thanks again to all of you!

Hi - not sure if this should go here or into the Fall @ambalek script. Installed the mod after installing Fall, but there was an update to Fall to access the grid, however I am now running into an issue with making gridkeys active within Fall, then able to to access a midi device (Plinkysynth in this case). But in that scenario the grid no longer functions for Fall and then going back to deactivate gridkeys doesn’t release it back to the Fall script. Nothing shows up in Maiden as an error, just a standard:
mod - gridkeys - TOGGLE_GRID_KEY = true
mod - gridkeys - TOGGLE_GRID_KEY = false

I can turn it on and off in Icarus and it will function in both sending note information to Icarus and lights on grid work.

Have you tried disabling gridkeys in the mod section of the system menu and restarting?

this sounds like a bug.
i’ll try to reproduce.

EDIT: i cannot reproduce. make sure to use the latest version as it sounds like a bug that could happen before this release.

new big release w/ support for scrollable grid layouts from gridstep.
(kuddos to @Quixotic7 for the original code)

basic mode is still default, go to the params menu to switch to q7 mode.


disabling is fine but it was really only in Fall’s it was happening. Will make sure I have the latest mod as suggested by eigen

Ah ha - two new lua are now in there, Q7GridKeys.lua and grid_utils.lua, so guessing that was the missing ingredients. Been getting odd ‘non-updates’, trying to clear the network lease on IP to see if there are others that aren’t getting proper updates, lease had been set to expire never on my end. Thanks @eigen

1 Like

After I reboot with this mod enabled, I need to select ‘virtual’ in Devices>MIDI right?
I don’t get that option.

Did you actually activate it? Using E3 in SYSTEM>MODS ? Then restart?
Just asking because I thought I was activating it with K3 but you need to use E3/

Cheers, yeah I did, that had bit me before, but I’m seeing the new MOD - GRIDKEYS submenu inside of mx.samples’ settings, so I’m pretty sure it is loaded.

1 Like

that’s weird, this midi device should be selectable no matter what (even without gridkeys).

maybe silly to spell this out, but just to be sure:

SYSTEM > DEVICES > MIDI takes you to a page of 16 of what we call vports which are like slots for devices; each can be assigned to one MIDI device and all assignments are empty by default. selecting a slot with K3 brings up the list of actual MIDI devices which should include virtual.


awesome that was what I needed to know. Still can’t get it to produce sound in mx.synths but that may be something for another thread.

i’ve just added crow and just friends support.

needs some testing as i don’t have any of those devices.


new corrective fix for the detection of “series” monobright grids (thanks to @Clashley1 for the bug report).

this may not work for earlier 40h grids as i’m not sure if they obey the same device id scheme.

1 Like

very curious to try this out! also interested in how this might work with the sines script. sines is just 16 voices droning with a cc volume control. perhaps; for the sines script, a sines version that is simply a regular 16 voice synth would be preferable?

maybe this could be incorporated as an option in the script, for example, use as midi synth [x].


apparently sines already respond to midi notes from the first midi device in the chain!

i don’t remember if it’s only for tuning the selected harmonic or all at once, though. if it’s the former, having a complementary “play” mode would sure be nice!

1 Like

IIRC it’s just for tuning the harmonic. I think a play mode would make most sense. I’m going to look into this :slight_smile:


Replying to a semi-old comment here, but could you implement a bank of sixteen faders by using the bottom two rows with sixteen values based on brightness steps moving from bottom to top and vice versa as values are changed? Thought of this after playing around with some of the controls in granchild and realized it’s probably conceptually possible to have 64 faders on a grid, though I need to work through more of the tutorials to wrap my head around how that might be mapped.