Re:Audio Fingerprinting using the AudioContext API
by MauranKilom on Sunday November 03, 2019 @05:17PM
(#21437102)
Example: On Windows, a sin() call usually goes into msvcrt.dll, and can thus return different results on different machines for the same binary. To name one possible reason: Different vectorization (due to different SSE support).
Corollary: Don't link to the CRT sin/cos/etc. if you want your binary to give the same result on different machines.
They are constructing a simple audio synthesis graph and rendering it for a few seconds.
But since all the audio processing happens in the browser, without OS involvement, how can the fingerprints be different between say 64 bit Firefox browsers running on 64 bit Windows?
I can understand differences between different browser binaries, since optimizations can slightly change the output due to floating point order of operation, but can a particular browser binary generate different fingerprints?