#64

‚Ello
I‘m wondering if my beloved but virtually unused 64 varibright Grid and Arc2 first generation can be used with Ansible. As i understand there is an obvious limitation of control because of their half size. And as i remember with community tweaking the apps, it was possible to some degree. Is ansible programmeable?
I was thinking of trying out Ansibles Apps with my two half pints upfront.

Is any1 doing this already?

#65

Kria will probably not be usable since you can’t access most of the parameters pages. Meadowphysics and Earthsea may work okay but of course half the control surface will be inaccessible. I know some users use 4-step 128s with Ansible apps successfully.

I have never used an Arc and am not too familiar with the Ansible apps for it, but this may work out a little better just because I think Arc rings map more one-to-one with Ansible’s output channels.

Certainly! Source code is here. Modifying Kria to work with a 64 is probably not possible, but changing Meadowphysics and Earthsea to only use 8 columns seems feasible.

1 Like
#66

Thanks, i need to really try these apps with my little ones and see whats going on

#67

Having an issue with my Ansible. Well, at least I think I am. (grin)

All four CV and all four trigger LEDs are lit continuously. Tried power cycling. Any other suggestions?

Thanks!

#68

what usb device are you attaching? any response?

firmware flash is always an option.

#69

This sounds very similar to an issue I had last year with my Ansible. Are the white CVs very bright and when you plug in a CV to V/8 does it make an incredibly high pitch tone? If so this sounds like the exact same problem I had, unfortunately Brian had to provide a specific fix

#70

Just my grid which seems to be functioning normally (Kria is running) minus the LEDs on the Ansible not changing.

I’ll try reflashing the firmware.

@Minimum, no sound out of any of the jacks but the voltage reading on my Mordax DATA is showing the highest value on all 8 outputs (TR and CV).

#71

Update: I updated my firmware to 3.0.0 which seemed to solve the issue. Cheers!

1 Like
#72

Continuing the discussion from Ansible Kria Feature Requests:

Bringing this topic back up. Doesn’t seem like the metasequence resets? Triggers are working properly. Is this possible? Would be helpful for overdubbing, etc.

Nick

Ansible bug reports (official)
Ansible Kria Feature Requests
#73

No that doesn’t sound right., I’ve not had issues with it not resetting to start of each sequence during metasequencing. Unless it’s not been spotted on the firmware update. I’m not on v3 though. I also hold the alt button when hand switching sequences so they reset.

#74

To clarify, the individual sequences are resetting properly, but the metasequence sequence isn’t when stopping and playing. It just picks up where it left off.

#75

Hello,
It doesn’t seem like the MetaSequence resets on start and stop when sending an external clock/reset into Ansible. The regular sequences work correctly. Is there a way to do that?

Thanks in advance,
Nick

Kria pattern position reset and meta-sequencing
#76

I’m selling my Ansible, but would like to test it before hand, the problem is that I don’t have Grid or Arc anymore… is there away to run it / test its functionality in some other way?

#77

You can connect a USB-MIDI controller and use Ansible as a MIDI-to-gate/CV converter, or use Ansible as an I2C output expander for Crow or Teletype if you have either of those.

#78

My post about the MetaSequence not resetting when external clocked/reset pertains to the Kria preset specifically, so a USB-Midi controller set up wouldn’t work. Would love to know if resetting the MetaSequence (in Kria) is possible.

#79

Wondering if there is a way to put ansible in duophonic mode for it’s midi mode? I see Meadowphysics does two-voice mode but couldn’t see a way to do it with a plain ol’ midi keyboard.

#80

Hi, same issue here. Just updated to 3.0.0 in the hopes of this being
solved/updated. Really wish this could be added in the future!

#81

Resetting the metapattern position on a reset trigger seems fairly straightforward to implement, but I don’t know if this is always desired behavior or if there are sometimes situations where the current behavior of just resetting the track positions is preferred. Which would mean it needs to be configurable, which means how it fits in the UI needs some thinking.

#82

Totally with you on that one, and the ability
to resync/recue most of the sequenceable parameters individually is of great value.
Nevertheless for me there’s a true necessity of a global resync/retrigger

#83

I’m not sure if this thread is for general questions, so I hope this is the correct place. I’ve just updated Ansible to firmware 3.0.0 and when I try to do a USB backup, the ansible-preset.json file is empty. Any ideas? Thanks!