@acajide + @mattlowery, thank you both for sharing such kind energy – i’m really really glad it’s all vibing well with you :hugs:

if everything goes as planned today, there will be a v1.1 update later tonight and a v1.2 update next week.

v1.1:

  • “rad sauce” pattern record mode, which wraps zilchmo row 4 gestures into the pattern recorders
  • start/end loop points for live buffer – everything from 100ms to 8s loop windows
  • “1-shot” mode for live buffer recording, which means the record head records into the live buffer’s loop window and stops recording when it hits the end point
  • each pad in each bank can have a unique decaying envelopes – everything from 100ms to 60s, for quick percs + loooooong decays
  • minor bug fixes (params MIDI-mapping, small buffer reference issues, etc)
  • minor enhancements (pattern record button blinks at specified BPM, etc)

v1.2:

  • streamline [filters] to a single hp/lp dj-style (like the op-z)
  • introduce pattern linearization + post-record quantization
  • introduce on-the-fly pattern manipulation
  • add additional arc params/controls, tune them for arc’s very hi-res control
  • @vinc there is no current way to switch modes without a grid. I hope to explore grid-less interactions (or just supplementary menus) in v1.2
19 Likes

more noiz with MANGL feeding Cheat Codes in the latest installment of
Late Night Noiz for Late Night Fiends:

1 Like

Heck yah! This will give some good control to the live buffer for my particular needs. Thanks!

1 Like

I ended up making some tape loops from my first cheat codes session, and letting them play asynchronously for a couple of minutes. Two at half speed, two at regular speed. It’s a big hot mess, but, man alive, cheat codes is where it’s at. :exploding_head:

11 Likes

just came here to notify y’all the v1.1 RC is in the dev branch + won’t be released till I can get docs updated tomorrow, but then jeeeeeeeeezus.

this is gorgeous, matt. damn. thank you so super much for sharing!

1 Like

This is wonderful. Absolutely wonderful. I’ve been wanting to get some time together to make a few piano and Just Friends loops together to play with in Cheat Codes. This is what I had dreamed it COULD sound like.

2 Likes

i know i post a lot…but these noiz weapons are so inspiring…
another session of Late Night Noiz for Late Night Fiends…
using MANGL (@Justmat) and Cheat Codes

and here is a pic of the noiz circuit:

8 Likes

v1.1 is up! docs in first post mega-updated! please please please read 'em, as much has changed + (hopefully) improved!

required reading for everyone: audio: recording Live + playing Clips section. lots changed, please review <333

overview of habit-breaking Live buffer changes

  • punch in/out: re-select a looping Live buffer to toggle punch-in / punch-out at the current rec head position (used to require ALT + Live buffer select, used to reset rec head to start of buffer)
  • clear a Live loop: ALT + Live buffer select (there was no previous option for this, but ALT + Live buffer select used to punch in/out. now, it’ll clear the audio in the selected Live loop’s bounds)
  • you can now adjust the Live buffer’s recording loop points!
27 Likes

totally gratuitous artifact. short loop duration + envelopes + pattern recording = very good. thanks! amazing work.

9 Likes

MIDI clock doesn’t seem to be working correctly for me…

Parameter settings:

clock: External MIDI clock
quantize 4x4 pads? Yes
quantize pattern button? Yes

The patterns will not record or play.

Switching from Ext Clock to Internal Clock and the pattern buttons can be activated or will jump to activation if I had pushed them already.

Switching back to MIDI Clock while it was playing and my Grid crashed and went completely dark.

Arc stayed lit up but the C bank knob would not move.

16n still works. I have it assigned to volume and filters and can see the movement.

Other weird thing…after switching to Ext MIDI Clock…the loop brackets would move but the play heads would all stay and put playing their audio snippet.
As soon as I set it back to Int Clock then the loop brackets act and play properly.

as seen here:


Sorry I can’t get info from maiden because I am using every single port on Norns with Grid, Arc, 16n and MIDI to USB box.

hey! weird! yeah, just sounds like the script wasn’t receiving your clock source. all those behaviors are normal for what was basically a full-stop in timing.

bummed to not have a new late night installment :slight_smile: sorry for the speed bump!

edit: found the trouble, will release a fix! thank you so much for the report!

1 Like

Really love the script! I spent all afternoon playing with it and hope to use it in a performance this weekend.

I noticed one possible issue: I was hoping to clock the script via crow, but the script seems to continue with the internal clock source instead. In maiden crow is recognized with the “initialize crow” command as well as the “CAW!” when selecting external in[2] as a clock.

If it helps any, clocking from a crow input seems to work fine with the less concepts script.

(I haven’t tested it extensively, but I also haven’t been able to get external MIDI clock working either—couldn’t start recording patterns and my norns locked up requiring a restart via maiden.)

@jflee I just tested crow, all working on my setup. docs don’t have steps tho, apologies!

  • plug crow into norns
  • select initialize crow in the PARAMS
  • set clock to external: crow (in2)
  • set quantize 4x4 pads? to yes
    • this will decouple the actual audio event from your presses in the 4x4 banks of pads. so, if you press a pad, cheat codes will wait until it receives a pulse at crow’s input 2 before it triggers the audio

so, crow clocking is fundamentally a performance mode only – it delays the execution of your most recent pad press to the external clock. but i’m realizing now that it would be super useful to be able to walk through steps of a pattern, as well. this ties in nicely with some v1.2 pattern linearization features that i’m planning, so thank you for the inspiration!

2 Likes

Ahhh, sorry! After checking things again it seems like the quantization seems to follow the clock from crow correctly. I just got confused with the visual feedback of the blinking pattern button, which seems to follow whatever was last set as the bpm of the last internal clock setting before switching. :man_facepalming:

1 Like

yes! another great point! the crow clocking might actually do nicely to blink the pattern record light as well. currently, that redraw is firmly linked to the internal bpm. i’ll add to the roadmap!

there are a lot of crow features to be added – more soon!

2 Likes

Thank you for such a great instrument and the quick feedback!

I really like how the script encourages me to listen deeply to whatever I put through it, with all kinds of manipulations ready at hand—really amazing. Looking forward to more developments!

1 Like

v1.1.1 pushed!

fixed:

  • MIDI clocking now works as designed
    • set clock to external: midi
    • set quantize 4x4 pads? to yes
    • this will decouple the actual audio event from your presses in the 4x4 banks of pads. so, if you press a pad, cheat codes will wait until it receives a clock signal before it triggers the audio
  • help menu instructions updated for v1.1 pattern recording changes

added:

  • if clock is external MIDI, bpm PARAM will slide to match incoming clock (so pattern rec LED blinks at expected rate)
  • arc filter cutoff is now exponential (thx for the feedback + idea @ypxkap!!)
13 Likes

thank you so much for the update!

more feedback from the noiz trench…
:slight_smile:
got MIDI Clock coming in and i see the tempo matching in Parameters.

though…it seems to drift a few beats up and down as it plays along.
i tried sending MIDI clock directly from an LXR Drum Machine and also tried sending MIDI Clock from an e-rm Multiclock box.

strange thing…with the e-rm Multiclock at 100bpm…Cheat Codes displayed an unwavering 100bpm and never moved.
at 120bpm though it would drift up and down a couple of beats.
(which may attribute to the next problem)

i just couldn’t get the patterns i would record to line up rhythmically.
they just kept drifting off as it went along and would be out of sync with the drum machine.

i am going to get a new iConnect box to trouble shoot a bit more.
(i think it’s this old USB to MIDI box creating issues)

was wondering…
(i apologize if this is kinda crazy or doesn’t make too much sense)
since each block of a/b/c is made up of 16 squares…
would it be possible to make those the sequence steps of the pattern?
as in…
the sequencer would dimly step through the 16 squares of the block and quantize to those steps.

was experimenting getting rhythms with this thing going through PHYLLIS (@Justmat) into Cheat Codes.
:stuck_out_tongue:

hey! these are helpful data points – tbh, I was always primarily attracted to external sync for live pad tapping and not pattern rec/playback, so this is super helpful to know!

nb. the bpm “matching” in PARAMS is just informational – it affects delay clocking + the blinking rate of the pattern button only. but, that was the smoking gun!

taking a look this morning, I see how things can be optimized. right now, external MIDI clock syncing is a flat 24ppq, which means 24 pulses per quarter note. that resolution is wicked nice to keep automated clocks synced – but the patterns you’re recording are entered manually. at 120bpm, that means finger presses are quantized to roughly the nearest 0.02 seconds – this will introduce super tiny offsets that may sound totally fine while they’re grooving on their own, but play it against a steady beat and it quickly becomes apparent how far off they’re drifting. even if the pattern recording end point was pushed by 20ms, that will have a drastic effect.

so, i’m gonna “dumb” things down a bit and give the pads a more generous quantization resolution.

I should have these improvements rolled in soon :slight_smile:

also:

this is part of the pattern linearization for v1.2!
it actually makes sense for patterns to linearize when an external clock is present, like earthsea + teletype – each clock event will just move to the next sequence in the pattern. this would mean that all presses would play at 1/16’s or whatever your clock-in rate is, for example.

3 Likes

https://soundcloud.com/joekehoe/0006-normalized-trimmed-converted

another pre work morning improv, free running op-z arepegiator recorded into the buffer. when these come out OK it seems to to secure the vibe for the rest of the day, very thankful! a couple minor thoughts below

bugs:
-at 30 and 59 seconds in on this file, it feels like the tape file lost a couple of ms? resulting in a click. not completely sure, and not a huge deal. didn’t edit them out just in case it’s of interest. with reverb and compression on, the script may be slightly overtaxing stock norns?

-i totally broke the arc pattern recorders. not sure how, but they didn’t work at all. (everything else is super smooth!)

ui suggestion:
-consider banning alt from affecting the pad banks. at a certain point in the recording you hear me holding alt to control the filter of bank a while trying to play a pattern into bank b and totally overwriting the pattern instead of playing it… (alt+pad is just used for copy/paste at the moment i think? which i love and use, but maybe could be done with a long press or something?)

8 Likes