Orca

DuellingAnts · 2021-01-15T13:16:14.608Z

Just restarted again and did an update in maiden. Works now! Thanks

josker · 2021-01-18T14:32:13.445Z

I’m getting quite a bit of hanging MIDI notes. Is there some type of panic command that would send noteoffs? It also seems like successive MIDI notes in the same ’:’ operator get dropped, but maybe it’s my MIDI setup, will have to troubleshoot.

Thanks!

easterner · 2021-01-26T04:48:09.117Z

Just a few more thoughts on Orca on Norns. I’ve spent a lot more time on Orca on a computer (on a Macbook), and had a few things that would be amazing to be consistent for Orca on Norns:

using the keyboard to select areas to edit. holding shift and pressing left or up arrow keys doesn’t allow expanding the selection box in those directions, only going right or down
when selecting beyond the visible screen, it would be great for the screen area to scroll with the furthest edge of the selection, I think, so you can see what additional rows or columns you’re selecting
pressing backspace or delete - would be great to be able to delete all characters within the selected box; for now, it just deletes the top left square of the selection box
for operator X, writing ‘E’, in the computer version, the E is only released when the write location is changed; on Norns, it seems to write an E every two frames or something like that?
the operator I, on Norns, starts from 1 to x, while on the computer, starts from 0 to x-1
^ operator, for midi cc - I’m using this with a 16n faderbank, which sends 0-127, but when I get to 127, it’s maxing out at ‘i’ or ‘j’? EDIT: I see that the full throw of the fader sends 0-127, and on Orca on Norns, it goes through 1-z several times; so it’s a matter of setting 16n faders to send 0-36 rather than 0-127… or it would be great for Norns to spread 0-127 across 1-z by default?
latest J and Y “wires” implementation would be great too!
looking forward to the Timber operator ‘level’ and ‘position’ parameters working!
and finally… for Softcut, I’m still trying to figure out what is going on - the best instructions were its_your_bedtime’s post here: Orca - #88 by its_your_bedtime but I’m still not quite understanding what is happening behind the scenes - where might be the best documentation for understanding what this is doing? Particularly the range of playhead rate and playhead position, and what the base 36 numbers make these do in terms of moving in discrete steps…

I do love being the Norns version for having quick access to grid, midi note, cc numbers though…

fourhoarder · 2021-01-26T15:16:01.862Z

JF implementation is

nokulture · 2021-01-28T11:52:25.556Z

nokulture:

I didn’t see in my maiden, Do I must change config in somewhere?

Finally I’ve got it, maybe it’s so obvious, but I need to uninstall the old version I’ve installed from norns to install the new one. It’s seems the maiden’s update doesn’t work for me.

TanSaturn · 2021-01-31T16:57:07.353Z

Is anyone else seeing an issue with using the arrow keys to navigate menus? I got everything updated the other day and since then up and down jumps two places. Everything is fine when I’m in the orca grid. Is this just a me thing? Sorry if this was already reported.

fourhoarder · 2021-02-01T05:45:14.977Z

yeah I get that too although tbh that’s the first time I’ve tried to keyboard through the menus. it’s a long scroll to sample 32.

ldezem · 2021-02-08T19:23:23.292Z

I’m having trouble understanding the MIDI CC operator “!”. Is it possible to send midi CC between #40-#60 range on Norns? Can the offset be changed?

gnsk · 2021-02-09T02:59:23.178Z

orca-colemak4032×3024 2.08 MB

Built from scratch. Two pcbs, one for bottom sandwich case.
Is there any way to use Colemak layout in orca?
tried “sudo dpkg-reconfigure keyboard-configuration” but nothing happend.

zebra · 2021-02-09T09:04:54.443Z

you would have to edit the keycode mapping directly:

github.com

itsyourbedtime/orca/blob/master/lib/keycodes.lua

-- keyboard map class
local keycodes = {}

keycodes.chars = {[0] = "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z"}

keycodes.num = { ["0"] = true, ["1"] = true, ["2"] = true, ["3"] = true, ["4"] = true, ["5"] = true, ["6"] = true, ["7"] = true, ["8"] = true, ["9"] = true }

keycodes.base36 = {
  ["0"] = 0,
  ["1"] = 1,
  ["2"] = 2,
  ["3"] = 3,
  ["4"] = 4,
  ["5"] = 5,
  ["6"] = 6,
  ["7"] = 7,
  ["8"] = 8,
  ["9"] = 9,
  ["a"] = 10,
  ["b"] = 11,

This file has been truncated. show original

(norns software stack does not take keyboard input from a console or X window, so console keyboard config is irrelevant. newer scripts can use the keyboard norns module instead of dealing with keycodes directly, so there is a single source for customization that could be made aware of /etc/default/keyboard contents.)

gnsk · 2021-02-09T09:27:29.889Z

Thanks a lot.
found that file in /home/we/dust/code/orca/lib/keycodes.lua
I’ll try it.