Skip to content

MIDI-GPT for REAPER v0.1.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Sep 23:27
· 7 commits to main since this release
v0.1.1
d63f36f

A patch release for v0.1.0. Windows users should update: the Desktop server shortcut in v0.1.0 couldn't start the server.

馃摉 Docs: https://metacreation-lab.github.io/midigpt-REAPER/

Install / update

  • New install: download MIDI-GPT-for-REAPER-v0.1.1.zip below and follow the v0.1.0 install steps.
  • Installed from the v0.1.0 zip: download the v0.1.1 zip, replace your MIDI-GPT folder with it, and run the installer again. Your REAPER projects and settings are kept.
  • Installed with the one-line command (a git clone): run ./update.sh (macOS/Linux) or .\update.ps1 (Windows) in ~/midigpt-REAPER.

Fixes

  • Windows: the server shortcut now starts the server. Start MIDI-GPT Server (and Start Server - Windows.bat) asked for a model named yellow, which doesn't exist, so the server stopped right away. It now loads yellow_medium, like the other launchers.
  • Drum tracks get drum controls whatever their name. Tracks named "Kick", "Snare", "Hi-Hat" and so on now show the drum controls (note density), not only a track named exactly drums. This matches how generation already reads track names.
  • Prism and Expressive only show the controls that apply. They now hide the per-track Core controls that don't apply to a track's role, as Yellow already did.
  • Retry when the server isn't reachable. Instead of "Model: (checking server...)" indefinitely, the dashboard says "Model: server not reachable" and has a Retry button.
  • Ticking an Enable or Limit box takes effect right away. Its slider now starts at a usable value; before, the setting stayed off until you dragged the slider.
  • The installers' final summary now says to use Change... in the dashboard for a remote server, instead of a separate script.

Full changelog: v0.1.0...v0.1.1

Assets 3
Loading