#11

everything i’ve added is in there, including KR.CV, track muting, teletype track clocking, etc.

3 Likes
#12

no earthsea, but iirc @scanner_darkly was going to pull the master into his earthsea branch once this pull request got merged.

2 Likes
#14

Cool. This will be my first Ansible software upgrade. Wish me luck!

#15

Hmm… ok so it looks like everything I have added to Teletype firmware was merged Feb 27th, which is after the last release (2.2 on Feb 15).

@tehn is it possible to bump a 2.2.1 release out to include those changes?

#16

I found tracking down the USB A to USB A cable the hardest part :slight_smile:

4 Likes
#17

yep, as @freqout said now that this has been merged to the master branch i will pull it into my earthsea branch. should be able to post a new beta today or tomorrow.

edit: new build posted: Ansible Earthsea

9 Likes
#18

Cool. I’ll start there. :slight_smile:

#19

Also I just realized the documentation I did for @tehn s meta-pattern mode is also up there. This one is a bit more complicated, but if you haven’t used meta-patterns in Kria yet and want to try to follow the docs, feedback is appreciated. @n-So I linked your sweet sweet tutorial video in the docs since it was how I learned to use it.

4 Likes
#20

can someone check to make sure these new features are documented?

#21

Thanks again all involved. I continue to love this more at every turn.

#22

Glad I could contribute something to this awesomeness! :grin:

2 Likes
#23

cool. Are there updates to the docs needed? It feels like I’m going to need to… rebase the Earthsea docs in, erk. Guess I have some fun typing times ahead!

#24

sure. I can also take a pass when I rewrite the final Earthsea docs - I think there’s mainly just some consistency to put in place, and also perhaps some tonal stuff to make it feel like a single thing. Before I’ve got a pull request ready to go, I’ll get in touch and we can confirm things!

#25

OK - @fma, @tehn, @freqout - I have taken a copy pass on my own fork of the docs. You can see the changes here - https://github.com/monome/docs/pull/37 - this is FOR DISCUSSION rather than me riding roughshod over anything.

Mainly what I’ve done is: brought things in line with the ‘house style’ which is entirely something I’ve reverse engineered. Also done some work on clarity for new users unfamiliar with Ansible, and making things more documentational and less narrative. I would prefer there was discussion on that PR rather than just ‘yay’ or ‘nay’. The diff view will show you what I’ve done.

The teletype commands still need documenting - I’ve added them at the bottom with !!TODO!! because I don’t know what they do yet.

My idea is: I am happy to tidy in the PR and get it to a point where everyone is happy. @Fma, this is great, especially all the illustration work.

4 Likes
#26

This is so good! Kria is getting better and better, more flexible and fun. Can’t really think of a better sequencing platform.

One question I’ve been pondering ever since I got my Ansible + Grid combo is duration. How does it actually work? To begin with I didn’t pay much attention to the feature because it didn’t seem to make any difference whatever I did with it. Just last night I revisited the docs and wanted to get hands on with it, and suddenly it made these wonderful accents to my sequences - but it only worked with one of my voices. After some testing I figured it wasn’t a bug with the firmware or module, but that it had to do with the set up of my voices. With my Tonestar 8106 everything works well - it is a full voice semi-modular eurorack module. So TR1 from Ansible goes to gate in and CV1 goes to 1V/oct. Now, with voice number two the set up is this: Just Friends in sound mode into LxD gated by envelopes from Maths into the CV input (not strike). So, TR2 to Maths trigger input and CV2 to v/8 time on JF. When I play around with the duration feature on Grid it doesn’t seem to make any difference. After som time I tried sending TR2 to Maths’ signal input thinking that inoput is direct coupled and cha-ching: duration changes seems to work to some extent depending on the envelope settings from Maths. With say, my 0-coast this doesn’t work as there’s only one gate input and it seems unaffected by the duration settings - although there may be some work around?

Hope this make sense.

So my question is: is there any knowledge on requirements for the duration functionality to work? And should the documents include this? Or should all this be obvious? I’ve read the documents over and over, and the duration part never came clear to me. Now that I’ve come to learn a little more about it and got to work with it, I have to say it is a super powerful feature. It can really make the sequences very lively!

#27

Kria provides a gate out rather than a trigger. So duration impacts how long the output voltage is held high.

With Maths, the trigger input will fire the envelope rise segment on the trigger, and immediately fall after the end of rise. Gate in will trigger the rise on fate going high, and hold high until the gate goes low at which point the fall section kicks in. So provided the duration of the gate length is longer than the rise time, you’ll hear the impact of duration.

5 Likes
#28

Thanks @GoneCaving! Makes sense : - ) I’ve been experimenting a bit just now, trying to feed the TR output from Ansible right into a LPG, with some cool results. Also with the signal input and pretty short and tight envelopes from Maths.

Ah, I love Kria…

2 Likes
#29

I’ll take a look when my tea has kicked in

1 Like
#30

just bumped another commit to this PR. Turns out 1.6.0 also includes shortcuts for track muting, and a way of specifying if a track is clocked by Teletype! The only reference to this functionality is literally in an old PR and early in the thread.

So:

  • I’ve added new prose to describe track muting (hold loop, tap track);
  • I’ve added description in the TT section of all the TT functions based on the code, I think I’ve done it roughly accurately, but a pass from @freqout would be good… mutes seem to be 0 for all, 1-4 for channel… but are KR.CV and ME.CV 0-indexed (ie, 0-3)?
  • also - when you say ‘top left of pattern page’ for enabling teletype clocking per channel - which row? Patterns are the top row of the pattern page, y’see. That’s about the only grid feature I can’t quite visualise from text and code alone.

Shouts to @fma for his work on the docs, though. Seriously: code patches without docs for them are trees falling in woods, and for everybody following every thread on Lines, there are monome product owners who just have the official docs to go from.

4 Likes
#31

Thanks for going over all this so carefully. This must be a typo… teletype clocking is switched on in the upper left of the scale screen.

I’m on my phone right now, but I believe the KR.CV and ME.CV go by the same indexing as the Levels and Cycles CV ops.