Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Keep four states separate
Identify the source you imported, the controls now visible, the output last prepared and the file already on disk. Changing a browser control cannot rewrite a file you downloaded earlier. A filename ending in “(1)” says that a duplicate name exists; it does not prove that it contains newer settings.
Regenerate after changing the controls
In Pitch Changer, change the intended setting and prepare a new output before downloading again. The current workspace invalidates its prepared result after settings change, so do not treat an old saved file as the current result. Keep the original outside the workspace and give the new copy an explicit settings/version name.
A duration marker for the version timeline
Original calculated example: an eight-second source at Speed 100% lasts about eight seconds; a 75% copy targets 8 / 0.75 = 10.667 seconds; changing the controls back to 100% does not shorten the existing 10.667-second download. Only a new prepared and saved output reflects the changed setting. Encoder padding can cause small duration differences.
Use a large, intentional temporary speed difference to identify a version, then restore the desired settings and regenerate the final copy. A pitch-only change does not provide the same duration marker: use an identifiable note or a separately verified playback comparison instead. These are calculated checkpoints, not claimed measurements of your file.
Swipe or scroll sideways to read all columns.
| State | Current controls | What the saved copy represents |
|---|---|---|
| First export | 75% speed | About 10.667 s from an 8 s source |
| Control changed | 100% speed | Old file is still the 75% copy |
| New output prepared and saved | 100% speed | About 8 s; verify actual file |
Prove which revision was saved
Open the downloaded copy from your file browser, not only the in-page preview. Compare its duration and one audible landmark with the intended settings. Record exact filename, modification time and byte count. A timestamp is evidence about when a file was saved, not proof of which controls produced it.
If the new file still seems stale, repeat with a distinct filename and one setting change. Record the source, browser, expected marker and observed result. If current controls are reflected correctly in the new output, retire the older delivery copy rather than repeatedly reprocessing the source.
Common questions
Can I repair an old download by changing the controls?
No. Browser controls affect work prepared from the loaded source. The copy on disk remains unchanged until you generate and save another output, or deliberately edit that saved file in a new session.