@akaye.world: It only works the other way around, use orca to control ableton instead.

what exactly is the behaviour of the note length parameter for “:”? Is “z” 100%?

@easterner: Orca converts the z value to the number 35, so the note is released after 35 orca frames.

@Frederickk ORCA x APL

3 Likes

@neauoire — Okay gotcha… I’m trying the other way around now. Orca output set to IAC Driver Bus 2, Ableton Input Sync set to IAC Driver Bus 2 and the “ext” sync button clicked. Still nothing at all…
Is this some Ableton glitch I’m experiencing? I feel like all the tutorial I’m reading for this are quite simple but I cannot get this to go

@neauoire :exploding_head::tophat:

Ah, got it! Thank you!

I’ve been talking about that Orca rewrite from Electron(120mb) to SDL(20kb) for a while, well, it’s finally coming together :slight_smile:

17 Likes

This tool was my gateway into synthesis. It remains at the heart of every patch, and it still boggles me how great it is. Thank you for your continued development.

6 Likes

Amazing! Cloning + building right now!

EDIT: oops, seems build.sh defaults to overwriting my orca wrapper in ~/bin :slight_smile:

1 Like

EDIT: oops, seems build.sh defaults to overwriting my orca wrapper in ~/bin

Oups, sorry, it’s probably better to just run the command in the README anyways so you don’t have a debug version.

Orca Workshop for Babycastles

2 Likes

Thanks, will try that!

I saw something along the lines of “this is not supposed to be a replacement for orca, it’s just for educational purposes”, is that overly humble (that is the plan is (eventually) to get up to speed with electron orca, or even replace it) or is that accurate?

I saw something along the lines of “this is not supposed to be a replacement for orca, it’s just for educational purposes”, is that overly humble (that is the plan is (eventually) to get up to speed with electron orca, or even replace it) or is that accurate?

It’s not going to replace the complex orca clients. The toy will probably not exceed 1000 lines of code. It’s mean to be a base for people, like me, who want to try and learn C or SDL. It could be a base for a much more complex orca system if someone is willing to put in the time.

But what I would like to try at least is replace the orca-js core logic with the C core of the toy or the tui. That way I don’t have to maintain the specs twice. It would be pretty neat if this could also be part of the Norns build at some point? we’ll have to see.

6 Likes

can somebody explain what’s goin on here?

https://www.instagram.com/p/CJhXmX1haNc

based on the caption it looks like they’re using orca to send midi triggers, one triggers recording and the other playback. INAB looks like some sort of elektron box internal resampling thing?

ah yeah looks like input A&B on octatrack

thanks

1 Like

yeah i think it could be a good test case for a norns “C extension.” the orca core logic could be a separate executable connected through pipes/sockets/OSC, or it could be plumbed in directly to lua through FFI. (the latter raises more questions about how we would generally support doing that in matron. open to suggestions…)

Sorry for the noob question, I’m new to ORCA. I see tutorials where they enter chars to be treated as letters rather then operators (e.g. “D”). I thought Ctrl+I was meant for this but, at least on Windows 10, this shortcut doesn’t seem to do that (apparently it doesn’t do anything).

well sometimes operators want letter input, sometimes numbers, sometimes both and to make it more confusing, lowercase letters act as conditional operators when banged but look as if they’re not doing anything when they aren’t. but capital letters are operators and need no special command or ctrl key action.

see the base 36 table for input values.

1 Like

ctrl+i is for insert mode, that should let you type in a series of letters.
If you just want to make inhert letters, write them within #, like # INACTIVE #.

Letters to the right and under of an operators are locked.
For example, 03TCAFE CAFE are locked since they are to the right of the T operator.

1 Like

ooooh that’s why you can’t capitalize that left field for R.

1 Like

Regards to all!
I just want to share my first jam in Orca & Pilot & Cassetter:

Bye :slight_smile:

6 Likes

Firstly I just want to say that after following curiously for a few months I’ve recently started using Orca regularly and its just awesome. Seriously one of the coolest bits of software I’ve used in some time.

I’m interested in following the development of Orca-toy and I can get it up and running, but have to make adjustments to avoid compile errors on macOS (not sure if the same happens on other OS’s) which is fine, but gets a bit tedious when I have to do it each time I pull the latest changeset :sweat_smile:

Just wondering if you’re seeing the errors I’m seeing (& if so how to avoid them?). Its all due to conflicting type definitions: random, move, setmode & select and gives an error like this:

orca.c:223:1: error: conflicting types for 'random'
random(Grid *g)
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/stdlib.h:228:7: note:
      previous declaration is here
long     random(void) __swift_unavailable("Use arc4random instead.");
         ^
orca.c:533:36: error: too many arguments to function call, expected 0, have 1
        setport(g, x, y + 1, cchr((random(g) % ((cb36(max_) - min_) || 1)) + min_, ciuc(max)));

Inspecting that output it looks like random is already defined in stdlib.h (at least in the MacOSX10.14.sdk). For now my solution is just to add an _o to the end of the conflicting function defs

Maybe its just a case of forcing xcode / clang to use a specific (older) SDK without those definitions, but I haven’t figured out a way to do that

1 Like