#378

next update of orca will run on any of the trilogy modules - white whale / earthsea / meadowphysics and ansible. lack of cv/gate outputs will not be an issue as it will be able to control just friends / telexo (and possibly er-301) via i2c.

like this: meadowphysics + txo = 4 sequenced voices in 10hp

16 Likes
#379

Instagram post mentioned running on Ansible too?!?! Is there space for it to run alongside Kria/Meadow/Earthsea or will it be a singular firmware?

3 Likes
#380

this would be great to know. thx!

#381

not sure how i forgot to add it! yes, it will run on ansible as well, as a standalone firmware (not part of the ansible firmware).

1 Like
#382

As I suspected. Maybe when archipelago is a reality the two could occupy the same firmware? I would love to have two Ansibles with your contributions residing on one :sunglasses:

1 Like
#383

i never really thought the grid was for me until i saw these videos. amazing work!

#384

thank you!

both archipelago and orca 3 will need to be done first, but yeah this is planned eventually.

4 Likes
#385

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
#386

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
#387

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
#388

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
#389

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
#390

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
#391

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
#392

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

#393

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
#394

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: )

#395

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
#396

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.?

#397

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

3 Likes