Thinking about this more, I think there must be something goofy with my beat clock(global clock n sync) implementation that is causing the clock to stutter and lose time.
@Frederickk did you use my best clock implementation or your own?
1 Like
i just tested $ in the official maiden ORCA and I get errors (halted playback) there aswell. reported some issues to @Frederickk re this. to me (very basic lua and norns-coding) this looks like there is an issue in trying to grab a scale from the table in musicutil. but iām in deep waters here 
thanks @Frederickk, i think I need to nail down more what Iām actually seeing. for some patterns saved through Edit, all the sample info is there and for some it seems like they were jumbled or missing. I meanā¦duhā¦the .pset file is right there next to the .orca file, itās doing something. so yeah, more investigation here.
Shoot me a DM when/if youāre able to suss out more.
1 Like
The latest fixes are looking really good for me!
2 Likes
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?
3 Likes
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.
2 Likes
2197
473
itās ableton link, no?
nice to use multiple clocks as a feature : ) iāve noticed it in other scripts as well and just scratched my head.
1 Like
ah ok, not an abelton guy.
1 Like
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.
5 Likes
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/).
Changelog
For those interested hereās a a list with some detail on the changes made:
- Updated operator functionality to match base Orca, e.g. updates to
B and L
- Integrated Crow functionality operators
~, ], }, and ` @coollerue and god mode now defaults to 0 These operators are a breaking change from previous Crow branches
- Fixed screen flickering with Crow
- Reimplemented OSC out as
= operator
- Fixed
$ (r.note) bug
- Fixed the
X operator typo
- 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
- Added tutorial/examples (pulled from here and demos for the different synth engines
- Merged
import and load project to handle loading of .orca, .txt, and .json files
- Fixed CLOCK > RESET bug
- Code refactoring and general bug squashing
If you uncover any bugs please let me know here, or file an issue.
32 Likes
massive thank you @Frederickk. this is it!
2 Likes
so so so much thanks. there is so much here!! I am overwhelmed. there are many great scripts on this platform but Orca is my favorite.
1 Like
JHC
480
They should put up a plaque for you or a star on Hollywood boulevard! Thanks so much for all your efforts!
5 Likes
kveye
481
Is it going to end up in maiden?
xmacex
482
Uuuh!
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.
4 Likes
Amazing work, can I just say also that your guides and docs are amazing.
4 Likes
ezbot
485
This is fantastic! Thank you for all your hard work
1 Like
