Ansible Docs

[tehn]

ah, i misread. patterns, not presets.

but yes, the idea is the same.

do you have some UI proposition for resetting a pattern?

[bassik]

well
the pattern page has a lot of free buttons as it uses only the top row.
Maybe we can say

2nd row reset (back to the 6 steps, no note, no clock division)
3rd row copy pattern
4th row past pattern
5th row and more no idea for the moment…

or maybe
2nd row reset first row of the pattern
3rd row reset second row of teh pattern
4th row reset third row of the pattern
5th row reset fourth row of the pattern
6th row copy entire pattern
7th row paste entire pattern

[scrag]

Can someone elaborate on the voice modes available for Meadowphysics? 8TR outputs sends triggers only, and each row has its own output, I get that. But I’m not sure how the other three modes are supposed to work, and no matter which of them I select, as far as I can see, I can only get a CV / trigger pair being sent from the top two outputs anyways.

What am I missing?

[marcus_fischer]

I am still a bit confused on the four voice mode
how to control which rows corespond to which trigger outputs.

[scrag]

Aha! From @tehn’s reply here:

Meadowphysics / Ansible question

the voice modes on MP are basically rotating allocators, so there is no explicit assignment per row. any row has a chance to occupy any of the four voices in four-voice mode. if MP is on “toggle” mode this becomes much clearer to see, when there are more held notes. typically in the trigger/blip mode there aren’t very many overlaps, so most of the notes go out voice 1 or maybe voice 2. i’m trying to imagine a voice assignment application-- are you thinking of rows split to specific voices? sho…

I’m assuming that the voice modes select which output pairs are in use, where selecting 1 CV/TR makes Ansible a monophonic device?

[fourhexagons]

The deeper I go into Monome, the more I appreciate the aesthetic. It’s so good. Thank you again, @tehn for making art out of this stuff.

So, I was looking through the Ansible docs and noticed a typo under Kria: Basic.

The second block, which contains Trigger, Note, Octave & Duration, starts on key 6, not key 5. It should read:

6-9: Trigger, Note, Octave, Duration

[rdfm]

Can anyone explain to me what the second and third config pages in cycles have control over? I can’t seem to figure it out on my own and it doesn’t seem to be listed in the docs

[Jonny]

In the second page, you can attenuate the output of the voltage. The 3rd page allows for more divisions per cycle for the gate output. Really useful features in a small system!

[rdfm]

That is super useful! Thanks for the explanation

P.s. @tehn I think this would be a very helpful addition to the docs for future users