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 
. 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
