#225

not sure if this is possible currently or not but when using random patterns is it possible to limit the range of certain params that are manipulated when creating a random pattern. Pitch for instance would be nice to set ranges

#226

no. for the reasons that dan already mentioned, and more.

if everyone likes Greyhole much more than the current standard output reverb, we can just replace it. greyhole and the standard reverb are both faust programs. greyhole is more expensive.

#227

I guess I’m confused now. I thought I understood why, but perhaps not.
Then, how is possible you can send to the delay that’s part of CC? Why couldn’t something like greyhole be used for the same purposes?

I understand why we can’t send to the master reverb, but I mean a new one that’s internal (like the delay, which isn’t part of the master FX)

#228

the delays within cheat codes are softcut voices.
cheat codes does nothing but manipulate softcut parameters.
softcut does not include an internal arbitrary effects chain.
individual softcut voices do not have their own outputs to supercollider or the norns mixer client.

crone process routing (mixer client and softcut client):
crone-process-routing.pdf (49.3 KB)

softcut internal routing:
softcut-routing.pdf (45.7 KB)

and here is the JACK connection graph:

jack_connections
jack_connections927×745 92.6 KB

3 Likes
#229

I like the current reverb as the default one! Greyhole is awesome but much more a niche/opinionated effect, I’d say.

3 Likes
#230

ahhh, I see. So, there’s no way to achieve an fx send setup for FX then?
Also, thank you for the amazing detailed reply. That helped a lot.

1 Like
#231

pretty much, yes — softcut is the only sound engine of cheat codes (cheat codes is, at its core, a hopefully very playable interface for softcut and a way to quickly program softcut through gesture rather than code). softcut’s position in the mixer chain doesn’t expose it to being routed through anything besides the built-in fx. that means the on-board reverb and the on-board compressor.

the delay effect is just taking advantage of softcut’s inter-voice routing. that said, i am excited by the prospect of showcasing softcut’s very broad and wild possibilities by extending the delay i cobbled together for cheat codes and allowing it to be a destination for further sonic exploration.

i am embarking on a massive overhaul of the code — with @Galapagoose’s guidance, i’ve already cut 400 lines out of its 5000. in a bit, cheat codes will be primed for approachable re-configuration :slight_smile:

edit! the above will make this:

super duper easy to reconfigure :slight_smile:

14 Likes
< codebreaking >: cheat codes livestreams
#232

this is sick
not sure why it excites me so much but i love hearing things like this

5 Likes
#233

I love hearing about people revisiting and refining complex machinery like this. When someone describes moving game engines, or why they updated versions or even why they changed what metal alloys they us in their work/product/process, I sink in to my seat and become prepared to listen to someone so much smarter than me teach me about what they love.

1 Like
#234

Thanks the patch is amazing!

One thing I’m having troubles with is saving presets or I dont understand how they work :slight_smile: I wish they would save the position of a loop and clips that I loaded. Is it possible? I’m not using grid, just loading a sample into 1 of 3 timelines.

#235

thanks for the kind words!

totally possible! the section about collections in the manual covers all of this :slight_smile:

please lmk if u run into any other trouble!

1 Like
#236

Oh! I was using the preset menu, the one below edit I think. Awesome!!! The script is insane and even has a manual. DOPE

1 Like
#237

I searched the manual but can’t work out how to toggle a pad’s play mode between 1-shot and loop. Could someone help please?

#238

hey! oh, weird. where did that go from the manual? apologies!

it’s the * key:

image
image376×762 9.29 KB

as always, ALT + * toggles loop/1-shot for every pad in the bank

1 Like
#239

Fantastic - thanks Dan :+1:

1 Like
#240

TouchOSC has the option to send accelerometer info (/accxyz). Would be nice to turn them into system parameter OSC events.

X Y and Z axis could be the three loop positions or playback rate, for example. I’ll give it a try later on.

I was thinking on further interaction with Holon.ist app where you can send OSC or MIDI based on all kinds of sensors, like heart rate to bpm.

1 Like
#241

agreed! these futures have all been highly motivating to the current code slashing efforts :slight_smile: ( i personally want to see sensors + dancer [!!] ). thank you for your enthusiasm and work on this avenue!

it may make sense to hold on deep OSC exploration (/time investment, as mostly everything will need a bit of remaking) until 1.4 – 1.3 (dropping tomorrow? sunday latest?) has already had something like 2k lines removed, 1.4 will focus on streamlining all the actions to terse descriptors (tytytyty @Galapagoose) and will be the perfect jumping off point for alt interface joy :sparkles:

{so many parentheses!}

5 Likes
#242

Funny this is exactly what I’m looking to implement, with Movesense’s sensor and the app it’d be instant!
I also have a midi to cv which I could use to control modular with my dancer’s movements.
My other parter in this specific project is a violinist. The intensity already modifies parameters on rack but I wanted to add a sensor to the bow as well. Link all this to visuals and you have a big interconnected A/V experience.
So many possibilities!

Can’t wait!

#243

wait no longer!

v1.3 thread

per usual, closing this one to streamline energy :sunny:

#244