I see. Usefull too. I think another option would be to play and rec the monophonic melodic sequence and than while it plays back send 2x cv/gate to the sampler module and dial in sounds to both channels. Could get chaotic and the hard part is on that sampler module i suppose. But technically i cant see a way it wouldn’t work. So basically sending the same sequence in 2ch pairs to 2 modules.
if you’re sending the same sequence why not just mult the output to both modules? perhaps i’m not understanding what you’re trying to do.
Probably i am too much into the future. The idea behind it was dialing in sounds (in a sampler) to notes of the sequence wich would make sense to add to the main sequence. For that i d need 2 Ch cv and gate. Given the multi outs of ansible i dont see why i d need a mult. But never mind… i think i ve to find out. The option of a sequence playing and live playing another module is allready a nice one.
Multiple sequences would be soooooo dope.
i have some ideas i want to explore but no definite timeline for that yet.
Edit: Figured it out.
Can someone tell me how to save patterns? I can’t seem to find it in the docs. Thanks
2x mode Long press one of the pads of the first row from up to down In the docs but i needed some time too. Loading = 2x mode and 2x pad
Gotcha. I was trying to figure out how to write/save patterns as opposed to saving presets. Saving presets is the long press/2x press.
To create patterns and “save” them you merely select any “pattern” in the 4x4 grid in the “patterns” page, then just create a pattern and it saves automatically. I think at that point you need to save the whole preset to maintain the saved patterns.
Is that clear?
Oh i didnt get that far yet and just saving presets for now might be i stopped trying when it wouldnt store, so the need before power cycle saving the preset would explain that.
Yes I feel ya. I have always been a “not saver” and basically start from scratch every time I fire up my rack. I think it is time to change that approach though.
yeah, there is no separate “save pattern” functionality, you can only save patterns by saving the whole preset.
Whats the meaning of this: When i am in voice allocation setting the furthest pad down is light up aswell. Same row as the 4 gate leds but actaully on the bottom of the grid. I can change it to the cv row from the gate row and back but not switch it off and not switch on both. I dont really get it. And since its in the multi voice settings, original earthsea documentation has no mention either.
a bit confused which row - could you post a pic?
Yep here it is… 20 ´/ ch. o
ah, you mean column, not row. does it stay on in other modes?
also, can you elaborate on this?
there are no cv/gate rows - do you mean voice allocation for recorded patterns / live?
Yes i meanin „pattern voices“ isnt that voice allocation? It is only visible when in the mode (pad left down depressed) It is there right after startup…just i think it wasnt at first. I can depress the next pad (cv collumn) then that one is lid and the one in line with the gates goes off. Nothing i do changes it and i ve no idea what it means
sorry, but what do you mean when you say cv/gate column? voice allocation does not correspond to ansible outputs. the column on the left represents pattern voices, the column on the right is live voices.
When the pad left/down is depressed, i enter pattern voices / live voices To my understanding the left of the 4 active pads (in my case only 1 active) represents the 4 triggers and the right the 4 cv gates?
But the led thats lid down there shouldnt be!?
Is there any othet manual for me to study then the original ES and the quick refernce? I feel i really missing basics
no, a “voice” is a CV/gate output pair. on voice allocation page the left column represents voices (so, both CV and trigger outputs) allocated for recorded patterns and the right column represents voices allocated for live playing.
did you see this manual? it has a very extensive section on voice allocation: https://github.com/infovore/monome-docs/blob/aearthsea-docs/docs/modular/ansible/index.md#voice-allocation
not sure why that LED is lit but if it doesn’t affect functionality i wouldn’t worry about it.
I was indeed missing that manual updated to aerthsea! Thank you!
Jup everything seems to work normal. I have voice problems with a disting mk4 multisample algo and thats why i noticed. But that issue is most likely not grid/earthsea dependent
