Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Freeze the review reference
Open the downloaded file you actually reviewed and record its complete filename and revision. Specify whether timestamps start at the file beginning or refer to another timeline. Do not send a new cropped copy while keeping timestamps from the old full-length version.
Write one observable request per item
Name the event and range, describe what you hear, then state the desired outcome. If you propose a technical setting, label it as a suggestion unless it is an agreed requirement. “The final word is cut short” is more diagnostic than “make this professional.”
A worked revision request with an acceptance check
The following fictional example is an authored form, not feedback from a real client or a measured recording. Reference: rehearsal-review-r02.wav; timestamps are elapsed seconds from that file start. Observation: the final consonant of the spoken cue at 18.4–19.1 s is missing. Request: extend the ending from the unchanged source so the entire word is audible, then retain the agreed short pause.
Acceptance: “Open r03 and listen from the preceding word through the pause. The cue must remain intelligible and no following private conversation may be included.” If the source itself lacks the consonant, report that limitation instead of promising to recover missing speech.
Swipe or scroll sideways to read all columns.
| Field | Example entry |
|---|---|
| Reference revision | rehearsal-review-r02.wav |
| Location | 18.4–19.1 s from file start; final spoken cue |
| Observation | Last consonant is absent |
| Requested outcome | Complete cue, followed by agreed pause |
| Must remain unchanged | Pitch and timing before the cue |
| Check on new revision | Listen to preceding word, full cue and pause |
Separate preference, defect and proposed method
“Too slow” can mean a preference for a faster practice tempo, a late entrance or a playback problem. State which one you observed. If it is a tempo request, give the intended speed or pulse and whether pitch should stay unchanged. If it is a late entrance, identify the event and desired position instead of asking for a global speed change.
For example: “In review-r02, the first clap is at 4.2 s; the agreed visual cue is at 4.0 s. Please align that entrance and preserve the later reference cue at 20.0 s.” This invented request defines two checks and leaves the editor room to explain whether one edit can satisfy both. It does not assert that this site has a multi-track synchronization tool.
Review the changed revision against the request
Ask for a new revision identifier and a short response for each request: changed, unresolved or clarification needed. Open the new download rather than replaying an earlier browser export. Check the named event and the surrounding context; a local fix can accidentally remove the next word or move a later cue.
If the new version has been trimmed, reordered or slowed, update timestamps before issuing more notes. Retain the original request reference so both people can understand what was heard. A marked-complete status records workflow progress; it does not prove that you listened to the new file.
Choose the tool only after defining the outcome
Use Audio Trimmer for a shorter contiguous excerpt and Audio Cutter for split, delete or reorder operations within one source. Converter changes format rather than rewriting a performance. For a new recording, unavailable source material or multiple independent tracks, explain that a different recording or external editing workflow is required.
This page concerns requests for an audio edit. For a browser feature that fails, use a reproduction report with steps, browser and error evidence instead of treating it as a creative revision.
Common questions
Should I specify the exact processing settings?
Specify required settings when they are part of the delivery agreement. Otherwise lead with the audible outcome and label settings as suggestions. An editor may need a different method to satisfy the same request, or explain why the source cannot support it.
Should I send “approved” after one issue is fixed?
Say which request passed and which issues remain. Checking one cue does not approve format, every edit or the whole recording. Keep acceptance scoped to the revision and checks you actually reviewed.