#186

no problem :slight_smile: it was the managed reverb that did not allow you to perform a sample HARD Pan:)

Thanks

1 Like
#187

ah! perfect – yes, the reverb will make it sound like a hard-panned pad is not fully hard-panned. thank you for writing back!

1 Like
#188

Thanks to you fo this amazing script! Grazie ancora

1 Like
#189

Hi,

after having watched the cheat codes live stream from 2nd of may two times (great video with loads of details and funny comments!) and some work with cheat codes on my own I am really impressed by this nice piece of hard work. Thanks a lot for that @dan_derks ! I especially like that I will now be able to gradually find out how I can integrate norns (hardware in my case: fates) with Sonic Pi live coding as I can clock norns externally using midi. I did some testing and thanks to the mentioned video I now know how to use the live recording buffer. This is all done very nicely.

There is one question I have not been able to give an answer to. In the video at around 23:15 you show how to set the recording end cursor (not quite sure how you label that) to set 1, 2 or 3 bars recording length. Now I was under the impression that you can move the cursor right to the end in order to record 4 bars. But that, as far as I see, is not possible. Is this a feature that if you set rec loop enc resolution to bar, you can only address three-quarter of the live recording buffer? Or have I missed something completely due to my lack of experience in using cheat codes?

1 Like
#190

hey hey! thanks for the kind words – i’m glad the video has helped, will do another one for this next release, as well :slight_smile:. excited to hear what you make with it! please note that there is a bug with the rec loop enc resolution and external clocking, which resets the length – it’s addressed in the upcoming version, but a temporary fix has been posted here: [cheat codes]: v1.3.1 (May 4, 2020)

it all depends on your current tempo and whether or not you’ve set the recording buffer to 8, 16 or 32 seconds.

for example: 95 bpm = ~2.52 seconds per bar. with the 8 second buffer setting, you only can fit 3 full bars (~7.56 seconds). if you switch the live buffer to 16 second mode, then you’ll fit 6 whole bars. 32 seconds will fit 12 whole bars.

to switch the buffer length:

  • navigate to [loops]
  • press and hold K1 until the screen switches
  • use K3 to navigate down to the recording buffer and use E3 to select between 8/16/32

please let me know if you have any other questions!

#191

Hi @dan_derks,

thanks for the prompt feedback. Yes, that makes totally sense. I keep forgetting that the recording buffer is basically real time-based (Sonic Pi has comparable functions but also very easily allows using beat/bpm-based time settings; that’s why I keep forgetting that).

I will have to check this out (will not be able to work on it until earliest tomorrow)… Though, I did use the default, which is 8 seconds, right? I also set the clock to 120 bpm so I reckon I should have 4 bars available (but I had 3). Or am I wrong?

If that is due to the bug you mentioned I will install the fix as soon as possible and it’ll be resolved.

Thanks again for your kindness :slight_smile:

#192

ah, no no, you’re right. i totally missed an <= (was just using <). thanks for finding this!

if you want immediate fix, line 247 of encoder_actions.lua needs to read:

elseif d > 0 and rec.end_point+((d/rec_loop_enc_resolution)/lbr[params:get("live_buff_rate")]) <= 9+(8*(rec.clip-1)) then

guh. i need to refactor that encoder_actions file something fierce :slight_smile:

1 Like
#193

Oh, great! Will apply that the next time I have time to cheat codes :wink: .

1 Like
#194

Hi, I had the chance to apply both ‘updates’ and now everything works as expected. Now it is only a matter of time, work and fun until I will arrive at something which you can call music… :slight_smile:

2 Likes
#195

got my norns and sp303 as permanent send / return devices in ableton. my favorite in studio/ making music setup ever !!

3 Likes
#196

increase pad level resolution? :slightly_smiling_face:

1 Like
#197

Gone from toe deep in CC to knee deep.
Watched the video twice (recommended! to glean even more tidibits) and read the manual several times. Think I added “dope!” to my lexicon
Wow. CC is impressive!

Just curious - as I learn more about what the norns can do with its built it engines, could it ever perform warping in the future?

-Eric

1 Like
#198

damn that’s fire. what’s going on there? did you chop up a sample in cheat codes and sync it with some ableton drums? either way, good work

1 Like
#199

thanks to @Galapagoose, wicked easy!

lib > zilchmos.lua, lines 53 and 54. current resolution is 0.125, so maybe 0.1 would give a bit more resolution without having to press a ton? either way, you’d just replace the second argument in z.level_inc in each of those lines, eg:

function z.level_down( pad ) z.level_inc( pad, -0.1 ) end
function z.level_up( pad )   z.level_inc( pad, 0.1 ) end

you could also redefine z.level_inc further down to scale values, so that you get a curve to it…

dooooope :slight_smile:

this isn’t really part of softcut’s built-in functions, but time-stretch techniques have been discussed here: Softcut - time streeeeetch?. from my perspective, it’d be a small conceptual break for cheat codes to employ time-stretch, as it’s really designed for chopping / slicing / restitching (which can all be done to a clock). mlr or cranes might fit the bill for that sort of feature, tho :slight_smile:

3 Likes
#200

yea this exactly!
just had norns as an external send effect…
chopped the sample in there and added drums on top…
with link, it’s really amazing being so in sync

3 Likes
#201

Might have been asked before, cant find it…in random mode pad’s time length is limited? Thanks!

#202

@dan_derks do we have auto advance feature implemented? I can’t find how to do it? Many thanks

#203

both implemented in coming update!

making good progress, just lots of small tweaky things that need addressed for the smoothest release possible. this will be the mother, though, and i’m excited to get it out right :slight_smile:

13 Likes
#204

forgive stupidity. getting super deep into CC and loving it!
ready to let the “bruise blood out” (deep cut. hope y’all get it)
Can’t quite figure how to use “loop sync across banks” - it restarts the loop but doens’t seem to sync to any other bank. Can someone explain this feature?
many thanks fellow noise nerds! :crazy_face:
Eric

2 Likes
#205

ayy! glad to hear you’re diggin in :slight_smile:

loop sync across banks will match the current loop points of bank to the loop points of another. which one depends on the gesture.

x x x -: sync to previous bank
- x x x: sync to next bank

let’s say you have these loop points:

a |------|------------------
b -----------|---|----------
c ---------|-----------|----

performing x x x - in bank b will sync loop b’s current points to bank a (since a is “previous” to b):

a |------|------------------
b |------|------------------
c ---------|-----------|----

performing - x x x in bank b will sync loop b’s current loop points to bank c (since c is “next” after b:

a |------|------------------
b ---------|-----------|----
c ---------|-----------|----

the prev/next logic works out as:
a: prev = c, next = b
b: prev = a, next = c
c: prev = b, next = a

hope this helps! i’m really glad you brought this up because I just successfully added variable clip length import (up to 32 seconds) and this needs looked at for the upcoming release :slight_smile:

6 Likes