#136

Hello,
Just to say that I have been playing extensively with the previous build and I am going to perform tomorrow with it as well.
No freezing or leds problems.
I have also used very fast clocks and very slow ones as well as internal clock.

It seems very responsive to me.
Finger crossed for tomorrow, I will try the new build after the gig.

2 Likes
#138

Two days ago I finally found the time to install the latest Ansible beta (2019/07/03). The update went flawlessly, so the the reason for the problems I mentioned earlier in this thread was in fact a wrong cable. Buying a new USB A-A cable did the trick.

The new Kria features are awesome. Thanks a lot for the hard work on this! (And no crashes yet: very stable so far.)

I have one issue though: I’m clocking Ansible externally (Pam’s -> In 1) and I don’t manage to activate independent time divisions on the TIME page. I switched the left and the right Glyph off (according to the manual) and tried various other settings, but when I change the note time division the trigger time division follows automatically and vice versa.

The middle Glyph (Division Cueing) doesn’t work either: Even when it’s lit, all time division changes are happening immediately.

I didn’t use the TIME page much in V. 1.6, so apologies if this is just a user error.

1 Like
#139

Are other parameter divisions also changing in sync? If either of the glyphs on the right side of the bottom half of the clock config page (key 1) are lit, divisions will also be synced even if the left-hand glyph is off.

Seems okay to me on this build in all modes I tried, with or without external clock. It’s a little more evident what it’s doing at slower clock speeds? Can you post or PM a video?

#140

All glyphs on the TIME page are off, all parameters I tried are linked. I PM’d you two videos (a second one for the cueing). If it works for you I’m probably doing something completely wrong.

Thanks!

#141

@csboling thinking i’ll tag 2.0.0 and post a release? we can do point fixes if needed. same with tt 3.1.0

#142

Teletype 3.1.0 I’m not aware of any issues or outstanding features, should be good to go.

Ansible is I think also stable enough to tag 2.0.0, think this will do a lot to reduce confusion. The following work is ongoing:

  • Investigating this weird crash which I think must have to do with specific I2C configurations or something else that makes it hard for me to reproduce. Sounds like most users have not encountered this.
  • I2C leader mode. This I think will need to wait for the next version: it has not been confirmed to work with JF or ER-301, and if you patch in a super fast external clock it will crash after a couple seconds.
3 Likes
#143

@csboling just replied to my PM regarding my time division problems, and of course it was just a user error: I changed the divisions on the CLOCK CONFIG page instead of the TIME MOD page. Sorry about that. Everything works as intended.

One related question though: The standard TIME MOD has the leftmost key activated, so I can only divide the tempo. What if I want to speed up (multiply the clock) of a parameter though? I could start with sending a 16x clock instead of a 1x or 2x clock to the Clock In, but then I would have to initialise the TIME MOD to a higher (division) value for each single parameter to start with a neutral timing. How are you using TIME MOD? Is there an easier way to achieve individual clock multiplications?

#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.