- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper explores how to keep context unchanged in speech repair. The authors propose several manually designed rules to generate candidates, along with a "no repair" candidate. These candidates are then selected using a WER-based validation method. The authors also analyze whether the repair alters the context outside the damaged span. Experiments are primarily conducted on the LibriSpeech dataset. Results show that direct editing (dots.tts.edit) achieves better recovery results, i.e., a higher pass rate and lower WER, but the method based on geometric constraint rules achieves complete context alignment and, in most cases, preserves exact context. The authors also analyze the biases between different ASR evaluation models.
Critical strengths
The authors described their experimental setup in detail and provided an anonymous code repository, which may be helpful to the domain.
Critical weaknesses
- This article appears to merely describe how to keep context unchanged in speech repair task using manually defined rules, which is simply an engineering improvement rather than a scientific innovation. The method's effectiveness is quite limited and is compared to only one baseline (dots.tts.edit), so it is difficult to position this paper within related work.
- The presentation of the paper is poor and difficult to understand. Adding more pictures and specific examples to illustrate the method (such as the nine proposals in candidate generation) may be helpful for readers to understand this paper.
Questions for authors
Can geometry-based policy be combined with existing models like dots.tts.edit to improve context invariance without compromising recovery performance? It would be good if the geometry rules could be plug-and-play across all speech repair models to achieve context-invariant speech repair.
3 comments
Thank you for the response. However, the authors have only clarified the current scope and limitations of the work, without providing new experimental results or supporting evidence. Since my concerns remain unaddressed, I will maintain my score.
Thank you for identifying the missing empirical evidence. We added a paired analysis of the archived dots.tts.edit outputs against no-repair. This is a new analysis of existing outputs, not a new generation run. It covers 2,346 corrupted cases from 782 source utterances (three corruption conditions per source). We average conditions within source and use 10,000 source-utterance cluster-bootstrap resamples (seed 20260919) for 95% intervals.
Under Faster-Whisper large-v3-turbo, the editor-minus-no-repair absolute difference in exact-transcript pass rate is +37.85% (95% CI [+35.34%, +40.41%]); the absolute WER difference is -13.41% ([-14.30%, -12.50%]). Under Wav2Vec2 CTC, the corresponding differences are +38.49% ([+35.98%, +40.92%]) and -17.39% ([-18.25%, -16.54%]). The archived outputs therefore show higher automatic transcript recovery than leaving the corrupted input unchanged under both frozen evaluators. These results do not establish naturalness, speaker match, or performance beyond this controlled set.
The fixed-map context comparison has a different limit: only 5 of 2,346 editor outputs align to the original time map; none of those five preserves exact context, and the other 2,341 are unassessable by this measure. The local controller aligns all 2,346 cases and preserves exact context in 1,236, but it uses nine proposals plus no-repair and known synthetic spans, while the editor returns one output. This is not a compute-matched comparison and does not establish that geometry can be applied plug-and-play to the editor. The revised paper reports the paired recovery analysis and clarifies these comparison limits in the Abstract, Results, Discussion, Limitations, and Conclusion.
The study evaluates a bounded post-generation decision rule over a fixed proposal family. VITS and SpeechT5 supply patches. The nine local proposals include the ASR word-time interval, duration-scaled target-difference intervals, two deletion-gap placements, and four deletion-boundary shifts. Each candidate is spliced without cross-fading; the controller retains no-repair when no proposal passes its rule (pp. 3, 5–6). These are controlled rules for stated spans, not an online natural-fault localizer.
The paper includes no-repair, several local selector policies, and one direct editor comparator. It does not compare a broad set of editing systems with shared input and proposal budgets. The experiments support a narrow assessment of automatic transcript recovery and fixed-map context under controlled LibriSpeech corruptions; they do not establish general repair quality.
The paper describes proposal families but reports no audio examples or case-level assets. The direct comparison does not apply geometry filtering to dots.tts.edit: that editor receives a word-difference instruction and returns one output, while the controller uses nine VITS proposals plus no-repair and known synthetic spans. The results do not establish plug-in compatibility or preserved recovery after integration (pp. 6–8).
Applying geometry to dots.tts.edit outputs would require mapping its output timing to the original corruption span and evaluating content and preservation under matched conditions. The current submission reports no such result.