I wonder if its possible to add more arc functionality to Ansible in later firmwares - I think this shift register sequencer from parasite Frames firmware would work really well with Arc https://mqtthiqs.github.io/parasites/frames.html

5 Likes

I asked this in another thread: is preset management independent of firmware update on the horizon?

3 Likes

I don’t think so but I believe there is a way to save the existing firmware code on the module onto computer

Right…but the presets are stuck with that version of the firmware. Need to be able to load presets into new firmware somehow.

1 Like

Yes I agree it’s a workaround only. The presets issue is the reason why I can’t update to v1.6 as I gig using v1.5 presets. I am seriously considering buying another Ansible as I want to use the Arc and Grid together anyway.

That’s what I’ve been doing. Took half a day last time. :man_facepalming:t2:

I have two for that reason.

1 Like

i just wanted to say thanks for this ansible update
very fun and more expressive even with the Kria/Whale sequencer --i am having fun with it

3 Likes

this is why i have 2 as well. highly recommend it.

4 Likes

Is it possible in the Kria 1.6.0 fw to tie notes together for a continuous output gate held across multiple steps? Didn’t see this documented anywhere …

yes, with the duration parameter set to maximum and the multiplier also set to maximum, the gate length will be the same as the clock step. it won’t re-trigger so it’ll give you something like a tied note.

2 Likes

Any chance we may see per-channel octave transposition for Kria in the future? I thought I remember that being highly considered for addition, would be amazing!

3 Likes

Hi so was wondering if saving a preset on Medowphysics overwrites the same location on Kria (for example) or can they co-exist ?

Is there a way to backup my presets?

Thanks!

meadowphysics and kria have their own preset locations, they do not overwrite one another.

you can back up your presets with the entire firmware, but you can’t export the presets to a new firmware update. for most people this is not very useful.

thanks got it!

if you don’t mind me asking why can’t we implement presets that will be saved with a firmware update…

since Teletype has this, I think it’s just a matter of finding a good way to do this (and the time to write the code!) rather than an impossibility.

Might be possible with a hex editor to inject your presets into new firmware. But only if the format of the presets doesn’t change…

A patch utility bundled with firmware releases might be the most realistic solution. Then if the save format changes it could pad / trim your existing presets as needed and inject them into the new hex.


Discovery of the day: Ansible will happily host a Roli block. These are cool because you can code a sequencer that runs on the block hardware. This is a simple 8 step note+velocity seq running. Ive also played with it as an XYZ pad sending CCs to Ansible CC allocation mode.

This brought up an interesting use for the currently unused TR in for the standard MIDI mode on Ansible. If Ansible could send some arbitrary note on/off (or maybe CC high/low?) when recieving TR in, then it could be interpreted by the block, which can be used to create custom apps with bidirectional communication. The MIDI arp app does generate MIDI clock from trigger in which is cool, but arbitrary commands would be more useful… I have a Rene style cartesian sequencer in mind

Would the TR handler code be inserted here following the same structure as the ArpTR handler??

The only thing confusing me is that the TR1 in MIDI mode is a Panic command, which I don’t see reference too in this handler. Sorry if im overlooking something, im not much of a coder and Ive not dug into Ansible code before

3 Likes

Not sure if this is the best thread to ask this kind of thing, but it struck me that I could possible leverage my ansible to handle my BopPad->modular setup when I don’t feel like setting up a whole laptop situation.

In looking through the documentation I’m after Allocation style 4: FIXED, and specifically learning how I have things mapped, but I’m wondering if there’s a way to do this more explicitly by telling the ansible what notes/CCs to respond to?

I’ve got a fairly in depth BopPad mapping where it sends all sorts of CCs for things like radius/pressure/etc…, and I don’t really know what order they will be sent out and it would be good to avoid having to learn/relearn until (and if) I get the mapping I want.

It is possible that CCs send out in the order they are listed in the UI, which would be good, as CC1 is what I want from each note/channel anyways, though it is different MIDI channels (13/14/15/16) for each quadrant.

Thoughts?

I’ve experimented with Ansible + Boppad before and had it working like you’re describing in fixed mode. When I assigned the velocity parameter from every quadrant to CC 16, for example, the CV out on Ansible ch4 updated to a new velocity every time I hit a new pad. I haven’t experimented with the continuous variables like pressure.

1 Like