Ansible Earthsea

Didnt know norns covers that too. No real plans to go there yet but will absolutely go for crow…different topic i guess and who knows…

So not a real chance for messing with the midi capabilities i suppose in ansible? But thanks for answering my questions.

not planning on adding midi capabilities to ansible earthsea, sorry.

So i finaly made the step. Trying to find out if you allready had a chance to bundle your port with the official 1.6.1 on monome?
Maybe i missed it. And thanks a million times for all the work and to help making ansible such a swifty knife.

Offtopic, didnt find the power draw of a 128 on monome page and wanted to find out if my row power 30 will handle the draw just fine when i get a grid one day.

re: power - row 30 should be sufficient for powering grid only if you use ansible (depending on how much power other modules draw, of course). it will NOT be sufficient to power grid if you use earthsea/meadowphysics/white whale. row 30 provides 0.5A on +5. the trilogy modules with grid connected might need up to 0.6A, so it already exceeds what row 30 can provide (and you always want to leave some healthy headroom instead of maxing out your power supply). row 40 should provide sufficient power (again, depending on what other modules you have).

Hey
Afaik we did not discuss the possibility to use a old type grid 64 with the earthsea port of Ansible. I read contradict statements about the topic (in general, not ES) so i am just trying to find out if that will work, be powered by Ansible and just be without runes as were mentioned.

We did discuss (at least from my part) if the midi modes could be further developed. I never meant ES to Midi. And i dont know if old grids are basicaly midi while new ones arent

there is nothing module specific about which grids work with which modules - if it works with one module it’ll work with others. specific firmwares or ansible apps will work with 64 but might be not very usable - specific answers will differ for each app as it’s all very UI dependent. @zebra provided some details here.

grids are not midi devices. they use their own protocol (which is different for older grids, but again, the library used by eurorack monome modules will support most models).

1 Like

Ok i think i get it. An example of „not very usable“ would be that patterns are located in the middle of a 16 pads long grid and would only be partial present on a 8 pad grid. Stuff like that?

Or i get the „perfom pattern“ part wrong in the image documentation. When looking at the official erathsea video it rather feels like i would simply be limited to a 8 step length and loose all the functions that are in the 2nd half of the grid. Not sure if it would be a functional 8 pattern instrument however.

1 Like

yes, basically anything located in the right half of grid 128 will not be accessible. you can check specific functions here: https://github.com/infovore/monome-docs/blob/aearthsea-docs/docs/modular/ansible/index.md#earthsea-grid and here: Ansible Earthsea

i’m not sure what do you mean by “steps”? you can have up to 128 events per sequence in ansible earthsea. an event is either a “note on” or a “note off”. for chords you have to count each note, so if you use 4 note chords you can have a sequence of up to 16 steps.

1 Like

I suppose i meant 8 patterns instead of 16.
Very useful links and info! Thank you

you can still access all 16 patterns on grid 64, pattern selection is in the left half. ansible earthsea supports 8 presets, each with 16 patterns.

1 Like

20 char of Thanks so much!

Got few more questions. Hopefully thats allrite

I know clocking earthsea was added. But could the unclocked, live looped patterns (earthssea sequence) somehow be used as the clock for the rest of the rack? I dont think so but better ask:)

Oh and wondering if key mapping is present?
But i have the chance to try it all out soon.

Is transposing always connected to arp use or can a pattern or a whole sequence be transposed by the left menue button without entering any apreggiation?

Finally on 8x8 the play surface is 7x8 right? Or less?

One more:)
I assume the first 2 runes work with 8x8?

Thanks!

Hi I’ve just noticed that if i press same note twice , the second time is not working… I have to alternate notes…:confused:

It wouldn’t be anyway regular, but you could I suppose use the edge out. How well that would work would depend on what you were using the “clock” for.

Yes.

Odd. Is that in all Edge modes?

You’re not using rings as a voice are you? Cos if so - you’ll need to trigger it with strum as well. I just suggest this as I’ve been using earthansible a lot and haven’t seen this problem at all.

How successful have ya’ll been using a-earthsea for LFO duties?

you have 2 options - if you route all voices to only one CV/gate output pair then you can use that gate out as the clock. this would obviously limit you to only one CV output. if you still want to have multiple voices then you will need an external gate combiner (logic OR) module to combine multiple gate outputs.

this version currently does not support key mapping.

7x8 since the left column is used for control buttons.

whichever runes are visible on 8x8 grid, even if partially, will work

1 Like

Just asking here too to make sure.
There is no chance the bundled firmware with this port messes with midi recognition right?
Having an issue that ansible wont „see“ my midi keyboard (other topic) thats why i am asking.

i would doubt that very much, but if you want to rule that out you could try one of the official releases and see if that makes a difference.

I’m pretty sure you can’t repeatedly trigger the same note with any situation on earthseansible (or earthsea for that matter) when just playing it like a keyboard (without arp and loop enabled). Would be nice if you could though…