Every cue reviewed at the exact second it matters
What a cue actually goes through
Spotting notes are the most perishable thing in post. A director watches a scene once, feels something is off two seconds before the cut, and by the time that reaches you it has become a sentence in an email. Pibox keeps the note attached to the moment that produced it.
- 01
Render the variation without leaving the session
The plugin uploads straight from your timeline. No bounce folder, no drag into a browser tab, no renaming a file so the client can tell it apart from yesterday.
- 02
Send one link that opens anywhere
Directors and picture editors rarely have your tools. They click the link on whatever they are holding, hear the cue, and mark the spot — nothing to install, no account to create.
- 03
Get the frame, not the paragraph
A note lands on the timecode it belongs to. “The hit is late” stops being a riddle, because you can click it and land exactly where the director was sitting.
- 04
Know which variation won
Three passes of the same cue stay in one chain with a status on each. When the mix stage asks which one is final, the file answers instead of your memory.
See it on a real cue
A reviewer flagged a section that sits wrong against picture. The revised pass 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 cues, reachable from anywhere the review happens
Sound design reviews rarely happen in a studio. Your project lives in the cloud — the director opens a link in a browser, the picture editor checks it on a phone, and you stay in the DAW. Same files, same comments, same version history.
What stops happening
Hunting for the newest render
Variations stack in one chain instead of scattering across a chat, a drive and someone’s downloads folder.
Decoding vague notes
Every comment carries the timecode that produced it, so a reaction stays a reaction rather than becoming a description.
Re-uploading for each reviewer
One link serves the director, the editor and the mixer — and none of them need your software to use it.
Guessing what got approved
A cue is waiting for review or it is approved. The state lives on the file, so it survives the three weeks until anyone asks.
Questions sound teams 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 comment without installing anything?
Yes. Share a link and it opens in the browser — no account, no plugin, no download. Comments they leave land back in your session.
How do you handle variations of the same cue?
Link them into a numbered version chain. Everyone always opens the current pass, and the earlier takes stay one click away for comparison.
Is the audio quality preserved?
Uploads are lossless — what your collaborator downloads is exactly what you rendered, not a messenger-compressed copy.
How do I know a cue is actually approved?
Every file carries a status — waiting for review or approved. The state lives on the file, so the answer is the same for you and the client.
Cut the round trip on your next cue
Upload one cue, invite one reviewer, and see how much shorter the approval loop gets.