#251

oh! apologies, the youtube video is a bit behind. if you change the rec mode to quant, that will sync to whatever the params > clock setting is. so if that’s set to midi, then quant will also sync to incoming midi :slight_smile:

the manual should be updated to reflect this workflow, plz lmk if u run into any more trouble!

1 Like
#252

Phew!

Thanks for clarifying. Been making my way through the manual. Can’t wait to dig in tomorrow! Gonna be a good day :slight_smile:

Nick

1 Like
#253

a lot of my samples are less loops and more single key, one shot or pad chords. What is some way of setting different pitches for a clip across its pads? not doing too much live input as it is. I’m sure there is something I missed beyond global pitch shift for clips. mostly get (wild) pitch shifting using random. spent a few hours trying to dig into this next to the manual (which is beautiful I really need to print this thing). something in there’s eluded me. any help appreciated! thanks so much.

#254

hey hey!

you can control the range of random pitches using encoder 3 on the rand pat [K3] item in the [timing] menu (use enc2 to scroll down the timing menu).

are you using a grid with cheat codes? you can easily get half-pitch and double-pitch (0.125x to 4x) using the fourth row zilchmo gestures outlined in the manual. you can also get “fifth-up” rates by pressing all four buttons on zilchmo’s fourth row.

otherwise, you can hold key 1 on the [loops] page and you’ll find a per-pad semitone offset parameter :slight_smile: that is specific per pad, so if you don’t have a grid you can use enc1 to scroll between pads – if you do have a grid you can just select a pad and change the semitone offset (-36st to + 24st). zilchmo row 4 gestures will perform additional halving or doubling from that offset, as well. you should be able to get into some nice zones.

lmk if this is unclear / if you have any other q’s!

1 Like
#255

oh yes I have an arc and grid. so ahhh there’s a row in the zilchmo slice I’ve barely touched. been a little too careful trying not to mess anything up. so if I derive a key from my samples is there some typical way I would want to tune them in CC, if that makes sense? also some slices will inherently just be the nearly silent decay part, can I save edits made to individual clips if I trim them for loop positions? there’s some smarter auto slice thing going only if I’d remembered where that is mentioned, right? it seems like my folder of OP-1 drum wavs would work better here rather than three variations of a snare (as CC works with three wavs per set). hopefully I’m not messing up the terminology in use/thinking out loud too much. Thanks for being so supportive @dan_derks! thank you lllllllines for all this space.

2 Likes
#256

ooo, i think i understand!

this will be best solved by cheat codes 2, which allows for up to 32 second sample import time + has a super direct “evenly slice the clip across the 16 pads” function.

once it’s out (2 weeks!), i’d say the best workflow for “i have a ton of very short 1-shot samples that I just want to mess with” would be:

  • if you have a collection of one-shots, lay 16 of them out in a DAW allocating two seconds of per sample (that’ll get you to 32 seconds). export the whole shebang as a single 48khz wav file.
  • that file will be one of the clips in cheat codes – so you can do this with process two more times, if you want to have 48 one-shot samples mapped across the three banks of 16 pads
  • load the file(s) as a clip(s) in cheat codes and assign a bank(s) to it(…s)
  • you’ll do the quick action on the grid to evenly slice the imported clip across the 16 pads – once for each bank
  • then, you can just go wild!

the best workflow for “i have a couple of longer 1-shot samples, like pads and single notes, etc” would be:

  • lay as many of them out in a DAW as possible – up to 32 seconds – and export the whole shebang as a single 48khz wav file
  • load that as a clip in cheat codes and assign a bank to it
  • use the encoders on the [loops] page to establish your loop points for each section (eg. if you have four longer 1-shots then i’d say set the first four pads to each of those sections)
  • copy/paste the first four pads into the rest of the pads
  • for pitching…
    • use [x][x][ ][x] or [x][ ][x][x] on zilchmo row 4 to either halve or double pitch for each pad
    • use the [loops] submenu to change the semitone offset for each pad
  • then, you can just go wild!

super weird hack: because you can go down to -24st with the global offset and another -36st from there, you could feasibly take a 17 minute file, pitch it up 32x in Audacity to get it down to a 32 second file and then compensate for the difference in cheat codes. it’ll get some really nice aliasing in the process :wink:

but yeah, in short, you definitely want to have a single file with a ton of sounds in it rather than files for each individual sound, because cheat codes works with three sample files.

also:

hopefully cheat codes 2 will help you feel freer to mash stuff up and get into the weird – i’ll continue to do the codebreaking sessions to highlight performance techniques and any process q’s that come up :slight_smile:

7 Likes
#257

Hi Dan, has the varied loop length in random mode implemented? I can’t seem to find it. Of course there is random note length which is super but do I miss something? Many many thanks for all your amazing v2 work man!

#258

hey hey!

remind me what this was? i couldn’t find any past discussion on it, but it sounds cool :slight_smile:

are you hoping for a way to say “i want x beats of random patterns”? is that the loop length you mean?

also, are you already on the beta? random note length stuff is beta-land. if so, let’s take this to the codebreaking thread :revolving_hearts:

1 Like
#259

Today after some time I reopened CC connected to the OSC template on ipad, I load the samples in the buffer but these last ones do not play.
visually everything works but it seems to be unable to load samples. What am I wrong about? Isn’t it enough to just load the loops and play?

thanks

#260

hey! welcome back :slight_smile:

cheat codes 1.3.1 defaults all the banks to the live buffer, so you just need to tell the banks to use the clip slot(s) with the sample(s) you loaded:

  • go to [loops]
  • hold key1 to get to the alt page
  • use encoder 1 to select pad 16 (which changes all pads in a bank)
  • use encoder 2 to switch to whichever clip slot you loaded the sample into

that should be it :slight_smile:. lmk if you run into further trouble?

1 Like
#261

Ho Thanks <3 all ok
I did not remember the passage of the secondary page (ALT)

1 Like
#262

this’ll be cleaner in cheat codes 2! thanks for the patience + communication :slight_smile:

4 Likes
#263

thank you for this awesome app:)

1 Like
#264

Looking at the parameters / manual control it appears zilchmo changes to all pads in a group don’t update here. So if I change the rate of all pads in group ©, the value on screen for rate doesn’t update live in the parameters / manual control view, prior to another © pad being pressed. Is there any other place outside of here and the help view that I can see what the current rate is? is there some type of rate reset (or perhaps a reset the whole clip to the way it was once loaded?) do I just load the clip again? perhaps a common pitfall is restarting the CC script after fiddling with start and end points (I just did :blush:) time for me to learn how to start saving the current state. thank you!

#265

true! those params screens are updated with a new pad selection if they aren’t updated directly — they’re designed to be midi controlled. BUT all to say, cheat codes 2 will have rates clearly displayed on the loops page :slight_smile:

save state with a collection — that pulls in everything for quick restoration

and reset rate with the grid ALT key + the button just to the left of the third zilchmo row!

(@accountboy, tagging you because i edited :slight_smile: )

1 Like
#266

Hey Dan!

Wondering if there’s a way to create “sections” in each audio buffer to add multiple (previously recorded) audio clips into one buffer. Similar to your segmenting workflow for recording live into the buffer where you are splitting the buffer up evenly into four sections, for example. Love that idea of stretching out each buffer to enable more sounds to be in a single buffer.

Thanks!
Nick

#267

hey nick! glad you’re digging the script :slight_smile:

cheat codes 2 will support clip imports up to 32 seconds in length, though no mechanism for targeted upload – maybe a good 2.1 project, but also if you’re working with pre-recorded clips i think this extended import time makes it feasible to stitch a few clips together in audacity and import in a franken-file.

i guess this is sorta what i suggested upthread, but hopefully feels useful?

#268

Sweet!

That’s the workflow I’ve been doing. Multiple sounds bounced as one file from the comp. That’ll work for sure.

Nick

1 Like
#269

So I made 7-8 second clips of module noodles, I realised that was a lot more fun for fodder than ”how do I get my pad sample one shots to become nice clips?”

I’m also navigating my way around the first page and the app itself a lot better than three or five weeks ago, cool!! Learning curve is neat and the sound is awesome.

Auto-slice is for Live buffer only? The alt + first button under bank pads-command seems to select clip a, or is it live buffer a? I haven’t (intentionally) messed with live buffers yet…

I just set a really small segment on a pad to a loop. How do I record pads in other banks to that particular loop tempo? The global tempo is for stuff like sequencer (not there yet) and delay I guess?

Thanks!

1 Like
#270

hey hey! awesome progress report! :slight_smile:

pretty much – it’s a half-bug that got squashed in cheat codes 2. auto-slicing is front-and-center in this next version!

i’m reading this as you set some loop points and you’d like to use those same loop points for another pad in another bank? in cheat codes 1.3.1, it’s this process.

2 Likes