Re: AU Lab not seeing my plugin when I start it from the command line
Re: AU Lab not seeing my plugin when I start it from the command line
- Subject: Re: AU Lab not seeing my plugin when I start it from the command line
- From: Michael Hopkins <email@hidden>
- Date: Wed, 20 Feb 2008 14:15:57 -0800
Brian,
As previously mentioned on this list, when you launch AU Lab from the
finder, it runs in 32-bit mode by default (unless you change the
preference in the Get Info window in the Finder). When you launch AU
Lab via command-line, it runs in 64-bit. Thus, your AU will not appear
if it is 32-bit only. If you want a 32-bit only version of AU Lab,
make a copy and then run the lipo command line tool on it to strip the
unwanted architectures. See "man lipo" for instructions on how to do
this.
Hope this helps!
-michael
On Feb 13, 2008, at 6:24 PM, Brian Whitman wrote:
Thanks to Brian for the tip about running AU Lab from the commandline.
I've run into a strangeness. My AU (symlinked to the right place)
passes auval fine and also appears and works correctly when I double
click on AU Lab.app from the Finder (or other AU hosts, I tried a
few.) But when I run AU Lab from the command line (via /Developer/
Applications/Audio/AU Lab.app/Contents/MacOS/AU Lab) it does not
appear -- I only see the default AUs. The same goes for using AU Lab
as a custom executable in XCode for debugging.
Does anyone know what I'm doing wrong here? I'm on 10.5.2
-b
_______________________________________________
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