#31

a couple of things to consider - you could use teletype for additional control of ansible apps (or to tie ansible presets to specific tt scenes) and you could read ansible values from teletype and do something with them (making chords / octave switching etc etc). you could build a macro sequencer or controller for ansible on teletype (and use grid to control it).

6 Likes
#32

Hey @EqualTemperament are you reading this about using Ansible from TT to make chords?

1 Like
#33

I did. What a great idea!

3 Likes
#34

the new N.C / N.CS / N.S ops should be handy for this! and use the param knob to select the chord (or perhaps could be cool using one of the kria tracks for chord selection?)

5 Likes
#35

Do you also have a teletype? Then you could try this ER-301 controller scene. https://forum.orthogonaldevices.com/t/grid-ops-base-controller-for-er-301/1907

#36

The released firmware is not able to save presets to a USB drive due to a typo I made. This has been patched in master and a fixed firmware build is here:
ansible.hex (371.3 KB - 2bd3eb0 - 2020/05/09)
You may wish to update from v3.0.0 to this build now so that you can save your presets correctly the next time you reflash. Otherwise carrying over presets from one firmware version to the next is quite a bit more involved.

Thanks @mlogger for finding this bug.

7 Likes
Ansible: help and issues
#37

Hi, not sure if this is the appropriate place to file bugs for ansible 3.0, please move this post if there’s a better place. I’ve updated my old Ansible to 3.0.0 recently and am now trying to learn Kria according to the docs. I have not yet stored any presets after the update.

Not possible to set different loop lengths parameters
According to the docs, “…each of the extended parameter subpages have their own probability, clock division and loop controls.” However, I can not set different loop lengths for e.g. the main note and the alternate note on track 1. So when I change the loop length for the alternate note, the loop for the main note follows this change.

Tied notes are only possible with master duration multiplier set to max
It looks like that the current implementation does not allow to combine relatively short notes with tied notes, as in order to tie notes, I have not only set the “duration slider” for the tied note all the way down, but also have to set the the master duration multiplier to its maximum value. As this prevents having relatively short notes, I wonder if this behavior is intentional or a bug. If I may make a suggestion: Wouldn’t it make more sense to always create a tied note if its “duration slider” is all the way down, and have the master duration multiplier only affect the remaining 5 positions of the “duration slider”?

Thanks for considering. My apologies if I am not understanding things correctly, please help me get it right.

#38

The default behavior is that “loop sync” is set to “all”, so all parameters in all tracks share the same loop. You can configure loop sync to “track” (all parameters within a track share a loop, but tracks are independent) or “none” (all parameters in all tracks have independent loops) via the Config page, described here.

Yes, I believe this is a limitation of how the duration feature is implemented; it just does a calculation of when to turn the note back off that currently only exceeds the clock interval when at this maximum setting (or something like that). I think something like your UI suggestion is worth experimenting with.

1 Like
#39

Thank you very much for your answer & help, highly appreciated!

#40

One more remark:
In the Kria documentation, the link to the description of the tuning mode (at the end of the paragraph about the Configuration page) points to a page whose content is just a duplication of the Ansible main product page (“Ansible – Far communicator, speaks openly.”).

The URL of this rogue page is: https://monome.org/docs/ansible/#tuning, whereas the information about the tuning mode can be found on this page: https://monome.org/docs/ansible/advanced/#tuning

EDIT

Some more things, I hope these are not again cases of myself not reading the documentation carefully enough :slight_smile: :

Missing description for Probability
How exactly does probability work? I could not find any documentation about it. From playing around it seems to work like this – I just don’t know the probability values XX and YY:
When holding down the Probability modifier, rows 3–6 set the probability of steps being played. A step in row 3 means this step will never be played (useful to temporarily mute this step), a step in row 6 (default) means this step will always be played. Steps in row 4 will be played with a probability of XX%, steps in Row 5 will have a YY% chance of being played.
If this is correct, would it make sense to add this to the documentation?

Independent adjustment of one note in a scale does not seem to work
Kria documentation says that “To adjust one note in a scale without affecting its interval relationship with the notes after it, hold the scale key while changing the scale note. The subsequent note is adjusted to compensate.” When I try this out on any scale key, it does not seem to have an audible effect, compared to changing the scale note without holding the scale key simultaneously.

Not all root notes accessible in Scale mode
As far as I understood it, the root note can be moved within a range from 0 to 7 semitones. It looks like there is no way to set the root note to 8, 9, 10 or 11 semitones, although this might be desireable when e.g. playing with others.

As it currently looks as if the combination of holding the Scale key and any of the Root keys does not yield an audible effect, perhaps the following could be added in a future revision:
• Scale key + root key 9 or 10 = root key transposition +8, root keys 9 and 10 will be lit.
• Scale key + root key 11 or 12 = root key transposition +9, root keys 11 and 12 will be lit.
• Scale key + root key 13 or 14 = root key transposition +10, root keys 13 and 14 will be lit.
• Scale key + root key 15 or 16 = root key transposition +11, root keys 15 and 16 will be lit.

How to reset a sequence manually?
I can reset all sequences by applying a rising signal to input 2 (reset). Is there a way to achieve the same by pressing a button on the grid?

Thanks much for reading!

AND ANOTHER EDIT

Copying Scales
I really enjoy editing a scale while a sequence is running, and of course switching scales is also fun. It would be even better if there was a way to copy the current scale to another scale slot to develop it further, while still being able to switch back to the original and forth to the new edited version.

From a workflow perspective, copying the current scale slot to a different slot could be accomplished accomplished by first holding down the current scale slot, then pressing the scale slot to copy to (while continuing to hold the current scale slot).

Voltage values instead of Notes
It would be great if a track could be set to output voltage values instead of notes. The reason: I’d like to use one or more tracks to control non-pitched parameters, and when doing this, it would be great if (a) the CV value is not be quantized to the currently selected scale, so that it won’t change when changing scales, and (b) if the CV value could be adjusted differently than setting notes and octaves.

To facilitate CV value adjustment, the current note screen could be changed to (1) give a coarse visual indication of the voltage of a step from 0–5 Volts, and (2) allow adjusting the voltage itself per step. The variable brightness of the buttons of row 3–8 could be used to indicate the voltage of a step like this: No button lit = 0 Volt, all buttons lit = 5 Volt, rows 3–6 lit = 2.5 Volt etc.

To adjust the voltage of a step: Press a button in…
…row 3 to decrease the voltage in a 1V step
…row 8 to increase the voltage in a 1V step
…row 4 to decrease the voltage in a 0.1V step
…row 7 to increase the voltage in a 0.1V step
…row 5 to decrease the voltage in a 0.01V step
…row 6 to increase the voltage in a 0.01V step

Again, thanks much for your time for reading and considering!

2 Likes
#41

I’m attempting the process described here to extract the preset .json from a dfu-programmer read dump. Looks like the Python script needs a new schema for 3.0.0. Is that as straightforward as creating a schemata/ansible/v300.py and updating all the C struct definitions to their 3.0.0 versions?

EDIT: looks like it’s a little more involved than that, I’m making some progress, will take any further questions to Github.

1 Like
#42

Note that if you are coming from v1.6.1, you can use the script to generate JSON and then load it onto a module running any later version of the firmware – the JSON format is forward/backward compatible (modulo me fudging the definition file). This is why I haven’t been very thorough in adding new Python schemas because this procedure is generally only needed when updating from a <2.0.0 firmware. If you flashed to 3.0.0 already and have new settings since then, that’s another matter since due to my bug you’re kinda stuck.

I have a Python schema file or two for a couple more recent versions but haven’t PRed them and am less certain they’re correct. Might be able to save you some work.

#43

Yeah, I had upgraded to 3.0.0 and already made some kria patterns that I wanted to save. I think I got it all sorted! https://github.com/monome/ansible/pull/80

2 Likes
#44

Can someone please explain how do I activate JF control from kria on ansimble? Couldn’t find any info on this in the docs.
Re controlling er301 from kria, is there a setting to activate this or it just feeds over ii by default?
Thanks!

#45

it’s in the advanced doc: https://monome.org/docs/ansible/advanced/#ii-leader-mode

#46

Im trying to adjust the tuning calibration with my ansible (it is not tracking across octaves) and Im wondering how to adjust the initial value for track downwards? The keys are not lit, and there does not seem to be a way to adjust in the downward direction. The issue Im having is, lets say I have my oscillator tuned to A, and then I plug in the v/oct from output 1, the oscillator will jump up 8-10 cents sharp rather than staying static. I can adjust the next step and have it be exactly right, as with all other steps in the sequence, but the initial step requires me to basically connect my v/oct, slightly retune the oscillator, and then everything is good. Id like to be able to avoid that if possible. Thanks!

#47

You can’t, the DACs are unipolar and the initial value is what they output when their digital input is zero. To get them in tune you have to find which output has the highest initial voltage and bring the other channels up to meet it. So unfortunately there’s not a way to keep this pitch jump from happening.

#49

dfu-programmer: not found would mean either that dfu-programmer did not install successfully through homebrew, or it did but your terminal can’t find it. Make sure that you don’t get any error messages from brew install dfu-programmer, if you do you can post them here or PM me. Sometimes you might have to restart terminal or something for a newly installed program to show up. Once you’re able to run dfu-programmer we can go from there with troubleshooting.

This just sounds like the default setting where loop mode is ALL, this is configured on the config page. It’s saved to the module so it’s possible you had changed this at some point in the past. If you don’t have Earthsea then you didn’t get updated though, but if this setting changed then possibly you reflashed the old firmware file you had?

#50

Is it an issue with the hardware itself?

#51

As far as I know, yes, DAC offset error is typically caused by things like inexact component values, even things like resistance mismatch inside the DAC chips. You would have to compensate for this with an external offset.