Kairatune 1.2 known issues

Official support for: futucraft.com


Here is a list of all reported and confirmed bugs found in Kairatune. If you've found a problem that's not on the list, please start a new topic and describe the problem.

Unconfirmed issues Fixed in 1.3.0
  • Some of the factory presets have been corrupted
Fixed in 1.2.9
  • Some parameters cannot be automated in VST3 version
Fixed in 1.2.5
  • The VST version does not work in OS X Yosemite. The AU version still works.
  • AudioComponent version mismatch fails Audio Unit validation on OS X.
Fixed in 1.2.4
  • The BEND parameter's display fails to display some values. The GLIDE and the Pitch ENV parameters' display is lacking resolution to show changes with small parameter values.
  • Kairatune's parameter updates have problems on OhmStudio
  • Ableton Live assigns some or all parameters immediately after setting the "Configure" state on, thus preventing the user from choosing the editable parameters. This behavior may not appear on every system or it may appear only occasionally.
Fixed in 1.2.3
  • Ableton Live 9 freezes on Windows after playing a few notes on Kairatune with the computer keyboard. Playing with MIDI controller works ok. This bug is present on 32-bit and 64-bit Windows but doesn't affect Macs.
  • Ableton Live 9 can't assign any parameter to the XY-control. This bug is present on all VST versions but doesn't affect the AU version.
  • Kairatune does not show up in 64-bit Ableton Live 9 on Windows.
Fixed in 1.2.2
  • Ableton Live 9 multiplies keystrokes entered in the preset detail editor on Windows. This bug doesn't affect Macs.
  • Kairatune AU component contains inconsistent version information causing Logic to validate the component on every launch.
Fixed in 1.2.1
  • The Set as default option can not be reset once set.
Not bugs
  • Keystrokes are blocked preventing text editing on dialogs on Sonar on Windows. The option Give all keystrokes to plug-in must be enabled in Sonar.

Return to “Futucraft”