Ok thanks, that makes sense. If it's reset to zero at any point than it must refer to the first sample. But I'm still confused about the relationship of .mHostTime. It seems to be set to a future time that corresponds to the NEXT callback time, this is particularly confusing when trying to put a timestamp to a sample on an input callback (remoteIO mic input). You would think that .mHostTime would be tied to .mSampleTime and that that time would be in the past for input samples.
On Wed, Oct 22, 2014 at 12:45 PM, Paul Davis <[email protected]> wrote: > > > On Wed, Oct 22, 2014 at 3:44 PM, Paul Davis <[email protected]> > wrote: > >> as a host author (and thus responsible for the value of mSampleTime), i >> can tell you that it corresponds to the *transport* position of the first >> sample to be processed as part of the render callback. >> > > this line was not supposed to be present in my previous message. ignore > it, please :) > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
