#81

One thing I totally missed was the Softcut Param ID’s because I never clicked the details tab

3 Likes
#82

It’s all coming together now…thanks!

1 Like
#83

I think it’s pitched playback 1-4 being forward and 5-9 reverse. I could be wrong though that’s what it sounds like to me.

1 Like
#84

hi there the timber operator ’ help file says Engine 1-sample 2-pitch 3-pitch 4-level 5-pos.
should there be 2 pitch controls?

#85

simple answer yes
but this may have changed (if posts above are correct )

@its_your_bedtime can you confirm?

#86

But I am still not 100% sure how this works, will it record on a bang? Play on a bang, do both on a bang? If the record level is first 9 and the soft cut is banged, then the record level is 0 will it just play whatever you have recorded? How long does it record for, until it has been banged again?

@mlogger the softcut params, what different input sources can be used? and what params does these have?

2 Likes
#87

I have to admit it’s trial and error for me as well, having spent some time trying to get things working last night. I wasn’t getting expected results with either of the softcut ops - / and \ - but I’m not sure if that’s due to me having an outdated version of the script or a murkier understanding of the ops/params than I imagined. I thought I had updated to the latest via Librarian :thinking:

I think that clear-cut, written examples of the ops would be helpful

2 Likes
#88

softcut / operator guide

Resets position on bang

Inputs

1. playhead ( 1 - 6): / required
2. rec (0 - z): 0 - off 1 - z - rec on + rec level / required
3. play (0 - 2): 0 - off 1 - forward 2 - reverse / required
4. level (0 - z): playhead volume
5. rate (0 - z): playhead rate
6. position (0 - z): playhead position

__

Forgot to update these help files, thanks!

15 Likes
//// pictures of our sound-making machines ////
#89

Thank you! Looking forward to expanding on some scripts later today.

For someone who never felt like “traditional” sequencers got them anywhere, norns + orca is truly a dream come true. I think I could do a whole album of material just using orca + sample library and a guitar.

3 Likes
#90

hi there,
i’m trying to run the grid operators but for some reason i can’t get them to work
pretty shure i’m doing something wrong again…

I have this script running but no light ob the grid:

D2
*>118

1 Like
#91

I’m sending midi out to an iConnect Midi2 interface. On other apps, my Moog Mother will receive the notes just fine, but midi out of Orca is causing my Mother to do a crash of sorts. It will play the correct note and trigger a gate for a few notes, but then lock up. It will stop on one pitch and stop responding to midi. The keyboard on the Mother itself even becomes non-responsive and I have to restart the Mother. Sending same midi to a Makenoise Ocoast works just fine. And again, the Mother works fine getting midi from other Norns Apps. Thoughts?

1 Like
#92

So in this example, you are moving the playhead position around randomly each time you trigger the sample?

1 Like
#93

I think! Looking at it more closely, it seems like I’m changing the playback rate (to manipulate pitch) by cycling through values via the Track (T) op. I’ll admit that I was definitely flying blind a little when I made that.

#94

@its_your_bedtime A couple of clarifying questions, if I may…

Re. the softcut playheads:

I’m curious about how the different playheads interact. One thing I’ve been doing is starting with playhead 1, recording something from the inputs, and then dropping the record level back to 0 to lock and loop that fragment of sound. Works great. But then, if I spin up a new instance of softcut and record to playhead 2, playhead 1 seems to get overwritten as well. My assumption is that playhead 1 wouldn’t be affected, but of course I may very well be wrong on that.

Re. softcut params

Is there a specific range we should be using to control these? I’ve tried various values to adjust panning, but they don’t seem to be continuous (i.e. a 4 will be panned nearly hard-left, 5 will be nearly hard-right). Different values (for panning) also seem to affect volume, FWIW. If this sounds like a bug, I’m happy to file over at Github.

BTW: the grid ops are incredible for triggering samples / engaging softcut. A total blast.

1 Like
#95

There are still things that require some tweaking (pan), i’ll fix this soon.

Softcut operators share same buffer

3 Likes
#96

That theoretically should work and light up in the top left square.
Are you on the latest version of Orca and your grid is being recognised?
What I do is similar and bang the > and randomise all the 3 numbers for a light show

The fun stuff is the < and hand triggering samples from the grid like an mpc and putting a randomise on the pitch of the samples as you trigger them.

3 Likes
#97

I’m weirdly getting cells that no longer do anything - normally after I’ve backspaced to clear them - is that a bug? or should I be deleting cells differently?

just to be clear - say put a ‘D’ in a cell - does it’s banging thing, delete it and then a short while later go back to that cell - out a ‘D’ - it no longer bangs

edit: I discovered you can fix the broken cells by putting a comment earlier in the line and then deleting it

also - lowercase ‘i’ not working for me

#98

I have the same issue.
I also have an issue where a Y / J cell disappears in a chain/chains

I opened two different issues on this @ github!

1 Like
#99

Thanks for reports, just pushed fresh version. I think theese are resolved

3 Likes
#100

you star!

So - can’t reproduce the broken cell thing anymore

the lowercase i issue - it works if you bang next to it - in its input zone! but not above it. likewise lowercase r