first time playing with the grid interaction and I am stoked. absolutely love having a button press.
naturally my first step was to do a random display with some gridded sample triggering. so all the sound here is coming from the left half of the grid, which is all greyed out waiting to be triggered. but you can see the random stuff happening on the right, including a few times when it will trigger a whole line or even the whole grid. what I have right now is triggering too fast for me to see how it gets a whole line or the full grid, is there a character that can act as “all” in the X or Y axis?
I just noticed there are two MIDI clock outs available, one in the Clock menu, and one on the main parameters page and they can run at independent BPM. at first I thought surely this must be a problem but I quickly moved on to viewing it as a unique feature. it provides for offset clock trickery by switching the dominant (params menu clock, ie script clock) on.
“link” as a choice for clock source in the Clock menu must be II? it would be useful to have “script clock” be a source option, just to be sure they’re synced, should you want that.
The current Orca version for Norns uses an older, proprietary clock system. The new Norns clock, which also has an Ableton Link setting, has no effect on this Orca script.
@Frederickk is currently finalizing a revised (Super) Orca version that will allow the use of the newer Norns Clock.
Hi,
I’ve just start with norns shield and orca. I’ve made my first try paired with my model:cycles. I’ve looked for the issue I have with random higher notes. You could see in this video:
When I enter the midi channel for kick (channel 1) we can hear random higher notes arrived (but I haven’t coded that in orca) after that I write channel 6 for chords, and magicly the higher notes switch to arrive in this channel… and again, when I enter the channel 5 for lead… the same… What I miss in this? I think I will become crazy because I don’t find why
Anyone have had a similar issue?
Thx.
EDIT: I find using the monophonic operator works fine. Because the cycles is monophonic, I guess I haven’t problems to use it. Seems the polyphonic operator is little bit buggy.
I’ve notice too a little delay clock, is there something to fix it?
Thank you all for your patience and support with these Orca updates. As you can see, this is a pretty significant update A special shout out to @tansaturn, @vicimity, and @klingklangmatze for their help with this; code contributions testing, and debugging
Over the past couple of weeks we’ve addressed a number of issues and integrated a number of features into a singular “Super Orca” script. This latest update has been pushed to github and is version. v1.4.5.
Installing
This and all future updates will be available via Maiden. Please ensure your Norns is up-to-date with the latest firmware.
If you’re a brave soul, developer, or just curious, here are more details on bleeding edge builds:
Summary
Create a developer version by installing bleeding edge versions into a folder called orca-dev with the following command in Maiden. If you have the primary Orca build via Maiden installed under orca this install process will not affect that.
norns.fetch("--single-branch --branch dev https://github.com/frederickk/orca/ orca-dev")
Or you can SSH into your Norns and running the following:
$ cd ~/dust/code/
$ git clone --single-branch --branch dev https://github.com/frederickk/orca/ orca-dev
v1.4.5 Additions
In addition to bug fixes, I’ve made significant documentation updates to help first- and long-time users of Norns Orca.
I’ve also added a number of tutorials (original) and demos to demonstrate basic and Norns specific functionalities. (these are installed automatically into dust/code/).
Squashed synth operator | bugs and added support for 4 different engines; FM7, Passerby, PolyPerc, and Timber (choose engine within Params > Edit menu)
Implemented in-between session save states; open last saved project on init
Improved overall pset params for better continuity between sessions
In some strange but perhaps accessible future I might contribute a MIDI → HID wrapper so that one could type on a music keyboard =
Of all the esoteric programming languages ORCA is one which gets real use, and with norns + this library the most mobile and the sweetest to rave to. Thank you so much for your work, and the documentation is very much appreciated.
Edit: I have speculated on an alternative, safety-improved UI editing modality where the change while pressing K1 and dialing with E1, E2 and E3 encoders wouldn’t come into effect until release of K1, to avoid making a mess. Of course breaking things is part of being esoteric One thing is protecting the body of the user, esp. the ? operator which can damage ears.
I might contribute a MIDI → HID wrapper so that one could type on a music keyboard =
That would be great, I’ll keep my eye out for the PR
I have speculated on an alternative, safety-improved UI editing modality where the change while pressing K1 and dialing with E1, E2 and E3 encoders wouldn’t come into effect until release of K1, to avoid making a mess.
I did have that implemented initially, I’ll give it another test. Sit tight.
on Dev Orca now, I freekin love it. in the main Orca thread I was asking about whether we could get something that doesn’t stream gates, a one shot, essentially. I thought it was interesting that @neauoire said there isn’t anything that is a fixed state. I never thought about it before, but, yeah Orca lives in a constant circle. but I found what I was looking for in the Crow operator. if you push the envelope decay out to just 3 or 4 you can lock the gate open. with a grid operator combined you get an on/off button. neat!
also the volume and position for the Timber operator are not working for me.
I might contribute a MIDI → HID wrapper so that one could type on a music keyboard 
= 
UI editing modality where the change while pressing K1 and dialing with E1, E2 and E3 encoders wouldn’t come into effect until release of K1, to avoid making a mess. Of course breaking things is part of being esoteric 
One thing is protecting the body of the user, esp. the 