Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Record the failed stage
Copy the complete visible error before retrying. In this converter, “FFmpeg could not load” means the engine failed to initialize; a queued file showing “Failed” with a processing message belongs to the per-file conversion stage. A filename extension alone does not identify the cause.
Change one input at a time
Keep the same browser, output format and settings. Try one small local WAV that you already know plays correctly, then the problem file. Do not queue three unrelated files and change output settings between attempts: that hides which variable changed. Keep private source audio local; a reproduction report can describe properties without sharing the recording.
A control matrix to narrow the next action
This is an original diagnostic worksheet, not a report of induced failures. Write the observed message in each cell. A control that succeeds makes a file-specific explanation more plausible, but does not prove which codec or byte sequence caused failure.
If both files fail while loading the engine, inspect the network result for the same-origin engine assets and retry once after the connection is stable. Do not rename a file or change bitrate to repair an engine download. If only the problem file fails during processing, verify its real container, audio track and completeness before trying an external decoder.
Swipe or scroll sideways to read all columns.
| Known-good WAV | Problem file | Next useful check |
|---|---|---|
| Engine load error | Engine load error | Connection / blocked runtime asset |
| Converts | Processing failure | Problem file container and track |
| Processing failure | Processing failure | Output settings and exact error |
| Converts | Converts | Reopen both downloads; preserve evidence |
Keep decoding and encoding hypotheses separate
“Processing failed” is broader than “decoder failed”: reading input, decoding, encoding or writing output can fail in that stage. Preserve the actual error instead of assigning a codec diagnosis from the label. A completed job still needs a downloaded-file check.
When reporting the issue, include browser version, input extension and byte count, output format, settings and whether the control succeeded. This is different from estimating browser memory: the matrix first locates the stage, then directs a narrower investigation.
Common questions
Can an audio file work in the pitch tool but fail here?
Yes. The waveform tool and converter use different decoding paths. Success in one establishes that one path can read the file; it does not guarantee the other engine supports the same container and codec combination.