not sure if this is the correct thread to ask this, I am having issues with a grayscale 128 non varibright grid with an ansible from the most recent batch as I am unable to create any sequences longer than 7 steps/triggers. Is there some sort of config I have to do or possibly something with the firmware? I have updated to the most recent version of Earthsea however it was occurring with the stock firmware beforehand as well

it would be unlikely. can you describe in more details what happens? also is it grid 64? or 128?

i see the post was moved here but i assume it’s not actually earthsea specific. which ansible app are you using, @Minimum? kria?

woops! sorry. i saw the word ‘earthsea.’

yeah it’s a bit confusing with multiple versions (and creates more maintenance) - @tehn, perhaps we could consider merging earthsea into the official ansible firmware?

It is specifically in Kria, however I just have the most recent earthsea firmware installed. Also it may be a good idea to create a general Ansible Q and A thread

it is a grayscale 128 non varibright grid

can you describe what happens exactly?

kria appears to function normally however if i try and create a trigger past the 7th column on my grid there is no visual feedback as well as no trigger and the sequence goes back to the first step. Otherwise if i just use the first 7 columns everything appears to function as it should

sounds like you need to extend the loop by setting the loop start and end points. https://monome.org/docs/modular/ansible/ search for loop modifier.

yes that’s it thank you very much, trying to learn kria with a non varibright grid has been proving to be somewhat difficult

What am I doing wrong. … when using alternate notes with a set scale, I still get sour notes every once in a while when the stars align.

I just got my ansible and grid and I am trying to access Earthsea, but I am only able to get Kria (orange) and Meadowphysics (white). No “whitish-orange” for Earthsea. Do I need to add it via firmware update? Literally just arrived in the mail today…

Figured it out, had to load this firmware: Ansible Earthsea

The firmware that came with the module did not seem to have this mode?

If I recall, the note is an interval added to to original note, so it’s easy to go away from the original key.

The docs a bit prematurely describe Earthsea and a couple other features for the 2.0.0 release, which should be released soon (pending me fixing some critical bugs). You can try a beta from here if you want to check out the latest changes. Sorry for the confusion.

1 Like

Thanks for the reply! I am enjoying Earthsea on the 1.6.1 and looking forward to the new release.

Hope this is OK to ask here.

I am trying to update the firmware on my Ansible. I did this:

use homebrew to install dfu-programmer. go to the homebrew page and scroll down to “Install Homebrew” where you’ll paste a line of text into Terminal.

After doing that, the Terminal said Password: and had an image of a key. I had no idea what to do with that, so I quit Terminal.

I also downloaded theansible-2.0.0 file from GitHub and placed it in a folder I will remember.

However, when I typed “brew install dfu-programmer” in Terminal, I got a message that said:

-bash: brew: command not found

any suggestions? I am not an experienced Terminal user…

Thanks!

start over, and this time when you install homebrew, type in your system password and press enter. the rest should work thereafter.

Thanks, I’ll try it!