from what i can tell, this is the current behavior, though. lol. sorry, i just want to better understand so i can improve the experience or documentation, whichever could use some love :slight_smile:

so, at the start of a fresh session, I set my rec loop enc resolution to 1 bar. then, on the [loops] page:

  • the live buffer loop points snap to 1 bar duration at the current bpm
    |....|............
  • i record into that bar
    |~~~~|............
  • use encoder 1 to jump the record window to the next bar (the bar to the right) so that the end point of bar 1 becomes the start point of bar 2
    ~~~~|....|........
  • record into that next bar
    ~~~~|~~~~|........
  • now i have two bars of unique audio and can jump between them with encoder 1
    ~~~~|~~~~|........ or |~~~~|~~~~........
  • i can also use encoders 2 and 3 to expand the start point or end point by 1 bar (my current loop enc resolution)
    |~~~~~~~~|........
  • and use encoder 1 to jump the current record window (which is now 2 bars total) to the right
    ~~~~~~~~|........|

so, i can jump between perfect bars without ever having to touch the rec loop enc resolution param again – i just need to adjust the windows on my [loops] page.

this section of the livestream a few weeks ago (11:33 until ~15:30) tries to showcase this as well:

3 Likes

D’oh.

So I’ve misunderstood this entire thing :joy::clown_face:

But still got some nice results from it that made sense, haha😊

I’m gonna approach this again tomorrow and just play with it again, see what I’ll make of it and if it might help in your documentation somehow. Not that it’s not good, but perhaps something will come out of it of some use😊

2 Likes

EDIT: Made a video on it. Here’s what’s going on when it’s taking clock input. Every time it snaps, is when I start the sequencer from an external source.


So I had another go this morning. With and without clock input, sampling directly from Tape instead.

When sampling from Tape, it behaves exactly the way I expect it to, and in the way you describe. I’m like, okay. Now it works. I assumed I’d got something wrong, since your description matches how I thought it would work, and since it didn’t (for me) I was using it wrong, somehow.

So here’s what I did now -
When sampling from external source and taking clock, the buffer snaps back to its starting position all the time. Settings are identical as above. It just behaves differently, kind of twitches and shifts as well, as if it’s trying to break free :slight_smile: a bit of a nervous eye twitch going on there.

So exact same settings and workflow, only difference is external source and clock.

Is this expected behaviour? That the buffer zone behaves differently, depending on if it’s getting clock input or not?

If so, it’s not all that useful to me (but I totally get that it might be for others, so I’m not advocating for change here, just want to understand if I’m getting this right).

At any rate, I’ll wait for the next update and if this is still present, I’ll make a proper repro case and not keep flooding this thread.

1 Like

this was super clear, thank you! totally was able to repro on my side with these steps (the key being clock start) – this is the weirdest cc bug reported, deepest gratitude!

audio and clock source actually don’t matter – what’s happening is that i wrote cheat codes to dynamically resize a clock-synced loop whenever the bpm has changed, but i didn’t account for times when you might have manually resized the window to multiples or moved the window (why? idk. testing brain!)

so every time you restart your midi clock, the clocks are out of phase and need to adjust, which calls this function and snaps the start and end back to where they are when you first set this parameter.

dope, this is really approachable! omg i feel better, do u feel better? i’ll hit you back in an hour or two and thank you again for sticking through to repro! :slight_smile:

7 Likes

:blush::clap: lovely stuff. I’ll be around :blush:

1 Like

dope, here’s the fixed version: cc-fixed.zip (42.3 KB)

you should be able to resize and move the window around and not have those same hiccups. i’ve retained the automated-micro-adjustments-based-on-bpm, but now it knows how many multiples the loop is at.

doesn’t have a lot of other small fixes that i’ve brought into the dev branch, but fixes this very big one! i should have the new version of cheat codes for everyone by end of next week. i think it’ll be a 2.0? we’ll see.

8 Likes

Not sure if this is the right place for it but I just happened to notice cheat codes front and center on this new Sylvan Esso video :slight_smile:

19 Likes

Fantastic :clap: will try this out and report back :+1:

1 Like

Came here to post this. So cool. I always liked them and now I like them even more

I feel like I must be missing something obvious, but my loops aren’t looping. When I first load up my pads are all in loop mode (per the params), but they behave as 1-shots. going into params and playing with the settings doesn’t change anything.

if someone could tell me the obvious thing I’m doing wrong, that would be awesome.

if you’re gridless, this is a known trouble-spot that will be addressed in the coming 2.0 update. apologies for the speedbump!

this should help get you back to looping:

I think my confusion is manifold, but I was mistaking the buffer settings for the pad settings.

maybe it’s because the manual I have is out of date, but how do I switch the pad loop/1-shot settings on the grid?

ah, yes, makes sense

the * key in each section:

1 Like

17 Likes

excerpt from my opz+cc session today

17 Likes

duuuuuuuuuuuuuuuuuuuuuuuude…this is so so good, thank u for sharing (+++testing!)

2 Likes

thank you for making cheats and giving me some pointers as well

love this thing to death!

1 Like

i might just be an idiot, but is there a diagram like this that shows what every function is in graphic format? or maybe a video like the “cranes how to”? i have the manual, but i still don’t know how to pitch up or down, or even exactly what im doing with the record buffers. maybe im missing some original manual? i do need to revisit the livestream you did also, but i think a concise layout would help me if one exists.

sorry for the basic bruh moment

i could figure out the touchosc layout fine. that was very easy but i dont really see how that translates completely with the grid. im also just newly getting used to the grid in general

i haven’t read through the entire manual yet, so maybe this is my fault. i just kind of looked at the layout diagram in there and realized it didnt have a step by step legend and gave up

hey hey, no worries! there are 5 tutorial videos on my vimeo, which might help get you primed on how the grid interactions work. for example, here’s one all about the pitch up and down stuff:

i tried to supply this on pages 6 + 7, which show every possible combination for each zilchmo:

(pitch up/down would then be x x - x and x - x x on the fourth row of the zilchmo)

pages 8 + 9 cover all the buffer stuff you need.

cheat codes is pretty packed, but a linear reading of the manual should get you from a to z. pages 3 - 9 should get you 100% off the ground – you could spend many days just working through those interactions, without going into all the other stuff like pattern recorders and meta sequencing. there’s also a built-in help menu on the actual cheat codes interface ([ ? ]) that should help get you acclimated with the grid interface.

icymi, here’s the full manual:

lemme know how it goes!

10 Likes

devonwho dropped stems for fans who want to remix his classic track anti-ragequit

here’s my take on the song
[made w/ 5 sample stems -> opz + cheat codes in tandem]

4 Likes