Fix Audio

When to use repair

The repair workflow is most useful when the analysis already tells you that the file is not ready to publish and you want a faster path than opening a desktop editor immediately.

What happens when repair starts

• The fix job uses the same storage-backed source as the analysis workflow.
• A repaired file is generated and stored as its own artifact.
• The plugin can reanalyze the repaired file directly.
• The UI then shows the latest valid result based on that repaired file.

What repair does not do automatically

AudioLinter does not silently replace the original audio attached to the post. The repaired file remains a separate output, so editors can review it and make an explicit publishing decision.

Download and retention

Repaired files are meant to stay available for a limited time, and the plugin should communicate that clearly. The repair artifact is useful for review, download and possible reuse, but it is not an indefinite archive by default.

When manual editing may still be better

If a team wants detailed editorial control, or if the repaired file is close but not exactly what they want, it can still make sense to fix the issue manually in Audacity or another editor and then analyze the result again.