#97

Not exactly the solution you were asking about, but if you have a teletype, you can clock each track individually.

3 Likes
#98

oooh… I didn’t know that! That’s a great tip.

#99

Had a clock mod idea inspired by the Befaco Burst, a “Distribution” control that takes the looping parameter and adjusts the step spacing over the loop. Picturing it living on the same page as the clock div. The demo video shows some nice slowing and speeding up of the trigger https://youtu.be/KMNqizaTN1o?t=323

Capture

Flicking through the Kria code for the first time I can’t see any obvious implementation though. Everything seems pretty well connected to the main clock, getting events independantly timed as would be the case here would mean a new clock timer and much work.

Just a random idea, I noticed that Kria has the probability, quantity and clock div stuff of this Burst module which got me to thinking about how a Distribution parameter would work

EDIT: Just realised Meadowphysics does something like this. Maybe doesnt need to be brought into Kria then

#100

Could this also be done via the currently unused sub-page for the duration parameter? I know that those sub-pages are supposed to offer extended functionality related to the primary parameter those views control but that doesn’t really seem to be the case with octave/glide. If it were to be done via the duration sub-page it wouldn’t have to affect the general layout at all.

#101

I don’t know if this has been discussed earlier, but I think I just got an idea.

What if you could latch or hold a note in a sequence with Kria by holding down the button you would like to keep ringing? So if you hold down a button you’ll send a gate until you let it go, and the sequence will go on. Hm. Just a thought. I love playing around with Kria, it is really by far my favourite sequencer. It would be so cool to have even more hands on playability. Like a merge of Kria and Earthsea, in a way.

I have also been thinking about how cool it would be if the note page in Kria could function like a arpeggiator, so that if you hold down certain notes you would engage the sequence/arpeggio. Maybe that sound like a different creature? I don’t know.

2 Likes
Monome ecosystem firmware development backlog
#102

Not sure if this is a request or just a question.

Let’s assume you have 2 patterns on track 1 in kria. Let’s assume you’re clocking that track with Teletype’s metronome script. Now let’s say you want to issue a Teletype command to switch patterns in kria, currently playing pattern 0.

KR.PAT 1

will switch from pattern 0 to 1, but it will do it immediately, or possibly it is switching on the next tick of the internal clock - I can’t quite tell. You can evaluate the current pattern length and position to achieve a pattern switch at the end of the pattern.

Something like this, for example:

M
KR.CLK 1
X KR.POS 1 1
Y - KR.L.LEN 1 1 1
IF EQ X Y: KR.PAT TOSS

will wait until the end of the current pattern, from the perspective of the trigger parameter’s length.

This is a lot of script lines though, and due to the length of the conditional line, takes a couple of variables. Is there any kind of function to cue the pattern to switch when the current pattern ends? Looking for something like a

KR.PAT.CUE x

Or is there a shorter way to write the code?

3 Likes
Monome ecosystem firmware development backlog
#103

That would perfect :ok_hand:t2:

#104

I can see that this would be useful, but also very specific. Since Kria is a based on phasing sequences, I would not want to tie this on one trigger track. Look at the ER-101/102, which had a similar problem to solve.

So my first thought was

KR.PAT.CUE x y z

with x and y specifying the reference track and z the pattern to call.

Of course I have no idea if it would be possible to conditionally cue/delay a command inside the Kria code. Generally I am fine with doing the more specific calculations in teletype and would prefer bugs being fixed before new features are introduced. But that’s a different point.

2 Likes
#105

Request: would it be possible for Kria to have a mode where it functions only as an 7/8-track trigger/gate sequencer with i2c possibilities?

#106

FWIW, that sounds pretty close to Meadowphysics :slight_smile:

1 Like
#107

Thats what I thought till I was trying out what I wanted to do earlier, rhythmically the results are very different.

1 Like
#108

Sorry if this has been asked before.

Is there a way to do longer notes? For example,
1,1,1,3, pause, 1,1…etc (1 is the clock beat)

What I have been doing is to put the note duration to full on the 1st row and note length
and punching in 3 notes in of the same pitch.

I know i can slow down each track so the notes are ‘longer’, but is there an easier way to do long and short notes on a track? Maybe like how you define loops, you can define how long you want the gate to stay open on a certain note.

1 Like
#109

look for the “duration” page in the docs. the duration parameter changes the gate length, but not the number of steps it takes up; I’m not sure if that’s quite what you had in mind or not

#110

For example I want a note to hold over 3 steps. I set the duration to full on all 3 steps in a row. This the only way?

#111

According to the kria manual, setting note durations should tie together steps completely, but unfortunately, there is a known bug in the code as of 1.6.1 which causes a the gate to drop for a tiny amount between steps resulting in a retrigger.

2 Likes
#112

Wondering if Kria and meadow physics would be given the i2c leader treatment (ala polyES) at some point making it able to speak directly with just friends and the 301? Could this be considered a feature request?

2 Likes
#113

That would truly be amazing and something I’d really like to see implemented but I’m pretty sure the person behind the i2c development said he won’t be doing it so hopefully someone with the skills could take over.

1 Like
#114

Yup read that too :laughing:
The wait continues…

1 Like
#115

For what it’s worth, you can already patch Teletype to allow direct control of Just Friends with Kria: patch Kria’s gate outputs to four gate inputs on Teletype and in each of the corresponding scripts write JF.NOTE KR.CV 3 V 5, where you’d change 3 to match which Kria channel you’re working with.

Something about as simple will work with the ER-301 or TXo (I mean, with the 301, you could just use patch cables too).

Notice this doesn’t factor in gate length, but given that you have five lines of script left, something could be figured out.

3 Likes
#116

Is there a way to go down in octave on the octave modifier page? I know I can start in the middle and tune my osc accordingly, but then my range up and down is limited… am I missing something or is this a feature request? :wink: