this is polyphonic earthsea. it takes what was in ansible earthsea and expands it to:
- ability to run on any of the trilogy modules (white whale, earthsea, meadowphysics) or ansible
- simultaneous multiple pattern playback
- up to 8 voices
- direct control of er-301, just friends and telexo via i2c
- octave, transposition and volume can be set individually for each output
- for telexo you can also set attack, decay, waveform (individually as well)
- each voice can be assigned to any combination of devices and outputs
- pattern start triggers can be assigned to any gate output
- each voice can be used as a modulation source (x/y/key)
- modulations can be assigned to outputs or any of the 8 mod buses
- arc can be used as a modulation source (assigned to mod buses 1-4)
- mod buses can be used to modulate any output parameter
- polyphonic midi support
please note this is an early beta, so there will be bugs (especially the i2c part).
bug reports will be greatly appreciated!
i will expand it and add a couple of videos in coming days.
for i2c control you will need to use a powered i2c board or txb module
please note that flashing new firmware will erase your presets
- bug fixed: front panel button stopped working on ansible
- midi keyboard support
- bug fixed with clock input on ansible
- ansible buttons work for next/prev pattern now
- ansible reset input fixed
- knobs are mapped to mod buses
- new parameter for txo: waveform fine
- bug fixed: just friends volume 0 didn’t work
- long press on front panel button will save current preset
- LED on ansible indicates current pattern start
- pattern copying
- preset copying
- arc support
- bug fixed: pressing half speed too many times would result in pattern not playing
- bug fixed: switching between arc/grid caused freezing
- bug fixed: rogue LED on gate settings page
- bug fixed: not being able to select fixed width of 1
- bug fixed: glyphs didn’t save
how is it related to other earthsea versions?
this expands on ansible earthsea (which itself was a polyphonic implementation of earthsea done as part of ansible firmware). i might also refer to this as multipass earthsea (see next question). this version was basically me porting ansible earthsea to the multipass platform and adding a direct control of i2c enabled devices. this was the initial plan but somehow i ended up adding some features originally planned for archipelago. but this will likely be it for this version of earthsea with the exception of fixing bugs. all other features will become archipelago - which will be a much expanded earthsea with a completely rewritten codebase. no plans to port this to norns (which has its own earthsea), but if somebody wants to try that i’ll be happy to help!
what is multipass?
multipass is a lightweight framework i’m developing which will make it possible to write firmware that will run on any of the trilogy modules or ansible (and possibly more in the future). i’m planning to make it public at some point (once i have a chance to document it properly). all my future firmware development (excluding teletype) will be done using multipass. i will be porting orca next.
what’s the point of running earthsea on meadowphysics…
… as it only has gate outputs? well, you could still use it as a trigger sequencer. but really what makes multipass useful is that it supports direct control of i2c enabled devices - er-301 / just friends / telexo. so even if you don’t have any CV outputs you can still use meadowphysics to sequence 6 voices of just friends, for instance. or do the same with white whale and use its CV outputs as modulation for other parameters.
but different modules have different hardware…
multipass allows the same firmware engine to configure itself for a specific hardware configuration. so on ansible you can use the module buttons to switch between patterns, on meadowphysics you’ll have a knob for controlling clock speed, on earthsea the other 2 knobs could be mapped to mod buses 1&2 etc. and it will use whatever outputs are available.
or, why not just continue developing this version? a couple of reasons - there is a lot of duct tape on this engine by now. rewriting it from scratch will allow to develop new features easier. also breaking away from earthsea will make it easier to introduce more significant changes, including the UI itself. while polyearthsea did employ several features originally planned for archipelago there is a couple of features that will (i hope) really set archipelago apart.
what’s next for this version?
modulation for transpose