Re: Can't Read the Audio Units(AULab 2.0)
Re: Can't Read the Audio Units(AULab 2.0)
- Subject: Re: Can't Read the Audio Units(AULab 2.0)
- From: William Stewart <email@hidden>
- Date: Mon, 12 Nov 2007 11:51:51 -0800
No, this should work.
This would occur because your AU isn't being found. If you do auval,
do you see your AU?
% auval -v au?? ???? ????
where the ?? are the OSType codes for you AU's type, sub type and manu
ID (from your component resource file)
Bill
On Nov 11, 2007, at 10:19 PM, norihisa nagano wrote:
Hi,
AU Lab2.0 can't read the Custom Audio Units (AUPinkNoise etc..)
from the Components path when starting double clicking /Developer/
Applications/Audio/AULab.app/Contents/MacOS/AU\ Lab.
(Components path is /Library/Audio/Plug-Ins/Components/ or ~/Library/
Audio/Plug-Ins/Components/)
so, AU Lab can't use as Active Executables on Xcode3.0.
There is no problem in AULab 1.0.3.
It's a bug?
Thanks
n. nagano
Monalisa-au.org
_______________________________________________
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