Ansible 1.5.0

dudadius 2017-04-23 21:40:11 UTC #21

I think I've made a sad discovery...so I use the DTFU terminal commands to grab presets off of my Ansible. I updated to 1.5, then restored my preset file to the module. The module is back at it's previous version!

I redid the process, this time checking after 1.5 update. It was successfully updated. Restored my preset file and now I was back to the older operating version.

So....when the DTFU process grabs the presets, is it grabbing EVERYTHING from he module, even the operating system? So when I restore my preset file, I'm overwriting the new update as well?

Is there a way to get around this? Grab a preset from an older OS, update to 1.5, then get my presets back on there? Or do I have to recreate the patterns? Wouldn't be an impossible task, but certainly tedious.

Leverkusen 2017-04-24 05:08:24 UTC #22

Oh, I see that this is a bit frustrating - I really hope that there will be an USB storage function on Ansible someday as loosing the saved presets really makes the updating cumbersome, esp. when you need to do an update for bugfixes (@tehn there still is the graphic UI error when the active part of a pattern folds around the end of a row)

If this DTFU process does work I would be happy to learn it - or maybe the new USB implementation @sam did for teletype could help to get it on Ansible too?

ghost 2017-04-24 11:44:20 UTC #23

Last night Ansible (Kria) got into a state where the gates were stuck on. Switching preset would turn them off but as soon as they were triggered they would stay on again. Turning power off and on again fixed it and it's not happened again since. I was playing with gate duration at the time and clocking externally with bursts from the wogglebug. I wasn't using meta sequencing or any new features. Not sure if anyone else has experienced a bug like this?

bassik 2017-04-24 14:02:00 UTC #24

Tried it last night...only have ansible and grid so not aware of any issue with teletype.

Of course it looks amazing but I am struggling to get my head around the actual meta-seq.
I am not able to sequence different patterns...also cannot get the loop lenght to work.

Apart from the above I have questions:

the pattern bank has 64 slots, which occupy the center four rows (64 positions). touch any position to edit

: Are those referred to the 4 Kria channels? (row 4 ch 1, row ch 2 and so on)

also which are the pattern selectors? first row?

Maybe I shall wait for the diagram.

tehn 2017-04-24 15:22:42 UTC #25

@ghost i've never seen this, sorry to say. please keep me posted if it happens again and any surrounding circumstances.

@bassik the 64 meta-pattern positions simply select one of the 16 available patterns. there is no per-track selection, a pattern contains all track data. documentation on the way soon...

thopa 2017-04-24 18:25:07 UTC #26

Thanks for this! Printing!

bradfromraleigh 2017-04-25 15:41:29 UTC #27

Thanks so much for this!

Will this version work on WW (even if just two track)?

dudadius 2017-04-25 16:28:12 UTC #28

I am having an issue in which my Arc4 (one of the last wooden ones) flashes wildly. First time it did this, I reinstalled the firmware update and it then behaved normally. Then it started doing it again. A restart of the case fixed the issue, but it happened AGAIN, and now a restart not fixing it.

I'll try another firmware flash tonight... Just thought you'd want to know.

samn 2017-04-27 17:04:12 UTC #29

this update is great, thanks so much i've been playing with it nonstop

ghost 2017-04-28 18:44:36 UTC #30

I've noticed that when I'm switching away from Ansible (MP and Kria) and back again, the module has a slight pause ( maybe 1/10th second? ) which interrupts the pattern before resuming as normal. I am using Firmware 1.5.0 but this also happened in the previous firmware too.

I've read there have been some issues with hot swapping in Ansible reported in previous threads but was under the impression it had been resolved.

ghost 2017-05-04 07:36:54 UTC #31

Does anyone else experience this?

tambouri 2017-05-04 13:45:47 UTC #32

Yea, when i jump back and forth on a switch between another module and Ansible I get a small lag in the timing (or at least that's how i'm perceiving it) when the grid is switched back to Ansible.

I'd noticed it on an earlier version and it seems to have persisted here on 1.5

I was playing around w/ clocking Ansible externally where it seemed to happen less frequently or noticeably, but it still happens w/ some regularity

tehn 2017-05-04 14:22:41 UTC #33

it must've been reintroduced. i'll check on it next week when i'm back.

ghost 2017-05-04 14:30:29 UTC #34

Great thanks Brian

I've tried this too and it certainly seems to help keep things in time. Glad to hear this isn't just a problem with my module!

gooooose 2017-05-12 11:52:18 UTC #35

that new video sounds fantastic...can anybody tell me where that bass comes from? it sounds really good to me.

rainlet 2017-05-12 12:43:06 UTC #36

I'd assume it's a Mangrove?

bradfromraleigh 2017-05-23 03:28:49 UTC #37

Has anyone tried MP with the update?

Specifically, I want to know if others are having an issue getting all 8 triggers to fire in 8 TR mode. I can seem to only get the first four (on the TR side of the panel).

tehn 2017-05-23 12:35:52 UTC #39

i tested this yesterday and it worked fine. is the CV side working with kria?

bradfromraleigh 2017-05-23 12:48:40 UTC #40

Kria is working fine. Maybe I'm experiencing operator error.

tehn 2017-05-23 14:52:48 UTC #41

try loading a blank preset?