[cheat codes 2] (rev 220524: LTS6.2)

After hours of tweaking on a previous session, I want to start fresh and clean :slight_smile: but perhaps my my mistake was to save the session I was working on as the default collection, for booting on it at startup…
So I wanna follow your advice, start CC, save the collection under a appropriate name, and Nuke the default collection. So after that I need to reboot and I imagine that a new default collection will be automatically created then?Again, thanks or your reactivity and support :wink:

1 Like

ah, yep! that’s likely what’s happening. and exactly, you can just open the default, re-save as a new collection, delete the default.

after that, cc2 will just load to what’s scripted – your “set and forget” settings will be retained via persistent_state.data, but everything else will restore like new :slight_smile:

1 Like

Perfect! Ready to dive into the rabbit hole once again!!! :wink: Thks!

1 Like

Hi all, just got a new norns and I am a total newbie, but cc looks incredible.

I also have a probably noob question: I don’t have a grid, and I am using the touchOSC template created for cc1. Everything works fine in cc1 but with the same template in cc2 I am only able to trigger pads, but cannot trigger looping, speed, reverse, loop window etc.

Am I missing something here or the touchosc template is not compatible with cc2?

hey hey! welcome :slight_smile:

cc2 has a ton of new features over the first one, so @CarlosUnch put together a fantastic new template: [cheat codes 2] (rev 210307: CPU optimization + 64/midigrid live rec fix) - #340 by CarlosUnch

i’ve put this up in the top post, where else would be helpful to surface? want to help folks avoid finding the old template instead of the new one :sparkles:


This looks great, thank you for pointing me to the post!

I had a look at some posts, but I couldn’t find it. I think it could be either added at the beginning (where you specify what cc2 is, maybe in the input section with grids, arc etc), or in the github documentation. Given that I did not find anything there I assumed the old template was the way to go :blush:.

Thanks again!

1 Like

I´m trying to send the clock to my modular via cvpal.
First of all, is this possible?
Following the cvpal manual (Mutable Instruments | CVpal - User manual)
I think the clock signal has to be send on midi channel 12,13 or 14. I tried to set this port in the clock menu. but no luck. as well I tried different settings under the transport menu.
maybe someone has done this and can help me?!

Edit: ok I realized that setting the port doesn’t mean setting the channel…hm

ah! this is a good clue. midi clock doesn’t require a channel argument – it’s just sent through to the device. from this post from Émilie, CV Pal just needs a little nudge on channel 12, 13 or 14 to transmit the received clock.

so, i’d say try setting up a pad to note to send a note to CV Pal on whichever channel you want to use (channel 12: 24 ppqn; channel 13: 8 ppqn; channel 14: 4 ppqn), and after that it should work out! lmk if you have any additional q’s.


That’s it!! Thank you!!!


rev 210315: rnd restore hotfix

just a small fix: rnd's weren’t restoring correctly when a collection was reloaded. now they are!


If I make a pattern that’s loose, can I make new patterns of the same length?

1 Like

there’s no direct way to use the length of a pattern as a fixed length for another, but that’s where Px sets bpm in the [timing] menu can assist! if you enable this setting, then your loose pattern length will set the bpm and you can then use bars mode to specify the number of bars at that bpm you want a different pattern to record for. ideally, you’ll get a good feel for how long a loose pattern is after a listen-through and can set others accordingly.

a more direct way is a nice feature request, though! noted :slight_smile:

i recently had a breakthrough while talking with @Deru about on-screen UI workflows, which i’d like to tackle now while i’m clear-eyed. patterns are going to get some love as soon as i can, tho!


After making a loose pattern (P1) I’ve enabled P1 sets bpm. Then I’ve tried to set rec mode for P2 and P3 distro instead of loose, but it seems that I only have distro 1.5 option for P2 and distro 1.75 option for P3. Are these numbers the bars? How could I have more options (specially integers)?

a few things happening here:

  • Px sets bpm must be set before making your pattern. it doesn’t work retroactively. the assumption is that if it were to activate immediately, it’d be destructive to something else you might have going on.
  • if you’ve already recorded a loose pattern on a bank and switch to bars (have you updated? distro lingo has been deprecated), then cheat codes will round the pattern to the nearest quarter note and show you that value as your bar length – that’s why you’re seeing different floats on your other patterns
  • to fine-tune a bar count, you can hold K1 and turn E3 to get 0.25 deltas :slight_smile:

lmk if you run into any other trouble!


Oh wow man. I’m excited that that was helpful!

1 Like

Thanks, Dan! Updated! It works like a charm! Now I can loop without sounding like these Steve Reich-esque phase experiments (which I love but from time to time I like to keep things tight!).

That would be very nice!

1 Like

CC2 is simply amazing, thanks @dan_derks for this script, it’s something really inspiring (but everyone here already knows it!) I will never stop to say it.

I’m wondering if there is a way to implement a probability behavior for the arp mode movement, to drive pads arpeggios to one or more random pad destinations, with probability, or maybe a “work around” to achieve this behavior not in arp mode?


So you have already tried to set the arp pattern to random in the arp controls page? Also try “additive” mode which is super fun!

Yep, random arp mode is nice and essential! Not sure what is additive mode
edit: ok found it :slight_smile:


Is it possible to use audio from Ableton as live input? How?