A Reaper integration reads your client's timestamped comments and waveform peaks straight into your DAW. Versions compare gaplessly. Stems come in clean, masters go out clean.
Four phases. The point is you stop alt-tabbing between your DAW, a browser tab, and a chat thread.
Specifically: a DAW integration that pulls client feedback into Reaper. That direction — cloud comments back into the DAW — is rare in this space.
Pair once via the device-flow approval page in your browser, the Reaper script stays signed in. It pulls each production's comments, waveform peaks and duration of the active version directly into your DAW. A native VST3 plugin is in active development — the script ships today.
On Pro and Studio plans the artist can upload stems directly into the production — drums, vocals, guitars, separated tracks. They land in your dashboard, not your inbox.
Your client A/B-compares v1, v2, v3 in the browser without ever pausing playback. They actually hear the difference between rev 4 and rev 5 — and they tell you which one they prefer.
Anchored to the playhead in MM:SS. Replies nest under the parent. You see the whole thread in the browser; the Reaper plugin sees the same data through the comments API.
Final master, instrumental master, stem-pack — all go into a dedicated deliveries section. Tied to the production, downloadable by the artist whenever they need them.
Pro: 50 GB. Studio: 100 GB. Multi-version FLAC + stem packs add up — but mid-project files aren't archived to cold storage, they stay instantly playable.
When your artist opens the player, every version of a track — v1, v2, v3 — is decoded into memory up front through the browser's Web Audio API. Each version sits on its own gain node, all of them wired to the same output.
Switching to another version is a single call: gain.setValueAtTime(0, ctx.currentTime) on the old version, gain.setValueAtTime(1, ctx.currentTime) on the new one. No HTML5 <audio> swap, no load(), no seek. The playhead position is preserved exactly. There is no audible gap.
Most browser-based players take a different route — one HTML5 audio element per version, which pauses and re-buffers on every switch. The Web Audio approach is what makes the playhead-preserving cross-fade possible.
Audio-collaboration and feedback tools we surveyed. The right-hand column summarises the field — if even one tool we looked at has the feature, we still mark it as "some". Retrieval date: 14 May 2026.
| Feature | CuePort | Other tools |
|---|---|---|
| Timeline-anchored comments | ✓ | ✓ |
| Threaded replies | ✓ | rare |
| Gapless mid-playback version A/B | ✓ | limited |
| Stem upload from artist side | ✓ | rare |
| Reaper integration (sync script) | ✓ | — |
| Deliveries (masters + stems) | ✓ | ✓ |
| Storage on paid plan | 50–100 GB | varies |
| Native German UI | ✓ | — |
Comparison summarises publicly available info from the pricing and help pages of each tool, retrieved 14 May 2026. "Limited" gapless A/B means competitors describe their version-switching as conditional, submenu-based, or do not document the underlying mechanism.
Free for the first project. Pro 6,99 € / month unlocks artist-side stem uploads, unlimited versions, deliveries and 50 GB storage.