#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
#271

hey! I tried that but I think what it does is move the loop points around in the bank of pads I’m trying to use for the overdub. I’m trying to use the looping pad in one bank as tempo for one shot bits from another clip. Not sure how to apply pad sync to this scenario as that command seems to change the playback windows of pads to match up, when I rather like the length and trim of this bank of unlooped audio bits as is?

I’m looping one pad, and trying to pattern record from another bank for overdub.

#272

gotcha re: loop point syncing not being the solution. the thing we’re trying to solve is still a little unclear to me, apologies!

so you have a pad that’s looping and you want to use that loop duration as the timebase for a pattern recorder where you record yourself pressing different pads and play it back? eg. you have a single pad looping 600ms of audio, so you want the pattern recorder to record at 100bpm so a bar of a recorded pattern would line up with the length of a single pad looping?

or is it that you have a pad that’s looping and you want the Live buffer loop points to match it so you can overdub that pad’s loop exactly?

or something else? i think i’m perhaps confused by what you mean by “overdub”.

1 Like
#273

this!

”overdub” is confusing perhaps that would involve playing additional segments from the same bank? the looping is in a bank of its own with just a single pad looping.

is this something better suited for the kria-style sequencer?

the pattern recording from the next bank is drifting. any better understanding of how one might quantize it is what I’m looking for! thank you a million.

#274

gotcha gotcha – that definitely isn’t a function in cheat codes 1.3.1. that could maybe get brought into 2.1, as it’ll require a bit more intentionality than I can give at the moment.

if you’re recording in “loose” mode, this’ll happen – the kria-style sequencer would help with this, where a reset could be planned on a steady clock tick. that does sorta get you back to the original problem, tho, if the artist’s sense of the clock is being dictated by a looping bit of audio (whose bpm is unknown) rather than an actual clock tick. this question of using a fundamentally unsynced thing to tightly sync other things has come up a few times and remains the script’s white whale, so i’ll definitely be giving it good thought soon (literally just had an idea lol) :slight_smile:

otherwise, quant+trim should get you clock-synced loops with no trouble.

good stuff to mull over, thank you for posting it + spending the time clarifying!

1 Like
#275

nice! will have a look. I’m sure this is the smart way of achieving the same thing.

#276

Hi all. I’m trying to control cheat codes without grid, but can’t seem to get it to work. Any ideas? I’ve tried downloading Touchocs, but can’t seem to get it to work. Is there a way to enable rec buffer without grid? Thanks

#277

Upon loading, the buffers are not armed, meaning all of the loops are empty.

From the clip loop page, hold down key 1, then press key 3, that’ll take you to the buffers page. Then pressing key 2 I believe (these could all be the wrong kets, but I’m pretty sure) to scroll down to the record buffer. You can arm recording from there. This way the looped portions will begin to have information in the buffer to playback.

I don’t know how on TouchOSC to get the loops/pads to refer to the clip buffer (if you’re loading clips), but the manual should get you there on that. touch OSC info is towards the end.

1 Like
#278

depending on the trouble you’re running into with TouchOSC, we can definitely help – can you share more about what’s not working and what steps are needed to reproduce the issue?

generally, the TouchOSC template does have controls for enabled the rec buffer – they’re the three buttons in the bottom right corner.

@kasselvania is correct that you can also enable the rec buffer from the loops page, but the steps outlined are for a different version of cheat codes :slight_smile:. you’ll just need to hold K1 in the [loops] menu, use K3 to navigate down to the L1 section, and then you can:

  • use E1 to change which record buffer you’re recording into
  • use E2 to turn recording on/off
  • use E3 to adjust the total record time

hope this helps! it’s all a lot cleaner in cheat codes 2, which will be released shortly.

2 Likes
#279

20 characters of OOPS! Don’t mean to create confusion…

1 Like
#280

Many thanks… You saved my evening fun :wink:

1 Like
#281

Thanks so much. I’ll going to try it out now and thereafter read the manual :wink:

1 Like
#282

is it possible to delete the audio buffer without a grid?
i dont find anything. thanks


this script is fun! thanks !!
4 Likes
#283

hey mathias! lovely video, thank you for creating + sharing it :slight_smile:

in cheat codes 1, there is no quick way to delete the audio buffer without a grid, no. you could adjust the feedback setting to get a full overwrite, but that’s it.

thank you for the question about it – there will be a gridless option for this in cheat codes 2!

1 Like
#284

The more i dig into it, the more i love it… but i still have those annoying crunches, bleeps and noisy artifact… Am I the only one in this situation? Could it be related to a faulty hardware? Or perhaps a faulty SD card? (don’t know if the audio is streamed from the SD card…) I am using sample mostly, Thanks for any tips regarding this behaviour… cos’ damn I love the potential of this script!!! :slight_smile:

1 Like
#285

thanks for the positive vibes!

i’ve heard this happen with folks who aren’t using a strong enough power supply to their pi. you could also try doing a fresh install of the OS / swapping your SD card. are you using a fates or a norns shield?

1 Like