#5

max version forthcoming. unfortunately it’ll be a couple weeks before i get a moment.

2 Likes
#6

I’m really looking forward to it. I’m kind of holding off on purchasing any sequencing modules until I’ve got more of my voice built out. Going very slow because I’m determined to solder as much of it myself as I can bear to.

#7

Installed :slight_smile: Are there plans for TT integration? What about automated changing of patterns? And I’d still a way to slow the sequence down more than 16/1.

#8

all on the list prior to a 1.0

1 Like
#9

I lost it @ 1:55 of the tutorial. So cool, I love that kind of polyrythmic parameter sequencing :slight_smile:

#10

this is fantastic work. i’ll put the firmware onto my ww on the coming weekend, but maybe i can already ask a question.

something I struggled with a bit also with orca is how to not end with endlessly continuing sequences but have pauses and breathing space programmed in.

would that be simply a matter of having an empty pattern and switching to that? is there a possibility to simply stop kira (or orca), maybe triggered via tt at some point, where everything stops and then continues exactly from where it stopped at a specific time?

maybe I’m missing something obvious.

Orca - alternative firmware for white whale
#11

i know what you mean - i get that too sometimes. the best way is to clock it externally from a gate sequencer - meadowphysics is really great for that! [also replied in the orca thread with a bit more orca specific info]

#12

What I’ve tended to do with WW and the previous beta of Kria is set the trigger start/stop across a range where there are no triggers. However, with the new pattern tab, switching to an empty pattern is probably easier.

#13

Amazing!!! downloading right now :slightly_smiling:

#14

Wow. Can’t wait for the max version! I need to invest in some euro.

This is everything I ever wanted to get added to a lot of the monome applications.

Does each step have its own time multiplier like a metropolis? Where you can set it up to pulse 3 then 2 then 5 then 2 then …
It seems like its global per parameter right?

#15

First of all, this looks fantastic. Excited to give it a whirl!

Certainly, once there’s a max version, I’d be happy to help; a bit slow at firmware updating on my end… In the meantime, relatedly, I’ve been playing with the new meadowphysics and have been scribbling notes. Do you have doc templates in source control somewhere? In particular the grid graphics?

#16

since trent has gone full-time on mannequins (no longer working for monome) i’ve fallen behind on manuals. he was doing the vectorgraphics in illustrator which i’m terrible at, so i need to find a new solution. and yes, i have docs under version control but they’re all tied up in our main private git on a webserver, not via github, so it’s a little unwieldy for collaboration-- i’ll work on this.

1 Like
#17

this is amazing, easily the quickest sequencer i’ve ever used.

so so SO useful thank you i have been playing with this nonstop for the last 2 days

quick wishlist for upcoming version:

stop pattern (similar to phase/position reset) - maybe hold the empty button on the left side of alt

accent mode on/off - would be nice to be able to enable triggers 3 and 4 when their respective base triggers are not on

loop position reset for just one parameter - the current loop-start move functionality and master pattern phase reset is great, i’m just reducing to a loop size of 1 and then creating a loop of another size elsewhere when i need to be precise, but would be handy to reduce this to one button combo press (maybe again, with the button next to alt)

once external clocking is implemented:

multiplier/divider control on external clock - would be cool to have control for the clock output similar to all of the parameters

in phase reset vs queued reset for loops/patterns - part of the fun of kria right now is jamming the start/sync combos (alt + combinations of 1 + 2). you can kindof make that jeff mills 909 start/stop effect and REALLY play the instrument. would be cool to leave it as is right now even when the external clock is plugged in, so that the external clock sets a tempo/quantized grid, but the actual start of the pattern can fall whenever you hit (maybe a few ms off of the 1 - swing opportunities abound). then there could be a queued start, similar to how the white whale currently works with queued pattern launching, maybe again by holding that button next to alt at the same time.

pattern backup - would be nice to be able to usb backup/restore similar to teletype, but i could live without this

teletype integrations:
it would also be really cool to be able to sequence the clock multiply/divide options for each parameter, but i imagine this could make the whole thing really messy… ratcheting drums and patterns that fall out of phase in the middle then click back into place… that would be absolutely insane… perhaps this could be implemented with teletype easily though.

on that note, it would be good to be able to sequence parameter resets or pattern phase/position resets with teletype as well

–

OK will keep messing with this and see what other magic awaits

2 Likes
#18

Looks very promising :slight_smile:
Does it output triggers only or gates too?

Thanks!

#19

Gates. Duration controlled on the second page (button to the right of the trigger/accent/octave button).

1 Like
#20

bumping this topic to see if there’s any news on a max version of kria?

and no rush! just love the idea of it and i’m curious.

5 Likes
#21

kria still has some refinements in the pipeline, and i’m hoping to have a settled version soon prior to moving the code into max (to prevent having to do this multiple times).

thanks for your patience!

7 Likes
#22

Curious if you have any follow-up thoughts on this? Sticking with illustrator or shopping (shopped?) for new options? Wonder if a new home for docs fits into the github re-org?

Cheers!

#23

Regarding this, in the thread about monome app preservation (I think) you said something that suggested that porting (to JS), may not be too hard in general since JS and C are so close syntactically. I wonder if this might not become something we can take advantage of in how we think about (re)structuring shareable bits. (Paging @jasonw22.) In any event, it’d be great if you could post a few reflections once you do the port. Might make for good fodder for the “build a sustainable monome code ecosystem” playbook.

EDIT: github tracking issue for the max patch here.

1 Like
#24

It’s also quite possible to write Max externals in C.

However we do it, I love the idea of finding ways to share code between Max, eurorack, and aleph projects.

3 Likes