Ansible 1.0

Leverkusen · 2016-11-09T23:45:29.299Z

While I know of only one sequencer that holds the voltage untill the next active step I see that my idea was not well thought through for this reason too now. I solved it for now with another trigger setting the voltag back to zero on the next step but the vca/envelope/slew patch might be more elegant. This is a strange day!

Leverkusen · 2016-12-29T11:12:06.481Z

tehn:

github.com/monome/ansible

Issue: preset import/export to USB disk
opened by tehn
on 2016-10-06
similar to tt
enhancement

Is the USB save/load functionality already implemented? Doing the 1.3 upgrade on Ansible and going back to 1.2.2 because it does not work killed some nice Kria presets which was a bit frustrating. Would be nice to prevent this on the next trial…

sakul · 2016-12-29T12:23:06.689Z

curious, what in 1.3 isn’t working for you that did before?

(I know it sucks, been there… but to be fair, there is a warning on the release page)

Leverkusen · 2016-12-29T15:38:51.873Z

sakul:

curious, what in 1.3 isn’t working for you that did before?

(I know it sucks, been there… but to be fair, there is a warning on the release page)

I have been a lot on Cycles over the last weeks. It has stepped voltages now which does not work for me.

I am sorry If my formulation was ambiguous, I am not complaining about losing presets when upgrading - I was asking if there already is an opportunity to save to USB before upgrading just in case an upgrade is buggy and you have to go back. I waited a few days and there was much happyness in the feedbacks on the 1.3 thread so I thought it would be relatively safe.

sakul · 2016-12-29T15:56:05.249Z

ah good to know… didn’t have the time to install the new release yet, which is a shame…

Leverkusen · 2016-12-29T17:01:03.022Z

Yep,I would not recommend the new release at this point - there are some more flaws mentioned here:

Ansible 1.3.0 - ii for kria/mp/levels/cycles

First time using Ansible as a Teletype expander; everything freezes up when I send a command. Requires a restart.

and here:

Teletype Firmware i2c Debugging

Loop Actions to the Ansible Skip Values in Scripts

sakul · 2016-12-29T17:23:16.182Z

well, bugs in new features are not unusual in general. it sounded though like old functionality did suffer…

I’m sure he will figure it out soon… been a lot on the plate recently! which is totally exciting…

Leverkusen · 2016-12-29T18:20:24.461Z

I’d love to still have your confidence - mentioned the skipped teletype remote commands in may for the first time:

Heavy slow downs with Earthsea

I am not sure if this is the heavy slow down issue but when I clock my earthsea from teletype every now and then it misses a step and occasionally it gets totally out of the step. After a short time it regains its composure.

Sounds like this - in the beginning you hear it stumbling around and then getting back in step. I did not touch anything, just hit record when it occurred.

https://soundcloud.com/salz-peter-zucker/unstable-earthsea

I just updated to 1.8, teletype is 1.11. It’s just a two line script clocking the ES on a tripper from MP into the TT an giving a pulse as a reference signal that is running on while ES is stumbling - did this to make sure that it is not the TT. It is the first time I am using a II script. They are all sitting in a ⅔ filled make noise shared system case with make noise power.

Don’t know if it related but when I tried out the help screen function, one LED in the lowest row was not to switch of again unless I powered down the whole case.