Re: Error Instantiating OutputUnit
Re: Error Instantiating OutputUnit
- Subject: Re: Error Instantiating OutputUnit
- From: Joe White <email@hidden>
- Date: Thu, 04 Jul 2013 18:54:30 +0100
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?
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.
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 :/
Again, thanks for your help!
On 4 July 2013 18:24, Kyle Sluder
<email@hidden> wrote:
On Jul 4, 2013, at 10:11 AM, Joe White <
email@hidden> wrote:
> Ahh yeah thanks Kyle, I forgot about that. I was in the process of deleting both versions of Xcode (the app folders from /Applications) and downloaded the latest Xcode 4 from the App store.
>
> Running:
> $ xcode-select --print-path
> /Applications/Xcode.app/Contents/Developer
>
> Seems to be correct, however I still the get the error (-1 in this case, and it affects all the previous CoreAudio projects I've worked on) Do you know any other places to check?
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.
--Kyle Sluder
--
Follow me on Twitter @diplojocus
_______________________________________________
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