#10

correct-- though my next ansible firmware update will have TT control over various parameters in all modes, including tempo, so this will be good for using the TT param knob for kria/etc internal clocking.

3 Likes
#11

TT -> Kria pattern change?

#12

Clearly, TT is becoming (has become?) the trunk of a wonderfully growing tree.

1 Like
#13

Yes, certainly. And more.

it allows for “unlisted” param modes and changes, which is pretty powerful for expanding functionality off-panel

3 Likes
#14

Cool - sounds great!:grinning:

#15

two badly-needed features that haven’t yet materialized:

  1. pattern stop. perhaps the first unused button on the control row? right now, the only way to stop playback is to leave one saved pattern slot empty and switch to it, which shortens song/setlist possibilities.

  2. quantized pattern changes. queue up the next pattern to run when the current pattern reaches its last step. when using kria as e.g. a techno groovebox, perfect 1/32 or 1/64-note timing is necessary to avoid wrecking the flow, as there’s always a noticeable lag between pressing the pattern button and its actual launch. maybe its delay length is related to the current tempo.

would be nice to have:

  • loop currently playing pattern while editing a different pattern, instead of launching patterns immediately upon switching. probably not trivial or practical to implement.

  • no auto-advance/no auto-loop. this would turn kria into something like @Galapagoose’s mlrv in “slice” mode! setting pattern inner-loop length to 1 is sort of similar, but not quite the same as it still loops endlessly. this feature would basically add the “stop pattern” request above onto every playhead move. possibly not practical to implement, as changing pattern length and moving the playhead is a two-handed operation, whereas mlrv slicing doesn’t require that many selection steps.

10 Likes
Monome ecosystem firmware development backlog
#16

Oh man, seconded. 20 characters worth of seconding this!

1 Like
#17

agreed!

note that i have many new features for the pattern portion of kria planned, but this will be part of it.

9 Likes
#18

Sorry, I mistakenly posted this in wrong thread so i’m moving here where it belongs.

Kria:
Ability to copy/paste patterns.
Button combination to trigger hard reset.

Kria/Teletype:
Allow teletype to set/get Time for parameters. This would allow for rachet mode scripts etc.

1 Like
#19

Kria:
Ability to copy/paste patterns.
Button combination to trigger hard reset.

Kria/Teletype:
Allow teletype to set/get Time for parameters. This would allow for rachet mode scripts etc.

At that point, the combination of ansible + teletype might yield the most advanced step sequencer on the planet. Even with a buy in of $1400(grids + mods), you’re still cheaper than a cirklon which is arguably your only competition at that level of functionality.

#20

I would love a way of telling Kria to play through multiple patterns… Something like being able to use the Length modifier key to select multiple patters to loop through on the pattern view.

Edit: One more thought… this with a faster clock speed (or clock multiplier) would allow for higher step counts for a sequence… i.e. you could string together four 16 step sequences playing at 4x clock to get a 64th note sequence… or something like that.

1 Like
#21

i have a design drawn up for this sort of multi-pattern meta-sequencing. just need to find time!

9 Likes
#22

Can’t wait to see how you do this!

#23

Speaking of meta sequencing - scale sequencing and transposition would be great too. I like programming chords on the scale slots for complex arpeggios with different pitch and trigger patterns, Being able to sequence scale changes an transpose the chords would make song structures more accessable…

4 Likes
#24

Yeah, I’ve been longing for chord progressions in Kria.

1 Like
Monome ecosystem firmware development backlog
#25

Probability for each pattern would also be awesome… i.e. play P1, then maybe play P2.

1 Like
Monome ecosystem firmware development backlog
#26

I don’t use probabilities page; a shame, but I never think of it in the moment. Perhaps that’s where scale/pattern sequencer will go?

#27

I implemented quantized pattern switching for Ansible’s Kria: https://dl.dropboxusercontent.com/u/125278/Monome/ansible-1.4.1-kria-ycros-quant.zip and my code is at https://github.com/ycros/ansible/tree/kria-quantization

@tehn said he’s doing some deeper stuff with the pattern system so he won’t be pulling this into the main version, but until that’s done here’s my version.

How it works:

  • It is off by default, and settings are stored per-pattern. It is accessed by holding down the time modifier button while on the pattern view.
  • There are two rows, the second row acts as a multiplier for the top row’s value, so you can quantize to greater than the length of one pattern.
  • Turn it on simply by selecting a value in the top row, turn it off by selecting the currently selected value in the top row.
  • When active, the pattern will reset when the currently set quantization length is reached. When a new pattern is selected, the current pattern will play out until the currently set quantization length is reached before switching to the newly selected pattern.
  • There’s a display when it’s active, showing you where the playhead is within the master pattern time block.
7 Likes
#28

Yeah, scale, pattern and transposition sequencing would be so cool…

But anyway, thanks a lot for doing this! I’ll check it out the next days, sounds great so far!

:+1:

#29

The ability to cut/paste patterns seems obvious. I’m new to Kria, how does everyone do pattern writing? Start over in each pattern?