#61

Do you have a volt meter or some other way to read the CV output level? If so I’d suggest trying to confirm that the output voltage is increasing by +1 volt for each octave you go up on the keyboard. If it doesn’t seem to be tracking to +1 volt something could be going wrong hardware wise.

The global offset is only settable via teletype but that also means it is highly unlikely that it is set to some odd offset (unless your ansible was used and it was set by someone else).

What is the oscillator you are driving?

Is there any chance you have really old firmware - pre v1.4? IIRC the two octave offset was added in v1.4. If there are any funky settings stored in flash you could try re-flashing the firmware to basically get it back to factory settings.

#62

thank for your help. yeah i have an es8 so il use the osciliscope in there to check things out.

my ansible is indeed used so we shall see.

how do i know what firmware i’m on ? if things seem wrong when i check the voltage output then maybe il try flashing the firmware. honestly feel a little over my head here but il try.

#63

Prior to v2.0.0, there’s not really a way to figure this out other than the presence / absence of certain features. As of 2.0.0 you can back up Ansible’s stored presets to a JSON file by inserting a USB disk – this file will contain the firmware version near the top of the file.

Incidentally, this is a way you could modify things like MIDI settings without a Teletype: dump a JSON backup to disk, edit the file on a computer (this part is… not remotely user friendly, but I can advise), then reload the edited backup onto Ansible.

If you have a grid and are used to using Kria, here are some indications of what version you’re on:

  • I believe trigger ratcheting, alt notes, and glide settings were introduced in 1.6.1.
  • In 2.0.0, Kria’s octave page will have 5 keys lit in the top-left corner of the grid, for a track-wide octave shift.
1 Like
#64

Interested in getting feedback from anyone who uses Ansible midi mode a lot, and in particular anyone who’s used the Teletype MID.SHIFT op to adjust the base note used by the midi pitch calculation. After investigating with @wolfgangschaltung (discussion here) we came to the realization that if you perform custom tuning/calibration on the Ansible side to correct for DAC offsets and tracking, then the 2 octave global pitch shift is not correct and results in midi pitches being out of tune relative to the other modes.

My question I think is: is it necessary for MID.SHIFT to allow you to give a sub-semitone offset, or would it be okay to quantize this value to semitones? This would allow applying the 2 octave shift as an offset into the semitone -> pitch CV lookup table, rather than an adjustment at the DAC level, so it would respect a user-customized tuning table. If this is acceptable, I think the best thing to do for backward-compatibility and avoiding any issues with existing flashed values is to keep the Teletype syntax as-is, but Ansible would quantize these values to the nearest semitone when determining the appropriate midi offset.

#65

I think it would be fine to quantize to semitones.

The feature was added specifically to help people who were finding it difficult to tune their oscillators to as low a pitch as they wanted when the MIDI note range was mapped directly to the unipolar 0-10V output range of the DAC. The default -2V shift seemed about right for the mangrove when testing.

3 Likes
#66

Does/can ansible send a clock to the attached midi device? Midi fighter twister has an interesting sequencer but needs to receive a clock to run.

1 Like
#67

IIRC it does not send MIDI clock out. MIDI clock in will pulse the internal arpeggiator and toggle one of the TR outputs in some modes but that is it I believe.

#68

I finally got a SevillaSoft midi to midi gizmo, and it let me hook up the excellent iOS Fugue Machine to Ansible in the quad midi mode…

Sublime!

1 Like