Re: TimeStamps with ischo. transfers

Subject: Re: TimeStamps with ischo. transfers

Date: Thu, 20 Oct 2005 14:42:18 -0700

Delivered-to: email@hidden

Hi Devendra

When your update runs, the timestamp is copied out of the hardware program into your time stamp buffer.

When you call notify( kFWNuDCLModifyNotification ), the hardware descriptors for the affected DCLs will be rewritten... your timestamps on the recompiled DCL may no longer be valid, so inspect them before calling notify().

Does that help?

.niels

niels gabel

firewire cpu software

apple computer, inc.

On Oct 20, 2005, at 4:40 AM, BlazeAudio Developer wrote:

One more thing:

Will calling a notify with kFWNuDCLModifyNotification(after each callback) have any effect on the time-stamping?

From what I'm seeing, it seems to me that the timeStamp does not really get updated until a very long time.

It's almost like the timeStamp gets updated before transmission on that packet starts, but the time-stamp is from the previous transmission of the packet.

Thanks.
Devendra.

_______________________________________________ Do not post admin requests to the list. They will be ignored. Firewire mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/firewire/email@hidden This email sent to email@hidden

Follow-Ups:

Re: TimeStamps with ischo. transfers
- From: BlazeAudio Developer <email@hidden>

References:

>listen DCL program woes (From: Philip Lukidis <email@hidden>)

>TimeStamps with ischo. transfers (From: BlazeAudio Developer <email@hidden>)

>Re: TimeStamps with ischo. transfers (From: BlazeAudio Developer <email@hidden>)