im9
EN JA

Support

Per-DAW compatibility for each plugin is listed on the plugin's product page under DAW support.

Install

M4L (.amxd) — drag the file into Ableton Live's MIDI Effect rack on a MIDI track. Live treats Max for Live devices as first-class; nothing else to configure.

VST3 / AU / CLAP — native builds currently ship for macOS only (Windows / Linux are not supported yet). Each release bundles two install formats: a .pkg installer and a manual-placement .dmg.

.pkg (recommended) — double-click to launch. The installer places bundles into the standard system folders automatically. Rescan in your DAW after install.

.dmg — for installing to a custom location, or skipping the installer. Open the DMG and copy the bundle into one of the standard folders below (or any path your DAW scans), then rescan:

  • VST3: ~/Library/Audio/Plug-Ins/VST3/
  • AU: ~/Library/Audio/Plug-Ins/Components/
  • CLAP: ~/Library/Audio/Plug-Ins/CLAP/

MIDI effects are slotted differently from audio effects in most DAWs. Notes per DAW:

  • Ableton Live — uses the M4L build. Live doesn't accept third-party VST3 / AU in its MIDI Effect rack.
  • Logic Pro — uses the AU build, slotted as an AU MIDI FX on a software-instrument track.
  • Bitwig Studio — uses VST3 or CLAP in the Note FX slot.
  • Reaper — after install, rescan in Preferences → Plug-ins, then place VST3 or CLAP on a track's FX chain before the instrument.
  • Cubase / Nuendo, FL Studio — currently unsupported. Host design has no third-party VST3 MIDI Effect routing path.
  • Studio One — currently unsupported. Note FX restricts to PreSonus-native MIDI plugins, so third-party VST3 / CLAP MIDI effects have no host-side routing path.

Update

All version updates are free, including for paid plugins.

Free plugins — re-download from the plugin's GitHub Releases page. Each product's Download link on its product page points at the current release.

Paid plugins — the download link in your purchase email always points to the latest binary, so re-downloading from the original email gives you the current version.

Contact

For a bug in a specific plugin, the fastest path is the plugin's GitHub Issues page (linked from each plugin's product page). Public issues are easier for other users to find later.

For anything else — license questions, paid-product issues that need im9 directly, general inquiries — use the contact form.

Contact