#144

One way you could fudge it with the new division sync options is as follows:

  • Set the master clock on the clock config page to the fastest clock you want.
  • Also on the clock config page, set div sync to “all” (4 keys together in the bottom right corner should be lit) and turn note div sync off (hollow square on bottom left)
  • Now go change the time division for any parameter using the TIME MOD page, to /4 or /8 or whatever. Since div sync is “all”, all parameters on all tracks update to use this time division at once.
  • Now you can go back to clock config to turn div sync back to “off”, allowing all parameter divisions on all tracks to be independent. You can now selectively speed up individual parameters via the TIME MOD page by decreasing their division amount.
1 Like
#145

Thanks, that’s probably the fastest way to achieve individual clock multiplications. I don’t know if this has been discussed already, but would it make sense to add clock multiplication the the Kria feature request thread? There could be a second row on the TIME MOD page, so one for divisions, another one for multiplications?

#146

Clock multiplication is liable to be more complex to implement than division, especially in the presence of external clocks from the IN 1 jack or Teletype. The master clock division on the clock config page is pretty central to how all timing on Ansible works, you could probably not make anything go faster than this without changing how clocks are managed. I am not actually too sure offhand how clock multiplication is generally done in software though. The 4ms QCD does quite a nice job (with up to x16 multiplication!) but I have not wrapped my head around its source.

1 Like
#147

please let me know if any changes are needed!

thank you @csboling and @scanner_darkly. these modules just keep getting more musical!

16 Likes
#148

Great timing. I just came on to check for new Firmware for TT and Ansible!

Small note - the version number on TT is displayed as " .1.0" - the “3” is missing.

1 Like
#150

thanks for catching that. my git version was out of date (--exclude wasn’t working and there was a bug in the makefile)

updating files

3 Likes
#151

Not sure if folks here have looked at this issue, but I’d love to get some feedback and maybe figure out a fix

Basically ansible is crashing if an HID device is plugged in. In my case this is with a Teensy based midi device (which also enumerates an HID)

Need to re-test with the new release version when I’m back home in a few days.

1 Like
#152

So this release after installing it should still read; DD55836 Dirty?

#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