#101

Still having issues with Y / J chains. (Sometimes they stop ‘working’ (i.e wont output the input)).
I’m also getting some broken cells when modulating inputs of the U-OP right now.

I have a question on the ^ OP; Everything stops when I put this anywhere - is it doing that intentionally?

edit: Saw you released another fix after I DL’ed and that has fixed the issues I mention here above

(This port is absolutely amazing by the way - thank you so much.)

U-OP when set to 0UX it still outputs as if it was set to 1UX. It should be muted when set to 0, right?

#102

(check out my post in the Latest tracks thread - this thing is so much fun with the sequencer engine as well & haven’t even started on the grid and soft cut stuff properly yet :slight_smile: )

#103

buttons mapped to hand trigger samples with the < operator.

What I also did was use a few ^ random note operators to randomly change the pitch scale so when the button is pressed you get different notes. It’s worth adding a random sample also per button press for more variety.

33 Likes, 3 Comments - mudlogger (@mlogger) on Instagram: “buttons mapped to hand trigger samples using the < grid operator in #ORCΛ #livecoding #sequencer on…”

15 Likes
#104

Shiiiiiet that is cool.

4 Likes
#105

When you add the Softcut looper to that patch it gets more interesting and turns into an instant drunk jazz drummer :slight_smile:

I am feeding the looper with drum hits to make wonky rhythmic things. Softcut is holding what I feed and randomly scrubbing / pitchshifting what I recorded, all from inside Orca. You start to get into live looping territory, triggered from the grid.

5 Likes
#106

Heres a 1 button patch

image
4DE34C66-0CDB-49E8-A532-CB5CD7D1E069.jpeg1936×1936 984 KB

Load a folder of 1 hit samples in the parameters menu - (“Load Folder” option).
The more varied the samples the better, it doesn’t necessarily need to be drum sounds.
Press the grid button a few times so you can hear your samples.
Now replace the “.” (above were the curser is) with a “z” in the Softcut code line.
Press the grid button a few times (not too many - 3 or 4 slow presses) to record into the buffer.
Press a couple more times.
Sit back, listen, and pretend you are Autechre, Stockhausen or a very drunk jazz drummer depending on what samples you used :slight_smile:
To stop and clear the buffer, where you previously put the z - shift 8 - which is the * (manual bang) on my keyboard.

If you set this up so you are recording live into a DAW. Start with a couple of button presses and keep adding the odd button press every 30 seconds to build up the loop. If it gets too messy, just clear the buffer and rebuild your loop. You can jam this way without ever stopping. Before you know it you have a 4 minutes tune, that never really repeats.

21 Likes
#107

awsome code. having problems with < grid wont light up and wont bang getting these errors in maiden:-

lua:
/home/we/dust/code/orca/orca.lua:194: bad argument #1 to ‘lower’ (string expected, got nil)
stack traceback:
[C]: in function ‘string.lower’
/home/we/dust/code/orca/orca.lua:194: in method ‘listen’
/home/we/dust/code/orca/lib/library/_grid_read.lua:21: in local ‘op’
/home/we/dust/code/orca/orca.lua:411: in method ‘operate’
/home/we/dust/code/orca/orca.lua:434: in field ‘on_step’
/home/we/norns/lua/lib/beatclock.lua:70: in function ‘beatclock.advance_step’
/home/we/norns/lua/lib/beatclock.lua:76: in function ‘beatclock.tick’
/home/we/norns/lua/lib/beatclock.lua:22: in field ‘event’
/home/we/norns/lua/core/metro.lua:165: in function </home/we/norns/lua/core/metro.lua:162>

cheers :wink:

#108

When you load Orca what version does it say on the home screen?
Mine is v0.9.5 and Timber I’m using beta 3.
Also where are you downloading from?

I go here https://github.com/itsyourbedtime/orca/ and clone download.
I delete the orca folder on Norns.
Unzip, rename so its “orca” and drag everything over to Norns with Cyberduck by hand.
I don’t use Library at all.

#109

version says v0.9.9.4
I git cloned and then git pull to update.

#110

What i’ll do is update mine now and see what happens because i had another person contact me and say the < wasn’t working

#111

I updated to v0.9.9.4 and it was messy.
< isn’t working. My presets don’t load and it locks up Norns.
Going back to v0.9.5

#112

cool do you know which commit v0.9.5 is?

#113

No i’m not sure - this is what im using orca 0.9.5.zip (48.2 KB)

I’ve not been updating too much recently because my presets keep getting zapped with every update, and i’m losing stuff.

1 Like
#114

cheers, thanks a lot :smiley:

1 Like
#116

After some pestering of @mlogger on IG, I rebased and got it working with v0.9.6 (orca), but if I give a row or column number, in x & y respectively, the whole row or column lights up.

Once I pushed all the buttons to turn off the lights, the grid button associated with the < worked fine.

I hadn’t thought about updating Timber as well, but it seems like grid ops may be the culprit, he mentioned super gratefully. :grimacing:

1 Like
#117

Sorry for your issues (and broken patches)!
New version is up and i think its much more stable :surfing_man:

Whole row / column lits and acts as a slider if no row/col specified. You can bang empty > operator to clear unused buttons

3 Likes
#118

Yay @ fixes! Thank you!

Would it be possible to have a function like the ^ operator that will only trigger when banged?

Edit; changing the rate of ^ does not do anything for me, maybe im using it wrong?

Btw, is there a list somewhere with all the available scales on Norns? Otherwise ill try to make one I think.

#119

this is a demo of 2 way grid operator patch. There is a different sample placed in each grid row using the <operator (you can see a faded button). Then a >operator randomly triggers each row

This is the < op

image
835C4D1D-4CD3-4137-A32E-548BDBE66279.jpeg1936×1936 792 KB

This is 2 of the > op buttons triggering samples

image
23B45111-F0A9-4469-BD14-136AD512A1FD.jpeg1936×1936 749 KB

6 Likes
#120

Hey Campers! I am trying to use the grid to enable and then disable a D function. In other words, hit a button and D starts banging a sample. Either hit the same button again or another button and disable D, or stop the flow of bangs (triggering a looping sample in Timber).

For instance, I thought I could have one button remote write a ‘0’ into the mod side of D, then have another button write an 8 into the same local, but it doesn’t appear that you can have multiple X functions write into the same slot AND I can’t get x to generate it’s operand only when banged, like:

11<
… *
24x8

Any other ideas?

#121

I wonder if the T (tracker) op would do the trick here. In theory, this should work:

...11>........
.....*........
.....c2.......
......12T80...
.......D8.....
.......*'02C..

The T op above D has 2 values - 0 and 8 - and then we’re using a lower case c (counter) to change the index of the tracker. That c will increment only if it’s banged, so in this case we use the grid op to do so above, using just one button.

Worth a shot, though I do think I read somewhere that lower-case ops on the Norns version don’t all quite work yet. That could have changed with a recent update, though.