[cheat codes 2] (rev 240301 LTS13.2)

hghrlearning · 2021-08-27T12:39:46.388Z

@JD800 @Reinert_Wasserman in addition, @DuellingAnts has some excellent youtube videos with in depth guides to different aspects of the script. worth a watch for sure

CarlosUnch · 2021-08-27T16:35:13.951Z

Forgot to share this exploration I did with CC and my acoustic box (kalimba springs rods cowbell) a year ago. The rack is just decorative

instagram.com

@verbosemusic

jonsimon · 2021-08-29T07:32:54.387Z

mother 32 and cheat codes

instagram.com

@disxiple_113

mk23 · 2021-09-01T12:48:17.727Z

first up, just wanted to say that CC2 has been a pleasure to learn so far, and I’ve barely used any other scripts on my Norns shield for the 2+ months that I’ve had it. I also really appreciated the musichackspace course and recommend others buy it to support your great work

However, I seem to have hit an issue and I’m not sure how to proceed. My set up is:
Norns shield running latest norns s/w
CC2 latest version
Launchpad mini mk3 x2

and I was hoping to use the Midigrid stuff built into CC2 with the Launchpads working as a 128 button grid. The GRID> options in CC2 seem to suggest this will work (i.e. one can set 128 or 64 grid, Midigrid etc). But I hit the following issues:

in the GRID menu, selecting a 64 or 128 grid seems to have the values reversed. By which I mean that to increase from 64 to 128 I have to scroll encoder opposite way to that which I would expect.
whenever I set the GRID>midigrid option to “Yes” it forces the other menu settings to 64 button and varibright.

On occasions I have gotten both Launchpads to be recognised, but they seem to duplicate what is shown. I don’t get a 128 button grid, rather 2x 64 grids that display the same stuff. For example pressing pad A2 on the first grid shows the same change being made on the second Launchpad.

But when I run in the 64 mode, then I can control the brightness i.e. changing from varibright to 4-step makes visible change on the Launchpads. The change is made on both grids.

From my limited troubleshooting I noticed this happen in maiden when I try to set CC2 to use the 128 grid:

lua: 
/home/we/dust/code/midigrid/lib/vgrid.lua:147: attempt to index a nil value (field '?')
stack traceback:
	/home/we/dust/code/midigrid/lib/vgrid.lua:147: in method '_set'
	/home/we/dust/code/midigrid/lib/vgrid.lua:173: in method '_relative_set'
	/home/we/dust/code/midigrid/lib/vgrid.lua:98: in function </home/we/dust/code/midigrid/lib/vgrid.lua:95>
	(...tail calls...)
	/home/we/dust/code/cheat_codes_2/cheat_codes_2.lua:4366: in global 'grid_redraw'
	/home/we/dust/code/cheat_codes_2/cheat_codes_2.lua:1374: in global 'draw_grid'
	/home/we/dust/code/cheat_codes_2/cheat_codes_2.lua:1935: in field 'event'
	/home/we/norns/lua/core/metro.lua:164: in function </home/we/norns/lua/core/metro.lua:160>

Was just wondering if 128 Midigrid support is working for anyone else?

Andrew_Eason · 2021-09-01T17:48:32.645Z

Just to briefly say I’m having the same experience, though both my mk2 launchpad minis do light up consistently, they’re always duplicates of one another. Changing over the 64/128 setting in GRID parameters doesn’t change that behaviour. (Shield here, too) I do think CC2 is brilliant, many many thanks.

dani_derks · 2021-09-01T18:16:34.352Z

hi @mk23 + @Andrew_Eason – thank you for the kind words! super glad you’re enjoying the script

cheat codes supports midigrid as 64 / single launchpad by default because the 128 layout for the script requires an unbroken distribution of pads in order to feel performant – upthread there are a few folks who’ve mentioned that the physical separation between the two launchpads just makes things feel wonkier than working with the 64 mode. so, i hardcoded the settings to reinforce the 64 as the ‘supported’ recommendation.

however, if you want to dig into the 128 config:

unplug the launchpads from norns
load the script and make sure PARAMETERS > GRID > grid size is set to 128 and midigrid? is set to no

edit this line to read:

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

reboot the script, connect your launchpads, get 'em into the correct programmer modes and you should be good (you’ll likely need to turn the launchpads to orient correctly)!

i’ve only got a single launchpad, but it’s definitely reflecting the top half of the 128 layout after following those steps. lmk if you run into any other trouble!

Andrew_Eason · 2021-09-01T19:12:54.045Z

Thank you! It’s not unlikely that I too will succumb to it feeling wonky, but now I can give it a whirl

Reinert_Wasserman · 2021-09-02T11:06:25.588Z

Hey quick question. It feels like the pattern record button triggers on release. Where in the script can I have a gander to change it so it acts more like the rest of the pads and triggers as soon as I press the button?

I find it takes a lot of effort to get a smooth loop if I already have a rhythm going on the grid that I’m pressing down on the beat and then have to time my record to release on the beat, which usually leaves me with a little hiccup.

I know I can set up a count in for auto record and have also have it automatically stop recording once I’ve hit two bars but, there are still a lot of times I prefer recording in “loose” mode.

dani_derks · 2021-09-02T11:14:09.140Z

i actually forgot that patterns were set to activate on release – i’ll definitely explore changing this permanently (or surfacing a param), but in the meantime i think you can should just be able to change this line:

github.com

dndrks/cheat_codes_2/blob/16e230d0e1b8aef035748fffc5d6106500d67b68/lib/grid_actions.lua#L197

    
      
                zilch_leds[zilch_id][k1][y] = 0
                grid_dirty = true
                if menu ~= 1 then screen_dirty = true end
              end
            end
          end
          
          

          
for k = 1,1 do
            for i = 1,3 do
              if z == 0 and x == (k+1)+(5*(i-1)) and y<=k then
                grid_actions.grid_pat_handler(i)
              end
            end
          end
          
          
for i = 4,2,-1 do
            if x == 16 and y == i and z == 0 then
              local current = math.abs(y-5)
              local a_p; -- this will index the arc encoder recorders
              if arc_param[current] == 1 or arc_param[current] == 2 or arc_param[current] == 3 then

to:

if z == 1 and x == (k+1)+(5*(i-1)) and y<=k then

if there’s anything else you’d think could help better facilitate your style of play, please lmk!

Reinert_Wasserman · 2021-09-02T11:33:53.929Z

Thanks @dani_derks. I do think that this is more a feature than a bug as I also recognize some performance benefits to it being on release.

I think if you were going to include some params being able to set a behaviour per state would be quite useful.

I think there are currently three states it could be in (“Arm Recording”, “Stop Recording” and “Play Pattern”)

I’d say the most useful params would be to toggle “play Pattern” to be “On Button Press” if you want to trigger patterns while you’re in a groove or “On Button Release” if you’re planning on queuing up to start a pattern at just the right moment.

A Param for “Stop Recording” would essentially just help whoever is already used to the current flow to not be thrown a curveball.

The “Arm Recording” state is perfectly fine and I assume most users prefer it to stay as is, as it gives you all the time in the world to psych yourself up to start playing the pattern. But for the sake of bringing this thought experiment home to be able to toggle it to start recording as soon as that button is pressed could be an option.

Again, Thanks for all your time, love, and support for this community.

hypnosapien · 2021-09-03T12:20:47.937Z

Great stuff! BTW, did you figure out a way to rotate the pad banks 90 degrees, or have you just adjusted your brain to use the pad banks sideways?

Ukasz · 2021-09-03T12:42:05.047Z

Yooo @dani_derks when is CC3 coming out? Can’t wait for the new version

stvnrlly · 2021-09-03T16:09:42.593Z

I can’t find this in the docs: is there a way to undo zilchmo gestures? Either an “undo last” or “reset to default” gesture could be useful.

jonsimon · 2021-09-03T17:19:31.737Z

my studio is very tight so i have a hard time rotating the grid, so i taught myself to see it sideways haha.

dani_derks · 2021-09-03T17:25:38.863Z

@Reinert_Wasserman , totally makes sense, thank you for the detailed request + kind words! i’ll play around with this and post a revision soon

Ukasz:

when is CC3 coming out?

honestly, best estimate is it’ll come out when it’s done
it is very close – i’m in the ‘play it like a stranger’ stage, which often the final round of internal feedback.

i’m really hoping to present it as complete as possible, so i’m just refining some concepts which feel critical to the identity of this alternate version (‘alternate’ because cc2 will remain supported and available as the ‘all-rounder’, with this next version as a refinement for particular use cases + interface interactions which i’m exploring more of in my personal practice).

stvnrlly:

is there a way to undo zilchmo gestures?

curious which one in particular you want to undo? hoping there might be a good ‘right now’ solution

stvnrlly:

“reset to default”

i’ve actually been thinking about this!! funny synchronicity. i’ve been digging into Richie Hawtin’s Plastikman Live system which hinged on this Kapture Max for Live device. this allowed him to snapshot the states of a few key elements so he could explore wild recombinations and modifications while also being able to recall a known/desired state with a button press. obviously cheat codes has a ton of variables, but i think it’d be fun to at least capture pad states (levels, pans, rate) to recall them after a button mash sesh

hypnosapien:

rotate the pad banks 90 degrees

gah, have to remember this one for the next rev. thanks for the bump!

stvnrlly · 2021-09-03T19:22:18.412Z

Well, I’m just learning the script, so I do a lot of things that could use undoing. Just opened up the docs again and it looks like I overlooked ALT + *1x, which might be what I need.

dani_derks:

i think it’d be fun to at least capture pad states (levels, pans, rate) to recall them after a button mash sesh

Very agreed, this would be super fun and would take some of the pressure off with tighter patterns.

mk23 · 2021-09-05T21:06:34.262Z

thanks for the advice @dani_derks. I can confirm that after a few reboots I got a 128 type grid going with that edit. Cheers!

JoseQuervo · 2021-09-06T00:04:34.582Z

Cheat codes with 128 grid layout using two LP minis mk3. Login • Instagram

DegradedEcho · 2021-09-08T08:58:32.382Z

New to norns, finding the ui quite confusing (app by app) but cheat codes is lovely, working out using it with opz. How can I turn off live input?

CarlosUnch · 2021-09-08T09:37:05.507Z

That’s on Norns leftmost screen, outside any script. IIRC one of the levels showed there reads “mon” for monitor.