Deepmark

Audio — Vigil

Overview

Vigil is our zero-bit audio watermarking model. It answers one question: does this audio carry our watermark, yes or no?

Use Vigil when you need provenance, not a payload. Typical use cases:

  1. AI-generation attribution ("was this produced by our TTS?")
  2. "Is this ours?" content verification
  3. Any workflow where a robust yes/no decision is enough

Why Vigil is different:

  1. Extremely robust. Because there's no payload to recover, Vigil can tolerate attacks that defeat most multibit schemes — including over-the-air recapture in non-lab environments.
  2. Tiny and fast. The detector is a small model designed for low-latency inference, cheap to run at scale.

Imperceptibility

The watermark sits below the perceptual threshold. In a blind A/B test, listeners cannot reliably distinguish the watermarked signal from the original.

Listen for yourself

Select an example to compare the original audio with its Vigil-watermarked version:

Original0:00
Vigil Watermarked0:00

Spectrograms

Side-by-side spectrograms of the same clip. The watermarked plot is visually near-identical to the original, demonstrating how little energy is added.

Vigil spectrogram comparison - Example 1
100%

Format & Configuration

PropertySupported
Sample rates16, 22.05, 24, 32, 44.1, 48, 96 kHz
ChannelsMono, stereo
Typical bit depths16-bit PCM, 24-bit PCM, 32-bit float

Robustness

Robustness is Vigil's headline feature. The detector is designed to hold up through real-world transformations that typically break watermarking schemes.

Supported attack classes

Attack classExample transformations
Lossy compressionMP3 (down to 64 kbps), AAC, Opus
ResamplingArbitrary round-trips (e.g. 48 → 16 → 48 kHz)
Speech enhancementDenoisers, RNNoise-style pipelines
WebRTC / call audioFull VoIP stack with codec + jitter buffer
Over-the-air recapturePlayed through a speaker and re-recorded in a non-lab environment

Background music mixing

A music track is mixed into the watermarked signal at a realistic SNR. This is the common "posted over a backing track" scenario.

Watermarked0:00
After attack0:00

Detection Result

Result Watermark detected

Gaussian noise

White noise added at 20 dB SNR — simulates microphone hiss, noisy transmission, or deliberate masking attempts.

Watermarked0:00
After attack0:00

Detection Result

Result Watermark detected

Cuts / splicing

A short segment is removed from the middle of the clip and the two halves are rejoined — simulates edits, ad breaks, or clip re-use.

Watermarked0:00
After attack0:00

Detection Result

Result Watermark detected

Why a Low False-Positive Rate Matters

A detector is only as useful as its negative answer. If Vigil returned TRUE on content it never watermarked, the positive signal would be worthless.

Provenance decisions are asymmetric:

  1. False positive (claiming unrelated audio as yours) is a credibility problem — it can lead to wrongful attribution, mistaken takedown requests, or legal exposure.
  2. False negative (missing one of your own watermarked clips after a harsh attack) is a missed detection — recoverable, and usually still detectable on a different segment.

Vigil is tuned for an extremely low false-positive rate across a wide range of unrelated audio. When Vigil says TRUE, it means the watermark is genuinely present.