Re:Audio Fingerprinting using the AudioContext API
by amluto on Wednesday November 06, 2019 @12:41PM
(#21464886)
Because, if the audio latency significantly exceeds the video latency, then the browser can’t do this without delaying the video.
Re:Audio Fingerprinting using the AudioContext API
by brigandish on Thursday November 07, 2019 @10:55PM
(#21479842)
It's simply moving responsibility from one entity to another, there's no technical reason that the content provide would be better at syncing the two, just as with any other network communication.
The browser is the presentation layer, it needs to know the latency of your headphones (or the system does). Why does the content provider need it? What's wrong with "here is frame A, please play audio A at the same time (while taking into account the latency that only you know about)" as a request?