From b7d44ff1a3888fec970c1f6b38ea5f9956bfb5a9 Mon Sep 17 00:00:00 2001 From: Victor Kuznetsov Date: Sat, 15 Aug 2026 11:08:09 -0700 Subject: [PATCH] Warn users that the invisible video path leaves audio untouched The finding lived only in the research archive, whose own banner says it may describe prototypes that were later removed. It belongs where users read limitations: the path strips every metadata marker while copying the audio bitstream byte for byte, so a clean local report on a clip with generated audio is unproven rather than a guarantee. Co-Authored-By: Claude Opus 5 --- docs/known-limitations.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/known-limitations.md b/docs/known-limitations.md index 8b7a73a..9bbdeba 100644 --- a/docs/known-limitations.md +++ b/docs/known-limitations.md @@ -112,6 +112,21 @@ measured 25.39 dB paired PSNR and a 1.058 motion-compensated temporal-residual ratio. This is one carrier, not a universal guarantee; hashes and exact verdicts are tracked in `data/evaluations/video-synthid-oracle.csv`. +### The invisible video path does not touch the audio track + +`remove_video_invisible` regenerates the video stream and copies the source audio +verbatim: the extracted audio bitstream of input and output has an identical +sha256, measured on two carriers. It also strips every metadata marker, so the +output can report clean from `get_ai_metadata` and `identify_video` while carrying +an untouched generated audio track. Google's verifier scores audio and visual +tracks separately, and a track this path never modifies is a track it cannot have +cleaned. + +Whether a given carrier's audio actually holds a mark the verifier reads has not +been established -- that needs a provider verdict, which has not been obtained. +Treat a clean local report on a clip with generated audio as unproven, not as a +guarantee, and check the audio separately when it matters. + The shipped engine streams sampled frames in bounded batches, computes its fidelity metrics incrementally, and pipes regenerated pixels directly to ffmpeg. Its frame and latent memory is therefore bounded by `--batch-size`