• 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: still no sound output -- bad API update install?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: still no sound output -- bad API update install?


  • Subject: Re: still no sound output -- bad API update install?
  • From: Chris Rogers <email@hidden>
  • Date: Thu, 8 May 2003 23:39:47 -0700

Try putting #if 0 around this code. This solved the problem for me.
The check here
is not necessary, or correct.

#if 0
if (expNumFrames != inNumberFrames)
{
// Here we allow for some slop +/- 2 frames
bool shouldExit = false;
if (inNumberFrames > (expNumFrames + 2))
shouldExit = true;
else if ((expNumFrames - 2) > inNumberFrames)
shouldExit = true;

if (shouldExit) {
printf ("Expected %ld frames, was asked for
%ld\n", expNumFrames, inNumberFrames);
exit(-1);
}
}
#endif


Chris Rogers
Apple Computer


>I'm trying to determine why I don't get any sound output after
>compiling and running the example app, DefaultOutputUnit.
>
>Prior to installing the update to the CoreAudio API, the previous
>version of that app produced a 440 tone. The current version
>does not. Furthermore, if I recompile and run the previous
>version, it STILL produces the tone.
>
>This leads me to wonder if the update installation was completely
>successful. i.e.: the example code has a modification date of
>May 1, 2003. But the AudioToolbox and AudioUnit frameworks
>both have mod dates from December 2002. Am I missing updated
>pieces? I haven't been able to find a manifest on the Apple site,
>so I don't know what the package was intended to contain.
>
>Any suggestions? I'd like to get back to having fun!
>
>The diagnostic output from the May 2003 example app follows.
>
>Thanks in advance!
>Scott
>
>
>
>## Component Manager: attempting to find symbols in a component
>alias of type (regR/carP/x!bt)
>testing at 16 bits, with 2 channels, at 8000.000000Hz.
>generating sin wave at 440.000000 Hz, 0.250000 amplitude
>Rendering source:
>
> SampleRate=8000.000000,BytesPerPacket=2,FramesPerPacket=1,BytesPerFrame=2,BitsPerChannel=16,ChannelsPerFrame=2
>Current Slice: inFrames=96, startingFrameCount=0
>Expected 92 frames, was asked for 96
>
>test has exited with status 255.
>_______________________________________________
>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.
_______________________________________________
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: still no sound output -- bad API update install?
      • From: Scott Frankel <email@hidden>
References: 
 >still no sound output -- bad API update install? (From: Scott Frankel <email@hidden>)

  • Prev by Date: still no sound output -- bad API update install?
  • Next by Date: Re: FireWire CoreAudio Recognition
  • Previous by thread: still no sound output -- bad API update install?
  • Next by thread: Re: still no sound output -- bad API update install?
  • Index(es):
    • Date
    • Thread