#127

Fillowing O&C with Marbles makes this even better.
Quantermain does a lot of its stuff step-wise. With Marbles, one can sample and loop the O&C output sequence, dial in a key change or whatever on O&C and then release the Marbles Dejavu for smooth sequence transitions. It very easy.

1 Like
#128

Since the output of Kria is already quantized and playing, it sounds like @fourhexagons is doing octave transpositions on the fly with no need to loop or record any sequences.

1 Like
#129

O&C does octave and key changes one step at a time. Going +- 1on octave or a half-step on key is smooth. Going further, isn’t smooth wo/ sampling.
For me, I don’t sample for octave changes because I only move 1 octave at a time but I do sample for key changes because they represnt more steps of movement.

1 Like
#130

I dig what you’re both saying, @Jonny and @Frogstar. I always end up using Marbles for additional voices to layer with Kria, but I like the idea of running Kria through Marbles for further processing of the melodic material. It’s now something on my list to check out.

2 Likes
#131

Sounds like a fun approach that can lead to some musical results. :slight_smile:

1 Like
#132

possible to add swing percent?
could be implemented in another modifier page like duration

1 Like
Monome ecosystem firmware development backlog
#133

I’m wondering if there is anyway to have a midi mode that outputs clocks for syncing and a mono voice.
I’d really like to have my op-1 sequence a voice and sync the rest of my system.
Could also be cool to have a few different clock times too.

1 Like
#134

Like this idea! Hope this gets it own control in the timing page possibly?

#135

Ive been thinking about this as well, some sort of swing or microtiming?

Maybe instead of the ratchet page, we could have a subdivision page that subdivides each note by a chosen global value (1-6?). And then have on/off buttons for each subdivision. That way you could still get identical ratcheting behaviour by setting the repeats to 4 and turning on as many as you’d like, but also get a world of subdivision possibilities

3 Likes
Monome ecosystem firmware development backlog
#137

I’m not sure this is possible with the hardware. Can someone confirm that these inputs cannot be outputs?

#138

the ansible’s input and output jacks are fixed re: direction.

if you want a clock output you can make a dedicated pulse with one of the four voices?

#140

I’ve been spending more time with my Stillson Hammer mk2 lately, and one thing I wish was easier to do on Kria is to basically change the cv scale. So, not “scale” as in “key + scale”, but as in changing each row from semi-tones to some other cv scale. So on my SH2 I can do 0-8v, 0-5v, and then a range of 2v (i.e. 2 octave) ranges for the sliders like 0-2v, 1-3v, etc.

Basically my goal is being able to use Kria to sequence modulation and not just notes. I know I can sort of do this by combining octave and note page sequences, but it doesn’t feel quite as immediate as being able to use a single page with a range of, say 3 or 5v or something. The note voltage steps are too small, and the octaves are too big.

Just call me Goldilocks…?

2 Likes
#141

bumping this to see if there has been an “official” fix to the quantizing issue in the firmware. I’ve read through this post and @tehn had mentioned it as a possible future fix, but haven’t found anything other than this post mentioning it. Thanks

1 Like
#142

Funny bc earlier today I would have said “nothing”, but I just had a beautiful moment with kria, and thought OH THIS NEEDS DRUMZ…
But my “1” on the melody was not on the one, so when I went to sync it to the op1’s clock, there was no hope without sampling each part, which would not work with Kria (always loose said “groove” this way!)

So my request is to be able to mark which step is the “1” on kria!

1 Like
Monome ecosystem firmware development backlog
#143

Here’s a build:
ansible.hex (244.6 KB - cc8f5b2 - 2019/05/17) (buggy, see below)

Ansible PR
Docs PR

5 Likes
#144

wow! merged. thank you, this is fantastic.

1 Like
#145

Right after this was merged I immediately found a bug where when loop start/end were swapped, reverse and triangle mode would wander off and start corrupting nearby parts of state. Fun, but not ideal - it might be amusing to code up some Teletype ops that would directly let you trash Kria’s state memory and see what happens. New build: ansible.hex (244.8 KB - a1798e5) current build, new PR. I also had apparently not understood “drunk” and “random” as separate things when first reading the post, so this PR also adds random mode.

7 Likes
#146

This is wonderful, thank you so much! I patched up something melodic and have one track set for drunk movement with sparse triggers of varying probabilities, which adds a really nice cohesive yet unpredictable element to the whole thing. Definitely has different quality than I was able to achieve soley with phasing previously.

Can you tell us more about how the triangle mode is implemented? When I have a track with parameters of different lengths, it seems like all parameters change directions once one of them hits an end of a loop… But I was also able to get one of my parameters to “scan” through a track somehow (i.e. a sequence of position: 1,2,3,4,3,2,3,4,5,4,3,etc). I’ll have to experiment more to see if I can replicate that behavior again it was pretty cool!

EDIT: ahh I figured it out, the track that “scans” is set to a slower odd division while the other track that flips the direction isn’t divided. The inherent phasing nature is manifesting in new ways :smiley:

1 Like
#147

Yeah I bet you’re right about the triangle mode, the state for “are we moving left-to-right or right-to-left” is at the track level rather than accounting for different loop positions etc for different parameters. This would cause all parameters to suddenly change direction when one hits the end. I’ll look at this later today to keep separate state for each parameter. Edit: fixed @kbit ansible.hex (244.8 KB - 79d1c8a - PR) current build.

1 Like
#148

Wow, this is great! Thank you. One question I’ve been pondering is how to save the state of the TT clocking mode in a preset. I think it currently defaults to not synced to TT when loading a preset. Will this store the TT sync clocking mode when loading a preset where TT clocking is enabled?

Monome ecosystem firmware development backlog