Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Identify the actual delivery
Write the saved filename and revision before describing its sound. Distinguish the unchanged source, edited master and review copy. If you regenerated the file after checking it, repeat the check on the replacement: the earlier observation belongs to the earlier bytes.
Split the note into observations and unknowns
Listen to the downloaded file, not only the preview. Mark the affected interval and describe the audible event. Put devices, listening conditions or measurements you did not examine in a separate untested field. Unknown is a valid result; passing one playback check does not resolve the others.
An original worked limitation note
The following is an authored scenario, not a report of a real delivery or a measured separation. Suppose a singer receives rehearsal-r03.wav made from an authorized source. The sender notices residual backing vocals in one passage. A useful proposed note would identify that passage, the practice purpose and an alternative if the residue prevents rehearsal.
Example note: “rehearsal-r03.wav is a practice accompaniment. In this hypothetical review, backing-vocal residue is marked at 00:32–00:35. Please check that entrance before using it for your rehearsal. Playback on the venue system and broadcast loudness have not been checked. Keep the original recording; request a different source or arrangement if this passage masks the lead.” Replace the hypothetical observations with your own before sending.
Swipe or scroll sideways to read all columns.
| Field | Illustrative entry | Purpose |
|---|---|---|
| Identity | rehearsal-r03.wav | Applies only to this revision |
| Observed issue | 00:32–00:35 backing-vocal residue | Recipient knows where to listen |
| Untested | Venue playback and loudness | No implied certification |
| Next decision | Check entrance before rehearsal | Use an alternative if it masks the lead |
Choose language that matches the evidence
Use “heard on headphones at the marked interval” for a listening observation, and record a measurement only if you actually used a suitable meter with a stated method. “No obvious click in the checked passage” is narrower than “click-free.” A setting such as 48 kHz describes an export parameter; it does not prove clean transients, correct lyrics or restored high-frequency detail.
Lossy source damage can remain after conversion to WAV. Re-encoding may also introduce changes. Keep these separate from the workflow limit: the converter changes supported encoding settings but does not reconstruct missing performance information or certify a loudness/true-peak target. The MDN codec guide explains the technical distinction between lossless and lossy encoding; the observation wording here is an original reporting method.
Close the limitation with a decision
Ask whether the stated limitation is acceptable for the named use, needs a revision or requires another workflow. Do not mark silence as approval. If a recipient finds another defect, add a dated observation tied to the same revision. When a later revision removes the issue, identify the replacement and ask for a new check; do not silently edit the old note into an unconditional success claim.
Common questions
Should I list every theoretical problem?
List relevant observed issues and important untested requirements. A long generic disclaimer hides the specific decision the receiver needs to make.
Does changing MP3 to WAV fix separation artifacts?
No. The output container does not restore audio already lost or remove residual instruments. Check the actual audio and use a suitable alternative when the limitation matters.