Kria strategies

[eblomquist]

Thanks… do you mean the signal input or the trigger input on maths? Or even the both input?

Would you then send the maths output to the cv input of a VC-1 or lpg?

I have a maths and an optomix as well as a Pittsburgh vca…

[alanza]

twenty characters of signal input

[eblomquist]

Thanks, and am I correct about the other bit?

[eblomquist]

And how would you set the rise and fall on the maths to take advantage of the differing duration from Kria?

[alanza]

if you patch a gate into the signal input on Maths, you end up with an ASR envelope, with the attack and release time controlled by Rise and Fall, respectively. So, to REALLY hear the effect, Rise and Fall maybe shouldn’t dominate too much, depending on your preference.

[gnome666]

Trying to post a question here, as I’ve searched the other posts and haven’t found much. My question regards quantizing/syncing timing changes with Ansible/Kria. Basically, I am trying to figure out how I can make changes in Kria in a quantized way. For instance, even switching from pattern to pattern, if my timing is a bit off there is a noticeable skip/jump as the new pattern resets. I think I’ve read elsewhere here that theres no function to be able to quantize this behaviour, so that the pattern will only change on the next clock pulse?

Also, I’m finding it frustrating that when I change time division for one track, lets say on the trigger page, all the other pages don’t snap to the same time division within that track. This necessitates paging through all parameters for one track and switching the time division on each page, which then makes them out of sync with the change made on the first page of the track…

Hopefully someone has come up with a technique to workaround this. I know that part of the attractiveness of kria/monome is it’s opennens and “unsynced” nature to allow for syncopation etc, which I also like using sometimes. it would be nice to have the other option as well

Lastly, I will add that I have found some mention to teletype having the ability to play some sort of role in addressing this issue, however I am nowhere near having any sort of functional knowledge of teletype…

Thank!

[Autogeneric]

The loop setting is on the config page, you can set it to independent, track, or everything. Take a look at the documentation.

[Autogeneric]

Oh and pattern to pattern - there is a button combo - I think the pattern page button and the pattern you want - that will wait for the pattern to finish and move to the next.

This isn’t exactly what you want - if you’re looking to swap mid-pattern but on the beat - but gets you part of the way there.

Sorry for imprecise details, am currently not at the modular…

[alanza]

On exercises, practicing, and rehearsing

play Awake on Kria

turn on each step for track 1 in the trigger page, write a simple 8-step melody, doesn’t need to be fancy on the notes page (make sure to set the note page loop length to 8!), and then press the note button again to get to the alt-note page. Set the loop length to 7, but write something relatively spare—two or three notes different from the root is plenty. Now you’ve just written 7 bars of music, with the added benefit of the feeling of musical progression coming from the phasing of the alt-note sequence against the main melody. And then of course there’s plenty to explore from there, but having that as a baseline is very exciting to me.

I didn’t see this thread earlier, but I guess this probably belongs here too.

[gnome666]

I’ve tried that, but as far as I could tell, that just makes sure that all 4 tracks have the same loop length. i.e. if you set tracj one to loop steps 2-5, then with loop config set to “everything” it makes tracks 2-4 also loop at steps 2-5. When i tried this it didn’t seem to have any affect on timing difference of steps on different pages within a track…

[gnome666]

will try this pattern page button thing. at least its something

[feathers]

wow! thank you for sharing this - i’ve neglected the alt note page and haven’t worked up the confidence yet to dive into meta-sequencing, so this is kind of game-changer for me in terms of putting together sequences that don’t sound like 16-step loops.

[kbit]

The “relatively spare” part of @alanza’s strategy is key in my experience. Setting the alt note to something like 12-16 steps long, divided heavily, can result in very long cycles that will be carry a theme of the note page with well placed variations via the alt note page.

I also find it a lot of fun to set the note and alt note pages to a very short loop length, like 3 and 4 respectively, then playing the notes on each page to manifest new melodies quickly.

[Autogeneric]

I may be mistaken, but I’m fairly certain I had this working at some point.

Anyhow, I should probably call out - and this is linked to Alanza’s post - that the ability to have different sequence lengths for different aspects of the same track - is one of the key points of Kria. Having gates, note values, alt notes, probability, ratchets etc - running with different phase relationships - is both rare and liberating in equal measure. (No pun intended, but it’s quite a good one…).

But it can be a chore if you need everything to end at the same time, if that functionality doesn’t work as I think.

[gnome666]

button combo for “quantized” partern changes worked as you described. Thanks for the heads up. I went back to RTFM, even though I RTFM’d many times before, and lo and behold, the button pattern you described is right there

[Bigtime_Snacks]

Relatively new grid/ansible owner here. I gelled with Meadowphysics and Earthsea pretty quickly, but Kria has me feeling a bit on the dense side (even after reading the documentation). I’m hoping someone can answer a few questions for me.

Steps: When you’re in trigger view, the upper left corner of Grid is lit in a 4x6 pattern. This means that the sequence is 6 steps long, right? Is there a way to edit the number of steps in your sequence?

Tracks: I’m not understanding how tracks interact with each other. Example: I program a few triggers in track 1 and then switch to track 2. I still see the triggers from track 1 and pressing the keys of those triggers will deactivate them in track 1. I feel as if I’m missing a major concept behind how tracks work.

I feel like once I have a firmer grasp on these two concepts that the rest of the app will fall into place for me.

[csboling]

When you’re in trigger view, the upper left corner of Grid is lit in a 4x6 pattern. This means that the sequence is 6 steps long, right?

The trigger page is the only page that lets you review all 4 tracks at once, so you can see when triggers happen relative to each other. So yes, in the default configuration Kria will have a sequence length of 6 for all 4 tracks. You really have up to a 16 step sequence, and the highlighted 6 steps are showing the selected 6-step “loop” that’s playing in that sequence – you can toggle keys further to the right on the top 4 rows to see them light up, but these triggers won’t be hit unless the loop selection includes them. To move the selected loop, hold the LOOP key and tap a key in the top 4 rows other than the start of the current loop selection. Note that the loop selection can also wrap around the edge - if you hold LOOP and then tap the rightmost key, your selected 6-step loop starts on the farthest-right key on the grid and wraps around the other side to include the 5 leftmost keys.

Is there a way to edit the number of steps in your sequence?

To change both ends of the loop selection rather than just moving the start point, you use a 3-key gesture: hold LOOP, hold the desired start point, then tap the desired end point.

I’m not understanding how tracks interact with each other. Example: I program a few triggers in track 1 and then switch to track 2. I still see the triggers from track 1 and pressing the keys of those triggers will deactivate them in track 1.

On the trigger page (6th key from the left on the bottom row is lit) you see all tracks, and can toggle any trigger for any track from this view. All other pages should control only the selected track (the leftmost 4 keys on the bottom row are the track selects). All 4 tracks can be programmed independently of each other. The only interaction between tracks has to do with how the loop selection works - by default the “loop sync” mode is “all”, which means that all four tracks share the same loop selection for all parameters. You can decouple track and parameter loop selections from each other by changing the options on the config page (shown when key 2 on the Ansible front panel is held).

Programming parameters within a track typically does not affect other parameters on the same track either. The exception to this is the “note sync” setting (on by default) which keeps the trigger and note pages in sync with each other – they share the same loop endpoints, and toggling a note on the note page will toggle the corresponding trigger step for the selected track, and vice versa.

[Bigtime_Snacks]

Many thanks for the detailed answer! Setting the loop length is exactly what I was looking for, I’m not sure how I didn’t pick that up in the documentation. I don’t think that I was processing the meaning of “track” in the context of Kria/Ansible either. Anyways, i think I’m on my way now. Thank you again!

[Bigtime_Snacks]

Thanks again for the information! I have a follow up question related to clocking Kria from the teletype. Using the M script with kr.clk makes perfect sense to me. I’m not sure what kr.period does though. Increasing the period value enough appears to make Kria skip steps almost. What is the relationship between the clock speed and the period?

I also notice with a fairly fast clock (M 194 for example) that the motion from step to step seems less smooth than Kria is clocking itself. Is this due to a limitation in the teletype? Thanks in advance!

[csboling]

KR.PERIOD can be used to set the period of Kria’s internal master clock, whether or not Teletype clocking is used. My recollection, which may not accurately account for the behavior you’re seeing, is that KR.CLK sort of requests a given track to advance, but I/O might only be registered on the next master clock edge. So you may need to use a fast internal clock setting on Ansible when clocking from Teletype at faster rates, to ensure that the incoming Teletype commands get “sampled” fast enough.