• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: DefaultOutputDevice timestamps
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DefaultOutputDevice timestamps


  • Subject: Re: DefaultOutputDevice timestamps
  • From: Doug Wyatt <email@hidden>
  • Date: Mon, 8 Oct 2001 14:42:02 -0700

I suspect that you're on 10.0.x and that the flags in the timestamp structure are indicating that the host time is not valid.

This has been changed for 10.1 - you should see that the valid-hosttime flag is set and you have valid host times.

See <CoreAudio/HostTime.h> for details about the units, and routines to convert to/from nanoseconds.

hth,
Doug


On Sunday, October 7, 2001, at 03:15 , email@hidden wrote:

Hey,

I'm trying to figure out how to write different signals as output in a
good synchronized manner but I've hit a snag. For the AudioTimeStamp
inputTime and outputTime I receive as parameters to the IOProc I give the
default output device, the mHostTime field doesn't seem to really work.
Judging from the NSLogs made while writing to the defaultoutputdevice, the
mHostTime rarely ever changes. I just ran it where the initial input
sample time was 563.000000 and the input sample time where the mHostTime
(for both input and output) changed was 6605737.000000 - that's 2 and 1/2
minutes given 44.1Khz sample rate. The mHostTime went from 1224094414600
to 1228389381896 which begs the question (and I know I should know this) -
what exactly is the unit the mHostTime measured in and what is its
starting reference point (0) based on? In other words, is it based on the
unix clock (1971) or is it prone to rollover, etc.?
What is it that I'm doing wrong to get mHostTime
to not update? I use the values the default output device gives me in the
callback method/IOProc that I give it. Since we're supposed to use the
inputTime and the outputTimes as the clock references for our audio I'd
like to figure out how to get it to update properly (and what units it's
in) as I want to try using it for resynchronizing waveform generators and
wavetable readers.
Thanks,

Ben

p.s. Sorry for any poor form but it's 3am.
_______________________________________________
coreaudio-api mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/coreaudio-api


--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden http://www.sonosphere.com

"He was the sort of person who stood on mountaintops during thunderstorms in
wet copper armour shouting 'All the Gods are bastards.'"
-- Terry Pratchett


  • Follow-Ups:
    • Re: DefaultOutputDevice timestamps
      • From: email@hidden
References: 
 >DefaultOutputDevice timestamps (From: email@hidden)

  • Prev by Date: Re: CoreMIDI (drivers)
  • Next by Date: Re(2): CoreMIDI (drivers)
  • Previous by thread: DefaultOutputDevice timestamps
  • Next by thread: Re: DefaultOutputDevice timestamps
  • Index(es):
    • Date
    • Thread