Where is the repo for this project? I’d love to try it out / contribute in some possible way! :slight_smile:

the official firmware: https://github.com/monome/ansible
the earthsea branch: https://github.com/scanner-darkly/ansible/tree/earthsea

2 Likes

This earthsea branch is all adds to the official firmware (nothing removed?)

yep, it has everything from the latest official release

1 Like

Hi thanks for the reply. Made a little video pls let me know if it works. You can see I tried saving a scale in a preset and upon loading to another preset the scale is still there. Perhaps I’m doing something wrong ? Or could it be the USB cable I used to upgrade to this firmware ?

it says i need to request a permission?

usb cable wouldn’t result in partially broken firmware, it would just fail to load it.

edit: scales are shared between all kria/mp/earthsea presets.

amazing, thank you…

https://drive.google.com/open?id=1VcXHEnng-rYxHRfRkGsb5ukIutC5J94o

Sorry pls try again didn’t enable sharing

Okay , but say I save a set of scales in one preset then want to keep those scales specifically for that preset and a set of other scales for a different preset. Would Ansible allow this ? Or am I getting the concept wrong?

Just a restart of the whole system seemed to solve the problems. Weird. I’ll get back to you if it reoccurs. Sorry for the trouble!

Great update! One thing I’ve noticed is that using the progress bar to jump positions when a loop is playing backwards has strange behaviour. Specifically - playback will move to the opposite of whatever position you select.

no, scales are shared by all presets (and shared by meadowphysics/kria/earthsea), which explains the behaviour you’re seeing.

thanks for the bug report - indeed, forgot to account for reverse direction, will fix this.

Playing around with aerthsea today and running into a situation where whatever clock I give it seems to be divided- couldn’t find anything about this searching the thread for a bit- is there a clock div page I’m missing somewhere?

i think there might be for kria? not for earthsea though, it should follow the external clock 1:1.

using it extensively for drums\chopped breakbeats at high bpm count, dividing\multiplying clock externally, never ran into this problem. but i almost always use it externally clocked for such duties.

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