@csboling since you already merged earthsea into your branch, do you want to do a pull request? alternatively i could update my branch from yours and submit a pull request, whichever you prefer.

do we want to merge first and then post a new beta, or do testing first? unfortunately due to family circumstances i have very limited time to work on any projects, so won’t be able to test it.

@infovore - that’d be great! as far as i can tell the only changes/additions that are probably not in the doc yet are these: Ansible Earthsea

OK. I will update that in the next day or two, perhaps on a plane tomorrow.

2 Likes

I have a branch with Earthsea merged in and with JSON preset support added for it, I can make a PR tonight. (edit: here)

I’m trying to keep the posted beta build current with master while also including other features in it that are still pending merge. Everything should be tested again once it’s in master I think, but the beta build as-is should be relatively close to the release version, excepting fixes for bugs found by users currently beta testing. We should be able to look at the diff between master and my dev branch after everything’s merged to get a sense of how/where master is different from the beta(s).

2 Likes

I can’t see how this would be possible, but here goes: is there any way to grab the current presets on an Ansible, update Ansible to this new preset-savable, then load the previous presets (Kria) into it? I know, I know…it ain’t gonna work. But man that would be sweet! :sob:

This is possible, see here. It should also be possible to export presets from the 1.6.1 + Earthsea build.

OMG…amazing! Will check it.

UPDATE: can somebody interested in Earthsea documentation / knowledgeable about current functionality check my updated documentation pass which you can read here. (this is my own fork of the docs repo). I’ve added the Teletype documentation and also the notes on skip-to-playback-position, rests, and scales. I’ve not had a chance to update the illustrations because I’m on a trackpad (sat at a gate during delays) but that will happen in due course. But because I’ve not run this firmware on my ansible yet, I don’t know if I’ve described it correctly! But basically this is ready to go with a PR.

(It also includes some of my tidying of the Kria docs - I am hoping nothing will be lost in the ultimate PR, I think it’s all mainly stylistic consistency).

4 Likes

Unless I am missing something… The doc link you posted seems to be missing any mention of ansible earthsea.

Oh god I probably linked to the wrong branch because I have been on transport.

1 Like

That’s it! Found the changes in your aearthsea-docs branch.

Here is the link

Fixed in my original post

1 Like

thank you - looks good!

a couple of minor things: ### Clocking Earthsea is not showing as a header, and in the 2nd paragraph under Highlighting scales on the key map there is a space missing in createyour.

OK, both of these things are fixed. I wanted somebody to check I’d understood scales correctly as I tidied up the copy there a bit. There are still some illustrations to do - that might not happen for a bit - but I’m happy to open a PR for now with master?

1 Like

“Holding PATTERN SELECT, the right two columns will be illuminated in a 2x8 block.” -

the block to choose a scale for keymap is 8 columns wide and 2 rows high and it’s on the right side centered vertically, perhaps to say “a 2x8 block on the right” would be sufficient?

1 Like

OK, made a quick change to that paragraph:

Holding PATTERN SELECT, a 2x8 block will illuminate one the right. These are scale slots - the exact same scales available to Kria and Meadowphysics. Pressing one of these will highlight keys in the keymap that are within that scale. To turn scale highlighting off, press the currently selected scale key again. (Note that this does not affect the pitches each key represents - it just acts as an ‘overlay’ to highlight notes within a scale).

which is in my branch.

2 Likes

Alright, iiiiit’s pull request time:

sorry about lack of mergeability. @scanner_darkly, I updated the graphic of parameters page to include highlighted scale keys - you might want to check that.

3 Likes

thanks - looks good!

1 Like

Just started looking into this mode. Thanks for the great work - seems like this has some wonderful possibilities!

How do people tune oscillators when using Ansible Earthsea? My goal at the moment is to be a bit fluent in playing chords. Not having a lot of music theory background I find it a bit difficult to find the different “harmonic shapes”. I tried to tune to E to get something similar to guitar strings (until the B string), which was fun.

I should probably just practise and listen more and get familiar with chord intervals. It certainly is a wonderful tool for learning. :slight_smile:

I suppose I don’t have a great question, but wanted some interaction while figuring things out. If anyone has a nice approach/some advice, that would be great!

Edit: Holding “pattern select” I don’t see the 2x8 bar indicating the different scales to have them light up in the keybed, as described in the Ansible documentation. Would you recommend getting the ansible beta firmware for this, or should it be included in the “main” ansible firmware on monome.org now?

2 Likes

It appears that this revision (linked from the first post in this thread) does not have the scale highlighting feature. I would recommend getting a 2.0.0. beta from here since this is what the github documentation reflects.

2 Likes

Ok - thanks for this!