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

[Microwave]

@dan_derks

if you have namesizer installed, cheat codes will use it for collection naming

[DuellingAnts]

Can’t wait to dig in (actually just gone to bed and all I can think of is playing CC)!

[zanderraymond]

i’m completely overwhelmed with excitement. cheat codes seems to grow a new tree ring every dang month at this point. such an important & impactful device – congrats on the new features!

[SPIKE]

holy fracken…i don’t…where to…what the?
WOW!!!

[MatthewAshmore]

Dan now THIS is the spice melange of updates!!!
Thanks so much for the transport goodness and all your hard work.

[edison]

so, i just dunno what to say…
this is an epic update…
they have all been epic! but this macros things is really incredible…
did some live input recording with macro control of everything…
whewwwwwww…
its the most interesting looper i’ve ever touched!
its truly insane, the depths!!!
hotdamn!

[blueroses]

whoa full-on midigrid support is a game changer

[lleicamun]

Today is a good day, much appreciated, thanks!

[Clashley1]

That demo video was so awesome . . .

[bc3]

Midi sync! Thank you!

[mbillz]

I’m being needy at this point but any thought on having synced / quantized looping with w/ delay or w/ tape? would be very cool to have a dual looping system. regardless, this instrument is a work of art in and of itself!

[yoyosandshoes]

So good! Macros are just what I was looking for but was unsure about. The transport sounds like it might fix some undesired sync idiosyncrasies too. Cant wait to dig in. Really the possibilities are extraordinary

[Helen]

@dan_derks

there’s a ton of stuff in this update

…and I can’t wait to try it!

Thank you so much for this amazingly comprehensive update, Dan!

[DoS]

Thanks for an extensive update @dan_derks ! I’ve been waiitng for midigrid support before diving in (being slightly intimidated by the complexity, I must admit), and will do so once I have a good amount of time available to really get to grips with cheat codes. Love the option to switch the LED styles too - really useful with the Launchpads.

I currently have two Launchpad Mini Mk3s set up with midigrid and they work fine as a 128 grid using include "midigrid/lib/midigrid in the relevant place in various scripts (eg awake). With the latest update to cheat codes, setting midigrid? to yes and grid size to 64 works, and the illuminated buttons on one Launchpad are mirrored on the other - pushing buttons on either lights up the same point on both. Switching grid size to 128 freezes both Launchpads until the setting is changed back to 64 and the illuminated buttons remain mirrored on both Launchpads.

I tried changing line 19 of cheat_codes_2.lua from

local grid = util.file_exists(_path.code.."midigrid") and include "midigrid/lib/midigrid" or grid

to

local grid = util.file_exists(_path.code.."midigrid") and include "midigrid/lib/mg_128" or grid

and with grid size set to 64, one Launchpad serves as a single page while the other is blank (as expected). However, when setting grid size to 128, while the two launchpads now light up as one grid, the button placements are off but do seem to respond* when pressed:
:

*I say seem here because I’ve not yet tried getting sound out of it due to time considerations, but that’s the next step.

[2197]

amazing update, cheat codes is very inspirational and powerful!
i also have a question regarding midigrid. will it work with an old launchpad s? i’m trying to set it up but without any success. been reading the alternative grids thread too for help, but can’t figure it out. i’ve sucessfully installed midigrid and restarted norns, flipped midigrid to yes in cc2. the launchpad appears under system - devices - midi, so i know a connection is established. are there any steps i’m missing, or is the launchpad s simply not supported?

EDIT: with some minor tweaks to midigrid, it now works with launchpad s!

[dan_derks]

stoked folks are already digging in!

@DoS

With the latest update to cheat codes, setting midigrid? to yes and grid size to 64 works

awesome, super glad to hear this! the midigrid layer is designed for a single launchpad in 64 mode, so if that’s workin’ then we’re in business

re: 128 with two launchpads, you changed the correct line – the script assumes that the standard midigrid library is installed, but doesn’t look for variants like mg_128. this is because…

@DoS

when setting grid size to 128, while the two launchpads now light up as one grid, the button placements are off

that’s actually just where the split is for the first 64 pads on a standard vertical 128 (unless by button placements you mean pressing a pad doesn’t perform the action associated with the pad). the two launchpad / mg_128 approach isn’t ergonomic for this script, because the gap between the two devices cuts through the second bank. so, for now, i’d recommend sticking with one launchpad and midigrid in 64 config.

@2197

will it work with an old launchpad s?

a quick scan of the alternative grids thread didn’t surface any talk about the launchpad s, so i’m assuming not – it might take a little bit of hacking on the midigrid library, but the device itself might also not support the developer mode that the newer devices do. the folks on that thread have been super helpful, so it might be worthwhile to check in with them

@mbillz

synced / quantized looping with w/ delay or w/ tape?

lol, mayyyyybe? at this point, i’d say there’s some interesting stuff to explore via crow pulses-per-pad triggering teletype control over w/ – but agreed, would be wild

[emho]

Great script update! Looking forward to the workshop end of Feb

One question: is it possible to use a Korg nano kontrol 2 (with monome 256) to map some parameters of the app?

[dan_derks]

@emho

is it possible to use a Korg nano kontrol 2 (with monome 256) to map some parameters of the app?

yeah! absolutely – there are a ton of mappable parameters under the manual control section of the PARAMS, as well as the 8 macros (under the macros section of the PARAMS). i think the new macros system is particularly fun for controlling many parameters at once – once you establish your macros, you can use the built-in norns system mapping mechanism to establish control over these parameters: control + clock - docs

[emho]

Thanks Dan
Will learn how to use the build-in norns system mapping then

[dan_derks]

oh! yeah, you’re in for a treat it’s a really fluid system.

mappings also get saved as you make them, per script, so you’ll not need to do anything special to have those persist across sessions.