It’s doing signal processing using floats, that can lead to differences in the result even if the implemented algorithm is identical. Float addition is not commutative so reordering some calculations, either in different implementations or with different compiler options, can lead to slightly different results. This just detects browser version and maybe OS/Architecture, the same browser binary should still give the same results between different devices with same hardware.

They just generate a sine wave and do some processing on it. The results are very similar but because the processing depends on functions like fast fourier transform, plus the exact algorithm in the browser code, tiny differences emerge.

Please stop wasting everyone's time with your random assumptions as to why this does or doesn't work and just click on the link in the article to the detailed explanation of exactly how this works.

> The technique is called audio fingerprinting, and you can learn how it works in our [previous article].

https://fingerprint.com/blog/audio-fingerprinting/

It's about variations in the implementation of the digital pipeline that are traceable to the output. It has nothing to do with analog processing or interference.