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

DuellingAnts · 2021-02-13T18:21:57.426Z

I’m glad to hear, thank you

bc3 · 2021-02-13T21:00:29.857Z

I know real estate is tight but the more I use the pads to play midi notes I’m finding that I wish there was a dedicated pad to enable/disable the midi note output on each bank.

The way I’m using midi notes out now is to play different tracks on the OP-Z and then record what I am playing back into CC2 on the buffer for that bank. It would nice to be able to switch off the midi note output quickly so you could then just play the slices with the pads.

dani_derks · 2021-02-13T21:04:05.038Z

totally agreed! i’m planning on doing a small update in the next week or two which will allow folks to assign the remaining keys on the main page to any one of a batch of actions – so like, if you don’t have an arc (which the four keys under each bank control), you can just reassign one of them to something like toggling MIDI output, or using those to pull up pages on norns without clicking around, or tap tempo, etc

i’ll keep this one in the log for assignable actions! thanks for the ping!

tho for now, you could map a MIDI controller under PARAMS > pad to note setup to quickly toggle bank x MIDI output? on and off

bc3 · 2021-02-13T21:14:13.487Z

So great, I knew this probably was already on your radar!

Yes, the midi controller idea did cross my mind as well but I will wait till you make the update as it will be so cool to have it right there on the grid.

Thanks as always!

Ukasz · 2021-02-15T22:04:35.969Z

Wow I just accidentaly realised that you can scroll through samples and quickly change them in EDIT - LOOPS+BUFFERS - CLIPS by turning E3 This is great

DuellingAnts · 2021-02-16T08:55:56.987Z

I’m having some troubles with the arps atm, they’re not getting activated on any of the banks. Something looks strange in matron too. Is the nanocontrol2 causing troubles?

matron

1

matron

supercollider

midi inconsistency for device: nanoKONTROL2

ALSA lib rawmidi_hw.c:111:(snd_rawmidi_hw_status) SNDRV_RAWMIDI_IOCTL_STATUS failed: No such device

grid added: 3 monome 128 m1001081 m1001081

script load: /home/we/dust/code/cheat_codes_2/cheat_codes_2.lua

cleanup

script clear

including /home/we/dust/code/cheat_codes_2/lib/cc_pattern_time.lua

including /home/we/dust/code/cheat_codes_2/lib/main_menu.lua

including /home/we/dust/code/cheat_codes_2/lib/encoder_actions.lua

including /home/we/dust/code/cheat_codes_2/lib/arc_actions.lua

including /home/we/dust/code/cheat_codes_2/lib/zilchmos.lua

including /home/we/dust/code/cheat_codes_2/lib/start_up.lua

including /home/we/dust/code/cheat_codes_2/lib/grid_actions.lua

including /home/we/dust/code/cheat_codes_2/lib/easing.lua

including /home/we/dust/code/cheat_codes_2/lib/arp_actions.lua

including /home/we/dust/code/cheat_codes_2/lib/rnd_actions.lua

including /home/we/dust/code/cheat_codes_2/lib/cc_musicutil.lua

including /home/we/dust/code/cheat_codes_2/lib/delay.lua

including /home/we/dust/code/cheat_codes_2/lib/euclid.lua

including /home/we/dust/code/cheat_codes_2/lib/midicheat.lua

including /home/we/dust/code/cheat_codes_2/lib/sharer.lua

including /home/we/dust/code/cheat_codes_2/lib/macros.lua

including /home/we/dust/code/cheat_codes_2/lib/transport.lua

script run

reading PMAP /home/we/dust/data/cheat_codes_2/cheat_codes_2.pmap

Engine.register_commands; count: 0

___ engine commands ___

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

script init


pset >> read: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset

pset :: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset not read.

output[1] initialized

output[2] initialized

output[3] initialized

output[4] initialized

~~~~~> no user defaults defined: save a collection as DEFAULT to establish <~~~~~

metro_stop(): pthread_cancel() failed; error: specified thread does not exist

>> saving PMAP /home/we/dust/data/cheat_codes_2/cheat_codes_2.pmap

pset >> write: /home/we/dust/data/cheat_codes_2/collection-MAPS01/params/all.pset

saved midi pattern 1

saved midi pattern 2

saved midi pattern 3

metro_stop(): pthread_cancel() failed; error: specified thread does not exist

metro_stop(): pthread_cancel() failed; error: specified thread does not exist

metro_stop(): pthread_cancel() failed; error: specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

pattern rec start

count 13

new start

new start

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

metro_stop(): pthread_cancel() failed; error:

specified thread does not exist

dani_derks · 2021-02-16T10:38:13.923Z

hey hans!

DuellingAnts:

I’m having some troubles with the arps atm, they’re not getting activated on any of the banks.

if you can make this happen again, any repro steps would help – i’ve seen this a handful of times, but rarely and without any way to cause it on purpose. in the meantime, there’s an arp reset trigger under PARAMS > loops + buffers > arps which will kickstart 'em as an emergency backup.

i’m sure this’ll also get cleaned up when i’m able to spend some time on the patterns update, so don’t stress if you’re unable to get a case

re: matron:

midi inconsistency for device: nanoKONTROL2 means the device was unplugged, before the script ran, it seems? other than that, nothing worrisome.
the other metro_stop(): pthread_cancel() failed; error: messages are innocuous and system-wide.

DuellingAnts · 2021-02-16T11:28:29.173Z

hmmm, arp reset didn’t work…seems like activating arp mutes the sample. will see if I can investigate further later

no need to stress this for me by the way, I’m deep into the macros atm

info


pset >> read: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset

pset :: /home/we/dust/data/cheat_codes_2/cheat_codes_2-01.pset not read.

output[1] initialized

output[2] initialized

output[3] initialized

output[4] initialized

~~~~~> no user defaults defined: save a collection as DEFAULT to establish <~~~~~

here

scanning psets...

ls:

cannot access '/home/we/dust/data/cheat_codes_2/cheat_codes_2*.pset'

: No such file or directory

scanning psets...

ls: cannot access '/home/we/dust/data/cheat_codes_2/cheat_codes_2*.pset'

: No such file or directory

here

here

here

pattern rec start

count 6

new start

new start

here

here

Denbuter · 2021-02-16T14:56:23.867Z

I just tried it and I really liked this layout! I’m just curious, it is even possible to make pattern recording work? I thought zilchmos didn’t work through OSC, or is there still a chance?

dani_derks · 2021-02-16T14:58:43.658Z

Denbuter:

it is even possible to make [OSC] pattern recording work?

not yet – part of the patterns update that i am trying to carve out some time to knock out

jemfiner · 2021-02-17T13:27:08.900Z

Hi @dani_derks, Cheat Codes is really wonderful, thank you !

I’ve started running into some problems with Patterns, I think since I updated to the latest version.

Recording a random pattern, either by hitting K3 in the timing page or using alt + *r on the grid, causes the loop start and end points to be randomised too, like hitting K3 in the loops page. Is that meant to happen ? Some randomisations are to values outside the current clip, negative values for a start point for example.
Hitting K3 while on rec mode doesn’t initiate a recording.

I’m not sure if I’m out of date with developments or I’ve run into a bug.

dani_derks · 2021-02-17T15:27:50.341Z

thanks for the kind words @jemfiner !

hmmm. i’m totally unable to repro this first issue. can you confirm that when you go to load cheat codes you see this in the preamble?

cheat codes 2
    a sample playground
rev: 210208

i ask because random patterns don’t touch loop points at all in cheat codes 2 – they used to in cheat codes 1, tho.

re: K3 on rec mode, it sounds like you’re using a grid (or have midigrid enabled), so the K3 to record function doesn’t work for patterns. this is a spillover from the fact that the pattern system keeps track of MIDI-generated and grid-generated patterns separately (another thing that’ll change with the mentioned pattern update) and that toggling pattern recording on a grid is super close to the place where you’ll play the pattern, so it just made sense to choose that as the trigger method.

hope this helps, plz lmk!

jemfiner · 2021-02-17T16:45:32.184Z

I can confirm that I am running rev: 210208

re: K3 on rec mode, understood, thanks.

Issue one though is weird. I’m wondering if I’ve set something in the background . . . can’t see anything active though in terms of >rand or macros.

dani_derks · 2021-02-17T16:49:46.861Z

jemfiner:

Issue one though is weird. I’m wondering if I’ve set something in the background . . . can’t see anything active though in terms of >rand or macros.

well, nothing should be bringing loop points to unusable values. hmm.

could you try these steps:

delete + reinstall the script (you won’t lose data)
delete any .pset present files in the top layer of data > cheat_codes_2 + the corresponding txt file eg.:

Screen Shot 2021-02-17 at 11.47.54 AM646×754 64.8 KB
- PSA: .pset files are not ideal for cheat codes – collections capture everything and with the new default loadstate functionality, you can load a custom default state
if you can reproduce the issue, save it as a collection and DM me the collection file along with repro steps?

jemfiner · 2021-02-17T17:01:52.536Z

Thanks @dani_derks, I’ll try these steps.

briangriffith · 2021-02-17T19:14:18.476Z

Is anyone else having a problem with Live Buffer 3 deleting itself after a certain amount of time? It seems to happen with it’s in 16 or 32s mode.

dani_derks · 2021-02-17T19:29:53.392Z

weiiiird, i’ll do some testing over here (just wired up mx.samples to cheat codes and it’s super bonkers fun!), but these are the only actions in the script which can cause a buffer erasure:

be focused on a live segment in [loops], hold k1 and press k2
press alt + key for the currently-focused live segment in the bottom corner of the grid
if you have the OP-Z template set up for zilchmo (even if you aren’t using it) and the midi note to erase buffers is received (23 notes above the base note)

if you can PM with a few steps to repro (loop vs 1-shot, was record probability on at all, what feedback levels are you using, how much time passes, etc) and a collection file that this seems to happen with, that’d be

briangriffith · 2021-02-17T20:11:49.771Z

Now I am having trouble reproducing the issue, soooo maybe it was user error, though this has happened before. I will take a video and PM if/when it happens again!

edison · 2021-02-18T01:04:13.118Z

lil live macro noodle. electric guitar and reface CP into CC2. all 8 macros going is just bonkers

dani_derks · 2021-02-18T13:40:21.659Z

holy shit, @edison – i particularly love these breakpoints of very definitive change (the pitch drop at 0:41 was massiiiiiive feels), which lends a wonderful impression of premeditated collage and structure. such a great improvisational outcome. damn, thank you for sharing this!!