New to Ansible diving into Kria

Have a 40h and now got a 128 Walnut vary bright + new Ansible. Updated to firmware 1.6. 1 Got most Max patches to work, red the manual 20 times at least and was able to produce something working with my modular. Now am just stuck with understanding the extended stuff. The manual says

  1. Loops and time dividers are per parameter, per track, and so the phasing of parameters a fundamental feature of Kria.
  2. Just like the primary parameter pages, each of the extended parameter subpages have their own probability, clock division and loop controls.

I just don’t get what is meant by Loops / Loop controls per parameter, per Track.
Config is set to “Track” but any change to loops is general and not per parameter or per track.

Please some enlightenment, thanks in advance.

“Track” means that you can only set the same loop length for all parameters of a track, i.e. a track will have the same loop length for triggers, notes, octaves and so on. To select a different loop length for a track, you either have to be on the first page (triggers) where you can see all four tracks at the same time or select the correct track with the four left-most buttons on the bottom row.

Try this: Go to the first page, press and hold the first of the three modifier-keys in the bottom row and then set a loop for one track by pressing and holding the first step of a track and then pressing a different step on that track - the loop should only change for that one track and it should be the same length for all the parameter-pages of that track.

1 Like

Thanks for fast reply ! :grinning:

@x2mirko I tried that many times but the loop length changes all 4 tracks (as display on first page).
I think I tried every other parameter, modifier and extended parameter and it worked just not with the loop.

I think you want to change the loop synch parameter to “none”. From the manual:

Kria has two parameters, represented on the left and right quadrants of the grid when Key 2 is held down.
Loop Sync is shown on the right quadrant of the grid. There are three modes:
None (nothing lit): all tracks and parameters can have independent loop points
Track (top single block lit): all parameters within tracks have the same loop, but tracks can differ in their looping
All (bottom row of 4 lit): all tracks and parameters have a synchronized loop
By default Note Sync is on and Loop Sync is set to Track.

1 Like

Oh, my bad :blush: sorry !

As I did not save anything yet, Ansible starts with default thus Config for loop is set to “All”.
Setting to “Track” it works as it should with different loop length per track :sunny:

@kbit Thanks for leading me in right direction !

1 Like

Another question: Duration

Manual: The duration view has downward sliders (lower is longer) and a master duration multiplier at the top.

Even all “slider” lowest, Multiplier max right/left does not seem to change anything.

Any hint appreciated, thanks in advance.

1 Like

Think found answer myself: Duration is about gate and has nothing to do with timing in grid.

One day confusion will end … hopefully …

1 Like

There’s also a divider row for duration length to make the max duration longer :+1:

1 Like

@kbit Thanks, got it.
Just doing really simple stuff while trying to wrap my head around the relationship of duration, time and GATE/CV. And this is only the beginning of complexity … Luckily no need to hurry :grinning:

Maybe should write something down, take videos … just not to forget :nerd_face:

1 Like

Please do! I find there’s not many videos at the moment, would be appreciated!

1 Like

Yay, missed a few more intro videos too. But making a decent video is a time consuming job, have to see what I am able to produce. :clown_face:

Wonder if anywhere the technical values for duration (steps, sliders), time (modifier) and time view can be found ? Maybe need to read the source code, must be somehow declared :thinking:
I admit that at the moment have a hard time figuring the correlations between all these time based parameters with the help of an oscilloscope (I like to visualize such things as a graph for better understanding)

Edit: I must say, wow, is this crazy. :exploding_head: Visualizing the outs is - at least for me - a tremendous help to understand what’s going on inside.
“negative” side effect: badly want a TT and second Ansible and everything else too just need :money_mouth_face: