Re: Audio Component Count "Badness"
Re: Audio Component Count "Badness"
- Subject: Re: Audio Component Count "Badness"
- From: Anders Norlander <email@hidden>
- Date: Tue, 2 Nov 2010 17:07:52 +0100
I think that i386 is the safe way to go. Even Logic has several features that don't work in 64-bit mode.
You can still build a universal binary, but set it to start in 32-bit mode by default.
That way people can run the 64-bit version if they want to.
I think it's the LSArchitecturePriority key in Info.plist
Looking at AU Lab I see that it is set to open in 32-bit mode, but I might have changed that myself...
-Anders
On 2010-11-02, at 16:52 , Andrew James wrote:
> Good call! I can confirm quite a bit of this with auval itself
>
> Initial-Installers-Mac-Pro:~ ajames$ auval -64 -s aumu 2>&1 | grep aumu
> aumu NBa3 -NI- - Native Instruments: Battery 3
> aumu Nik4 -NI- - Native Instruments: Kontakt 4
> aumu dls appl - Apple: DLSMusicDevice
>
> Initial-Installers-Mac-Pro:~ ajames$ auval -s aumu 2>&1 | grep aumu
> aumu Clm5 -NI- - Native Instruments: Absynth 5
> aumu NBa3 -NI- - Native Instruments: Battery 3
> aumu NiKP -NI- - Native Instruments: Kore Player
> aumu NiMa -NI- - Native Instruments: Massive
> aumu NiR5 -NI- - Native Instruments: Reaktor5
> aumu Nif8 -NI- - Native Instruments: FM8
> aumu Nik4 -NI- - Native Instruments: Kontakt 4
> aumu dls appl - Apple: DLSMusicDevice
>
> Doesn't this mean that a universal binary will not solve the problem since on a 64 bit machine it will always run the x86_64 "sub-binary"? By way of confirmation, I'm on a 64-bit machine and let's run the auvaltool binary that auval wraps
>
> Initial-Installers-Mac-Pro:~ ajames$ file /usr/bin/auvaltool
> /usr/bin/auvaltool: Mach-O universal binary with 2 architectures
> /usr/bin/auvaltool (for architecture x86_64): Mach-O 64-bit executable x86_64
> /usr/bin/auvaltool (for architecture i386): Mach-O executable i386
>
> Initial-Installers-Mac-Pro:~ ajames$ auvaltool -s aumu 2>&1 | grep aumu
> aumu NBa3 -NI- - Native Instruments: Battery 3
> aumu Nik4 -NI- - Native Instruments: Kontakt 4
> aumu dls appl - Apple: DLSMusicDevice
>
> Since I'm writing an AU hosting app, this seems to mean that I must build an i386 binary so that I can get those AU plugins that have not been built for a 64 bit architecture yet?
>
> --aj
>
> From: Anders Norlander <email@hidden>
> To: Andrew James <email@hidden>
> Cc: email@hidden
> Sent: Tue, November 2, 2010 6:32:27 AM
> Subject: Re: Audio Component Count "Badness"
>
> Make sure your executable and components support the same architectures.
> For example, if your executable is x86-64 only, like in a debug build, then the component
> must also support that architecture.
> You can use tools like file or otool to see what architectures a binary supports:
> file /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
>
> Or just build a universal binary and run it too see if the results are different,
> if they are the cause is the above mentioned (don't run it in the debugger).
>
> -Anders
>
> > All,
> >
> > I'm seeing a discrepency between audio component counts when I use auval and my code when using AudioComponentFindNext. I'm hoping someone can enlighten me in regards to some misunderstanding illustrated by my code.
> >
> > Here is the auval output for music devices on my machine. We can see that there are 8 music devices
> < snip tail of thread >
> _______________________________________________
> 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
_______________________________________________
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