#21

Damn! Nice work Dan… Thank you so much for all the hard work on this… F’en amazing program

1 Like
#22

I am seeing the same thing.

but also:

Loving exploring the new v1.2!
Thank you for the good works and generosity!
:facepunch::heart::clap:

1 Like
#23

getting addressed in a release later today :slight_smile:

addressed! @laborcamp + @SPIKE, feel free to pull in the changes from maiden.

@yoyosandshoes, the clear function has been adjusted so it doesn’t clear unintended Clips, but full functionality still not there for Live buffer – waiting on upstream confirmation that the softcut function generally works as expected.

thanks for exploring!! excited to hear what you make!

3 Likes
#24

Awesome!
This thing is pushing me to buy Grid. It’s another animal.

Thanks a ton Dan!

3 Likes
#25

@dan_derks
just another idea…

was wondering…is there a way to put a start timer on the recording buffer?

kinda like a simple countdown on a camera timer for setting up a photo.

reason i ask…
sometimes i find myself trying to create noiz with percussion or another touch synth while trying to record into Cheat Codes.

having 3-5 seconds before it starts recording would be very helpful.

1 Like
#26

@dan_derks, looks like copypasta, blind possible fix here

1 Like
#27

Thanks for this, it’s endlessly inspiring.

Thanks especially for the ongoing updates to the manual. What a fantastic resource! I was using an older manual and couldn’t figure out how to clear a live buffer… but printing off the 1.2 version got me there and more. What an effort to establish and support a community around this software. I appreciate it.

2 Likes
#28

Now that I’m thinking about printing myself the manual, like I do for my new modules, would this be a good time to do this floor Cheat Codes? Or do we see more features coming soon?

#29

You never know with Dan Derks, you think it’s perfect but he doesn’t. :grinning:

6 Likes
#30

Is there a way to stop monitoring input signal? Like 100% wet CC?

I haven’t seen it.

#31

thanks for the kind words, y’all!

re: manual, it’s pretty firmed up – there won’t be any super big changes for a little while, but there will be refinements. if folks are committing physical resources, i’m going to start including a summary sheet of changes with each new manual version – that way, you can just have a quick overview of the differences between the one you printed and the next one(s). no reason to re-print all that just for a few sentences.

i’m also going to be releasing some videos to supplement the manual, so you can always catch up on changes there too :slight_smile:

all on the global LEVELS page (if you exit cheat codes and spin E1 to the left, it’s the first page) – you’ll want to turn mon down.

you can also use SYSTEM > AUDIO > monitor.

12 Likes
#32

Excited for the videos! And I haven’t looked at the manual, but a reference sheet that is just Zilchmo commands will be y’all useful (I think we have that…?)

As for the commands for full input and not, this seems like something that will be able to controller better once midi global commands become a thing.

#33

indeed, in the manual:

image
image874×1534 56.6 KB

3 Likes
#34

I really should check more before I respond. Thanks kindly for thinking 2 steps ahead, my friend!

I’m actually working on a patch that is mainly teletype and cheat codes as the driving forces. If it turns it to something other than gobbledygook I will share! But really, no promises there. Lol

#35

I just tried out the random pattern function and YOOOOO it’s amazing!
A few questions:

  • I can’t quite tell how long the patterns are that it makes. Sometimes them seem quite long and other times the loops are more recognizable and shorter, but it’s hard to tell in general. Is the length controllable? That leads me to my next question:
  • The manual says the random function “works in conjunction with the [timing] modes”. Is that explained anywhere? Or would you mind if not?

Thanks @dan_derks!

2 Likes
#36

it’s definitely the most fun “let’s see if this works” feature :slight_smile:
as such, it’s in it’s infancy.

right now:

  • random patterns changes rate/start-point/end-point of every pad
  • random patterns are made of anywhere from 2 to 24 events
  • each event can have length of 1/16th note through to 1 bar at the current bpm

so, entirely possible to get a pattern that’s 24 bars or just two sixteenth notes. (random, baby!)

will add:

  • breakouts for those random parameters, cuz sometimes I want random timings but I want to keep my pads set up the way they are
  • some sort of length interface to say “I want this many bars/events/etc”

the way [timing] and random patterns work together is pretty close to how hand-recording a pattern works with [timing] – I had a false start with making a video to illustrate, hoping to get that done this weekend, sorry y’all!

  • loose: a random sequence is generated and played back without modification. uses its own metro instead of listening to the main clock tick, so there’s some wiggles and wandering to the timing. definitely the wildcard option.
  • distro: a random pattern is generated, but is contained within the closest whole bar count at the current bpm – so if you generate a random function at 120bpm with ‘distro’ mode, it is guaranteed to last some multiple of 2 seconds. the fuzzy clock option, because it uses its own metro, but its total duration is more “synced” than the ‘loose’ mode.
  • quant: a random sequence is generated and the events are executed exclusively on the main clock tick. very steady, not wandery, nice to do two patterns with ‘quant’ and hear them phase if they’re not the same duration.
  • quant+trim: a random sequence is generated and the events are quant’d and the pattern is contained within the closest whole bar count at the current bpm. super tight timing, super clean x-bar loop.

tl;dr: if you’re making free-flowing ambient things where none of the patterns need to mesh, use ‘loose’ for everything. otherwise, I find it’s nice to start with a ‘quant’ or ‘quant+trim’ as a base layer and use ‘distro’ to pepper in shuffling rhythms. the v1.2 video up top heavily employs this approach.

hope this helps :revolving_hearts:

2 Likes
#37

Thanks for this info! It explains everything.
And those eventual additions sound great!

I’m sort of amazed at how much the randomization adds. I think it’s because you’re randomizing rate in addition to window that some really nice surprises occur that wound’t happen while manually programming.

One more question that I should probably already know: is there currently a way to trim down a sequence in length? Say the randomization makes a long sequence but the beginning is really good - is there a way to trim it down to x number of bars or whatever?

1 Like
#38

absolutely – it’s been super fun to start sessions with a random pattern and build around it. @swhic, thank you so much for asking about random in the old thread!

no, but pattern playback manipulation and inter-looping have definitely been on my mind. the pattern shuffle feature was a first step onto that road. the real thing I want to chase is a way to help gridless folks use the random patterning to deepen the usefulness of cheat codes in their process. a pattern management feature is a necessary component of that. it also opens up a buncha infrastructural q’s.

i’m sure i’ll start messing around with that soon :slight_smile:
thanks for the energy, ben :revolving_hearts:

oh, wait, duh. @deru, depending on your needs you can also just use the meta-sequencer for that bank for timed re-triggering.

1 Like
#40

No doubt you will :wink:
Thanks Dan!

#41

Question:

I have a situation where I am using the arc movement recording on one pad. Then when I select a different pad from the same bank, and have this looping, at some point the playback automatically switches to the pad that had the arc movement recording going. It appears to do that when the arc recording loops (when it starts over).

Is that an intended behavior?
Feels like a bug to me.

I am really into the arc movement, and love that these are now saved with collections!
(EDIT: I swear I had one loaded after a save/restart… but now starting again I don’t see the arc recording loading… maybe this did not make it into the update after all?)

ALSO:

when setting up loop points is there a way to have the loop durations “snap” to incremental divisions of the session BPM?

1 Like