#153

fixed again! new file is up (though functionally the same)

1 Like
#154

the documents seem to have a section within Kria duplicated and i dont seem to see anything to do with the newer sequence direction? I may be wrong but it might be worth checking.

1 Like
#155

Just to report back.
The gig went very well and the ansible was flawless!!!
Next step now is updating to 2.0.0

Thanks for this work I could program sequences on the fly and be able to properly improvise with the grid!!!

1 Like
#156

Thanks for catching the duplicate, here is a PR to remove. The direction modes are under the description for the Scale page: “The next 4x5 group of keys to the right lets you select direction modes for each track.” Not sure if possibly there is another place that makes sense to mention this as well?

1 Like
#157

Ah great, I see it now. I feel like it’s quite an important feature and deserves a bold sub title within scale?
Also wondering if the i2c control made it in to the current version or if that’s in the beta only? I’ve got both a JF and a ER-301 connected directly to ansible using a backpack. I’d be happy to do some testing for setups that don’t have teletype.

#158

Awesome, thank you! It is not in the 2.0.0 build, give me a bit to post a new version with some bug fixes for this feature. In particular I think the key to avoiding crashes is probably in some of this discussion relating to some I2C changes that were necessary for Polyearthsea.

1 Like
#159

Are you able to export the current Kira presets and install them into 2.0? Or is it once you have 2.0 you can then do that for the future?

#160

Both, a step-by-step procedure for extracting a hex backup from your module, converting this to a JSON file, and loading this up after you reflash to 2.0.0 is described in this post.

1 Like
#161

Is key mapping in Earthsea part of this release (a la @scanner_darkly’s Ansible Earthsea feature implementation)?

#162

Yes, see the official docs. Also this is his Ansible Earthsea implementation, unchanged.

2 Likes
#163

Woooooooooooooo!! This is a game changer. Thanks so much @csboling for all your hard work on this!

1 Like
#164

stoked to update this! Ordered my A to A cable from y’all the other day :v:

1 Like
#165

Posted 49013cd in the top post. JF I’m the most uncertain about. Since it accepts a velocity parameter for the JF.VOX command I decided to map this to Kria duration, and am not sure I got the value range right, so it’s possible you need to crank up the duration settings to get any sound out of JF? Also not sure if this correspondence makes sense since I have unfortunately not used a JF.

The UI is now as follows:

  • In any grid app, press the preset key. In the center of the third column over, there are enable toggles for I2C followers. Pressing any of these will enter leader mode and Ansible will no longer be able to receive Teletype I2C messages. From top to bottom the default followers are: Just Friends, first TXo, second TXo, ER-301. Disabling all followers will exit leader mode and return to follower mode. This setting is saved to flash and loaded on startup.
  • Hold the lit bottom key of this column, and touch any follower toggle. You are now viewing the configuration page for that follower. Touching a different follower toggle will select that follower instead. Touching the bottom key again will exit follower configuration mode and return to the main preset page.
  • The top-left 5 lit keys are a master octave shift for the follower, in analogy with the Kria track-wide octave shift added to the octave page in 2.0.0. This is handy for transposing up the base frequency of notes sent to that follower, e.g. the default TXo setting is +3 octaves since the lowest note TXo can output is C_-1 (8.18 Hz).
  • There is now another column of 4 lit keys to the right of the follower toggles. This is a track select. By default all Ansible CVs/triggers are sent to the first 4 voices on a given follower, so all 4 toggles are on. You can disable one or more tracks to direct Ansible not to signal those followers when those tracks trigger. All primary outputs on the Ansible panel remain active, unaffected by this setting.
  • The right side of the follower configuration page is for configuring what messages are sent to the I2C followers, in case you want to reprogram some slots for different followers, or send messages other than gate/CV to followers.

All follower-related settings are saved to flash when preset mode is exited.

5 Likes
Multipass - a framework for developing firmwares for monome eurorack modules
#166

:exploding_head: what an amazing idea. Ive been using Just Friends driven by Kria with Teletype and have had trouble figuring out a way to use the duration parameter.

I would be happy to test this build as well, will give it a shot tomorrow… and I gotta say it would also be suuuper cool to be able to read the duration parameter in Kria as a value in Teletype since it doesn’t measure gate length.

1 Like
#167

This sounds useful, perhaps KR.DUR t p (track, pos) in milliseconds. I’ve been trying to think if there’s a good way to consolidate all the Kria parameters you might want to know into fewer ops, but probably you mostly want like duration, final computed note, maybe to know if a given trigger position is active. For the time being with Teletype 3.1.0 you should be able to measure gate length:

# I
SCRIPT.POL 1 3

# 1
IF EZ STATE 1: X TIME
ELSE: TIME 0

SCRIPT.POL 1 3 or $.POL 1 3 configures the polarity of trigger input 1 to 3 (execute on both rising and falling edges).

2 Likes
#168

Quick question as my Ansible is out for delivery - does the Ansible have any response to Arc button presses, i.e. the older push button encoders?

#169

It doesn’t, the monome device interaction code receives the messages for Arc key presses and Grid tilt but ignores them. You could pretty easily modify the firmware to do something with these if you have a use case in mind.

#170

Anyone know which firmware the newly shipped Ansibles have loaded on them? (mines out for delivery today! woohoo!)

Edit: Plugged it in and loaded it up. It seems to be loaded with at least fw 2.0.0

#171

Apologies for gushing, but I just wanted to say a huge thank you to all the work on Ansible 2. It really is an extraordinary leap forward, making a deep module waaaaaay deeper (will I ever find the bottom of the rabbit hole?). What’s so clever is that you’ve still managed somehow to leave the interface completely familiar to users of the old version.

What an inspirational musical tool!

(Also: thanks @tehn for the repairs!)

10 Likes
#172

Would be nice to have Ansible’s buttons extended to the Arc buttons, so that menu diving could be done on the Arc itself without having to touch Ansible.

1 Like