3 ms·
It was the interaction between the expected amount of required buffering and the thread scheduling behavior that caused the problem. As typically happens when t
by PaulDavisThe1st 6y ago
It was the interaction between the expected amount of required buffering and the thread scheduling behavior that caused the problem. As typically happens when there's a video programmer around, the audio timing is considered less important, and there's a belief that "we can always get the audio we need for the video". Ergo, not much need for buffering. In this case, the odd/incorrect behavior of the thread scheduler exposed the optimistic assumption that you can rely on waking up every 15ms and handling the audio.
- marcan_42 6y agoAnd further, video latency is much less noticeable than audio latency. ~nobody will notice one dropped frame, but ~everyone will notice 16ms of audio missing, because you get a blatant click. Therefore, it is always important to prioritize audio buffering over video buffering.
- gpderetta 6y agooh, yes, I had to use some videoconferencing software recently that appears to drop audio before video. It was basically unusable.