<html>
<body>
<font size=3>Hi Niels,<br><br>
Okay, I'm getting a bit confused here now!<br><br>
Perhaps I should ask a simple question:<br><br>
When I do the callback processing, I need to know the time when the last
packet (which was sent before the callback) was transmitted.<br><br>
For receive DCL programs, this is working as expected.<br><br>
Can you provide a sample procedure, steps, required to do this?<br><br>
Also, I'm a bit afraid of changing the flags for when the update should
be run, not knowing exactly what all happens in the update.<br><br>
Thanks.<br>
Devendra.<br><br>
<br>
At 02:38 AM 10/25/2005, Niels wrote:<br>
<blockquote type=cite class=cite cite="">Hi Devendra...<br><br>
On Oct 21, 2005, at 9:58 PM, BlazeAudio Developer wrote:<br><br>
<blockquote type=cite class=cite cite="">Hi Niels,<br><br>
Can you confirm two things for Send NuDCLs:<br><br>
a. The update step happens before the buffer is transmitted on the
wire.<br><br>
b. If a is true, then, does it imply that the timestamps being copied are
invalid/stale.</blockquote><br>
<blockquote type=cite class=cite cite="">And if a. and b. are true, then
what is the proper way of getting correct timestamps for sent
packets?<br>
</blockquote>The update is triggered by the DCL being "run",
that is, by the packet being transmitted. (We get an interrupt from the
hardware) So the update runs after the DCL is transmitted... but by
default the update runs after your callback executes.. perhaps this is
not what you expected? You can use the NuDCL setFlags() API to set the
"kUpdateBeforeCallback" flag.. This will cause your update to
run before the callback is run.<br><br>
You can also run the update step manually by calling
dcl->update()...<br><br>
.niels<br><br>
<br>
<b>niels gabel</b><br>
</font><font size=3 color="#808080"><br>
firewire cpu software<br>
apple computer, inc.<br><br>
</font><font size=3></font></blockquote></body>
</html>