Does an audio watermark survive MP3 320 kbps?
MP3 320 kbps passed on the same local fixture matrix for all three bands. A higher bitrate reduces codec damage, but it does not make recovery universal; source material, encoder settings and later processing still matter.
How Aureal handles it
At 320 kbps the codec has more bits to preserve the signal, but the watermark still competes with the source. A quiet or narrow-band master may behave differently from the fixture. Test the actual encoder and the platform's transcode; a high bitrate upstream does not guarantee what a streaming service does downstream.
Common failure mode
“320 kbps is transparent, so there is no need to test the watermark.”
Why it fails: Higher bitrate reduces codec damage but does not make the result universal. The encoder, source material and any later processing still affect recovery.
Verified example
Run the same test at the bitrate you distribute:
ffmpeg -i master.wav -codec:a libmp3lame -b:a 320k test.mp3
node aureal-watermark.cjs detect test.mp3 --id 883921
Do not infer 320 kbps survival from a 128 kbps result, or the reverse.Example only. Validate against your own audio, codec and processing chain.
Scope and limits
- Fixture result: 20 s, 44.1 kHz, strength 0.5, named encoders.
- Higher bitrate reduces codec damage but is not a guarantee.
- Test the actual delivery chain and record the result.
Frequently asked questions
Is 320 kbps safer than 128 kbps?
It reduces codec damage in the fixture matrix, but it is not a guarantee. Test the actual encoder and the rest of the delivery chain.
Do I need to test if I only use 320?
Yes. Source material, encoder settings and later processing can still affect recovery.
Related topics
Test the actual delivery chain. A fixture result is a starting point, not a guarantee for your material.
Open the Studio →