#100

The release version of Ansible 3.0 had a bug that prevented presets from saving to a USB disk, so maybe that’s what you’ve encountered. Mentioned here: (ansible) 3.0.0 release - #36 by csboling

2 Likes
#101

Thanks for the info! Tomorrow I will update the firmware to 3.2 version. Well, first I will check which firmware version currently I have because I have a module from December stock.

#102

Be advised that updating the firmware will wipe any presets you have saved. If you have a bunch of work already saved that you want to carry forward, please make a firmware hex backup as described here and PM me the hex file and I’ll get you sorted.

1 Like
#103

Is there any way to adjust the range of LED lighting for Kria CV? If I’m sequencing over a couple octaves, it seems like they’re all barely lit. I could tune the oscillator lower and bump the sequence up a few octaves, but that feels a little hacky.

#104

If the circuit is the same as Teletype (the processor and DACs are, so I imagine so) then the LEDs are just connected to the analog outputs; they are not digitally controllable except by changing the output voltage.

#105

Oh, thanks, but this won’t be necessary. I don’t have anything that I want to be saved.

Anyway, thanks for the help, guys. This afternoon I will try to update the firmware.

EDIT/SOLVED:

I’ve downloaded the hex file from @csboling that @morgulbee linked a few posts above. I’ve also downloaded the “official” firmware 3.0 from github, because I needed the update_firmware.command file. I’ve replaced the “offical” hex file with the one downloaded at the beginning. Then I updated the firmware successfully. And I’ve checked that now I can save presets on a USB disk (ansible-presets.json isn’t empty!). So problem solved. Thank you, guys! But I have one question more: what’s the difference between hex file from @csboiling and hex file from github? Cheers,

#106

yikes let me check tomorrow if the files are updated

1 Like
#107

Hi all, I’m considering getting an ansible(and grid, and teletype, and just friends, and…) but I’m confused as to whether or not it can do midi2cv w something like an octatrack?

I just don’t want to buy it instead of a midi2cv module and get stuck not being able to sequence anything until I can get a grid.

#108

An Octatrack (or really anything with traditional 5-pin MIDI DIN ports) combined with a basic USB MIDI interface such as a Roland UM-ONE mk2 or iConnectivity mio should work fine.

All the basic MIDI to CV functionality is available from the Ansible front panel but the more elaborate settings require a Teletype in order to send commands over the ii bus.

#109

Hmm ok thanks. So if I wanted to configure ansible to output CCs and clock on some of the outputs I’d need teletype?

#110

I’d recommend reviewing the ansible MIDI mode documentation to get a better understanding of what the different modes offer and decide whether it meets your needs. The FIXED mode has a learning feature which can be initiated from the ansible front panel. FIXED allows 7-bit CCs to be mapped to the module’s CV outputs and specific notes to be mapped to the gate outputs. The MIDI functionality is limited to the various configurations which are built into the firmware. The firmware does not currently support setting up arbitrary mappings of MIDI events to hardware outputs as is found on larger dedicated MIDI to CV modules. The teletype integration does provide access to some settings which cannot be modified via the front panel such as certain arpeggiator features like euclidean rhythms but it does not add any features beyond the existing MIDI modes.

#111

Any update on this? I just updated and wanted to make sure I am actually updated. Or need to do it again

#112

Eep, I think this is my mistake, there have been several issues fixed but it looks like we did not make a new official release since last April (because I said to hold off, and then it completely slipped my mind). If you have a chance then a new release I think would be good, I will try and do a quick round of tests on the current code tonight.

1 Like
#113

oh! thanks for the heads up. i can get together the release this week.

4 Likes
#114

I got an Ansible mid December, and finally had a a good play with Kria yesterday. I had a great time, really gelling with the interface so far.

But I ran into a weird issue:
With two tracks active, the pitch of each going to the top and bottom oscillator of Instruo Cs-L respectively, the two oscillators are playing in tune. But if I set the first track to play in reverse, the bottom oscillator (getting pitch from track 2) is pitched up something like a quarter tone.

Is this is a known bug? If not, I’ll try to record it. Or could something else be causing this?
[EDIT: Disregard this, can’t reproduce it…]

#115

Hi everyone,
I’m trying something a little new with my Kria and was hoping to sequence Collision in Ableton Live, through my crow with Kria on my Ansible.

Now, I have set things up in which I have placed Trig and CV 2 of kria in to the INs of my crow. Then, sent the INs of the crow M4L tool to Collision. Using a tuner, I find that notes are just varying WILDLY. I’m a little curious if folks feel the need to use a quantizer when using Kria as a v/oct source…

Is there maybe something I can do to fix this issue?

#116

The CV outs on Ansible are not the most accurate when translating 1/12th of a volt to the corresponding MIDI note, but there is a fine tuning procedure included in the latest firmware version to compensate for this. It requires fine tuning every note value on all 4 cv outs but it can be remedied.

Check out the bottom section of this doc entry for details:

2 Likes
#117

Man, I wish there were a good software quantizer. I’m assuming one could easily be made in Max if I had just actually paid attention and figured out the Midi stuff in Max.

Thansk

#118

I don’t know how much an additional quantizer would actually help, because it’s the CV source that’s inaccurate and going beyond the threshold points of what voltage corresponds to what note - it all comes down to Ansible’s CV output.

The fine tuning takes some time but it’ll get you where you need to go :+1:

1 Like
#119

Alright, thanks for that! Yeah, I was having an odd thing where if I tried to hit middle C, and used a tuner, some notes would be C, some would be C#. It was drifting by full semitones, which seemed wild to me, and you’re right, wouldn’t be helped TOO much by a quantizer depending on the scale.

I’ll give the tuning a shot. If it fixes the problem, then great! If not, I’ll maybe just have to pass the ansible on to another soul who will get the best usage of it.

Thanks again for helping me out!!

Edit: Wooooow, I don’t know if this was an initial build issue, the previous owner set up some sort of bizarre microtonal scale or it has drifted, but going through the tuning process has shown the CV ports to be WAY off! Thanks for letting me know about this setup. Now, to see if I can get the incoming CV from an ES-9 to Midi data in Live without having to buy Silent Way or boot VCV on the side.

:crazy_face: