#95

When I power the rack on after having updated the firmware from 1.6.1. and go to the config page by holding key 2, none of the three configuration graphs is lit.

I can not select different loop start/end points for for one or more tracks independently from each other.

This is not possible to achieve - neither with the hollow square glyph lit or greyed out.

I have not tried beb7a60 yet but will as soon as possible, although the issue is not that sync modes are not working correctly but that it is not possible to turn them off. I try to get the Ansible out of the rack and look after the board revision (i2c cabling makes taking modules out a bit cumbersome sometimes…). I guess it’s an early one as I bought it right in the beginning together with the first new Arc4.

#96

I think this should be enough info, I know mine is also a pain to unrack, thanks.

Do you have external clock and/or reset patched in? I think that bug made it into some builds but that was a little while ago, I also thought it only affected the clock config page. It’s really interesting that the glyphs are not lit, but the sync is active. Also do other apps seem to work okay?

#97

there is only one rev of the Ansible board

up until this new batch

1 Like
#98

No external clock or reset patched. On a short glance Earthsea an MP are working correctly, but I have not fully tested all features. (still have an original ES, so I have to dig into the differences). Also when I came back to Kria from ES the grid became unresponsive. Switching through the apps again fixed that. The note wrap loop ghost is gone though, wich is great! :slight_smile:

1 Like
#99

I think my problems to update Ansible to the beta firmware is a cable problem. I lost my USB A-to-A cable, so I’m using a USB A-to-C cable to connect Ansible to my Macbook Pro. I powered up Ansible while holding the button next to it’s USB slot, but when I’m executing update-firmware.command the dfu-programmer says “no device present”, which probably means, that it can’t detect Ansible?

When I updated Ansible to 1.6.1 I used the original Ansible USB A-A cable and a USB A-C adapter and that worked, so I probably just have to get a new USB A-A cable.

1 Like
#100

So as of the last couple builds there are I guess up to 5 separate glyphs on the key 2 config page, depending on how you count:

  • Top left corner: Three “radio button” keys, the rightmost is lit by default. This is for specifying your preferred brightness settings, to adjust for 1, 4, or 16-step (the default) varibright grids. Currently 1 and 4 are the same but more brightness tweaks may be added in the future.
  • Centered on the left side: Hollow square for Note Sync. On by default.
  • 4 keys in a row, collinear with the bottom line of the Note Sync square: Loop Sync = All. On by default.
  • A single key above the Loop Sync = All row: Loop Sync = Track.
  • Bottom right corner, in the key that corresponds to Kria’s key for accessing the Scale page: Go to tuning page.

When key 1 is held for clock config, the existing clock configuration UI is shown unchanged, along with 4 new glyphs along the bottom half:

  • Hollow square in the bottom left corner: Note division sync, for syncing the time divisions of the trigger and note parameters. Off by default.
  • Filled square bottom center: Time division cueing, for waiting to latch time division changes until the loop ends. Off by default.
  • Row of 4 keys bottom right, collinear with the bottoms of the other two squares: Div Sync = All – all tracks will share time divisions for all parameters. Off by default.
  • Single key above the Div Sync = All row: Div Sync = Track – time divisions are shared within each track, but tracks may have different divisions from each other. Off by default.

Do these options have the described effect on time divisions? Do other new features, like direction changes on the scale page, or trigger clocking work? I’m pretty well out of ideas – clearly if I’m grasping for hardware differences. Sorry this has been such a pain.

1 Like
Kria loop length feature broken?
#101

Oh, I seem to be embarrassing stupid. I pressed and held key 1 instead of key 2. I only used the config page to switch all sync options off and then never again by now and the glyphs felt so familiar when I saw them that I did not notice my mistake. I feel terribly sorry for the hassle I introduced.
:flushed:

I hardly dare to pose another question now, but on the ratchet page, when an active trigger has ratchet sub triggers and the next steps are inactive on the main trigger page, the step indicating light is moving on the row of the last active ratchet sub trigger instead of the highlighted main step row (row 6 on the grid). Is this for a special reason?

Also regarding the irregular sub steps - I cannot find any circumstances to reproduce this. It is just happening every now and then under all circumstances, maybe more often at higher (but still reasonable) tempo. Sometimes sub steps are missed, sometimes there are extra substeps (as in: all step subdivisions even if one is off/greyed out). If there is any possibility to introduce this by accident I might have done it somehow of course, as we know now…

1 Like
#102

Yeah I worried about this being confusing! These glyphs on the clock page are just similar to the ones on the config page as far as the set of parameters they link together. Do you think a different glyph should be used or they should be visually distinguished some other way?

I imagine it was probably a little easier to code this way since I think a fair amount of stuff is determined with “if a trigger happens, change X” and so another event hasn’t happened yet to reset the row the playhead is on. It might be possible to reset the vertical count when the last gate goes low, I’ll look into it.

The messed up ratchet behavior is interesting. The next time you see it, one thing we could try is saving it as a preset, then backing up to USB disk and sending the JSON file over to me, to see if it preserves the glitchy behavior. That process is described here. I’ve tried running at pretty fast clock rates with a random set of 10 or 20 ratchet triggers set, then counting the triggers with Teletype to check for skipped triggers, and it’s looked okay. But maybe the skipped triggers and the extra triggers are cancelling each other out…

#103

I am not sure - I think as soon as this is official with a manual one would go through it could be clear that there are two config pages. The glyphs are indicating the same behaviour for different features in the end and having the division setup on the clock page is already an indicator.

I will look into the USB preset JSON file thing as soon as I have some spare time again and then try to send you a file.

#104

@csboling I have a quick question and haven’t had time to try any of the betas just yet. But what I have seen from the videos is amazing. Thankyou for all these updates!

On the original v1.6.1 Kria one thing i found frustrating was having the master tempo being set in the global menu, and not set per preset. This mean’t when i play live, each preset played at the same default global tempo unless I clocked externally. This also mean’t that if I changed the global tempo, it effected every preset. The way I use Kria is basically, every preset is a complete song and I want each song to have its own default tempo. I know you can clock divide per preset, but is it possible to have a master tempo set per preset? My workaround for this is to set the global tempo quite high and don’t change it, so then, I have room to divide it down on each preset.

1 Like
#105

This seems possible but would take a bit of doing. I might want to make sure it still works if you try to load a global clock setting, since I’m not sure if other users are maybe relying on the existing behavior? Seems like it makes a lot of sense though, and something that if it’s going to be changed should happen before the 2.0.0 release.

2 Likes
#106

I can understand that and backwards compatibility is really important.
I wouldn’t want breaking changes were you could potentially lose work or have to edit prexisting tunes made in v1.6.1. So I would still want global tempo to be there, but as an option.
How about having the global tempo set as normal “on” in the default globals but also an option to switch it “off” in global. With the default being “on” as normal so it doesn’t affect older firmwares. When you switch it “off” there is some option that appears in a preset?

I’d be interested to know if other Kria users are happy about the way the global tempo is currently setup and if it effects them when they move from preset to preset. I just find it a bit frustrating because I could never remember the original tempo I used for each preset. I used to take photos of the master tempo, then gave up and just kept it the same for all presets.

1 Like
#107

This sounds great and I think since this wouldn’t affect any existing behavior unless you opt in, it wouldn’t be so critical to have it ready to go this release. Since the global clock frequency is such a core piece of configuration I’m a bit hesitant to try and do this and be confident that it’s been thoroughly tested on top of everything else that’s changed. I think probably I will follow up with you on developing and testing this to go in the next version.

New build (afbc529) has a simplified tuning UI and some bug fixes. I think I’m basically ready to call this feature-complete for 2.0.0, but I am planning to put a little more time into looking for bugs, new and old.

8 Likes
#108

as a possible addition to v2 would leader i2c mode be worth considering? something very simple:

  • a choice between follower mode (how it currently works) / leader sending to txo / leader sending to just friends / leader sending to er-301 - this would be shared by all apps / presets. could be simply 4 button switch on preset page?
  • no custom mapping, 4 txo/jf/er-301 voices simply mirror ansible outputs
  • no glide support - i don’t think i2c would handle it well
  • because of the above, probably only enabled for grid and midi apps?

should be a fairly trivial change using polyES/multipass code.

5 Likes
#109

TXo and ER-301 both support messages for setting the slew duration, would it be sufficient to send these once to the appropriate follower when a glide setting is changed?

1 Like
#110

Any chance to implement as well the possibility of channel output/routing selection per pattern as in polyES?

#111

haven’t thought of that - great idea, this might do the trick!

i think this would overcomplicate the UI too much.

#112

Didn’t realise it was a UI matter, thought it was about disk space. If it is a UI matter, would it be confusing if these assignment options appeared only in the ES app?

#113

if something were to be added for free voice mapping ala polyES, it would be more consistent to apply it to each app, not just earthsea.

i’ve heard complaints that polyES voice assignment is too complex, which is fine for polyES - if you’re willing to learn it you’ll have the ultimate flexibility and some really neat tricks that come with it, and since polyES is a standalone alt firmware you know what you’re getting (although you don’t ever have to touch voice/output assignment for basic use). but adding it to ansible would likely create confusion for more users.

i would just see the leader modes as a simple way to send notes over i2c (and, used with MIDI app, a way to sequence TXo or JF with MIDI).

5 Likes
#114

@csboling: what changes, if any, need to be made to the documentation to reflect all the new functionality?

5 Likes