Sorry for ignorance, everything works. I thought it also worked with samples from the library instead I tried to record and everything is great :slight_smile:

it does – page 21 of the manual is all about how to change between live and clips without a grid.

basically:

  • on the [loops] page, hold K1
  • you’ll get to an alternate menu:

if you want to make all the pads in a bank use a sample from your audio library

  • use E1 to select pad 16 (this sets all the pads in the bank)
  • use E2 to change to Clip X (whatever clip slot you loaded your sample into in the PARAMETERS menu)
  • K3 will move to the next line

hope this helps! please ask any other questions you have :slight_smile:

1 Like

Simply great with TouschOSC and iphone❣️

5 Likes

The TouchOSC template also works with my Android tablet. But I had to deactivate “Bundle Messages” and “Send Ping”. Are these two options important?

(Thanks for Cheat Codes! :black_heart::control_knobs:)

5 Likes

ayyy, great to see you got up and running!

those two options gave me the best performance in testing, but if you got going with 'em off then no harm :slight_smile:

2 Likes

Hi! I was testing cheat codes with touch osc… so far it works flawlessly… but I’m experiencing serious glitch and clipping… any ideas why this is happening?
Thanks in advance!

oh, weird — any steps to reproduce the issue? also, any examples of what this means exactly? if you’re using a lot of random values, for example, there’s a chance a loop window would get very small. i can protect against this, but any detail would help identify :slight_smile:

1 Like

@dan_derks In fact, when I launch the script, just as the buffer starts to write, I hear glitches, like “pops” amplified by the reverb. And things get worth when I trigger loops via the trigger page on touch osc… just like a non zero crossing sample… perhaps this is due to my SD card… but it works flawlessly with any other softcut script…

I’ve got this working on my android phone (using the iPhone layout template, but the iPad works as well, if tiny) – but for whatever reason the pad indicator ‘dots’ won’t light/stay lit; likewise for the playback speed indicators. Sliders and everything else responds. The pads work, I just can’t tell which is active visually.

Anyone know why? Some touchosc setting, perhaps?

CHEAT CODES IS AMAZING @dan_derks thank you thank you thank you for bringing my little norns shield to life for me.

3 Likes

I also had this problem, but the following helped. In Cheat Codes / Parameters / OSC Setup there is an OSC port (not the IP), this number (which you can also change there) you have to take over as IN Port in the TouchOSC Android App.

3 Likes

ah. yep yep.

some info to help clarify:

  • the basic structure of cheat codes is a single write head and three read heads, all working on a shared buffer. this is part of the script’s core identity – record audio at 1x, read it with 3 different rates
  • the live audio buffer is segmented into three 8 second sections
  • if you have all three read heads pointed to the same section of the live buffer where the write head is actively writing, there will be a discontinuity every time any of the read heads passes over the write head
  • currently, this discontinuity resembles a pop. in a future norns update, softcut will duck level on the crossing playhead, so that the discontinuity is less disruptive
  • until then, the way around this is to not continuously loop-write to the live buffer – there’s a 1-shot record mode, which will fill the buffer with a single pass of audio and you won’t experience the pops.

as far as other softcut scripts, mlr and cranes couple read/write as a “default”, so they aren’t crossing over. those implement softcut to create different performance structures, though. also, their longer buffers help with less frequent crossings.

anyway, hope this helps and if you run into the same issues with non-looping recording or importing samples, let me know! :slight_smile:

1 Like

Absolutely useful! Thanks for those clarifications and insight explanation! I haven’t already wrapped my head around all the mechanics of cheat_codes… but from what I’ve understand, it’s amazing!
I gonna try this one shot record mode and let u know!
Thks again!

1 Like

No luck unfortunately. The incoming port was already set to 9000. I also don’t get the ‘page’ labels at the top of the touchosc template to switch between loops and pads. Not a big deal but curious why these small pieces aren’t working!

screenshot

Really, i feel a bit dumb to ask here for this… but after reading the manual, I haven’t found any significative answer…
When u use touch osc and set the buffer recording to 1-shot… with recording of this buffer stoped… how do you trig the recording on?

Feeling like a complete noob :confused:

on the larger ipad/table layout you just press the rec button corresponding to the buffer you want to record into, it’s the 3 round buttons bottom right.

2 Likes

Thanks :slight_smile: but unfortunately i’m using the iphone layout on my android phone :confused:
wanna check if i can use the ipad layout on my device!
EDIT : found it… sometime things are in front of your eyes… :slight_smile:

1 Like

I always feel a little bad making feature suggestions, given the unreal level of complexity baked into cc already, but —

Some kind of sidechain compression? Probably tough to do on the Lua side, but it would be so sweet to apply compression to one bank using another’s level.

On a non feature-request note, let me say that cc has (once again) pulled me out of a creative dead spot. Thanks again for all of your hard work on this, dan.

3 Likes

20 chars of :heart_eyes::heart_eyes::heart_eyes::heart_eyes::heart_eyes:. Though I’ll say, Izotope De-click works absolute wonders on this kind of thing (in case that’s helpful to anyone in the meantime).

2 Likes

Hi @dan_derks I wanted to ask you a question about the pan settings. note that there is no hard pan setting for the samples. that is, even if I carry a sample all on one side, the other channel feels attenuated. it’s normal? it is a choice to ensure mono compatibility? Thanks in advance:)

hey! could you provide some steps to reproduce the problem? you can definitely hard-pan the pads, so if you can share you’re approaching things, it would help clarify the trouble :slight_smile:

1 Like