#61


ableton, cheat codes and link are friends bro
some random 60s track on my hard drive and some drums… 15 minute fuck around…

using norns as a send return/device with link capabilities is insane!
good shit man…

23 Likes
#62

Wow… Auto advance.
This just keeps getting better.

2 Likes
#63

this line of thinking and the existing UI would make a nice starting point for a Rene v2 port :slight_smile: :grimacing:

2 Likes
#64

Another amazing update. I finally had time to get lost with the meta sequencer. Lots of potential.

Question/suggestion: with the random rec prob, could it be an idea(if it’s possible at all) to have a one shot random rev mode that keeps recording until the entire section of the buffer you’ve selected is filled with audio?

#65

First quick creation with Cheat Codes! Sampled a guitar loop (Cheat Codes synced to Blooper) and played the Grid live: https://www.instagram.com/p/B_5VI0CBNhx

6 Likes
#66

Wonderful. Love the rythmic vibes in this.

2 Likes
#67

hey ya @dan_derks!

been really digging into this new version of CC!

question…
during my broadcast a couple of nights ago i had a weird issue with bank 1.
i used your new bar recording and pad distro trick.
then i assigned all of the levels and panning for each pad.

while i was performing i noticed all of my levels would change when i would randomize the pattern in bank one.
is that supposed to happen?
generally all the levels were jumping back up in volume to the default state,

also…
a question/suggestion: would it be possible to add LFO control (particularly S&H) to panning or…is there a way to randomize the panning for an entire bank of pads?

thanks!!!

#68

thanks for sharing such dope artifacts @edison (that track found such a nice pocket) + @mbillz (the small phasing loops are very nice)!

to the q’s (apologies for delay!):

currently, you can reset the rate of a single pad by holding ALT + pressing the first unlit key to the left of zilchmo row 3. i’ll make that a global action, though.

i don’t think i fully grok this – could you share a bit more about it? :hugs:

yep, random patterns currently auto-level:

{ [0.125] = 1.75
, [0.25]  = 1.5
, [0.5]   = 1.25
, [1.0]   = 1.0
, [2.0]   = 0.75
, [4.0]   = 0.5 }

generally, this is because random patterns also randomize pitch – i found that a bunch of pads running at 4x and full-volume makes for a really uneven experience.

how about this:

  • a global auto-level toggle in params to turn this on/off
  • an option to get random patterns without also randomizing pitch (so that you can get really nice loops and one-shots chosen ahead of time and then use the random to jump across 'em)

about 4 minutes before i read your post, i wondered if LFOs would be nice to add :grinning:

you can currently randomize panning for an entire bank by holding grid-ALT and pressing all three pads in zilchmo’s 3rd row. if you add some slew to the panning (under params > manual control), one press gets you some nice movement as pads are switched. i’ll also be adding this zilchmo row to pattern recording.

4 Likes
#69

Ok. I had to draw to try and explain the “random rec one shot”

image
image3024×4032 3.05 MB

The rec head will keep passing through the selected part of the buffer until it is completely filled from start to end. So this means that it will keep recording until the buffer is filled. The randomization will decide how many passes it will need until it is filled, and when the selected part of the buffer is filled, the rec stops(as it does with normal one shot). Does this makes sense?

It is probably not the easiest thing to implement as the rec head would need some info of what parts of the buffer have been recorded on each pass.

1 Like
#70

ahhhh, this makes sense – thank you for the sketch!

it’s a cool idea for sure, i’ll do some thinking on it. there might be some middle ground between buffer sentience and making safe assumptions within constraints :slight_smile:

1 Like
#71

So! I have been having some interesting experiements and thoughts about Cheat Codes! I was thinking one really cool tool would be if we could have a Quantize function I’ve thought of (I know Cheat Codes hasn’t been built around quantization, but I keep having these desires to use it like a supped up SP-404!).

The function would basically work like this: Start point of the pad is unquantized and can be moved anywhere, but when editing the end point of the pad, it snaps to different divisions of ones BPM, so, you could quickly spin between 1/4, 1/8, 1/16 and so on. This, along with the proposed playthrough option would allow for some really cool layered samples and some swinging possibilities.

This could also be hella cool because you could add in different styles of time signatures. This along with the metasequencer could be used to create entirely generative, yet grooving tracks with a solid tempo throughout, especially when feeing in to the live buffer!

Does this make sense/seem plausible?

2 Likes
#72

it does this already!! zilchmo style dude!

2 Likes
#73

zilchmo does sorta cover this, but just to confirm…

this would sorta work like the rec loop enc resolution does, but only on the end points of the pad windows?

fwiw, i didn’t roll out the new options for play loop enc resolution because i needed a bit more time to sort out the most useful way to implement. if that’s what you mean, then this is a compelling direction to explore, for sure.

otherwise, zilchmo has this basically locked down:

  • grid-ALT + 3rd pad in 4th zilchmo slices all pads to 1/16th durations (OR use the new auto-slice feature)
  • grid-ALT + [1+3] pads in 4th zilchmo doubles the loop length to 1/8, 1/4, 1/2, 1 bar, 2 bar, etc by moving the start point
    grid-ALT + [2+4] pads in 4th zilchmo doubles the loop length to 1/8, 1/4, 1/2, 1 bar, 2 bar, etc by moving the end point <~~~~ this feels closest to what you want

and then use E1 on [loops] to slide the window along

1 Like
#74

Yeah, I was actually thinking that the Start of the loop is one of the most useful aspects of playback and needs to be freely adjustable, to get good crossings and the type of hit that might be desired for whatever the effect is, so adjusting the length in hard quantization mode to note signatures would probably be best handled with the END of the loop. Rarely do I have an end of a loop that is most important that I want to land on a beat. I find when working with quantized stuff, the initial hit is what is most important. Then, its looking at the end of the window to see how I like it. With this ability to alter just the end, it could also work for building the tension in a performance, begin with one bar, 1/2 note loops, 1/8 note loops as a build.

The resolution of the actual loop position on the buffer could work both as a fine tune or a quantize to musical measures as well. I could see it being really useful to have fine/non-quantized resolution to move just so slightly around the buffer, but if you’re working with something very in time in the live buffer, being able to know you’re goin to move in quantized chunks as well… I hope I’m doing this justice with my descriptions…

I’m going to give this input method you shared a try again. My one issue with this in the past is that after a while, a lot of the zilchmo commands become a bit tough to remember, and programming loop lengths this way can be a bit frustrating. Being able to set up the project I’m working on to a time signature, and have the encoders able to just flick through the pad lengths would allow for some flexibility and ease of alterations and explorations.

But I also totally understand that this is just my preferred way of working right now and is totally just some niche aspect of a script that is clearly meant for more freeform work! I had just found that I was using the encoders less and less for arranging my start/end points and realized I would love the ability to quickly and easily keep things in time while also easily altering them.

Once again though, I’ll give these a shot and as always, thanks for the great work!

1 Like
#75

I can’t get the cheat codes in sync with my Mutable instruments Yarns. My Yarns is sending a midi clock through a midi-usb converter (Uno) to the norns. The norns has the converter as first midi device. When im changing the speed on yarns it isnt changing the speed of CC also when im start stopping yarns it isnt start/stopping CC. Is there anything i need to setup? I already have norns clock on midi.

#76

hey hey!

just to confirm, when you change the speed on yarns you should see:

  • the tempo in PARAMS > CLOCK change to match (system-level awareness)
  • the counter on the [timing] screen change rate (script-level awareness)

are neither of these happening?

#77

I see the tempo on the params > clock page changing but it isn’t the same as the yarns clock. It actualy fluctuates a little bit around 24/25/26… This is getting wierder. Maybe there is something wrong on Yarns side.

#78

mmm, idk what yarns normally sends, but i believe the clock module on norns expects 24ppq. if you’re able to adjust this on yarns, that should help! lmk how it goes :slight_smile:

2 Likes
#79

Hi i started trying again this morning and norns doesnt react on any yarns clock division setting (also tried 24 ppq). I have the feeling that the m-audio uno doesnt send the clock to the usb or something like that :confused: Now i dont know if that is a norns or yarns problem (or the usb)

EDIT: seems like the problem is in the usb uno it is sending midi clock and start message but without any data. I also can’t update the yarns through midi with the Usb uno. Does anyone have any tips on usb midi converters for norns? I know a bit of topic :frowning:

#80

Fwiw - Midi clock/start/stop/continue do not send data bytes. It’s only a status byte for each of those

@bloc I am testing right now with an m-audio uno from Yarns to norns and I get clock/start/stop just fine. If I push the start/stop button on yarns I get those messages on norns and then clock sends/stops.

As a test I loaded cheat-codes and went to the params page, set source to midi, then started yarns and mashed on the tap tempo - I saw the tempo in CC change over time.

Perhaps it’s a Yarns setting that is not quite right?

1 Like