Where’s the outpouring of support for Scanner_Darkly on this Orca port? I’ve known this group to have a lot more enthusiasm for advancements than we’re seeing here on this thread. Throw some encouragement out there.

1 Like

i can’t keep up with the rate of development on stuff, but this has me super stoked, if i can figure out putting it on my ansible, and then get myself a i2c board…

2 Likes

I love the original Orca, it’s an instant melody machine. Now having it running on Just Friends will free up my Mangroves - awesome work. @scanner_darkly

1 Like

ha, the tweet was mostly me being surprised at the multipass concept not getting more attention rather than asking for encouragement. and orca is getting long in the tooth and could use a redesign…

so, multipass. more announcements will follow but basically i’m setting up a new way of building firmware with the idea being that any firmware built this way will run on any of the trilogy modules and ansible. this wouldn’t be very useful due to difference in the number of outputs, but with trilogy modules confirmed working as i2c leaders this matters much less now, since you could just directly control just friends / telexo / er-301 with up to 100 voices (although i’m not sure what kind of firmware would use 100 voices…)

8 Likes

Amazing! This could really change things and breath new life into the trilogy modules that kind of seem to be on their way to be replaced/forgotten about like other v1 modules.

Any thoughts on how orca might utilize the knobs/slew on earthsea (which is the feature that keeps me from selling my earthsea in favour of just using ansible-earthsea)?

Appreciate your contributions and work for this community :heart:

2 Likes

that’s exactly my hope!

i might consider adding slew in a future version of orca. re: knobs - the new approach will take advantage of controls available on each module (so, you’ll be able to use all 3 knobs on earthsea and use the 2 buttons only available on ansible etc), just need to think how they can be utilized (on ww only 1 knob is used right now, for instance). one idea is controlling the waveform when used with telexo (or using one knob to select the starting waveform and another to control the spread across 4 oscillators). at some point it will also support telexi module(s) as additional controls so you’ll get 4 extra knobs and cv inputs (right now cv control for orca is only available via teletype).

3 Likes

Very very cool to see all this happening. I was wondering - might a possible arrangement of apps be:

All grid apps for Ansible and separate firmware of all Arcs apps ?

I don’t have an Arc (yet) but I can see wanting to get another ansible to run those separately (and simultaneously)

(I did have a passing fantasy of being able to select which apps you want in your firmware on a web page and getting a custom build - but I’d not want to support something like that so unfair to suggest anyone else did :slight_smile: )

2 Likes

Seems like a good idea this separation of Arc and Grid apps

plans on integrating multipass with ansible:

any firmwares done using multipass will run as a standalone app on trilogy/ansible. but also planning to have a way to easily integrate such firmwares with the ansible firmware. this will always be the case of the official ansible + one multipass app.

it’d be awesome to have the ability to pick and choose which apps you want, especially with the ability to auto generate your custom firmware - if somebody wants to take on this will be happy to help!

re: arc vs grid apps - why would you need to separate them? you could just use only grid apps or only arc apps. the only benefit would be if we run out of space at some point. should mention the upcoming usb switch will also be useful for switching between arc/grid when used with, say, ansible.

1 Like

Ah - my mistake - I thought you were running out of space! if they can all squeeze in then thats great

(I still see myself buying another Ansible when the time comes to buy an arc :slight_smile: )

we are close to running out of flash memory (with ansible earthsea added), so the number of presets you can store in each app is the limitation. this is one of the reasons for only having one app in addition to the official firmware (so, would be ansible+earthsea, ansible+orca etc).

1 Like

I’m being dense here likely, but the original explanation of multipass is not being found by me. I’m guessing it was the Instagram message about Orca running on Ansible, TXo, etc.?

the only info posted is in this thread, the most important bit is this:

3 Likes

really looking forward to this, can’t thank you enough for all the amazing work you’ve done on everything. got a rough ETA on when orca will be ready for ansible?

1 Like

thank you! probably a couple of weeks (as a standalone firmware).

7 Likes

Hi there, Ive been seeing your awesome release of this in vcv rack, was wondering, does this currently run on meadowphysics?

no, i started on porting orca to multipass (which would allow to run it on MP/ES/ansible) but since multipass didn’t support USB save/load i needed to implement that, started and got sidetracked. just too many things to do. at this point i won’t promise anything seeing how my last one was ā€œ2 weeksā€ - a year ago…

i would say that orca’s heart is quite a different beast, and i am considering at some point porting it to eurorack.

4 Likes

Sounds good, thanks for your efforts! I saw a cheap meadowphysics on reverb and got excited at the possibility :heart_eyes:

Amazing app. Still hoping very much that it will be ported to Ansible some day. Would gladly buy a WW only for Orca, but they are next to impossible to get these days.

10 Mh

1 Like

thank you!

i’m wrapping up development on multipass (eurorack) version of orca’s heart which is essentially a new version of orca - it’s quite a bit different but i think it distills what made the original orca special and builds on it. as anything developed with multipass it’ll run on any of the monome eurorack modules.

2 Likes