#611

Yay!

image

I need a standalone orca machine with midi

2 Likes
#612

I just made one with a raspberry pi 0W and an old MOTU midi interface I had lying around. Bought a little screen on Ebay. Can’t recommend it enough!

That being said, does anyone know if it’s possible to build Orca-c on rpi so I can run it just by typing orca [filename] in the terminal? I keep running the ./build instructions but if there’s a way to have it do all that automatically that would be swell.

#613

when you launch orca after building, do

./orca somefile.orca
1 Like
#614

Hello everyone! It happens that with the recent updates I can’t input the # character for comments anymore. I kept updating until the most recent version but still getting the issue. I’m on Mac OS 10.13.3

Also, is there a way to tempo sync orca w/ Ableton Live?

PS. Huge fan of @neauoire work here: thanks a lot for this amazing enviroment, been using and following orca since the early releases then recently started to integrate it properly into my workflow :slight_smile:

#615

I’ve just downloaded the newest update and I am having the same issue with the # comments. I also can’t seem to find where I could choose the MIDI Input to send a clock from Live to Orca. Pretty sure it’s a simple thing that I might have overlooked.

1 Like
#616

Are you getting an error in the console(cmd+.)? If you select some cells and do cmd+/ what happens?

Also, is there a way to tempo sync orca w/ Ableton Live?

Yeah, press shift+space instead of space and it will send midi clock stuff to IAC driver, you can sync ableton to that to get the clock.

I also can’t seem to find where I could choose the MIDI Input to send a clock from Live to Orca.

Open the console, press cmd+} to cycle through the inputs. It’s not something I’ve used much so I’m not 100% sure that works reliably.

2 Likes
#617

Looks like there’s no error in the console, although the cmd+/ works perfectly.

Thanks for the hint, that’s what I was looking for!

#618

Hi Guys!

same as @L4COUR I was so involved that I started using #orca in all my setup and I will do a workshop in Fano - Italy juanuary 17th!

trying to spread the world!
:nerd_face:

if ther’s somebody around…

now to the intresting part… With the new update i’m not longer able to change bpm, i’ve noticed this new commeand bpmShift: but it increase the clock for one bpm, also if you type a totally differnt one… did someone has the same error?

thanks guys!

1 Like
#619

Hey that’s cool, I’m originally from Ancona, hopefully will be there around that time to attend the workshop! :slight_smile:

Same here, looks like I can’t change the bpm with the command line. When I type : it interprets it as shift: therefore the bpm doesn’t change. Although, you can still switch the bpm 10 by 10 with the cmd+> and cmd+< commands.

#620

fine! do you know this festival called Bitnet01? https://bit-01.net/

1 Like
#621

Did anyone post this yet?

10 Likes
#622

Ah, that gives me a hint! Now, since I can’t replicate the # bug on Linux nor OSX, my guess is that you must be using a non qwerty keyboard? is that possible? Could you and @Ste_v send me a picture of your keyboard layouts?

#623

I’m using a standard european qwerty keyboard. I was able to input the # before updating (if I remember correctly it was until before 3 versions ago, although I hadn’t been updating constantly before that…)

IMG_0934
IMG_09343910×2932 2.41 MB

#624

yes same layout too, it was running until version 144 for me

#625

20 characters of same here

#626

gracias ORCA
fan sample >https://www.instagram.com/p/B4xhoyMpu1L/?utm_source=ig_web_button_share_sheet
ORCA track >https://www.instagram.com/p/B40dli6pv_D/?utm_source=ig_web_button_share_sheet

3 Likes
#627

@mo_o @Ste_v @piearesquared I’m trying to figure out that keyboard issue these past couple of days, I just pushed a little update that tries to address that, could you have a look and tell me if that works for you?

2 Likes
#628

@neauoire Just installed and tested the latest update but the issue persists.

Also, just noticed that I can’t input the * character neither (can’t actually remember if you’re supposed to just write it down to bang operators manually or not).

Wish I could be more helpful in spotting the problem. I tried with my alternative keyboard layouts (Japanese hiragana and qwerty romaji) but looks like I can’t input those characters anyway… I thought it was something about those special characters on that side of the keyboard but adding or removing columns and rows with cmd+[,cmd+] and cmd+{,cmd+} works fine though…

#629

damn, that’s disappointing…
I think I have no idea how to fix that one until I find a way to replicate it.

I’ll try and find someone who might know.

1 Like
#630

Hi everybody,
just downloaded latest version, ver149 (btw…ctrt-R does not show the release version anymore but release number is shown at the start up, for 2 seconds…) and I can change the bpm through the commander (ctrl+K) and the usual bpm: command.
Here everything is working fine and I have a qwerty keyboard too, same @Ste_v layout.
@neauoire do you need some testing?

edit: Some commands from the menu are not working (eg. file->open) using mouse. The shortcuts works fine, however.