Reference

No. The AIAPS watermark is embedded in psychoacoustically masked regions of the audio signal. It is designed to remain inaudible to listeners while remaining detectable by compliant verification tools. The audible quality of a protected recording is identical to the original.

No. The AIAPS plugin operates locally within your DAW. All analysis and watermark embedding is performed on-device. The only data transmitted externally is the fingerprint and metadata required for registry registration.

Yes. The audio fingerprint is designed to support identification despite common format or processing changes including lossy compression, normalization, minor equalization, and format conversion.

The NO_AI_TRAINING policy code designates that the recording is prohibited for unauthorized AI training, dataset ingestion, voice cloning, style modeling, or synthetic generation without permission from the rights holder. This is the default and currently only policy code defined in AIAPS v1.0.

Traditional watermark systems embed a generic marker into audio. AIAPS watermarks are song-specific — each watermark payload encodes the protocol version, policy code, AIAPS record identifier, registration time representation, and an integrity check field. The watermark is embedded into psychoacoustically suitable regions of the audio signal.

AIAPS v1.0 applies to finished music recordings and exported stereo masters. The plugin supports WAV, FLAC, and AIFF input formats. Verification also supports MP3 and AAC. Additional format support may be added in future versions.

An AIAPS ID is a human-readable identifier assigned by the registry in the format AIAPS-YYYY-NNNNNN, where YYYY is the registration year and NNNNNN is a zero-padded sequence number. The registry is responsible for issuing valid identifiers and ensuring uniqueness.

A tool may claim AIAPS v1.0 compatibility only if it generates an AIAPS-compliant fingerprint, embeds an AIAPS-compliant watermark, registers the protected recording in an AIAPS-compatible registry, supports AIAPS verification workflow, and preserves required protocol fields and policy information. A tool that only writes metadata notices, only fingerprints audio, or only registers files without watermarking is not fully AIAPS-compliant.

The AIAPS plugin is the official implementation of the standard and is currently in development. Join the waiting list on the AIAPS website to be notified when it becomes available.