fix for jump to pos not working after a pattern is reversed:

ansible.hex (273.2 KB)
ansible_es.zip (86.9 KB)

this concludes this version development (with the exception of any critical bugs discovered) and has now been superseded by Polyphonic earthsea for trilogy/ansible and er-301/just friends/txo

10 Likes

@scanner_darkly:
i think i found a bug but i maybe wrong.
with both this last update and the preceding one, if you clock ansible and then try to use the /2 or *2 runes, they don’t work.
i’m able to get the /2 rune to do something if i press it repeatedly a lot of times and then the sequence is basically stuck at the first step of the playhead and doesn’t advance.

i think you can replicate this.
don’t know if this is a bug or if i’m missing something, but i remember using the /\ and the / runes (with ansible externally clocked) and being able to sort of reduce or augment density of events. now this is not possible.
thanks!

double/half speed runes never worked with external clocks. but there was a bug i fixed that might explain the change in behaviour - previously the runes didn’t account for chords (earthsea will treat notes that are within 30ms of each as chords) so at some point you would cross the threshold and it would sound different. now the runes will leave chords intact.

this sounds like a bug, will fix.

1 Like

strange, i really recall using them on the chopped breakbeats (er-301), so the ansible was clocked, for sure. maybe they worked for some reason without you knowing it? :slight_smile:
anyway thanks for checking it out!

the fix for half speed rune not working when pressed too many times: ansible.hex (273.3 KB)

5 Likes

new version that includes fixes from here: Kria: How to create "longer" sounds and faster gates

ansible.hex (273.5 KB)
ansible.zip (88.8 KB)

edit: updated with the better fix for tied notes

6 Likes

How do you install this? And what if installing it bricks the Ansible?

This is exciting but also terrifying because I have no experience with this kind of thing at all…

I’m very minimally experienced when it comes to stuff like this and I’ve upgraded an Ansible and Teletype several times each from a Mac without any trouble. Just follow these directions and you should be fine. Edit: Only change to the Monome instructions is to use the file above, rather than the one on the instructions page.

I’ve updated my Teletype, Ansible, TXo’s, TXi’s, W/, Stillson Hammer, O_c, ER-301/101/102, and a bunch of others and nothing has ever been bricked. Jump in and simply follow the instructions like @ceedotgeedot pointed you to.

20chars of thank you!

1 Like

Once you have homebrew installed it’s a breeze. I just got a 2nd hand white whale and loaded orca on it last night

Just want to caution that in my experience Ansible (mine was bought new from monome mid last year) uses the at32uc3b0512 chip, which has more flash than the at32uc3b0256, and I believe this backup procedure did not back up the presets from flash unless I used the

dfu-programmer at32uc3b0512 read > firmware-backup.hex

command listed under the Teletype instructions. If you want to try out a new firmware and then go back to the saved Ansible presets you had, I think you might be unpleasantly surprised when using the at32uc3b0256 command.

1 Like

good catch!

@tehn - looks like this page needs to be updated for the above: https://monome.org/docs/modular/update/

6 posts were split to a new topic: Ansible: help and issues

should we merge earthsea into the main ansible branch? was there any functional compromise compared to master? (i apologize i haven’t kept up!)

2 Likes

I think the main concern is with running out of memory/flash on Ansible that could be a constraint for future feature development of existing apps: Ansible Earthsea I haven’t actually tried to build a firmware with both Earthsea and the new Kria features + preset saving included, and Earthsea would also need kind of a large JSON document definition which would also take quite a bit of space. I can try to merge ES into my dev branch and see where we’re at with memory… once I’m back at my computer late tomorrow night.

2 Likes

yeah, definitely memory / preset concerns. not just for expanding existing apps but for adding other apps in the future - should earthsea be part of the standard pack? or should this space be reserved for some future app?

no functional changes done to the official firmware other than having an extra grid app.

a side note (which shouldn’t drive the decision): merging earthsea to official ansible firmware would also mean i don’t have to rebase each time the official firmware is updated. at this point i’m afraid i don’t have the resources to maintain both ansible earthsea and polyearthsea. getting ansible earthsea working with presets is probably the last time i’ll touch ansible earthsea.

thank you - this would be super helpful!

1 Like

After merging and adding the preset save/load functionality here’s the binary size info:

   text    data     bss     dec     hex filename
0x1ccf2  0x1cb0 0x4af08  432298   698aa ansible.elf

So if I’m figuring this right we’ve got 0x7E000 - 0x698AA = 0x14756 or about 82 kB left flash, or 16%.
Here’s master for comparison (30% available):

   text    data     bss     dec     hex filename
0x1a5e2  0x18a4 0x3a278  352510   560fe ansible.elf

This approximately doubles the time it takes to save/load presets (from 10 seconds to a little over 20 seconds). That’s probably largely because it almost triples the size of the JSON file, (to about 1 MB) since Earthsea state has a more nested structure/fewer buffers compared to Kria, so the JSON structure is less compact. Branch is here.

3 Likes

this is great - thank you! could you post the hex file, and perhaps folks could help with testing it?

significantly increased time and file size make for a strong argument against including ansible earthsea in the official firmware.

I just wanted to cast my vote in favor of including ansible earthsea. It’s likely my most used ansible app, but not even close to the “only” app I use. :slight_smile:

3 Likes