jitter buffer size?
earthtoobi:
i used to have one-way audio, jitter buffer underrun issues early on (there are threads already on that).
all of my problems went away with tomato firmware and the patches to Obi.
nowadays, even-though i sometimes see jitter buffer underruns/overruns, the voice quality is not affected.
RonR:
Quote from: earthtoobi on August 22, 2011, 12:42:21 pm
i used to have one-way audio, jitter buffer underrun issues early on (there are threads already on that).
all of my problems went away with tomato firmware and the patches to Obi.
nowadays, even-though i sometimes see jitter buffer underruns/overruns, the voice quality is not affected.
The issue with jitter buffer size isn't one-way audio or buffer underruns, it's latency (delays) encountered with larger buffer sizes. The larger the jitter buffer, the more delay that's introduced. On stable, low jitter networks, decreasing the jitter buffer size can significantly reduce the latency encountered.
earthtoobi:
Quote from: RonR on August 22, 2011, 12:56:57 pm
The issue with jitter buffer size isn't one-way audio or buffer underruns, it's latency (delays) encountered with larger buffer sizes. The larger the jitter buffer, the more delay that's introduced. On stable, low jitter networks, decreasing the jitter buffer size can significantly reduce the latency encountered.
i mentioned the above note to only say how my audio issues were sorted out.
wrt your specific point on latency, that is what the adaptive jitter buffer is supposed to do.how do you specify on a per call basis whether it is a stable or a relatively slow network. the adaptive jitter buffer should in real time adjust size of buffer if it works as intended.
RonR:
Like others have reported, I've had excellent results reducing the jitter buffer size in PAP2's with no adverse affects, resulting in very noticeably less latency than the OBi provides. It would appear the adaptive algorithm in the OBi doesn't work all that well or is too generous with the buffer size for what many of us would prefer.
LeftRight:
Just in my personal opinion,a fully adaptive jitter buffer algorithm would be preferred for majority of Obi users. I don't think that anyone can predict the network condition, thus obtaining a optimal "jitter buffer latency" for all the incoming/outgoing calls is almost impossible.
Fully agree that algorithm optimization may be needed in long term (balancing off latency and packet loss??), but I just don't see a necessity of adding parameters for the manual configuration.
Navigation
[0] Message Index
[#] Next page
[*] Previous page