The last revision, without the guesswork
Why round four exists
Nobody budgets for four rounds. They happen because each one carries a little ambiguity forward: a note nobody could locate, a client comparing today’s pass against something from last month, an approval that lived in a phone call. Tighten those three things and the fourth round usually disappears on its own.
- 01
The pass goes out numbered
Upload from the session and it joins a version chain. There is exactly one current pass, and it is the one that opens — no filename convention required to prove it.
- 02
The client compares like for like
Versions swap inside the same player while the transport keeps its position. They hear the change you made, in the same spot, instead of two downloads and an impression.
- 03
Vague notes get a location
“The vocal could come up” arrives pinned to the bar where they felt it. You stop auditioning the whole track trying to find the sixteen seconds they meant.
- 04
Approval is a state, not a memory
A pass reads waiting for review or approved, and it keeps reading that way. When someone asks in six weeks whether the master was signed off, the file answers.
See it on a real revision
The client asked for the low mids to come down. The new pass is already loaded — loop the range and flip between v1 and v2 to hear the difference the way they will.
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 passes, reachable wherever the client listens
Clients check a mix in a car, on headphones, on a laptop at midnight. Your project lives in the cloud — they open a link on any of them, and their notes come back to you with a timecode attached. You stay in the DAW the whole time.
What stops happening
Filenames doing version control
No more v3_final_FINAL_b. The chain holds the order, and the label on the file is just a label.
Clients judging an old pass
The link always resolves to the current version, so nobody spends a round reacting to something you already fixed.
Approvals living in a phone call
Sign-off is recorded against the file. It is checkable later by anyone, including the client who gave it.
Guessing where a note applies
Comments carry their timecode, so a remark about the second verse opens on the second verse.
Questions engineers 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 clients review without installing anything?
Yes. Share a link and it opens in the browser — no account, no plugin, no download. Their notes land back in your session with the timecode intact.
How do I keep revisions straight?
Link passes into a numbered version chain. The client always opens the current one, earlier passes stay one click away, and nobody has to name a file v3_final_FINAL.
Can they A/B two passes properly?
Yes — versions swap inside the same player while the transport stays in sync, so the comparison is like for like instead of two downloads and a guess.
How do I prove a pass was approved?
Every file carries a status — waiting for review or approved. The state lives on the file, so weeks later the answer is the same for you and the client.
Try it on the next revision
Send one pass through Pibox and see how much shorter the approval loop gets.