• 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: Error Instantiating OutputUnit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error Instantiating OutputUnit


  • Subject: Re: Error Instantiating OutputUnit
  • From: Kyle Sluder <email@hidden>
  • Date: Thu, 04 Jul 2013 11:22:20 -0700

On Jul 4, 2013, at 10:54 AM, Joe White <email@hidden> wrote:

Your sample code doesn't involve anything from the Core Audio SDK, so we can rule that out.

Sorry, I always thought Core Audio was the all encompassing term for the audio frameworks from Apple. The code I linked breaks specifically at 'AudioComponentInstanceNew()', which is declared in the Audio Unit Framework, so you think it must be an issue with my version of that?

Core Audio is an umbrella term. By “Core Audio SDK”, I am referring specifically to the downloadable stuff on developer.apple.com that is used for authoring Audio Units and drivers. AudioUnit.framework is part of the operating system, not part of that downloadable package. Just like how Foundation.framework is part of the OS, but the headers and such are part of the Developer Tools package.


If you're running on 10.9 and linking against the 10.9 SDK, then you might get different behavior than if you had linked against the 10.8 SDK. I would start by cleaning the Build Products directory and triple-checking the SDK being linked against. If that fails, I would take the same executable and run it on 10.8 (making sure it's linked against the 10.8 SDK). If all else fails, I'd check the 10.9 release notes for anything related to Core Audio, and file a Radar if necessary.
In short, this sounds like an OS issue, not a an Xcode issue.

I'm running on 10.8, targeting 10.8 in the build settings and cleaning the products directory many times. 

Well, that rules out that possibility, which is good.


I created a new test user account on my system and surprisingly the project builds and runs! So I think you're right it's not an Xcode issue but maybe an issue with my user account somehow, something that changed after installing the Xcode Developer Preview and it's updated Developer Tools. 

Now I'm just unsure where to check to see what's different :/

There might be some documentation about this either in the Xcode 5 release notes or in the WWDC 2013 videos. I'm not sure if there is or where it could be found.

--Kyle Sluder
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Error Instantiating OutputUnit
      • From: Joe White <email@hidden>
References: 
 >Error Instantiating OutputUnit (From: Joe White <email@hidden>)
 >Re: Error Instantiating OutputUnit (From: Kyle Sluder <email@hidden>)
 >Re: Error Instantiating OutputUnit (From: Joe White <email@hidden>)
 >Re: Error Instantiating OutputUnit (From: Kyle Sluder <email@hidden>)
 >Re: Error Instantiating OutputUnit (From: Joe White <email@hidden>)

  • Prev by Date: Re: Error Instantiating OutputUnit
  • Next by Date: Re: Error Instantiating OutputUnit
  • Previous by thread: Re: Error Instantiating OutputUnit
  • Next by thread: Re: Error Instantiating OutputUnit
  • Index(es):
    • Date
    • Thread