<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2716.2200" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=694285212-10062002><FONT face=Arial color=#0000ff size=2>The
latest CVS version of the common lib portability issues have been
resolved. I've submitted the fixes to the folks with cvs access to put
them in the tree. Dunno if they've made it in yet or not, but they will
eventually I'm sure.</FONT></SPAN></DIV>
<DIV><SPAN class=694285212-10062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=694285212-10062002><FONT face=Arial color=#0000ff
size=2>--Ivan</FONT></SPAN></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
owner-ag-tech@mcs.anl.gov [mailto:owner-ag-tech@mcs.anl.gov] <B>On Behalf Of
</B>Robert Olson<BR><B>Sent:</B> Monday, June 10, 2002 7:49 AM<BR><B>To:</B>
s.booth@epcc.ed.ac.uk; White, Derek [NCSUS Non J&J]<BR><B>Cc:</B> Nolan,
Kevin [NCSUS]; ag-tech@accessgrid.org<BR><B>Subject:</B> RE: [AG-TECH] Audio
losses synch (more technical questions)<BR><BR></FONT></DIV><FONT size=3>We
typically don't run with lipsynch activated between rat & vic (reasons
include the necessity to play with .mbus files to get the synchronization to
work properly between audio and display machines, the fact that vic's synch
support is indeed out of synch with the support in rat, and that when on a
good-quality network, the casual synchronization resulting from best-effort
transmission results in "good-enough" lipsynch).<BR><BR>All that being said,
if you get this working that'd be great, and we should look at integrating the
fixes.<BR><BR><BR>
<BLOCKQUOTE class=cite cite="" type="cite">At the moment this would not be
enough to fix a standard AG node, if audio<BR>and video sources are from
different machines the cnames will not match<BR>anyway as these are derived
from the IP address.</FONT></BLOCKQUOTE><BR>We've had some other discussion
lately about changing the AG stuff to define CNAMEs on a per-node rather than
per-host basis.<BR><BR>
<BLOCKQUOTE class=cite cite="" type="cite"><FONT size=3>I managed to compile
up the AG vic code linked against the most up to date <BR>UCL common
library. (There is some new crypto code that has been<BR>seperatly added to
both development trees but if you delete the files<BR>from vic the program
still links ok)</FONT></BLOCKQUOTE><BR>An aside on why this is there - vic
doesn't use the libcommon mechanisms for RTP transport (it has its own
internal RTP handling code). The crypto code that's in libcommon is there in
support of rat (and other clients of the libcommon RTP library). Vic has
analagous crypto code in a module conforming to the vic crypto
interface.<BR><BR>
<BLOCKQUOTE class=cite cite="" type="cite"><FONT size=3> This might be
enough to fix this<BR>problem. It should be as all the mbus code would be
from the same<BR>revision.</FONT></BLOCKQUOTE><BR>Did you see any weirdness
with vic built with the latest libcommon? if not, we can go ahead and merge
the new libcommon in with vic. <BR><BR>Did you use the CVS version, or the
latest release version (1.2.8). Ivan found some win32 portability problems in
the latest CVS version; not sure of the state of resolution of
those.<BR><BR>--bob<BR></BLOCKQUOTE></BODY></HTML>