#216

I’m currently using Ansible 2.0, but I assume this was the same before: Is there a reason that the sequence is not visually running when pressing the Probability button? I think selectively editing the probability of specific steps would be much easier with visual feedback.

2 Likes
#217

I’ve often thought this could use some sort of “current position” indication, as well.

#218

I love this idea! Also having a toggle, perhaps in the top right corner to define both rise and fall slew, because IIRC the slew is only applied to the rise, correct?

#219

The slew is applied in both directions, and the DAC code only has a single slew value, so separate rising and falling slews might be a bit of work. I really like the idea of having a time scale selection for the slew like the duration page, are people OK with giving up the top row of keys? Arguably you have more control over this if you have a top row that lets you scale up the slew time, I just need to convince myself that this won’t change the behavior of any existing presets.

3 Likes
#220

I don’t know if this was discussed before, but it would be great to have a “Counter mod”, so for instance an octave shift of a specific step would only be applied every second, third, fourth… time. This could be implemented switchable instead of the Probability mod or on the “empty” Alt Duration page.

2 Likes
#221

I’m currently composing a piece for performance and concentrating on building a playable arrangement on kria, and just came up with an idea that I think would be incredibly powerful and useful:

Each channel has its own sequence preset, so when you’re on the preset page, you’d be able to change patterns of each of the four tracks separately. For example, you have a bass line that you want to repeat but you want to change a lead melody. Instead of copying that bass line over to a new sequence, you’d simply just change the lead sequence while the bass remains on the same sequence.

Perhaps a stop function per channel could be implemented here too, where the channel freezes as opposed to being muted, with two options: one being a stop per track per sequence (so changing sequence would bring a voice back in or out), as well as a stop per track that keeps the voice from triggering even when changing sequence.

Would this be possible at all, @tehn, @csboling? And I don’t know if it would work at all with the current meta-sequence feature, but wow it would be so good! Maybe there could be a button above the sequencer page button that could toggle this functionality and the regular sequence page with meta-sequencing?

3 Likes
#222

Why did I never think to self patch ansible in cycles mode before? It really opens things up. If you patch 2 of the gate outs into 1 and 2 you can get cycles that self perpetuate and speed/slow in strange ways depending on the divisions of the rings. Just posting in case anyone else didn’t think to do this yet. Lots of fun.

9 Likes
#223

I think that it would be nice to add root not transposition greater than a fifth to Kria, maybe using an ALT key and a different shade of brightness? Perhaps this could allow for interesting jumps of greater than a fifth elsewhere in the scale too? Would that be tricky to do, @csboling?

1 Like
#224

Yes I would love a feature to transpose root note more then the it can currently go to be able to create scales from all 12 notes

#225

So I’m afraid that my nonexistent understanding of music theory makes this discussion go a bit over my head. However from the 2:44 mark of the video referenced in the thread and the source for the original White Whale Kria I believe I’ve got the compensate-shift functionality implemented in a new Ansible beta (c88f558) I’ve just posted here. This is accessed by holding down the scale page key while selecting a new scale note. Not sure if that is adequate to achieve the transposition function discussed in this thread?

#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.