Is it normal for ansible to freeze after a lot of arc activity?

[Leverkusen]

Which would be fine if does not alter the name of the file but thanks for pointing me to this. It is the same setting that autoplays downloaded audiofiles…which annoyed me as much as downloading them instead of playing them in the browser window…not anymore now.

[Leverkusen]

it should be clarified there were 2 groups of changes made to the libavr32 library - there were some i2c fixes a few months ago. i believe all the official firmwares should have those now.

then there were some additional stability changes i made in june, only the official ES firmware and the beta TT version i posted a while ago have them right now. at some point these changes will likely go to TT 2.1 (along with improved keyboard and screen response), and we will update all the other firmwares as well.

hope this clarifies things! have you had a chance to try the latest ES firmware? are you experiencing any issues still?

At the moment I have this version installed I think. Together with all latest official versions for Ansible, Teletype and Meadowphysics. So should this work or shall I get back to first group of library changes?

And yes, actually I just found an issue: the second diagonal double gesture that is going down from the root note does change the three CV outs as expected and restarts the sequence but does not change the root note as all other double gestures do.

[scanner_darkly]

if you’re using the latest official firmwares (including ES that was posted on june 19th: https://github.com/monome/earthsea/releases/tag/v1.9.4) there shouldn’t be any issues with freezing / lock ups with 2 exceptions:

• i was able to get one of the TT 2.0 betas to lock using an extreme case (audio rate triggers / super fast metro script with lots of i2c commands). i didn’t try reproducing it with the official 2.0 firmware but it’ll likely produce a similar result. unless you do want to use it in such extreme manner you will be fine with the official release. i was able to fix the issue and posted a test version here: Does your teletype stop responding after an hour or two? at some point this should become the basis for official 2.1 release, before that happens i will start a new thread and ask for help with beta testing. to reiterate, if you’re not planning to use TT in extreme manner use the latest official 2.0 version.

• lock up issues with earthsea that were reported here: Earthsea Edge lock-up should be fixed in the latest official ES version. i asked several times in the thread if people were still experiencing the issues but didn’t get any replies… then there was an issue @saintcloud reported in that thread with shape outputs becoming corrupted, i was not able to reproduce it, which makes it difficult to fix. it would help a lot if others tried the latest version and reported back.

for the issue you mention i’ll take a look but it doesn’t sound like it’s related to i2c/lock up issues.

[jasper_ryder]

This is the firmware I have been running for awhile now. My grid became unresponsive on it a few days ago. It has only happened once.

[Leverkusen]

for the issue you mention i’ll take a look but it doesn’t sound like it’s related to i2c/lock up issues.

You are right - I just tested it and it obviously never worked before (I tried it back to earthsea firmware v1.8), just that no one had noticed it. So maybe @tehn could have a look on it?

[tehn]

could someone please start a new thread about the ES bug and describe it fully? or revive an old thread that describes it?

[Leverkusen]

could someone please start a new thread about the ES bug and describe it fully? or revive an old thread that describes it?

It’s there: Earthsea two finger gesture bug

…not fixed though.