#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!

#84

Unfortunately this is known to be broken in 3.0, but fixed in the current beta. If you have presets you want to carry forward, please take a backup using this procedure and PM me the ansible.hex file and I’ll generate an ansible-preset.json for you from it. We should try and do a bug fix release here soon I think.

3 Likes
#85

I have an i2c related issue:
How can I debug follower mode on the ansible?
Everything works fine in leader mode, but I am not getting any response/change when trying to send commands from norns (Fates, 200712) to ansible (3.0.0) through crow.
From the doc it seems like it’s in follower mode when nothing is plugged in, is there anything else I need to do?
Thanks!

#86

If you have activated any follower, ansible will remain in leader mode until you deactivate all followers. Ansible continues to operate with its existing settings when you disconnect your controller from the USB port, this is by design so that you can hot-plug your grid into some other host without interrupting your sequence. When you exit the preset / ii configuration page, leader settings are saved to flash, so Ansible will also remain in leader mode after a power cycle and be unable to receive commands from other leaders on the bus.

If you can share your complete script or the crow.ii-relevant portion this might help to troubleshoot further.

#87

Brilliant, that worked! I didn’t realize the presets were saved to flash. Thanks for the help!

1 Like
#88

Does anyone know if this diy arc wil work with ansible? https://github.com/TheSlowGrowth/MonomeArcClone

#89

Hello! I’m the proud new owner of an Ansible and 2015 (or newer) Grid I got off of Reverb and both are working well. I watched the Ansible tutorial video from a different thread (posted in July–I forget the name of the thread) and my pattern page looks different than the one on the video, plus I don’t have the option to shift all triggers in the octave page, so I’m thinking I have an older firmware.

I found the page for updating Ansible, so I guess my question is do I only need to update Ansible and Grid will show updated kria pages, or would I also need to update Grid?

Thanks!

#90

Just Ansible. I don’t believe there’s been a firmware update for grids in a long time. Welcome!

1 Like
#91

I think this design has worked for people on the release versions of the firmware, but if I remember right my current beta firmware has a change that works fine with stock Arc but doesn’t with this DIY build. Possibly this could be fixed via a firmware change for this clone if someone who has one is willing to help debug the firmware.

1 Like
#92

Thanks for confirming that and for the welcome. Starting slowly with kria and I anticipate coming back with more questions in due time. :slightly_smiling_face:

#93

I posted this in a different thread but just found this one which may be more appropriate -

I have an older grid 64, and alas an older Arc 2 – does ansible accommodate these more limited options (in terms of buttons and wheels). I’ve been eyeing the monome stuff since more so getting into modular, but I’m not sure if it makes sense to jump in with the 2 monome devices I have…

#94

hi hi!
unfortunately, ansible requires 128 grids and arc 4’s. while there’s alternate LED support for the different generations of 128’s, there’s no support for 64’s.
i’ll make sure this gets in the docs, thank you for the bump!

#95

Are there any good options for connecting my older/smaller devices to a modular set up? (Unfortunately, even most of the Max oriented apps utilize a 128 or arc 4, though they will work in a more limited state, and I haven’t had time to really dig in and develop something for my own use…)

#96

any of the original trilogy (white whale, meadowphysics and earthsea – all discontinued, but pop up on the used market) will work with 64 grid’s, with usability caveats:

no module support for arc 2

however, a norns shield + crow combo would cover all generations of grid + arc and give access to many more applications. a bit of rolling your own will be necessary, but there are tons of resources to begin.

also teletype’s grid ops support 64 grid! no arc support (yet?).

hope this helps a bit!

#97

Yes, thanks! Will dig in some more. I was reinspired by a video I was watching yesterday so started thinking about it again. (in the spirit of “work with what you have”).

So in that suggestion, does norns provide the interface for the grid / arc to connect to crow? Seems like an interesting option, and an excuse to actually get a raspberry pi… :slight_smile:

1 Like
#98

for sure – if you have access to Max and some sort of USB CV interface, that’s where Max would come in most handy. understandably, time is a precious resource – this is a very real bummer.

apologies for forgetting, but multipass is also a very direct way to build alternate firmwares for ansible.