#30

Confusing at first…but I suppose if the module was being clocked, you could switch to that mode to have it come off of the clock and fall under manual control. Is that the intended use?

#31

I’m synching Ansible to MIDI clock in Ableton. It’s only receiving 1/4 note pulses from my MIDI out.
Is this normal, and if so, do I need a clock multiplier to get 1/8th, 1/16th, etc notes using Kria and MP?

I’ve set the Time setting in Kria/MP so it’s at the highest rate, but my sequences will only go 1/4 note per step at the fastest.

#32

Instead of sending midi sync, send 16th notes from a midi clip out to the ansible.

#33

How do you make the connection between Live and Ansible?

#34

Of course, why didn’t I think of that! Though it would be nice not to need a dedicated 16th note track.

MIDI clock out from iRig Pro Duo or iConnect MIDI4 through Pittsburgh Modular MIDI 2 CV, Sync Out of PM to Clock In of Ansible. I’m pretty sure I can’t tweak the MIDI clock settings for either of the i-devices, though I haven’t yet looked at the clock specs for PM M2CV.

#35

While the PM M2CV would be the device to look after, I don’t think it has a tweakable clock setting. The iDevices should not be able to do it since they just submit midi clock. You could try an audio track with a steady trigger signal output too, if there is on left unused, depends on what Ansible/MP expect.

There are some options you could buy but maybe the sending a faster midi track to the gate out is the simplest/cheapest.

#36

MIDI clock out should be one trigger per eighth note as per the docs, of course there could be a bug.

The larger question is whether 1/8th note timing is was a good idea in the first place (there was a reason for it but that reason escapes me).

If 16th note clock is better it is an easy change.

I should add that one intended enhancement was to allow the midi clock rate to be configurable via teletype.

#37

16ths would be rad. I’m always for faster clocks, easier to divide down than multiply up.

edit, missed this:[quote=“ngwese, post:36, topic:4726”]
I should add that one intended enhancement was to allow the midi clock rate to be configurable via teletype.
[/quote]

very cool idea! i have TT, but ansible currently lives in a smaller case on it’s own - so no ii coms for my setup. are you thinking this would be something you could set from TT, and then would be saved as default to ansible, or would you need to run an INIT script with each power cycle?

1 Like
#38

Hello,

it might be a very stupid question but I have tried to delet a pattern or better to reset it and I was not able to do so…

the only way I found is to go into preset, change it without saving , then go back to the previous one.
Is there a way to do in the pattern view directly?

I might miss something so please forgive me.

#39

this is basically correct.

if you’re working on preset 1, and it was blank when you started, if you want to reset to nothing you can just reload preset 1.

but if preset 1 has data stored in it and you want to erase it, you’ll need to do as you suggest. load preset 2 (or whatever is blank) and the write that to preset 1. no need to reload preset 1 as you’re already in a blank state.

#40

Thanks for the reply :slight_smile:

well do not want to sound too picky but assuming I have done a lot of work on other patterns and I just want to reset pattern one and I do not want to loose the preset, I am not able to do it without basically going through all the pages of KRIA and reset everything.

Sometime it can be a very complex game.

Any possibility of thinking about it in an update?

Thanks

#41

ah, i misread. patterns, not presets.

but yes, the idea is the same.

do you have some UI proposition for resetting a pattern?

#42

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

#43

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?

:confused:

1 Like
#44

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

#45

Aha! From @tehn’s reply here:

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

#46

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

1 Like
#47

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

#48

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!

3 Likes
#49

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