Ansible for JUST midi/cv conversion

That is strange. Here is a picture of my UM-ONE, the pen is pointing at the location of the switch. It is very small and hard to see.

UPDATE: Is it possible you have an original UM-ONE (discontinued) and not a UM-ONE mk2 (currently available)? Looking at the specs on Roland’s site the “mk2” model has the switch. If you do have the original model I’m afraid that it might not be compatible.

Definitely no switch. I believe it is the Mk1. Better hunt down a mk2…Thanks for the speedy response!

For what it is worth I was recently given an iConnect MIO
…I plugged it in just now and it was recognized so that is another option with the same cost/form factor.

Great, I’ll hunt down one of these options.

What’s tha possibility of adding midi clock out over usb?
Inputs 1 or 2 could act as clock in and the buttons could be a tap tempo. It could be useful to have the outputs function as clock dividers

Further into this though it would be really really cool if teletype could tell the clock what’s what

Adding a teletype command to set the internal clock rate (or reset the arp) would be fairly straight forward.

Clock out through MIDI would be more involved but doable. The basic problem is that MIDI clock is typically 24 ppqn which means it one would most likely have to implement a phase locked loop setup in order to multiply the modular clock up to the equivalent MIDI clock frequency.

I had started (but never finished) a high resolution clock for an alternated meadowphysics firmware - that alternate clocking mechanism would probably be useful if one tried to implement this…


I have a Keith McMillen K-Mix that I’m using as my audio interface as well as a controller for Ableton. I’m wondering, could I pick one of these MIDI expanders they offer ( and then use a cable like the Roland one referenced earlier to play Ableton MIDI tracks directly through Ansible?

1 Like

I took a quick look and I would expect that in combination with a Roland um-one mkII (or equivalent) would work fine.

…assuming that the kmix along with that expander is designed such that your computer can output through it as if it is a normal midi interface.

1 Like

Hello ngwese
I figured i ll ask here too as i did in the earthsea topic

I wanted to ask if there is a slight chance the midi functionality of Ansible will ever recieve some kind of clever code changes that would allow for a few slimmed down functions that are usually only accessible via the monome hardware modes.
I am thinking about very simple sequencing duties like note/melody loop for example. Not sure what else exactly… but while thinking of it, on a pure performace perspective i think having some spare keys on a keyboard for functions instead of notes would be quite possible? Not knowing a bit about how hard that might be to implement. Just the performance

I dont have my hopes up, but figured i would ask.

Another idea would be to have spare cv/tr outs that arent on voice duty be usable for things like lfos? Would sth like that be possible and in your interest of Ansible?

I am asking bc i am more of a keys person than buttons. The layout of keys is just more intuitive for me, so i would most likely use Ansible via midi and feel like missing most of what it actually can do.

It’s not the best solution to your question but you could always use keys to lay down a MIDI track in a DAW like Ableton or something and then send the MIDI track through Ansible.

Never. the most daw i might do is running an ios sequecner but even that is a compromise. Really displike using puters for music

I don’t personally have any plans at the moment - all my free time is going into norns right now.

One of the main challenges with respect to expanding the midi modes is really just ui. The grid has the advantage of being consistent - beyond size, the capabilities are largely the same. Midi controllers are wildly varied so it is difficult to come up with an extended ui which uses anything other than midi notes. The existing ansible midi behavior is already pushing the limits of what can be squeezed into the three buttons on the front panel. There is functionality which is currently only accessible via teletype to tweak pitch offsets and the arp logic. Part of me doesn’t like the idea of requiring another piece of hardware just to unlock certain functionality but in the end I felt that there were enough folks that would end up with both a tt and ansible in their rig that it would prove useful to a sufficiently large number of folks.

If you have specific ideas on what you think would be interesting to see in ansible I’m happy to discuss further.


The flexibility and custom behavior that it sounds like you’re looking for is in computers, though. That doesn’t have to be a DAW. It could be a Max or PureData patch that you set up, then close the laptop most of the way and play your keyboard basically the same way you’re describing it might behave being plugged into theoretical extended Ansible firmware.

You could also code custom Ansible firmware and then it’ll do whatever you tell it to. But that’s a taller order. PD is free though, and can be set up and then turn away from the screen.


You probably don’t even need Ansible in this case. What you’re looking for I think could be achieved with a CV recorder like Brain Seed and a keyboard that outputs CV like a Keystep Pro or the Keith McMillen one (think it’s the Qunexus?). You’d also save 2HP with the Brain Seed.

1 Like

Lovely idea but really above my tech skillz i suppose.

But what exactly would get me play the patch away of puter here?

Totaly see your points. Thanks for being detailed about them.

Well this is pre coffee but i suppose a bit of added candys to the midi mode would be all i hope for. Then one could get ansible and be open to get grid in future but get still a good use out of it beforehand.

Mainly a cv record of the midi notes played. Could be basic like a looper with the buttons doing add-erase-start/stop. Even a fixed time would be fine here. Like 15-20 sec maybe
And a way of having at least one lfo to a gang of 3 voices/ midi cv‘s

I have no idea how hard this would be to implement but that would be so useful tools for every key player that might not need the complex sequencing of the main modes with grid/arc.

Btw are there any custom/alt firmwares around on github? I suppose i would have read about them here if there would

I mean the entire point of Ansible is to have a physical form of apps specifically made for Grid and Arc. The MIDI capabilities are just kind of an added bonus I think. Just seems like the wrong tool for the task at hand, a general CV recorder/looper like Brain Seed would be exactly what you’re looking for I think.

1 Like

Ofc and thanks for the cv recorder suggestion, being the place this is i throw this function in as a nice potential idea or suggestion for a midi addition as midi additions where earlier said to be welcome to discuss here.
To explain why this would matter to me is simply i need a midi cv for now, i would be interested where the i2c might develop concerning ansible, and the modules future flexibility also with potential addition of a grid or arc later. All this is happening on 56hp so maybe it gets more understandable why i ask?

I dont see a better future save module to take, allready as is, many roles in this context and i wonder if the cv record to its flash would be doable in a not overly time consuming way

I will however see if i can hunt for cv rec in 2hp not sure how easy it would be to implement but maybe you are right and its the best solution

Not so much away from the computer, but without needing to interact with it. Ansible is basically a small chip running software, so it’s not terribly different. Plug your MIDI into Ansible or into your computer and run a program.

Though to be fair, Ansible outputs directly to your modular, and a PD patch wouldn’t do that per se w/o something like an Expert Sleeper’s I/O module that has DC coupled outputs.

Just trying to come up with ways to maybe get what it sounds like you’re describing you’re looking for, given that doing it w/ Ansible would require firmware development and most folks in the community who do firmware development appear not to be working on Ansible at the moment.

What I think you’re describing wanting is custom behavior particular to your setup, which means you’d probably need to do the coding, and PD is much more approachable than firmware development.