#631

I think I found a simple solution, could you give it a try and let me know if that fixed it?

#632

@neauoire
With ver150, when using “open file” with mouse in the console I get “File chooser dialog can only be shown with a user activation.”. Shortcut ctrl-O works fine.
Also “open theme” give the same warning. I can drag the theme .svg file directly.
Everything else seems to work perfectly.
Do you want me to test something in particular?

btw…Please show again the active midi device in the Midi menu…

edit: just read previous posts and discovered the menu issues are due to Electron 7.0, sorry…and thank for the good work!

Cheers

1 Like
#633

@neauoire I noticed that with the latest update ver150 I can input the * properly again (I also tried while pausing the sequencer) but still no way for me to input the #.

@pangrus which OS are you on?

#634

@Ste_v I’m on windows7, I can input both # and *

Cheers

########################
#.......COLORS.........#
########################
##...R..R..R..........##
##.rV2gV4bVb..........##
##..D2................##
##....bKrgb.gbr.brg...##
##..$co:24b;4b2;b24...##
########################
1 Like
#635

hi guys

i think the problem is on mac os… I’ve not tried yet ver150 as i do i will post a comment if its fixed…

I’ve also find the same prblem of @Ste_v with # caracther its impossible to type in

maybe with the new realease it works

#636

I’m not sure what the issue with # is, I’ll have to find someone who can reproduce it and also know a bit of JS so they can inspect why it doesn’t register in acels.js

In related news

We printed a few sticker sheets with the Orca character as an alternative way of supporting the project, they came out pretty nicely!

DSC09635%20(copy)
DSC09635%20(copy)2120×1200 238 KB

12 Likes
#637

Lovely! Gonna order a bunch of them for sure! You guys deserve a lot of support for all of your projects and your inspiring vision :slight_smile:

1 Like
#638

Oh wow! Sold out! Congratulations!

1 Like
#639

Dang, we didn’t expect that.
We’ll make a bunch more!

4 Likes
#640

I haven’t had time to test it yet, but I will let you know as soon as I do.

#641

Sounds good! Keep me posted :slight_smile:

Built a little web-based sampler to play with orca.

Tweaking knobs in Orca with the MidiCC operator

13 Likes
#642

looks fantastic, thank you
will Enfer be available on ichi.io or github?
(perhaps with a new rabbit character?)
also,
do you recommend midi or osc for ORCA to communicate
with supercollider?
cheers
(stoked to be awaiting the arrival of a sticker sheet :slight_smile: )

#643

Shirts might also be cool!

1 Like
#644

do you recommend midi or osc for ORCA to communicate
with supercollider?

It really depends what you want to do, you could send frequencies directly via osc or udp, or if you just wanna send notes, then use simple midi and midiCC.

Install Orca as a progressive web app

You can now install orca directly into chrome’s cache to make it work offline!

Screenshot%20from%202019-11-19%2009-43-44%402x
Screenshot%20from%202019-11-19%2009-43-44%402x2560×1600 756 KB

Orca in the wild

I stumbled on this video on IG where someone uses a projector I had never seen before, it’s very elegant.

D.........
.H........
xE........
.....E..HH
......2gSS
10 Likes
#645

wish i could find a place to buy that thing

#646

Hi @neauoire i’m having the same problem with ‘#’ on a macbook pro since pulling the latest commits from your git repo.

I’ve figured out what’s happening: to type # on macbook requires pressing ‘alt’ and 3. The acels.js listener is catching the alt key press, and then has nowhere to send the glyph, as it is then looking up ‘#’ in the acels.all table and cannot find an entry. I made orca set a cursor.write(’#’) function call in the acels menu setup as a test and could then input # like normal. Of course this is not ideal as we don’t need a menu entry for the # glyph.

So, it’s to do with alt key press being caught and the context is captured for the menu accelerator list.

Sorry if this explanation is a bit confusing, but hopefully we can find a work-around.

I’m trying to figure out how normal glyphs are captured from keyboard presses, but haven’t found the entry point yet. Any tips?

EDIT:; seems it’s in acels.js, the onKeyDown method?

#647

Ah, i see it now. It’s not the acels capturing the alt key press, it’s the commander.onKeyDown method being called via the pipe which is capturing the alt key and returning before setting the # glyph…

Or perhaps a combo of the two. It needs some way to pipe # specifically to the pipe so the commander gets a ‘#’ glyph to set the right command.

EDIT god i’m awful at writing. But also as i just opened this account i can’t reply again. Anyway, disabling the alt capture in the commander onKeyDown does in fact allow the # glyph to be entered in the grid like normal. I also added a condition in the acels.js convert method to route the # out as a normal key without alt like so:

if (event.altKey && accelerator !== ‘#’)

3 Likes
#648

Ah! That makes everything clear now, okay so, your # is behind an alt shortcut.

Edit: I’ve just pushed a new version that tries to address the Alt+Accelerator issue which should fix the # injection. Please give v153 a try and let me know if that works for you :slight_smile: @cupcake @piearesquared @mo_o @Ste_v

Orca in the wild

Someone made a very cool workshop combining Orca with Ableton and Unity3D, you can read the workshop notes here.

4 Likes
#649

@neauoire just tried it but looks like the issue is still there :confused:

#650

Same for me. I tried to debug the js but vs code debug only works properly on the main process in an electron app. Think i have to add chrome debugger or something.

Update for @neauoire - i’ve been able to create a debug session in vscode. The control flow is working as you planned it, except that what is happening is that the conditional evaluation at the start of the commander.onKeyDown is catching the event.altKey flag every time.

It seems unnecessary to be looking to filter modifier keys in that method as far as i can see because they are already being filtered in the acels.js file, when key events get put through the acels.convert method. So i think it would be safe to just remove line 147:
if (e.ctrlKey || e.metaKey || e.altKey) { return }

Will do more debugging and see if once i comment out that line i can ever get control flow to hit the commander.onKeyDown method when it should have been filtered already.