After a couple of years as a Norns user I started using Orca few days ago.
I think it’s fantastic and very easy to use (after the first minutes of complete silence… )
For now I’ve tried just few operators to trigger samples on Timber, like D,C,T,R,/, and so on, the result is very nice, having the ability to modulate Timber and Softcut parameters as well is very cool.
I would like to ask one question: seems that the script doesn’t like long samples, as soon as I load long samples Orca starts to go silent all the way, or only the track I used for the longer sample.
Is this an expected behavior?
Would be amazing for me to use long samples (like 1/5 minutes, so I mean very long samples…)
Thanks!
EDIT: the internal clock is very, very unstable, i remember i was reading something about it through the topic somewhere time ago, something like with further orca’s update this issue would have been fixed, am i wrong?
Hey y’all. I just fired up orca for the first time in a while and am having a problem with my keyboard. Orca isn’t responding to it at all. It works fine when navigating the Norns UI. I’ve tried all my USB ports, multiple restarts and even deleted and reinstalled Orca. Any tips?
EDIT: Figured it out. Didn’t have my keyboard selected in devices>hid
Digging into the Norns version recently. I have some updates to support another i2c device that I’m testing. Will submit a PR soon if it’s stable. EDIT: PR submitted. If you’re feeling adventurous & have an ER-301 you can give it a whirl: ;install https://github.com/echophon/orca
One quirk I’m finding is with lowercase ‘i’ - AFAIK it should increment only when banged. But it appears to “catch up” with the clock delta instead. I’m mostly cognizant of this because of former heavy use of desktop Orca. Maybe the use case is different here?
On desktop ------------------ On Norns
D6 D6 D6 D6 D6 D6
*i *i *i *i *i *i
1 2 3 1 4 7
Reviewing the js operator vs. the lua, it appears the lua does not reference the current value in it’s calculation.
Here’s a pattern using lowercase i which will allow the < grid read operator to act as a toggle instead of just a momentary button. With creative use of other lower case operators, you can use this to mute on & off different scenes within a patch
11<....
.......
..i2...
..1A1..
...22T*
...aV..
Line 1 reads in the momentary button from col1, row1 on the grid
Line 3 increments on the bang from the button press
Line 4 adds one as T will ignore 0
Line 5 advances a T track with a bang
Line 6 stores into a variable and will hold the bang in place until pressed again
Hello, is it normal that internal clock isn’t steady when using Orca? I’m always experiencing a lot instability, I’ve watched a lot of videos about Orca with rhythm patches, but I’ve never noticed something like that.
it should be steady after a fresh launch - although i often find after using it for a while, i hit a point where it gets a bit ‘sticky’ and unreliable. usually after starting a new patch or changing the engine. i know you’re suppose to stop & restart the clock after engine changes, but it often locks up for me regardless.
Base36 is base36, but for hitting each of the 128 MIDI cc knobs i wonder if any wizard would have design ideas … i can think of no direct way, but maybe a user definable mapping would not be implausible and not soooo far from the (esoteric) Orca way to do things…
Given eg the following user defined mapping for eg NTS-1, where MIDI cc 43 is filter depth
param
cc
a
14
b
16
c
19
d
42
e
43
f
44
Then to ramp the filter
........
.D..1Iz.
..!1e...
........
Note the e, which the param would map to MIDI cc 43.
I use a french keyboard (AZERTY) and i configured the HID to the FR layout.
It doesn’t seem to work for Orca. Anyone knows how to get around this problem ?
I just submitted a pull request with a tweak I made to the cc op. I added another parameter for knob offset. This is clamped to 3. The offset gets added to the knob param.
So
!00z0 sends to cc 35
!01z0 sends to cc 71
!02z0 sends to cc 107
!03z0 sends to cc 127 (any cc over 127 gets set to 127)
I made it so the current cc is displayed when the cursor is on the knob parameter.
I’m gonna test it more this afternoon, but it seems to be working well. I’ll holler here if/when my pull requests is approved by @its_your_bedtime
I’ve just discovered Orca and have been playing with it on my Norns Shield, triggering sounds on my OPZ. It seems like it’s going to be a crazy fun new way for me to make music.
I’m noticing that my sequences in Orca tend to stumble a little here and there. These stumbles are kinda interesting more than undesirable at this point in my figuring things out, but I’m wondering what causes these stumbles and whether there is anything that can be done to mitigate them? My shield is a 200323, so maybe with an older Shield it’s worse?
I’ve not tried Orca on a ‘general purpose’ normal computer yet to see how that compares. Maybe I’ll do that soon. I was hoping it might run on my little Panasonic CF-U1 (which I use for Sunvox/PaulStretch), but alas Orca does not do 32bit.
Yes, unfortunately I’ve never been able to use Orcλ by itself, the clock goes crazy, the more op’s I use the more the clock is unsteady. I have stock Norns, but with every firmware it’s seems the same.
I’ve noticed that if I switch from the user/script screen, to the general/edit pages, the clock seems to be stable? So sad about it , I would love to use Orcλ on Norns alone.
Never tried external MIDI clocking, actually…
)
, I would love to use Orcλ on Norns alone.