Skip to content

REAPER guide

The source builds a native REAPER plugin and contains a macOS development deployment script. No public package, supported REAPER version, checksum, signing status, or clean-install guide is published.

Use this mode when songs are separate .rpp projects in a backing-tracks folder. Prest represents each project as a song and can request the host to open the appropriate project.

Use this mode when the show lives in one .rpp project. Prest represents marker-delimited sections as songs using an internal section reference.

The exact public marker naming and lyric/chord source conventions still require a clean representative-project walkthrough before publication. Do not invent marker syntax from internal parsers.

  1. Start REAPER with the verified Prest plugin installed.
  2. Open the prepared project or project source.
  3. Wait for Prest to report its local server address in REAPER.
  4. Open that address in a browser on the same private network.
  5. Confirm the runtime-connected state.

Use Editor to create the performance order. In Performance, select the setlist and song, then verify play, pause, stop, previous, next, and position tracking during rehearsal.

  • Plugin missing: verify the package path and supported architecture from the release guide.
  • No address: inspect the REAPER console output and plugin load result.
  • Wrong songs: verify whether the source should be a project folder or one marker-based project.
  • Transport mismatch: stop the show workflow and reproduce with a safe test project before collecting diagnostics.

Next: Connection troubleshooting.