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

#30

pattern page: long press is writing current pattern, while short press is loading.

2 Likes
#31

One more note so that it’s in the “log” – I’d also love to see note repeat and delay as options in Kria. That would really make this an all-in-one sequencer. At the moment I use external modules to kluge this together, and I’ve been experimenting with TT scripts. But having repeat and delay views like the probability view would be amazing.

2 Likes
Monome ecosystem firmware development backlog
#32

THIS is the thing that always bites me. It’s a little too easy for a short press to become a long press. Before you know it, you’ve overwritten the pattern you were intending to load.

#34

we can increase the hold time

3 Likes
#36

I don’t know - maybe it’s me being a bit stupid but I think I lost as many patterns by accidentally overwriting the one I wanted to read as by accidentally reading an old one instead of writing the actual one on that position.

It got better now and I hope I get used to it as I got used to not just long pressing the panel button for a quick save as it works on the trilogy modules.

I am not sure though if it would help me to have different flashing buttons with another pattern I have to learn apart from long holding vs. short pressing the preset button. It probably would confuse me even more and I might not remember if saving the pattern was a long press or a short hold…
:hushed:

#38

Maybe I did not fully understand your proposal but I don’t feel that I need a visual feedback while I am reading/writing. I see that this is useful when you load a new firmware, just to see if you are progressing and if it worked out in the end.

It does not seem to make a big difference to me memorizing a long/short press vs. fast/slow flashes. And in case you realize that you don’t want to do what you do just doing, how can you get out of it then?

Another point would be that, personally, I find the Mutable Instruments practice to work with long and even longer button presses combined with several LED patterns horribly impractical - I never know which mode I am in and constantly have to look it up form the manual. Plus I find long and longer button presses much harder to distinguish than a short press and a longer hold.

So for reading/writing presets I would prefer either a very clear solution as W/R indicators to press (maybe while holding the respective preset button) or a very simple solution as it is now that should be the same across the whole monome line.

Somehow connected to this is what I really would like to have on Ansible: There is a gap in performance when you read or write which de-syncs everything and you have to reset and start again when you just saved something nice. It would be great if we were being able to play the presets too and switch between them instantly. A short and simple single press to read a new preset would perfectly make sense then…

#40

I would want clear visual indicators as the big W/R to press on for writing or reading - I would not want abstract indicators as a fast or slow flashing button while pressing long or short on another button.

I could see it working when it starts flashing slowly for a moment and then flashes faster. Releasing the button while the first phase would do nothing, releasing it after the first phase would read and releasing it after the second phase (when it stopped flashing) would write. It just would be to complicated for me as I would have to memorize the flashing phases, then have to get the right point for releasing the button while not getting to upset as in “uh, it’s flashing - what have I to do now to not mess everything up, was it short or long flashes…”.

You may not want to write a pattern after doing some changes just because you want to read another one.

I think trying to get the function of double check boxes as on a computer (“Do you really want to overwrite or quit without saving?”) with flashing buttons and combinations of button presses/durations of holding a button on a 8 x 16 grid makes things more complicated. Pressing on a single letter as in W/R would be okay, I think.

But all of this depends on if it is sought to have playable instant preset changes possible.

#41

Interaction design is a very difficult vocation. I trust @tehn to make the best decision (making the long press time a little longer for pattern writing may be sufficient).

Note that pattern writing and preset saving are two different interactions. I believe the W/R proposal came up regarding preset saving.

2 Likes
#42

Yes, I see now that it switched from pattern saving to preset writing after @tehns proposal.

And you are right regarding interaction design.

#43

fixed, in the next update

#44

After playing with Kria on Ansible for the last month, I re-discovered a lot of the joy that I had when I first encountered Parc. The one feature I’m wishing after most, though, is Parc’s multi-note logic. For the uninitiated, it allows you to select multiple notes in a column (which would typically form a chord) and as it passes it selects one of them, keeping monophony. Seems in line with Kria’s wheelhouse.

(OT: anyone know how to achieve this with another module in tandem?)

8 Likes
Ansible Development and Beta Firmware Discussion
Monome ecosystem firmware development backlog
#45

A quantizer (could be Teletype) being fed random voltages from a S&H or a switch, could alter individual notes for you in a controlled chance manner. S&H for more chance, switch for more control? (quite a few different ways to set this up)

1 Like
#46

TT seems like the next piece of the puzzle. Thanks for that!

2 Likes
#47

One request on the next update would be updated documentation. I keep moving between the video for the original WW version and the (seemingly) incomplete ansible kria illustrated docs, neither of which give a full picture as far as I can tell. A new manual that doesn’t take any previous Kira knowledge for granted would really be a huge help!

11 Likes
#48

yessssss. join us :slight_smile:

2 Likes
#49

This may already be implemented but to madeofoak’s point above, I don’t see it in the manual… if its there, I will edit my below post :slight_smile:

I would like to have an “all phase” reset per track. I typically keep note sync off so that I can let the trigger, note, and octave tracks phase melodically but I would like to be able to simultaneously run a percussion or drum track along side the melody. Its hard to keep the track in phase (for instance, for a predictable kick drum sequence or bassline) without a reset. I know I could just change my workflow to build the track with note sync on and then turn it off but seems easier to be able to perform a reset.

EDIT: an idea for the UX implementation might be a pressing of each parameter (trigger, note, octave, duration) and also the first step of the track to be reset. You can press multiple parameters to reset whichever ones you want (i.e., just trigger and note).

I would also love to see the current version of Kria ported to WW if its possible to do so (obviously, with a lower/different track count). Not really a feature request but would be great for those of us with WW to be able to keep up since Kria seems to be the future.

2 Likes
Monome ecosystem firmware development backlog