<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mike Taht wrote:
<blockquote
cite="mid158277e20605030941p44745a69jeb04c1bdf7485348@mail.gmail.com"
type="cite"><br>
<br>
<div><span class="gmail_quote">On 5/3/06, <b class="gmail_sendername">Jean-Marc
Valin</b> <<a href="mailto:Jean-Marc.Valin@usherbrooke.ca">Jean-Marc.Valin@usherbrooke.ca</a>>
wrote:</span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>
I must say I really like the generalized jitter buffer though :) It's a<br>
> cleaner and more flexible implementation and can more easily be
adjusted<br>
> to contain additional information with each packet.</blockquote>
<div><br>
This looks interesting to tie into asterisk's jb and plc code as well. <br>
</div>
</div>
</blockquote>
<br>
Yes. Jean-Marc has made the API more similar. <br>
<br>
Jean-Marc: Have you looked at the API we have for the
asterisk/iaxclient jitterbuffer? It's pretty close to what you have
now -- the major difference is that your jb still assumes it can "own"
the data passed in -- it copies it, and it destroys it at will. With
the API I put together, the jitterbuffer only keeps a poiunter to the
data, and considers it opaque -- if it wants to destroy the data, it
needs to return the pointer with a flag, and then the caller is
responsible for whatever cleanup is needed.<br>
<br>
Here's that API:<br>
<a class="moz-txt-link-freetext" href="http://svn.sourceforge.net/viewcvs.cgi/iaxclient/trunk/iaxclient/lib/jitterbuf.h?view=markup&rev=470">http://svn.sourceforge.net/viewcvs.cgi/iaxclient/trunk/iaxclient/lib/jitterbuf.h?view=markup&rev=470</a><br>
<br>
It would be cool if the speex JB could use a compatible API, then
people could always mix/match these things, and see which one works
best for different situations.<br>
<br>
-SteveK<br>
<br>
</body>
</html>