Your artist's feedback.
Right inside your DAW.
CuePort Sync pulls the comments your artist left on the active version's waveform into the open project as real Reaper markers. Hover one and you read the whole note without leaving the DAW.
What it does inside Reaper
The script reads from CuePort and never uploads anything. Your mix stays in your DAW; only the feedback travels.
- Comments as markersOne per comment on the ruler, all in the same colour.
- Tooltip on the markerAuthor, timestamp and the full text.
- Waveform in the windowThe active version, every comment pinned where it was left.
- The DAW's own play cursorClick or drag the strip to move it.
- Comment listA column beside the waveform; switch it on in Settings.
- Loudness of the versionLUFS, true peak and dynamic range.
- Production artworkIn the picker and in the production header.
- A/B against the uploadPast the master to outputs 1/2, under one transport.
- Render startTells the script where the rendered mix begins.
- Pairing with a codeNo password ever goes into the script.
- Per-project bindingEvery .rpp remembers its own production.
- DockableDrag it into any Reaper docker.
- Pill on the transportQuick access. Needs JS_ReaScriptAPI.
- Markers are optionalKeep the ruler to yourself; pins and list still show everything.
One window, not a second program
Artwork, loudness figures, waveform and comment column on one screen — the column is a switch in Settings. Every project remembers its own production inside the .rpp, and the comments come back from the project cache on open, before a single request goes out.
Installed through ReaPack
Reaper's usual package manager. Set it up once and updates arrive with everything else.
Have ReaPack and ReaImGui
ReaPack comes from reapack.com, ReaImGui after that through Extensions → ReaPack → Browse packages.
Add the repository
In Reaper: Extensions → ReaPack → Import repositories… and paste this URL.
https://raw.githubusercontent.com/m3lotunes/reaper-scripts/main/index.xml
Install CuePort Sync
Browse packages → CuePort Sync → Install. Then search the action list for cueport — the action is called Script: cueport_sync.lua.
Connect and pick a production
Press connect, approve the code in the browser, pick the production. It syncs straight away.
What it needs
The script has a page of its own for this, and says so at launch when something required is missing.
| Component | Status | What for |
|---|---|---|
| Reaper 6.68+ | required | The host. The floor comes from ReaImGui — the script itself checks no Reaper version. |
| ReaImGui | required | Draws this window. Nothing you see exists without it. Install it through ReaPack. |
| curl | required | Every call to CuePort goes through it: pairing, productions, comments, audio, artwork. Ships with Windows 10 and later, macOS and Linux. |
| SWS Extension | recommended | Reads the project time under the mouse. Without it the script works that out from the arrange view itself. |
| JS_ReaScriptAPI | recommended | Carries the pill that attaches to the transport, and the window probing behind it. Everything else works without it. |
What it writes into your project
The complete list, the same one on the script's own About page. All of it happens only when you ask for it.
- Comment markerson Sync — the previous set is removed and the current one written. Nothing at all if you switched them off.
- A render start marker and the project time offsetwhen you press Set, and taken away again when you press Clear.
- A hidden A/B track and one audio filewhile the reference is loaded. The file sits next to your .rpp — for a project that has never been saved, in a shared cache instead — and goes once the project has been saved without the track.
- The bound production with its cached comments and waveformin the project's extension data, on binding and on sync. This marks the project modified.
- The edit cursorwhen you click the waveform or a comment.
- Nothing else, and nothing outbound— no part of your project is ever uploaded. What leaves the machine is a device token and a production id.
Syncing markers, setting or clearing the render start and removing the A/B track are named undo steps. Inserting the A/B track is not — use Remove rather than Undo for that one.
The script is free. It needs a CuePort account.
The comments have to come from somewhere: your artists leave them in CuePort, on their own login, pinned to the second on the waveform. The free plan is enough to try the whole loop.