- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
The paper claims to model the retokenization mismatch inflicting token-level audio watermarks as a channel degradation, instead of trying to boost token match rate.
Critical strengths
The idea of modeling the retokenization as a lossy channel, and attempting to fit with readily available, unwatermarked audio is novel and principled.
Critical weaknesses
The paper is generally opaque, difficult to read, and presents the results questionably without standard literature metrics. The core mechanism is not explained well. Tables 1 and 2 are uninformative and have no basis in the watermarking literature. Tables 3 and 4 attempt to present TPR and FPR but do so in a peculiar way.
Questions for authors
Please include unwatermarked audio as a quality baseline and FPR check.
2 comments
Thanks for the response. I appreciate the effort in disambiguating the paper, and especially the listening study and supplementary materials. Unfortunately I maintain that the presentation is very opaque and low-quality. I will keep my score.
Response to Reviewer LmLu [1/1]
We thank Reviewer LmLu for the assessment that modeling retokenization as a channel and fitting it from unwatermarked audio is novel and principled. We answer the weaknesses in the order of the review, then the question.
W1. Readability and the core mechanism.
A: As our AI Use Statement discloses, we used AI tools to help draft the manuscript and improve the quality of the writing. Every AI-assisted passage then went through a final revision by the authors. We take the readability concern seriously all the same. To make the paper easier to follow, the revision adds algorithm boxes for the sender, the dictionary fitting, and the verifier (Algorithms 1–3, App. F.9), states the endpoints in standard terms (W2 below), and rewrites the Limitations paragraph in plain sentences. The mechanism in one sentence: after any channel, the watermark likelihood ratio equals the conditional expectation of the sender's ratio given the received audio, taken over unwatermarked data, so a receiver can be fit from unwatermarked (generation, received audio) pairs alone.
W2. Standard metrics; Tables 3–4.
A: We did not make the correspondence to standard metrics explicit. The revision does (App. F.9):
Tables 3 and 4 now report rates, and Table 4 is labeled "TPR @ 1% FPR".
W3. Tables 1–2 (joint owner–payload recovery).
A: The task is to identify the generating key among many and to recover its message, which a presence metric cannot measure. Table 11 shows why a joint metric is needed: with identity responses, 299 of 301 failures decode the correct payload under the supplied key, yet the owner is rejected. Detection or bit accuracy alone would hide this. Joint recovery requires both attribution among 105 keys and exact message recovery. The revision explains this and reports Table 1 as rates, next to message accuracy with the supplied key (App. F.9).
Q1. Unwatermarked audio as a quality baseline and an FPR check.
A: Both were in the submission, and we have added stronger versions of each. App. F.9 now lists every table in which unwatermarked audio serves as an FPR check or a quality baseline.
Quality baseline. New: the FAD between marked and unmarked audio matches the FAD between two unmarked sets in every channel. New: in a study with 49 listeners, the watermarked clip was identified 49.7% of the time [46.6, 52.8], and the MOS difference to unmarked audio is +0.013 [−0.083, +0.105] (App. F.8). Already in the submission: Table 17 compares every method with unmarked generations for the same prompts (CLAP; WER/CER for speech).
FPR check. Every cell of Tables 3–4 includes 512 unwatermarked controls. In the new experiments (independent reference keys, nonce search, crop search), no unwatermarked input was accepted. The submission also reports 393,216 owner-absent queries and 4,096 real recordings (Tables 21–22).
On the ethics flag. The research itself, that is, the method, the experiments, and the analysis, was carried out by the authors. Our use of AI tools is disclosed as the ICLR 2027 policy requires, and we take responsibility for all content.