#226

I’m not sure if it’s possible but I’d love to see a morph sequence function added to Kria like in Awake.
Saying this, the physical inputs would be the main issue as there are only two linked to clock amd reset. So I was thinking maybe using the reset as a morph input? They could share functionality so when you reset the sequence it also morphs? Or using the clock input at a selected division to choose when it morphs but I’m guessing this would involve far more work the linking morph to reset. It could also be an option to use crow connected to ansible for the extra inputs?
Either way I think it would be a great addition especially if it could be done only with ansible.

#227

This is great, thanks and likely to be super useful! But I don’t think it was quite what I was looking for. Put simply, the bottom row of the scale page allows us to increase the pitch of the scale by semitones (i.e. transposing it into a new key) but only allows a shift of up to 7 semitones maximum. What would be awesome would be if you could shift all the way up to 11 semitones. As it stands, if your oscillators are tuned to C (or if you’re using Just Friends over i2c for example) you can use all the keys from C through to G, but none higher than that - which is a bit weird. The workarounds described above involve using a different root note than the “real” root of the scale and changing the other intervals to kind of fake the scale. This works, but is a bit clunky and has other problems (for example, the highlights root note on the Earthsea grid will be in the wrong place). So, what I was hoping for was a way of adding an additional shift beyond the 7 semitones allowed by the grid.

Here’s one possible approach:

Use one of the spare keys on the bottom row as a shift key. Press a key on the scale editor - this lights up, but so does the last light on the row. The pitch shift for this row is then the sum of both lights. E.g. if you press the first light with the shift key pressed, you get the first light and the 7th light lit up, giving a total of 8 semitones.

Does this make sense?

Sorry for endlessly suggesting new features to Ansible - it’s already the greatest sequencer ever, so it does seem a little greedy :slight_smile: but this feature of only being able to play in some musical keys does feel peculiar and is a bit awkward to explain when I’m collaborating with other musicians!

3 Likes
Ansible Development and Beta Firmware Discussion
#228

Yes this is the one thing that has been bugging me with Kira since i use its to have multiple scales in the different sequences and not able to get some of the desired scales.

i feel like the scale menu needs to be its own page. something like the first 2 rows are the scale presets vertically then an empty vertical row then the scale and then 12 options for each row of the scale. you could then get to the rest of the scale options by using the scale button again and have it blink similar to the functionality of the alt features on gates and notes.

4 Likes
#229

Not sure if this is a limitation of the hardware, but I’d love to be able to change some of the CV out’s to do trig/gates. I only really control 2 melodic voices at once, it’d be lovely to get the other 4 output jacks to be used for drums.

Tangentially-related, it’d be nice to be able to implement accent out using an unused CV out.

#230

Seems like you could effectively do this by programming some tracks or notes for +5 octaves to get ~5V out of the CV outs. Lots of stuff has a much lower trigger threshold like 0.5V or 1V though.

#231

I have sorta tried doing that, it’s hit or miss from my experience. The user experience for doing also is uh… not quite as smooth and elegant as the rest of the Kria experience (which says a lot about how great it is!)

#232

Might need more detail about what the problem is. Meadowphysics has a mode where all 8 outputs are used as triggers, does that work for you?

#233

I’d love to have the Meadowphysics setting of being able to configure the voice mode for trigs vs. CV’s in Kria, basically.

#234

Frozen pattern view with meta pattern while editing pattern:

I would like to create sequences with more than 16 steps. So I can use meta patterns: It`s simple to chain two 16-step patterns to a “32-step pattern”. But now if you are in the sequence editing creative process (adjusting note, duration, octave…) the view of the pattern constantly switching from 1th to 2nd to 1th pattern… so if you like to focus on one particular note for example you have to wait til the “other” pattern is through and the pattern which you like to edit is “active” again. If you imagine you created 64- or more steps “meta chained patterns” it would be quite anoying always to “wait” til the 16-pattern which you like to edit is looped again.

Therefore it would be great if you could somehow stop the chasing view of the single 16-step patterns and select the pattern by your own which is currently viewed for editing, while the meta pattern chain still runs. Perhaps my request is somehow already possilbe.? If not perhaps it would be possible to implement this feature in the config-page with a toggle switch: off for normal view / on for “frozen” view. It would has to be implemented a pattern view selector-button or something.
Also if you use kira as a modulator-meta-pattern-chained device, you often like to use faster clock times, which also would make editing quite impossible, since the single patterns reviewing in “light speed”.
What do you think?

1 Like
> teletype: grid # code exchange
Ansible Development and Beta Firmware Discussion
Ansible Development and Beta Firmware Discussion
#235

Can’t you just stop the meta-sequencer while you’re editing the note in the pattern you’re interested in? I don’t see the value of having Kria continue to play other patterns you’re not currently editing.

#236

Hi ganders,
its most times quite interessting to listen to the complete meta pattern to „understand“/ feel the changes in the context. Also for live situations you could prefer this way of workflow - then you definitively can‘t stop kira :hushed:. Also for mentioned fast clocked modulator usage it would be an advantage to make change on the fly.

#237

Give this build a try: ansible.hex (371.3 KB - 2020/04/12 - a688a80)

The way this works is that on the pattern view, if meta-pattern mode is on, you hold down the pattern key (bottom right key) and tap the pattern slot (top row) you want to edit. That pattern slot will start flashing as well as the pattern key – this pattern is now locked as the pattern you want to edit. The pattern key will keep flashing on all other Kria parameter pages to remind you that the pattern you’re editing may be different from the pattern that’s currently playing. To disengage, hold the pattern key and tap the flashing pattern slot again. You should now be able to freely edit the locked pattern while the whole metapattern sequence continues to run – the Kria playhead will only appear when the active pattern and the pattern being edited coincide.

Edit: and I’ve just realized this conflicts with how you select a cued pattern, which I guess I thought was disabled in meta mode. Other UI ideas appreciated. Maybe it makes sense to access this when you hold the loop key on the pattern page instead?

2 Likes
Ansible Development and Beta Firmware Discussion
(ansible) 3.0.0 release
#238

What you describe is just fantastic and frees a lot my sequencing process as this is much more powerful than my workaround with tt. Last night I’ve just finished to walk through the kira manual in deep. To your edit-passage: So if I understood your implementation correct it is not a conflict at all.? I didn’t give your build a try yet, but (in 2.0 firmware) if you push and hold the pattern key; then pushing the pattern in the top row isn`t anything else than only pushing the pattern in the top row. The cued pattern thing works like this (in 2.0 firmware): Push and hold the pattern key; then push (not the pattern in the top row, but…) the pattern sequence button (row 3-6). So if I haven’t fundamentaly missed something or there is another missunderstanding (you are perhaps refering to a beta firmware 2.x where this extended cued pattern option is already implemented?) your build should work perfectly as intended.?
On the other side your suggestion instead of using the pattern key to use the loop key wouldn’t be a conflict as far as I can say as a newbie to kira.

Hey csboling,
just give it a try and it works perfectly! Quite cool! Thank you again!
Perhaps you could reduce the blinking to 1-2 sec - would be enough to be warned I think :slight_smile: . Is there a possiblity to support you - patreon or something like this? In my opinion it is not common to get such a fast and uncomplicated support!

I just saw something else in the preset page:
IMG_8673
You see 3+ 1 buttons in the middle which should not be there right now (true for 2.0 firmware). If you are aware of this and it has something to do with a beta-update, then everything is okay :slight_smile:

1 Like
#240

Topic: Metapatterning - divider in row 2

Another question concerning meta patterns is, if it would be possible to optionally deactive the divider in row 2. Why?:
Imagine you chain a pattern with 16-step tracks and one with 10-step tracks. This would result - if the divider is set to 16 - that the pattern with 10-step tracks will play once through all 10 steps but then loop again step 1 - 6 and then “interrupts” that pattern to start with the next pattern.

Independance from the devider would have the advantage that if you sequence patterns which have different step length they could finish til last step of its pattern and move forward to the next pattern. Of course the user would need to arrange the different lengths by itself, that at least the complete song is not “out of rhythm” - if not even prefered :wink: .
And there is the problem if you have a pattern which contains tracks of different length. There I think have to be done a restriction that for example such a pattern plays as long as the longest (counting in steps) track will take to play once to end. Of course there could be a lot of different rules…

This is only an idea…

#242

This is a new feature in v3 firmware for the configuration setting of the other modules connected on the i2c bus. It would help if there were diagrams on this page.

1 Like
#243

Hi there I love KRIA !!! and the amazing people improving with each firmware release!

Not sure if this is mentioned, is it possible to speed up a track? Currently you can only speed down. :slight_smile:

#244

Clock multiplication was included in earlier releases but taken out because it wasn’t solid, which is why there’s division only now. It’s not the most intuitive but you can start with a master clock rate and start your tracks at a higher division value, then switch to no division if you want a track to go faster.

2 Likes
#245

Yes will experiment ! Thanks!

#246

I’ve set up a preset which has all tracks at 1/2 division, and just copied that into all preset slots in Ansible so I can multiply up one easily.

1 Like
#248

After playing around with an Usta (and selling it for a second ansible, hahaha) I’ve been left with the desire to use sequenced raw (unquantized) CV, until I had the thought that perhaps this could be implemented into kria.

There could be another sub menu under duration where you could turn it on and off per channel (this could also be in the third column of the scale page instead), as well as set a range per step, that could have a fine tune in the same way that the internal clock can be fine tuned? The resolution could be set to go from fractions of a volt up to whole volt numbers, using varibright to indicate. It still might be stepped, but this would be very useful in smaller voices using less than 4 voices.

1 Like