Re: [mediacapture-transform] Document timestamp (non)synchrnoization behaviors (#35)

I agree with https://bugs.chromium.org/p/chromium/issues/detail?id=1180325#c3, and generally this is what Gecko does. We have the "functional component" discussed in the last paragraph, that allows reclocking audio streams by carefully measuring clock drifts and resampling smoothly so that audio can be piped from a clock domain to another clock domain, with minimal latency. The latency depends on the resampler filter size and the respective render quantum size of the two sides, generally in the order of a few dozen milliseconds for high quality resampling and an output latency of 20-40ms. 

-- 
GitHub Notification of comment by padenot
Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/35#issuecomment-839742246 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 May 2021 12:45:54 UTC