#1

cheat codes

IMG_0090
IMG_00902224×1668 207 KB

a sample playground for norns

v1.1.1.1.1.1.1.1 (last updated Feb 18 2020 PM as commit d89a76f )

behind this needlessly ridiculous version number are a ridiculous number of needed additions:

[loops]
hold K1 to reveal:

  • gridless control over pad selection, buffer assignment, and buffer recording
  • per-pad semitone offset
  • extend the Live buffer from 8s -> 16s or 32s

nb. hold grid’s ALT key and press the unlit square to the bottom right of each bank to reset your currently playing pad’s speed to 1x

[levels]

  • env now enables at a 3 second envelope (was 0.5), to allow artist to “dial in” rather than forcing an immediate change
  • fixed bug where level change would immediately raise volume of an already-decayed pad

[filters]

  • new lp/hp dj-style filter
  • improved ergonomics (each encoder controls its own filter, rather than one filter at a time’s controls spread across the three encoders)
  • hold K1 to set the filter tilt of the currently playing pad
  • per-pad slew parameter glides filter between different tilt values

[timing]
complete overhaul of timing parameters, manual is a must read

  • highlight bpm and tap K3 for tap-tempo
  • MIDI and crow clocking retain the ‘swing’ of your recorded Patterns, allowing for easy integration with external gear
  • crow: configurable to send clock (+ clock divisions) or pulses with each pad press
  • Pattern linearization
  • Pattern stretching across bars at specified BPM

Patterns + meta-sequencing
completely new stuff, plz see manual

  • store up to 8 Patterns per bank
  • Kria-inspired 16-step sequencer to play Patterns
  • use toggle keys to switch between looping and 1-shot Patterns

collections
you can save it all! sessions restore right where you left them, Patterns and all. this helps cheat codes be useful in long-marinading compositional endeavors :slight_smile:

there are still a few things I want to incorporate, but nothing that was worth delaying the release (any longer). mountains of gratitude to everybody who has pushed energy toward this script, but especially the test crew: @yoyosandshoes, @stripes, @jflee, @zanderraymond, @kasselvania, @noiserock, and @claasp. this wouldn’t have felt ready to go without your attention and care :revolving_hearts:

Requirements

  • norns (200129 or later)
  • grid strongly encouraged, not required
  • arc strongly encouraged, not required

Documentation

cheat codes manual 200217.pdf (9.4 MB)

for reference: previous version discussion, which holds many beautiful artifacts from the community

Download

In the maiden package manager as cheat_codes (commit 8420953).
Don’t see it? Please refresh using the refresh button next to the community header.

50 Likes
Cheat codes (v1.1.1)
#2

boop boop!

quick fix: made a muuuuuch nicer arc curve for [filters]. it is riiiight in the sweet spot now, if you happened to update in the last 41 mins + have an arc you should grab it :wink:

5 Likes
#3

Thanks so much for this, and all your hard work with it
Truly impressive and inspiring.

3 Likes
#4

Wow Dan!!! Can’t wait to dive in. Now do I take the chance of revamping my live set for Friday to encorporate Cheat Codes…? I’m thinking yes :+1:

1 Like
#6

If you can connect Norns and your iphone to the same WiFi network you should be able to access norns.local from your iPhone. If you have a reasonable data plan you could even try hotspot mode on you phone and connect Norns. (Disclaimer I have not tried either)

#8

first run at it…of course i immediately jumped right into external MIDI sync…and…FRACKEN AWESOME!

this is the sort of sonic ideas i heard in my head when first experimenting with Cheat Codes!

THANK YOU A MILLION FOR THIS!!!

here is some of tonight’s noiz…again with the SOMA Pipe and the DRM MkIII:

2 Likes
#9

Thx for the update dan, read through the pdf on work and can’t wait to go home :wink:

1 Like
#10

We need to buy @dan_derks a pizza or something to say thanks.

7 Likes
#11
bug identified + fixed

I’m getting some unexpected behavior on the filters page after loading a collection saved with the previous version of CC. The knobs don’t work to control the cutoff parameters. They do work on the other two parameter sets though (timing and jump behavior). My Arc works to control cutoff 1, but not 2 or 3, despite pressing the appropriate channel buttons.

I assume that this might mean that collections saved from older versions are no longer compatible? All good if so, just checking.

THANKS.

Here’s the Collection. I have two previous collections. I find that it’s happening with both of them so let me know if you’d like the other as well.
collections2.data (5.2 KB)

I don’t see any data being output in Maiden when I turn the encoders. I’ve never done this before so I think I’m doing it right (loading it from Maiden and looking in the output window below), but let me know if not.

#12
bug identified + fixed

hmmm, that is really unexpected. i put a good number of barriers to help avoid compatibility issues, but maybe i overwrote my old files early on. can you please use Cyberduck and DM me the collection data file? also, any maiden output when you turn the encoders would be :100:

dust > data > cheat_codes > collections[x].data

<3333!~

edit: fix pushed! please download the new patch-up ( 8420953 ) thru the project manager!

if it’s interesting: the new filter is technically a hidden “filter style 4” when compared to the original code, so when restoring an old session that has “filter style 2” or similar selected, the new version is looking for “filter style 4” and so isn’t making any changes.

2 Likes
#15

That was seriously the fastest bug-fix in history. Thank you DAN!

1 Like
#16

filters feel great! also deeply appreciate the change to env default! can’t wait to try to understand meta sequencing page. you might double check the arc delay knob with the delay page—some weirdness going on, seems like the arc doesn’t call redraw on that screen?

amazing work as always

1 Like
#17

hey hey! so glad you’re digging the changes :slight_smile:

it isn’t – will take a peek, thank u!

edit: yep, forgot to comment out something (line 134 of arc_actions.lua). low-impact fix, will release later today!

#18

jeeeez dan this is so fun

2 Likes
#19

Hey @dan_derks. Really small thing here, but it might be nice if the ALT button on the Grid switched the screen over to the semi-tone adjustment screen when on the Loops page (like it does when you press the first Norns button). I’m not sure if that’s possible or not, but I realized that it could be a nice ergonomics thing, as holding the Norns button while adjusting can get a little tweaky.

I also wonder if this alt mode could be a toggle instead of momentary… But either way, THANK YOU FOR IT.

#20

hey hey!

ah, we’re coming up on the edge of some design choices :slight_smile:

I purposefully kept grid-ALT and norns-ALT separate for that page, as I found myself using grid ALT to take care of grid functions while needing to see that norns-ALT page – linking the two became really undesirable because now they each have such different contexts.

but, holding norns-ALT to toggle in/out of that screen is brilliant and easy enough to implement. will roll it in today!

#21

Amazing. Got it, and thank you.

And I finally hooked up a mic to CC to do some live sampling (up until now it’d been all samples)… And wow… I’ll stop asking for things and simply praise you for a second (at least, hah) – what an amazing instrument you have built!

1 Like
#22

I’m going to dive into this tonight.

I really appreciate the effort you put into this (and the awesome documentation)!!!

1 Like
#23

Trying to wrap my head around performing a piece with CC. There are two areas that are tripping me up a little.

LEVELS:
If I want to fade in or out all the pads in a bank I know that I can press Alt on the Norns and adjust them all together (this doesn’t work while pressing ALT on the Grid am I right)? What confuses me is that the volume doesn’t go all the way down to 0db. It get quiet, but then I need to stop the loops or patterns in some other way? This leads me to my next question:

STOP:
Pressing the stop button has a hard cut off. The volume goes to zero very quickly. If this is indeed the only way to make a loop go to 0dB then might it be nice for a fade out option when stopping clips?

Or maybe the idea here is to create really long fade out envelopes for every pad even if you plan on using it as a loop in your sequence? Seems like this could be a work around.

I’m guessing that I’m not playing the patch properly at this point so please don’t take that as a feature request just yet. Lord knows I’ve given a lot of those :wink:

-B

#24

hey hey!

could you please try re-approaching? here are three ways I’m able to pull levels to silence on all the pads at once:

  • hold grid-ALT and press the leftmost key in the 2-pad row of zilchmo until i get to full silence
  • hold grid-ALT and use the encoders on [levels] -> silence
  • hold norns-ALT and use the encoders on [levels] -> silence

here’s a clean fade in and fade out, using these methods:

if you’re able to reproduce trouble, please share concrete steps + I’ll be happy to investigate :slight_smile:

it’s technically a pause, so yes! you shouldn’t need any workarounds for levels, so lmk how re-approaching goes.

1 Like