#39

thanks for spotting, will check

https://github.com/monome/ansible/issues/6

1 Like
#40

docs bump, grid diagrams by @laborcamp

http://monome.org/docs/modular/ansible

9 Likes
#41

Thanks for all the work!

What I did not get by now is what it means that in meadowphysics a CV/scale can be mapped to a track. And regarding the modes 4CV/TR, 2CV/TR, 1CV/TR, what happened with the outputs that a re left when MP/ansible is in 1 or 2 CV/TR mode?

#42

Is there a way to save the contents of the module in a usb key ?

#43

This is great, I was scratching my head a bit on some of the kira features.
Not anymore! Thank you very much @laborcamp !! :smiley:

1 Like
#44

Seriously: ALL credit goes to @tehn.
I am just happy to help out a little :slight_smile:

5 Likes
#45

Itā€™s going to be an all-Ansible weekend! :v:

#46

added to feature requests

1 Like
#47

Great news.
The module is really deep and it appears that it can be seen as the heart of whole performances. So saving would be really important.

#48

The manual says about Kria: ā€œA note will occur only when a trigger is setā€.

Now it seems that the voltage stays at the same note value even when no trigger is set. Is this intentional or can it be changed somehow so that no voltage will occur when no trigger is set?

#49

I noticed that Ansible stops responding when I switch between it (with Kria running) and the Meadowphysics module using the switch module. It stops playing then and the grid stays dark. Often it starts playing again after a few moments, but sometimes I have to shut the whole case down.

Also I just I pressed the preset button and it just stops playing without showing the preset page. Another press did start it again and another press got me on the preset page.

#50

What do you mean by ā€œno voltageā€? 0V? Normally sequencers hold the voltage until the next step.

1 Like
#51

Yes, and normally sequencers connect the gate and the voltage per step and all parameters and tracks are running with the same tempo - I am only aware of one other sequencer that keeps the voltage held over inactive steps until the next active trigger (Verbos Multistage) and it is a pretty nice feature. I just understood the manual in a way that it would apart from that go down to 0 V again on steps without a trigger,

and inquired if this was intended or a bug or could be adjusted as the connection between gates and voltages can be overridden too on this sequencer.

If it is to understand as ā€œA voltage change will only occur when a trigger is set, otherwise the previous voltage is heldā€ it would be okay too and nice to know. Having the CV only occur when a trigger is set would be nice too.

So while it practically would make no difference I donā€™t mean 0V but rather ā€œno voltage informationā€.

#52

So what do you mean, precisely, by no voltage information???

#53

It seems youā€™ve worked this out, so Iā€™m not trying to overstate, but it might be clearer to say

ā€œthe note value is only updated when a trigger is setā€

Whatever voltage was assigned on the last trigger event is held until the next trigger so it seems you are experiencing normal behavior.

My guess is the initial distinction was to clarify that while you can see the playhead in kria moving over a sequence of notes, if you fed your oscillator or sound source directly to an audio output instead of gating it, you would not hear all the intermediate steps between triggers, as you might on other sequencers, and instead the note will only update on the triggers.

If you were looking to clamp the value of your CV back to a base value (0v or otherwise) after each trigger, pairing ansible and teletype might be logical way to accomplish this. On a trigger could have TT read the CV value, and then after a delay reduce to a designated base note. But I donā€™t think thereā€™s really a ā€œno voltage informationā€ state of CV to jump to after a trigger has occurred

#54

As I said, practically it would be 0V and what I theoretically expected was that when a trigger occurs ansible reads all parameters (CV, duration, octave) and then outputs the voltage for the duration of the step and cuts it down to no voltage when the step is over until the next step occurs.

#55

I donā€™t see why youā€™d want to do that, but hey, itā€™s open source :slight_smile:

#56

Multi the trigger out to a VCA and route the v/oct CV through the VCA to the OSC, would also ensure 0V.

#57

Perhaps to make it more clear, it occurred to me when I tried to modulate a non pitch parameter on an oscillator. When working with pitch holding the CV is great as you wonā€™t have ghost notes then with envelopes that have a longer release (and mandatory on a phase thing as Kria). And "no voltage makes not really much sense with pitch cause there will still be the oscillators pitch and mostly not ā€œno pitchā€.

What I tried was modulating a tone parameter just on some single steps and that did not work as the modulation amount stayed constant. I will find another way now for sure.

In general I like the new Kria! While loosing the obscure clock divisions it seems to be far more immediate now. Thinly thing I miss a bit is the scale sequencer but you canā€™t have everything. If I could hack it I would sacrifice the probability page for it but I can see that this is interesting for the original whit whale people and I think it has become a pretty nice combination of its straight forward sequencing and krias has magick.

:grinning:

1 Like
#58

@GoneCavingā€™s solve sounds right up your alley, youā€™ll just need a spare vca. Would probably also be fun to run the multā€™d trigger signal through a slew generator or treat the trigger w/ an envelope before running to the vca