#67
4 Likes
#68

finding that meta sequencer vibe. this shit is nuts!

8 Likes
#69

Loving the Cheat Codes!
Thanks again @dan_derks for the awesome work.

Q_1:

is there a way to record the output of cheat codes into a buffer, so that it can be saved as audio file? And potentially landed again into Cheat Codes for further mangling?
OR
in general: to record within the digital domain to minimize noise artifacts going out via analogue outs?

Q_2:
Totally in love with recording the arc movements! Is there a plan to have these saved with/within the collection, along with all other “states”?

Q_3:
The built-in collections load/save setup works great! I was initially confused about this vs. using the K1 long-press save/load scenario. Does the long-press K1 not work with the CC now? I swear I tried using this to save a “default” and it did not work. If not does not work, maybe worth disabling?

I am sure I will have more questions.
But for now: any advice will be much appreciated.

1 Like
#70

You can record to the Norns tape and then use something like SAM to cut out sections to reuse!

2 Likes
#71

dang, @edison, you are on fiiiiiiire. thank you for sharing these artifacts!!
and @laborcamp, thank you for sharing that artifcat!

laborcamp's q's

@vcvcvc_val has it right – recording to Tape will be the best move to record the output from cheat codes.

@andrew’s pro-tip: if you export to Audacity (or similar) and pitch your samples up a few octaves, this will allow you to import samples that are “longer” than 8 seconds – you can use the offset feature to pitch them back down (either in PARAMS or on the K1-alt screen of [loops]) and you get a really nice effect from the sample rate reduction.

eventually, yes! it’s on the roadmap, for sure :slight_smile:. if it helps clarify the design choice, i always see arc as a temporary + expressive modulator – but i also totally understand its value as a compositional cornerstone!

the long-press K1 while on the PARAMS screen to get to presets is a system-level menu action – it lives above the scripting layer and is always available (so I don’t think it’s possible for a single script to disable). it saves all the settings listed in the PARAMS screen – the reason why collections exists is that a single cheat codes session can be comprised of 1000+ data points, stored inside of tables. from what I can tell, I’d need to expose these all as parameters in order for presets to capture them.

i’ll do some digging to see if there’s a way to force the collection action from the act of saving a preset, but honestly collections is the simplest way I can imagine to ensure the integrity of the sessions. it also affords some scripting niceties around Pattern data, once you start saving multiples on the meta page.

hope that all helps, @laborcamp, and thank you for engaging with the script!

if anyone has time today...

…it’d be mega dope to get some eyes on the latest version before release – i tested pretty thoroughly on my side, so I just need to make sure it doesn’t cause any weirdness for others.

please back up your dust > data > cheat_codes folder before testing, as the new version is designed to make fundamental changes to the structure of existing pattern data. we cannot retrieve your old pattern data if something goes sideways, so make sure you feel comfortable with backing up!

if you run into any troubles, just PM me directly.

https://github.com/dndrks/cheat_codes/archive/patchup.zip

changes are primarily:

  • live buffer save/restore no longer requires extra steps! all taken care of with the save Live buffers? param
  • added a reset/clear crow param function, in case crow stuff gets wonky
  • fixed Live buffer clear function (grid-ALT + Live buffer select)
  • fixed PARAMS: delay send , which now moves in 0.1 chunks (rather than binary on/off)
  • fixed some residual delay-centric [level] issues
  • mega-big updates to snap to bars w/r/t external timing – this is super rock-solid now, making it really easy to play + swap Patterns when clocking thru MIDI or crow. read more here

latest manual: cheat codes manual - 200301.pdf

3 Likes
#72

image
image1536×2048 1.17 MB

:joy::heart_eyes_cat:

14 Likes
#73

man that cat loves those buttons!

3 Likes
#74

thank you for this one

man
MAN
it’s good

2 Likes
#75

ok last one for a bit… but got midi sync and saving all figured out!

6 Likes
#76

Dude, these have been so good. Killer stuff.

1 Like
#77

thanks man! just learning and really vibing with the norns.

1 Like
#78

It’s a really really fun platform with a tool that can fit in to almost any part of a workflow chain. Welcome aboard!

Btw, with the most recent example, were you working mainly from recorded loops or the record buffer?

Guessing the digitakt and norns were in parallel? Or was the digitakt passing through norns?

#79

yea it definitely is! just has this science experiment vibe to it! i’ve been using my computer as a sound source. just sampling random plugins etc from ableton… digitakt is just doing drums and norns is going into it. need to try and run the digitakt in to norns… save my live buffers and use them as clips then live sample the digitakt into the buffer! ah! so many possibilities…

2 Likes
#80

It’s so wild. It’s cool to have some pads be the live buffer and some be recorded clips. That way, you’ll know what’s happening in the pattern only a certain percentage of the time. Means you can feed stuff through the buffer and twist up what would be a “normal” cheat codes buffer. A lot of fun!

#81

I’m really just barely understanding it bc I got too excited to finish the manual, but now that I got this far, I know I must!

Thank you so much, @dan_derks! This has already taken me places only my Cocoquantus/Plumbutter combo ever did before (and I sold them and so this is fucking awesome!) I really seriously appreciate all you do.

Anyways, this vid is all cheat codes, and some random gifs I had saved over the years from the internetz.

5 Likes
#82

@jonsimon, suuuuper dope. really excited that you’re working with cheat codes! :revolving_hearts:

a quick v1.2 progress report

the last few days has actually been spent building out the tempo-synced methods of play!

with @edison’s feedback, I’ve made some major improvements to the whole linearization/quantization/snapping jumble and created a few crystal-clear performance modes for Pattern playback (each bank can use its own mode):

  • loose: Pattern plays back exactly as recorded
  • trim: Pattern will automatically stretch/truncate to fit the closest number of bars at the specified bpm. this gets you the fun “fuzzy clocking” as the pads play back but the total length of the Pattern is predictable + definitive.
  • quant: Pattern entries are tightly quantized + event playback is synced to the clock. the length of the Pattern is unchanged (so you can have a 7-beat pattern against a 9-beat pattern for weird phasing goodness)
  • quant + trim: Pattern entries are tightly quantized + event playback is tightly synced to the clock. the length of the Pattern is clamped to the nearest bar measurement. this way, you can just record your Pattern and cheat codes will say “that’s closest to a 3 bar loop at the current bpm” and your Pattern will be automatically trimmed to fit a clean 3 bar loop at the current bpm.

these settings are available per-bank, so you can really structure the playground how you want without having to menu-dive in performance and execute arbitrary actions.

the results are a lot cleaner. here’s an improvised session from the other day, running the clock from cheat codes into an sp404. Patterns were set to the 4th mode and i ran audio from the sp back into cheat codes to record into the Live buffers. while my Patterns played back, i randomly switched whether the current pad was playing from the Clip or Live buffer (@kasselvania with the pro-tip!!):

(i don’t ever have success making beats, but this was a delightful approach to experiment with and was wholesale inspired by @edison’s artifacts)

ok, w/e, what needs finished before release?
  • updating the manual
  • decluttering the [timing] UI to reflect clearer adventures to choose from
  • sorting out how Patterns get saved session-to-session. i’ve implemented these new modes pretty non-destructively, so when reloading a saved collection quantized Patterns return to their non-quantized state. not ideal, but a fun problem to have! hopefully will wrap that up this weekend.
18 Likes
#83

Looks amazing Sounds amazing Cant wait to play :slight_smile:

At what point do you think the sync/timing approach will be stable enough to warrant a deep dive and a tutorial? I’ve been making really fast, tight dance music and want to see how far I can push CC as a sampling platform.

1 Like
#84

honestly, i should do this right out the gate with v1.2 – working through this update has made me feel a little like “what was I thinking?” w/r/t how the sync stuff is implemented in the public version, lol. having something concrete to point to that’s instructive and goes through each performance scenario would be super helpful.

also, tbh, i want cheat codes to be approachable to folks whose primary language isn’t English. the manual is a double-edged sword — it is comprehensive but also can be challenging. i can imagine this presents a sincere hurdle (maybe even barrier). so, i‘d like to do a few longform videos that show vs tell.

thanks for the patience everyone! learning tons :sweat_smile:

8 Likes
#85

I’m glad that trick worked for you! I’ve been trying it out a bit and enjoy the process but still haven’t gotten things to where I want to share. Might be the first time in the lines/monome forum history that I’ve provided anything considered a “Pro-Tip” :wink:

2 Likes
#86

whoo! so stoked to mess with this! timing options sound great! thanks for the shouts! and thanks for taking my ramblings into account haha… question, if you save a collection, and everything is set to “trim” does it recall that way too? also might play a show in april and it’ll be all CC for sure… you’re a legend bro!!

4 Likes