Keep the track moving, not the mailbox
Where the weeks actually go
Ask any producer where a record loses time and nobody says writing or arranging. It goes on the gaps: waiting for a reply, re-sending a bounce because the last one got compressed, discovering that the vocalist has been learning to the wrong version for four days. None of that is creative work, and all of it is avoidable.
- 01
The bounce leaves the session already shared
Render through the plugin and the file is up. Nobody opens a browser, hunts for a folder, or invents a filename that explains which take this is.
- 02
The whole room hears the same thing
Artist, label, co-writer, manager — one link, and it plays for all of them at full quality. What they hear is what left your monitors, not a chat app’s idea of it.
- 03
A note points at a bar
Feedback attaches to the moment that caused it. “Second chorus feels crowded” arrives with the second chorus underneath it, so you are not reverse-engineering an opinion.
- 04
The current version is never in doubt
Takes stack into a chain, and the newest one is the one that opens. The stems stay next to it, so a mixer picking up the track later finds everything in one place.
See it on a real session
An A&R flagged a section that sits muddy. The revised take is already loaded — loop the range and flip between the two versions to hear exactly what changed.
Edit: Creatures Of Sun
This section feels muddy — can we clean up the low mids here?
Hats feel a touch sharp here — worth a listen.
This section feels muddy — can we clean up the low mids here?
Hats feel a touch sharp here — worth a listen.
Your session, reachable from wherever the band is
The people who need to hear a demo are rarely in the room. Your project lives in the cloud — the artist opens a link on a phone, the label listens in a browser, and you never leave the DAW. Same files, same comments, same version history.
What stops happening
Working from a stale bounce
Nobody rehearses to a version you replaced on Tuesday, because the chain always surfaces the current one.
Audio arriving degraded
Uploads keep full quality. The label hears the record, not a re-encode that lost the top end on the way.
Feedback scattered across apps
Voice notes here, a screenshot there, a paragraph in email — all of it collapses into one thread attached to the track.
Mixing internal talk with client talk
Comments can stay private to the production team or go public to everyone, so candid notes never reach the artist by accident.
Questions producers ask
Does it work with my DAW?
Pibox ships as an AAX plugin for Pro Tools and VST3 for Cubase and Nuendo, on macOS and Windows. The desktop app installs both.
Can the artist or label comment without installing anything?
Yes. Share a link and it opens in the browser — no account, no plugin, no download. Whatever they leave lands back in your session.
What happens to the stems?
Upload them alongside the bounce and keep them in the same project. Everything for the track stays together instead of scattered across chats and drives.
Will the audio get compressed?
No. Uploads are lossless — what a collaborator downloads is exactly what you rendered, not a messenger-compressed copy.
Can some notes stay between me and the producer?
Yes — comments can be public to everyone on the project or private, so internal notes and client-facing feedback do not end up in the same thread.
Start with one track
Upload a demo, invite the people who need to hear it, and let the notes come back in context.