Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Write the chain before exporting
Start with the source revision, then list each tool in the order used. For each operation write the input filename, settings, selected range and output filename. A file downloaded from one tool must be explicitly imported into the next; this site does not run a shared multi-tool batch chain.
Change one ordering choice at a time
To compare two orders, create both branches from the same unchanged source. Keep pitch, channels and final encoding choices fixed where those controls are relevant. Do not feed branch A into branch B and then call them independent alternatives.
A compact operation record
This authored plan uses an imaginary 60-second recording. It is a calculated example, not an observed export. The intended material occupies source seconds 10 through 20. Speed is 50% with Pitch at 0 st. In this example, changing speed stretches duration by a factor of two.
Swipe or scroll sideways to read all columns.
| Stage | Input and operation | Result to document |
|---|---|---|
| 1 | source-r01 → trim source 10–20 s | clip-r01.wav, approximately 10 s |
| 2 | clip-r01.wav → Speed 50%, Pitch 0 st | slow-r01, approximately 20 s |
| 3 | slow-r01 → final delivery conversion if needed | Format and actual output settings; no new edit |
Why reusing the same timestamps changes the task
If you first slow the entire 60-second source to 50%, it becomes approximately 120 seconds. Source second 10 now occurs at output second 20, and source second 20 occurs at output second 40. Selecting 10–20 seconds from the slowed file therefore selects approximately source seconds 5–10. To retain the same original material after the slowdown, select output seconds 20–40 instead.
The difference here is the coordinate mapping, not evidence that one order has better sound. Audio-frame rounding and processing behavior can affect actual results. Open the saved downloads, compare the intended first and last events, and record actual durations before accepting either branch.
Swipe or scroll sideways to read all columns.
| Workflow | Range selected | Original material represented |
|---|---|---|
| Trim 10–20 s, then 50% speed | 10 s source clip → approximately 20 s | Source 10–20 s |
| 50% speed, then trim 10–20 s | 10 s from slowed file | Approximately source 5–10 s |
| 50% speed, then trim 20–40 s | 20 s from slowed file | Approximately source 10–20 s |
Record boundaries when effects add sound
For an effect workflow, include whether you trimmed before the effect or after it and whether the selected end retained the audible decay. Write an actual end boundary rather than only “reverb added.” A later crop can remove part of an effect tail; changing the crop can also change which source material feeds the effect.
For order comparisons involving reverb or reversal, document the exact steps and inspect the sound actually produced. Do not generalize the timing calculation above into a claim that arbitrary effects commute or that every processing order produces identical samples. Use the dedicated rising-texture tutorial for the reverse-reverb procedure.
Keep intermediate files until the chain is accepted
Record final encoding once, after the edits you intend to keep, when that fits the receiving workflow. Repeated lossy conversion cannot restore information already discarded. A WAV intermediate avoids adding another lossy encoding stage, but does not undo losses in an MP3 source.
Save the source, the stage log and the final download together. If a result is wrong, return to the stage that introduced the change instead of repeatedly processing the final file. Audio Trimmer exports WAV; use Audio Converter separately if a different supported delivery format is required.
Common questions
Does a list of settings describe a repeatable chain?
Only if it also specifies the source, operation order, selected ranges and the file passed between stages. Two people can use identical speed and trim values but choose different source material when they apply them in a different order.
Is this a measured sound-quality comparison?
No. The worked example calculates time coordinates for a 50% speed change. Verify the saved file with the actual tool; no listening result or numerical sound-quality improvement is claimed.