• 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
Float64 to unsigned bug shows in mSampleTime
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Float64 to unsigned bug shows in mSampleTime


  • Subject: Float64 to unsigned bug shows in mSampleTime
  • From: email@hidden
  • Date: Fri, 23 Aug 2002 05:24:27 -0500 (CDT)

I recently purchased a new dual 867 PowerMac and installed the new
developer's tools on it. I tried running my project and everything worked
fine except that at some point the mSampleTime field didn't look proper.
I store the the first mSampleTime as the basis for when I receive
subsequent sample times and the difference would occasionally show up to
be 1 sample less than expected - usually within the first ten callbacks.
It seems that the code

curSampleTime = (unsigned)(inOutputtime->mSampleTime-initialSampleTime);

can cast erroneously under Jaguar. I think it is erroneous for three
reasons:
First, it worked fine previously. Second, when I printf() the value
(inOutputtime->mSampleTime-initialSampleTime) as a long float, it shows
the value to be correct but the cast unsigned value can still be 1 less
than it should. Third, if I change the aforementioned code to

curSampleTime = (unsigned)(float)(inOutputtime->mSampleTime-initialSampleTime);

it always casts correctly. Therefore it seems that Float64 to float
works and float to unsigned works but Float64 to unsigned can fail. As
this is such a limited case and creating sample code would require a
large amount of time, I haven't submitted a bug report. I thought it might
be a good idea to post this here in case anyone else hit the same problem
or if someone else has isolated the problem better than I have. The
problem occurred when recording either with the built-in audio controller
or with a Tascam 224. After I found the work around casting I stopped
investigating (for now) so the depth of my knowledge about the problem is
limited to pretty much what I've already written.

-Ben

p.s. When can we start discussing API changes in the most recent
developer's tools? I haven't heard that it's public yet.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Float64 to unsigned bug shows in mSampleTime
      • From: Jeff Moore <email@hidden>
References: 
 >Re: inOutputTime accuracy? (From: Jeff Moore <email@hidden>)

  • Prev by Date: Re: iMic Pops and Clicks
  • Next by Date: Re: iMic Pops and Clicks
  • Previous by thread: Re: inOutputTime accuracy?
  • Next by thread: Re: Float64 to unsigned bug shows in mSampleTime
  • Index(es):
    • Date
    • Thread