Not sure it applies. but I have found that on a Mac USB keyboard, you have to use the actual Control key for the key combos and not the Command key as you’d expect.

Cut is fixed :slight_smile:

Also few updates:

  • Keyboard controls in norns menu / parameters page
    Press shift + arrows to jump between timber sample settings

  • Grid sliders - leave one of the inputs of < operator empty to create slider

14 Likes

Just looked this up… there are different key codes for CNTL and mac CMD key so for the moment the keyboard lib (and thus this Orca implementation) is probably a bit PC centric.

The mac CMD key codes are “MetaLeft” and “MetaRight” and Orca here is using “ControlLeft” and “ControlRight” so they are considered different keys

If I have time in the next few days I’ll look at an option to see if you could define which keyboard you’re using.

1 Like

I’m trying to do some modding to the library now, is there a way to get a simple printout of what keypresses are registered in orca in matron? would make it a lot easier to “translate” keycodes.lua

You should probably just use my HID demo script to get the codes you want to change and then cross-reference those in keycodes.lua

FWIW - it might be a good approach to make a separate keycodes.keys-norwegian array in the keycodes.lib and then we could see about using a preference to load the keyboard map you want to use.

2 Likes

this is so amazing. @tehn is there any way this could be implemented at a lower level? at the moment it only works if orca is the loaded script

2 Likes

All this keyboard stuff is part of the HID functionality. The functions to do this are already implemented for any script if that script author wants to use it.

The specific Keyboard functions used here in orca is using a translation library I made to turn the HID keycodes into “letters” (or arrows or other keystrokes).

What you’re asking would be to integrate HID keyboard commands into the full norns UI (specifically menu.lua). Might be doable, might not.

3 Likes

Thank you for the explanation. I will do some poking around next time I’m connected to maiden

it is possible, yes. the menu code needs some clarification

Just completing a couple days of Orca study using the computer-based version (per recommendation of @mlogger :nerd_face:). Ready to boot up the Norns version. Any tips on getting Timber and Softcut integration, or is that pretty self-revealing?

It’s pretty self-revealing! All the norns-specific ops (see the top post) “just work,” although as you might expect, loading samples into Timber requires setup in the Param menu.

1 Like

The Add Folder feature is great for samples in the app Parameters, but can lead to a lot of frustration in scrolling down and finding the samples you ended up using in your code. So, I would say being judicious about loading samples will make your life easier when you want to go and modify the params for those samples. I guess I would like to see maybe a grid UI with your samples laid out in order and when you click on one, it automatically navigates to it’s params? That would be super helpful.

2 Likes

You can modify params with " operator, also scrolling params with shift+arrows is pretty painless

8 Likes

Oh my goodness, how I had overlooked both of these?? That is just great, thank you @its_your_bedtime!

2 Likes

First try using the :

  • > g.write (x y value ): Sets grid led on bang.
  • < g.read (x y): Reads specific coordinates. If value > 6 outputs bang.
8 Likes

Finally had some time to dip into orca a bit. And I am having such a blast with the Timber operator! Recently filled my sample library up with kitchen percussion and skateboarding sounds. Perfect food for orca.

But I am having issues wrapping my head around getting the softcut operator do anything. Anyone want to give me some simple pointers on how to get it looping? Not sure what to feed into the different parameters to, let’s say, get it to loop something going into input 1(and maybe also a different example on how to resample from orca itself).

Gave up on fixing the HID stuff with my weird Norwegian keyboard. I “fixed” it with some stickers.

9 Likes

I was also a little confused on the softcut op at first, mostly because the volume parameter (the 4th) has an inverted range, IIRC: 0 for max, z for min.

Here’s an example that works for me (and keep in mind that the softcut op will simultaneously record both the physical inputs and any samples being triggered from Orca itself)

.D1.....
.*/1540z

1 is the specified softcut buffer (1-6)
5 is the record level (could be 0-9)
4 is speed (still a little murky on this, TBH)
0 is volume (max, in this case)
z is position (0-z)

The position parameter I’m still wrapping my head around — at its lowest setting, 0, it seems to record at a pitched down, low quality level. Feeding that parameter a z gives me the highest recording quality.

I tested this with a simple sound coming into the inputs and it did the trick.

3 Likes

Sounds like you were modulating speed somehow…

Oh - I just noticed now that the parameters for the softcut op have changed…

I’m all for this as well