My public REAPER tools, published as a ReaPack repository — install once, and REAPER keeps them up to date.
In REAPER: Extensions → ReaPack → Import a repository, paste this URL, then synchronize:
https://github.com/solyarisoftware/reaper/raw/master/index.xml
Manual install, if you prefer: copy the .jsfx and its .jsfx-inc companions into the same
folder inside your REAPER resource directory (Effects/<category>/ on Windows).
| Package | ReaPack category | What it does |
|---|---|---|
| CCScope | ccscope |
Oscilloscope for MIDI CC: scrolling graph and fader bars, per channel, with performance metrics |
| PolyTrills | polytrills |
Turns held notes into trills — one note passes through, four give two parallel trills — with a rate in notes per second and a gesture calibrated on measured performances |
Each package keeps its documentation next to its sources — README, changelog, screenshots:
ccscope/— README · changelogpolytrills/— README · changelog · gesture corpus
Issues and discussions are the roadmap for each package; no separate roadmap file is kept.
This is a ReaPack repository, so the folder tree is the package taxonomy: ccscope/ is
installed as Effects/ccscope/<file> and appears under the ccscope category in ReaPack, and a
file placed in MIDI/foo/ would land in Effects/MIDI/foo/ under the MIDI/foo category. One
folder level per category level — not a copy of REAPER's resource tree. The index.xml at the
root is generated from the files' metadata headers by
reapack-index running in GitHub Actions — do not
edit it by hand.
Each package lives in its own folder, with everything it needs: the sources, the includes it imports (which resolve relative to it), and its own documentation.
- Bug: open an issue with reproduction steps and expected versus actual behaviour.
- Idea or workflow need: start a discussion in Ideas.
- Defined feature or change request: open an enhancement issue with completion criteria.
Start titles with the tool name, such as CCScope - …. Open topics are not promises of
implementation or delivery dates. Testing, documentation and code contributions are welcome.
Full guidelines: CONTRIBUTING.md.
The scale collections are separate projects, each with its own documentation:
IF YOU LIKE THE PROJECT, PLEASE ⭐️STAR THIS REPOSITORY TO SHOW YOUR SUPPORT!
A star costs nothing, and it is the only signal GitHub shows to whoever is looking for a tool like this one: the count is what makes a repository look alive.
If you want to go further, there is a donate button in the Sponsor menu of this repository:
Donations are entirely voluntary and help cover investigation, development, testing and documentation. You do not need to donate to report a bug, propose an improvement or join a discussion. A donation does not guarantee implementation, priority, a delivery date or support. It is not a purchase: nothing is unlocked and nothing changes in the license. The minimum is 5 EUR, for a practical reason — below that the PayPal fee takes most of it. The same button funds the other open-source work of mine (dxconvey, the scale collections), so one pointer covers all of it.
MIT — Copyright (c) 2025-2026 Giorgio Robino.